Agilent NetMetrix PC

Agilent NetMetrix Performance Center
Users Guide
Version A.01.03
Microsoft is a U.S. registered trademark of Microsoft Corp. Netscape and Netscape Navigator are U.S. trademarks of Netscape Communications Corporation.
Contents
Chapter 1 Introduction to NetMetrix Performance Center Introduction to NetMetrix Performance Center . . . . . . . . . . . . . . . . . . . . . . 1-2 What are the Views? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Data Sources for the Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 The Hierarchy of Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 The Function of Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Color Coding and Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Capturing Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 NetMetrix Performance Center Architecture . . . . . . . . . . . . . . . . . . . . . . 1-8 Integration with HP OpenView Network Node Manager . . . . . . . . . . . . 1-9 Web Browser Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 NetMetrix Performance Center Interface and Navigation NetMetrix Performance Center Domain Health Summary . . . . . . . . . . . . . 2-2 Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Resizing the Navigation Tree Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 Content Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 Domain Health Summary View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 History At-a-Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 Current Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11 At-a-Glance Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12 Data Source Health View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 Traffic Direction Selection Control . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14 Top Hosts by Data Source View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16 Top Protocol View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18 Errors/Congestion View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20 Detailed Statistics View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22 Utilization by Data Source View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23 Zoom Analysis View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Chapter 2
iii
Top Protocols by Host View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-27 Top Talkers and Listeners View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-29 Most Active Data Source View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-31 What are the measurements shown in this view? . . . . . . . . . . . . . . . .2-31 How can certain metrics be expressed as % of Capacity? . . . . . . . .2-31 Selecting Host Name Display Preferences . . . . . . . . . . . . . . . . . . . . . . . . .2-33 Setting Time Frame and Time Interval for Data Display . . . . . . . . . . . . . .2-35 Selecting a Time Frame for Historical Data . . . . . . . . . . . . . . . . . . . . . .2-35 Selecting a Time Interval for Data Collection . . . . . . . . . . . . . . . . . . . . .2-36 Managing Events in NetMetrix Performance Center . . . . . . . . . . . . . . . . . .2-39 Event Viewer Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-39 Using the Event Viewer Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-40 Categories of Event Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-40 Right Click Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-41 Filtering Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-42 Filtering by Severity and Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-43 Filtering by Time Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-44 Filtering by Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-45 Chapter 3 Interpreting What You See in NetMetrix Performance Center High Utilization on a WAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2 Broadcast Storm on a LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6 High WAN Latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10 High PVC Utilization on a WAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11 High Utilization on a Switch Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-13 High Utilization on a VLAN on Switchlinks . . . . . . . . . . . . . . . . . . . . . . . .3-15 Configuring NetMetrix Performance Center Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1 Configuration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1 Immediate Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2 Periodic Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-4 Navigating the Configuration Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-5 Context Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-5 Apply, Reset, Set to Defaults Buttons . . . . . . . . . . . . . . . . . . . . . . . . . .4-5 Toolbar Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-7 Global Policy Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-8 Setting Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-9 Setting Data Storage Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-11 Setting Global Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-13 MLM and Agent Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-15 Adding Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-17
Chapter 4
iv
Viewing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Agent Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Agent SNMP Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Agent Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Agent Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Interface Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Device Alarm Information . . . . . . . . . . . . . . . . . . . . . . . Adding New Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing/Modifying Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing an Agent Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring PVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a New PVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a New VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring WAN Latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customizing Agent Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administering Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Agent Auto-Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 5
4-19 4-21 4-23 4-24 4-25 4-28 4-30 4-31 4-32 4-32 4-33 4-34 4-36 4-38 4-38 4-43 4-45 4-46
Exporting Data from the NetMetrix Performance Center Database Exporting Data from the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Accessing the NetMetrix Performance Center Database . . . . . . . . . . . . . 5-2 Retrieving Database Data into Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Database Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7 Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7 Domain Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8 Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 Agent Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10 Port Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 Interface Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12 Data Source Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 Statistics Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15 StatMib Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16 Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17 Collection Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17 Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18 Interval Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18 Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18 StatValue Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19 Protocol Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20 Protocol Distribution Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20 Application and MAC Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
v
NlHost Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-21 Application and MAC Conversation . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-21 SDConversations Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-22 Glossary Index
vi
Introduction to NetMetrix Performance Center

Welcome to Agilent NetMetrix Performance Center. You have purchased a powerful integrated network monitoring solution. NetMetrix Performance Center runs on Microsoft Windows NT and analyzes data derived from RMON1 and RMON2 devices in local area networks (LANs) and wide area networks (WANs). NetMetrix Performance Center provides these benefits:
v Ease of installation v Application up and running quickly v Requires minimal configuration v Aggregated data views allow you to quickly assess the health of your netv Zoom navigation (based on time correlation) allows you to navigate to v Alarms that allow you to respond to network traffic problems before end
users experience any disruption of network service NetMetrix Performance Center is designed to save you time when it comes to troubleshooting your network. deeper levels of detail and back up again - saving you time during troubleshooting work
1-1

NetMetrix Performance Center monitors a network domain. A domain contains the network elements managed by NetMetrix Performance Centers Server. The network elements are the LANs, WANs, switches, and switchlinks in your domain. This domain is a subset of all of the network devices in your enterprise. You can install NetMetrix Performance Center at strategic points in your enterprise to help you monitor key areas of your network:
Within the domain, the Server collects local network data from the various devices on your network. These network devices are also known as agents or data sources. The Server is the layer between the NetMetrix Performance Center user interface and these data sources. The Server contains NetMetrix Performance Centers database and performs the computations that result in the graphs that are displayed in NetMetrix Performance Centers various data views.
1-2
NetMetrix Performance Center Users Guide
What are the Views?

The data views display the graphs of network data collected and reported by NetMetrix Performance Center. For example, the first view you encounter in NetMetrix Performance Center is the Domain Health Summary. This view shows you an overall picture of your networks health for both historical (over 24 hours) and current data.
This view and others are discussed in detail in Chapter 2, NetMetrix Performance Center Interface and Navigation.
1-3
Data Sources for the Graphs

The various views can contain these types of graphs:
v Bar graphs (both vertical and horizontal) v Radar graphs v Pie charts v Numerical tables v At-a-glance charts
v Application protocols - Supported application protocols include: HTTP,
These are the supported protocols for NetMetrix Performance Center and help determine the data you see in the graphs: FTP, TELNET, DNS, POP3, SUNRPC, NNTP, NetBIOS, LOTUS-NOTES, X11, BOOTP, TFTP, SNMP, and SNMPTRAP. Configuration of other UDP and TCP protocols is also supported. NET, XNS, ARP, VINES, APPLETALK, and SNA. This table shows the data sources for the monitored network elements which helps build the data displayed in the views:
Network Element Uses RMON1 Stats and History? Uses RMON 1 Alarms and Events? Uses RMON 2 Data Collection? Uses NMX Proprie -tary MIB? Uses generic SNMP MIB, MIB2, etc., for Agent ID? Yes Yes Yes Yes Uses NMX Proprietary Echo MIB for echo test?
v Network protocols - Supported network protocols include: IP, IPX, DEC-
LAN WAN Switch Switchlink
Yes No Yes No
Yes Yes Yes Yes
Yes Yes No Yes
No Yes No Yes
No Yes No No
The data views are arranged in a hierarchy, and as you move from one level of the hierarchy to the next, you drill down into a finer detail of data, or back up to more general data.
1-4
The Hierarchy of Views

Data in NetMetrix Performance Center is arranged in a hierarchy. The data that you see when you navigate to the lower layers is predicated on choices that you made before. The choices can be the type of data (LAN, for example), individual data source (a specific LAN), an activity at a specific time (10:00 AM), a selected host for that LAN, and finally, protocols for that host. As you move through the views, the data that you see goes from general to specific. You can then traverse back up to a general view, depending on what data you need at the moment. For example:
Wider visibility; less detail
Narrower visibility; more detail
This illustration shows (in general) the types of data you encounter for a LAN as you navigate through the hierarchy. A full discussion of navigation through the NetMetrix Performance Center interface appears in Chapter 2, NetMetrix Performance Center Interface and Navigation.
1-5
The Function of Time

Time is important in NetMetrix Performance Center because it is one of the factors that affects the data that you see in the views. There are two types of time intervals:
v Historic data collection (this interval cannot be changed) v Realtime monitoring (this interval can be changed)
The default time interval for realtime monitoring data collection is 30 minutes. You can specify different time intervals for data collection for data source health views. Changing the data collection interval affects the views that you see and allows you to control the time granularity of the display in the graphs. For example, with 5 minute data collection interval in place, a graph could look like this:
Note the time intervals in the bottom axis.
You can also change the date of the data displayed in the data source health views. The default is to show data for the last 24 hours; however, if there is historical data in the database, you can view data for a specific day and time. See Selecting a Time Interval for Data Collection on page 2-36 for information on changing collection intervals and the date in the views.
Color Coding and Aggregation

The data in the views is color coded in red, yellow, and green. The color scheme indicates when violations of configured thresholds have occurred. Yellow indicates a warning, and that the first threshold has been exceeded; red indicates that conditions are critical and that the top threshold has been exceeded. Green tells you that no thresholds have been exceeded and that network operation is in the normal range.
1-6 NetMetrix Performance Center Users Guide
The color coding of the data is derived through aggregation, a technique by which NetMetrix Performance Center derives a summary (higher-level) status for the network conditions from a set of lower-level statuses. This means that when any individual elements status becomes red, the entire status for that network element or data source is indicated as red. For example, in a group of six LANs, if four have green status, one has yellow status, and one has red status, the overall status of the group is graphically represented as red. If, later, that group has three LANs with green status and three with yellow status, the overall group status is represented as yellow. You can reconfigure the default thresholds for your network, if desired. See Setting Global Thresholds on page 4-13 for information on threshold configuration.
Capturing Events
NetMetrix Performance Center provides an event viewer that displays threshold violations, RMON alarms, and other network events. This viewer can stay open on your NetMetrix Performance Center desktop to allow you to get a quick view of network events. See Managing Events in NetMetrix Performance Center on page 2-39 for a detailed description of the event viewer and its functions.
1-7
NetMetrix Performance Center Architecture

NetMetrix Performance Centers architecture has three layers of operation:
v User Interface NetMetrix Performance Center has a Java based user interface, called the Performance Console. This interface can run as an applet through a web browser, in stand-alone mode, or on the same machine as the Server.
1-8
v Server The main components of the Server are: w Service Broker Interacts with the Server Services and Database Server w w w w
to get network data, configuration changes, and network events and sends the data back to the user interface. Server Infrastructure Services (MIS) Contact point for user interface; sets up application sessions. Database Server Handles data movement in and out of the database. Data Collectors Collect RMON1 and RMON2 measurement data from agents using SNMP protocols and stores the data in the database. Web Server Allows download of the application as an applet that runs in a Web browser.
v Agents and Data Sources These are the basic sources of network perfor-
mance data. Examples of agents are embedded RMON sources (in a switch, for example) and RMON probes. All supported agents are SNMP based and can have multiple data sources. For example, a hardware probe can have multiple interfaces as data sources.
Integration with HP OpenView Network Node Manager

NetMetrix Performance Center and Network Node Manager integrate to provide visibility into your network devices and topology. You can launch NetMetrix Performance Center from Network Node Manager either from an application menu or from within the application display. See the Installation Guide for details. This integration allows you to use the two applications together and compare the displays in Network Node Manager with the data you see in the views in NetMetrix Performance Center interface.
Web Browser Support

You can run NetMetrix Performance Center from the application console or from a web browser. Running the application as an applet from a web browser allows you to install the application remotely, in locations where you do not wish to have the Server or Performance Console installed.
1-9
Next Steps
The web browsers supported are Netscape 4.7 with JRE 1.1.5 support, or any later version for Microsoft Windows NT or Microsoft Windows 98, and Microsoft Internet Explorer 4.0 for Microsoft Windows NT or Microsoft Windows 98.
Next Steps
Proceed to the NetMetrix Performance Center Installation Guide, and follow the steps to install the product. Then return to Chapter 2 of this guide, NetMetrix Performance Center Interface and Navigation to get a quick overview of the interface and to get comfortable with the NetMetrix Performance Center navigational tools. This should not take long, and will help you get to know NetMetrix Performance Center and start to use it effectively.
1-10
NetMetrix Performance Center Interface and Navigation

This chapter describes the various aspects of the Agilent NetMetrix Performance Center interface and navigation paths, including:
v Understanding the NetMetrix Performance Center interface v Using the data views shown in NetMetrix Performance Center, including v Selecting host name display preferences v Using tools for controlling the time frame and interval of data display v Managing events
navigation to and from each view
2-1
NetMetrix Performance Center Domain Health Summary

When you launch NetMetrix Performance Center the Domain Health Summary displays:
This view is divided into two panes. The left pane contains the navigation tree, which shows a hierarchical view of your network domain. The navigation tree allows you to access the various levels of data views available in NetMetrix Performance Center.
2-2
The right pane is divided into three areas: Center
v Toolbar shortcut buttons for common actions in NetMetrix Performance v Content area the main data display area v Status Bar a brief description of the current view
The following sections describe each of these areas in detail.
Navigation Tree
The navigation tree appears in the left pane of the NetMetrix Performance Center interface:
2-3
The navigation tree is a hierarchical view of the NetMetrix Performance Center-managed domain on your network, displaying icons representing the various elements. You can open the folder icons to display more detailed views to which you can then navigate. Click to expand a folder and show its contents. Click to collapse a folder and hide its contents. Click any network element shown on the navigation tree to display its associated data view. The navigation tree also offers easy access to the:
v Configuration views v Event Viewer v Online help system
Resizing the Navigation Tree Pane You can make the navigation tree pane wider to see more text or narrower to move it out of the way when you are not using it. To resize the navigation tree pane, position the cursor over the right edge of the navigation tree pane until the pointer changes to . Click and drag right or left to resize the pane.
2-4
Toolbar
The toolbar provides quick access to common actions you might take in NetMetrix Performance Center. The buttons that appear on the toolbar vary depending on the current view displayed in the content area. The following is a list of the toolbar buttons available in NetMetrix Performance Center and a description of each:
Returns you to the Domain Health Summary (the top level of the data views). Goes back to the previous view or to the Domain Health Summary if you have not navigated to the detailed views. Goes to the next view. This arrow is active only if you have previously navigated to more detailed views. Refreshes the data on the current view.
Freezes the data in the current view. Use this icon if you would like to keep the data from updating. This is useful if you want to look at a certain data condition, or to print. Displays the Event Viewer dialog. See Using the Event Viewer Dialog on page 2-40 for details. The event viewer lists network events. Prints the current screen. Before printing, it is good practice to click to freeze the data view that you want to print. These settings on your system will allow optimum printing: Video memory: 4MB Desktop area: 1024 x 768 pixels Color palette: 16777216 colors Refresh frequency: 75 Hertz Font size: Small Displays the Global Configuration panel. See Global Policy Configuration on page 4-8. This icon allows you to access the various configuration screens. Displays the context sensitive help cursor. Then click the area of the screen about which you want to display context sensitive help. Pressing F1 also allows you to access context sensitive help. Displays the online help window, which allows you to access the help system.
2-5
Displays the Interval Selection dialog, which allows you to change the default time interval for data display. See Selecting a Time Interval for Data Collection on page 2-36 for details. Displays the Select Date/Time dialog, which allows you to choose historic data to display. See Selecting a Time Frame for Historical Data on page 2-35 for details. Allows you to add an agent, PVC alarm, etc., in configuration views. This icon is context-sensitive and what you add depends on the screen you are displaying. Allows you to navigate to the Agent Interface Threshold configuration panel.
Allows you to navigate to the Device Alarm Information panel.
Displays the Display Preferences dialog, which allows you to show either friendly host names or network addresses to identify hosts. This choice applies on the Top Talkers, Top Listeners, Top Conversations, Top Protocols by Host, or Top Talkers and Listeners views.
Content Area
The content area of the interface is where the graphs containing network data are displayed. It shows the data views that help you to observe, analyze, and manage your network. The data that is displayed in these views is collected in the background at 30 minute intervals. The data views and tools available in the content area of the interface are described in Data Views on page 2-7.
Status Bar
The status bar at the bottom of the NetMetrix Performance Center interface displays a brief description of the current view, or notification of an action in progress:
2-6
Data Views
NetMetrix Performance Center offers a number of ways to look at network data. The views display the data measured by NetMetrix Performance Center as bar graphs (both vertical and horizontal), radar graphs, pie charts, tables, and at-a-glance charts. The views are:
v Domain Health Summary View v At-a-Glance Chart v Data Source Health View v Top Hosts by Data Source View v Top Protocol View v Errors/Congestion View v Detailed Statistics View v Utilization by Data Source View v Zoom Analysis View v Top Protocols by Host View v Top Talkers and Listeners View v Most Active Data Source
Navigation through NetMetrix Performance Center is based on context. That is, what you select in terms of network data sources, key metrics, and time intervals determine the view that results.
v An introduction to each view v Instructions on how to get to that view v Information about where you can go from that view
Each of the following sections provides:
Domain Health Summary View

When you launch NetMetrix Performance Center, it displays the Domain Health Summary for the current domain. This is the primary data view in NetMetrix Performance Center from which you can access all other views.
2-7
Data Views
This view allows you to quickly identify potential problems on your network, and provides information for you to start to find the source of problems. It is designed to immediately give you the maximum amount of information without you having to drill down to other views.
Network Elements Date and Time of Data Measurement
Time Slots
Key Metrics
Hot Spots
2-8
Note: The first time you start up NetMetrix Performance Center, this view contains little or no data. This view will display the data as it collects it; however, it takes 24 hours for this view to be fully populated with network data like the graphic shown above. The Domain Health Summary view is divided into two panes offering two types of summary data for the current domain:
v History At-a-Glance v Current Health
These panes are described in the following sections.
v Launching NetMetrix Performance Center displays the Domain Health Sumv Click
mary view for your monitored domain. from any other view. Where you can go from this view:
To display a Domain Health Summary view:
v All navigation through the application begins with the Domain Health Summary view. The next two sections, History At-a-Glance and Current Health, provide specific information about where to go from this view. History At-a-Glance The History At-a-Glance pane displays a historical status of the networks activity over a 24-hour period. Each row represents a network element - LAN, WAN, switch, or swichlink (for VLANs). When you look at the History At-a Glance pane, you can begin to isolate any apparent network problem for a certain network element. Here is an example of a History At-a-Glance graph:
Each colored block in a row represents a 30-minute period (the default data collection interval, which you can change). See Selecting a Time Interval for Data Collection on page 2-36 for information about changing the intervals.
2-9
Data Views
The data represented by each block appears as red, yellow, and green. If any one metric for a particular network element exceeds a configured threshold, the colors will change. The colors indicate the aggregate status of all metrics for each network element in each time interval relative to predefined thresholds as follows:
v Green indicates that no thresholds have been exceeded. v Yellow indicates that the warning threshold has been exceeded. v Red indicates that the critical threshold has been exceeded.
Note: You can reconfigure the thresholds, if desired, using the configuration panels. See Setting Global Thresholds on page 4-13 for more information. Using aggregation, NetMetrix Performance Center determines the status of each group of data sources based on the most active data source in that group. If, for example, in a group of six LANs, four have green status, one has yellow status, and one has red status, the overall status of the group is graphically represented by a red box. If, later, that group has three LANs with green status and three with yellow status, the group is represented by a yellow box.
v Click the name of a network element (for example, LANs) to display the
At-a-Glance chart for that element. See At-a-Glance Chart on page 2-12 for details.
Where you can go from this view:
2-10
Current Health The Current Health pane displays a graphical representation of the realtime network health, showing a radar graph for each network element. These graphs allow you to quickly identify the specific cause of a network problem. Each axis on a radar graph corresponds to a key metric. Different key metrics are displayed for different data sources. This is an example of a current health radar graph for LANs, which shows a potential problem that involves the metrics Utilization and Octets:
Key Metric Link
Hot Spot
The red, yellow, or green dot, called a hot spot, on each axis identifies the data source which currently has the highest value for a given metric. The color of each hot spot indicates the level of activity for the associated key metric. In addition, activity is also indicated proportionally: the further the hot spot is from the center of the graph, the more active the data source. If you hold the cursor over a hot spot for a moment, the name of the data source associated with that hot spot appears near the cursor. This view allows you to quickly identify the hot spots on your network.
v Click a key metric link to display the Most Active Data Source View on v Click a hot spot to display the Data Source Health view for the single most
active data source for the selected key metric. See Data Source Health View on page 2-13 for details. page 2-31.
2-11
Data Views
At-a-Glance Chart
On the Domain Health Summary, from the History At-a Glance pane, click the name of a type of network element type (for example, WANs) to display the At-a-Glance chart for that element. The At-a-Glance chart displays activity on a list of data sources over a 24-hour period.
By default, the members are sorted from most active to least active. The Name/Status bar allows you to sort the members in the At-a-Glance list. You can:
v Click Name to sort the members by name in descending alphabetical order. v Click Name again to sort the member names in ascending order. v Click Status to return to the default sort (ascending and descending).
Note that there will be two entries for each WAN and full-duplex LAN probe listed. The names of the entries indicate the direction of traffic for each data source:
v One for incoming traffic, for example, WAN-4245-IN v One for outgoing traffic, for example, WAN-4245-OUT
See Traffic Direction Selection Control on page 2-14 for more information. To display an At-a-Glance chart for a specific network element:
v On the Domain Health Summary, click LANs, Switches, WANs, or v On the LANs At-a-Glance view, click the name of a LAN to display the
At-a-Glance chart for a individual LANs. At-a-Glance chart for Switch Ports. Switchlinks to display the At-a-Glance chart for the selected network element.
v On the Switches At-a-Glance view, click the name of a switch to display the v On the WANs At-a-Glance view, click the name of a WAN to display the
At-a-Glance chart for a WANs logical interfaces.
2-12
v On the Switchlinks At-a-Glance view, click the name of a Switchlink to display the At-a-Glance chart for a Switchlinks logical interfaces.
v Click an item listed in the Name column to display a more specific

At-a-Glance chart or a Data Source Health view for that item.
Data Source Health View

The Data Source Health view displays detailed data about each key metric for the selected data source over a 24-hour period. (The time span may be less than 24 hours if there is insufficient data.) The key metrics measured for each data source correspond to the key metrics displayed for that data source on the Current Health pane of the Domain Health Summary. This is an example of the Data Source Health view:
2-13
Data Views
Note: The unit of measurement for utilization is percentage of media capacity or, in the case of WANs, the rate associated with a selected PVC. The sample screen above is the Data Source Health view for a LAN. Different key metrics appear on this view for switches, switchlinks and WANs; however, the functionality of this view is the same for all key metrics.
v From any At-a-Glance view, click a data source name. v From the Event Viewer, select a data source, right click, and then select Elev From the Agent Interfaces view (one of the Configuration views), select a v From the Current Health pane of the Domain Health Summary, click a hot
spot. data source, right click, and then select Element Health. ment Health.
To display a Data Source Health view:
v Click a time interval bar to display the Zoom Analysis view. (See Zoom v Click a tab at the top of the view to display another view. (Note that the
graphic shown above is the Data Source Health view for a LAN. Other data sources may have fewer or different tabs on this view.) Traffic Direction Selection Control For full-duplex probes (WANs and LANs equipped with a full-duplex probe), the Traffic Direction Selection Control can be displayed in the top right corner of the Data Source Health view. The Traffic Direction Selection Control indicates the direction of traffic reflected in the current view. Analysis View on page 2-25.
v Data Source Health View v Top Hosts by Data Source View v Top Protocol View v Errors/Congestion View
2-14
The Traffic Direction Selection Control can also appear on the following views:
v Utilization by Data Source View

You can change the In+Out Traffic view, if desired, by clicking one of the unselected option buttons in the Traffic Direction Selection Control. If you click In+Out, the In+Out Traffic view displays:
v A color -coded vertical bar graph for each network key metric v A proportional representation of the In + Out traffic for the data source v A 24-hour history graph for each key metric with each bar on the graph representing a 30-minute time interval Note that the key metrics displayed for WAN interfaces vary depending on the type of interface.
The In+Out Traffic view includes:
2-15
Data Views
Top Hosts by Data Source View

The Top Hosts by Data Source view displays a vertical bar graph for each key metric for the selected data source. You can access data on additional metrics by clicking the tabs (to view data for Packets or Octets, for example). Each bar on the graph represents a host with the hosts identified by color to the left of each bar graph.
The sample screen above is the Top Talkers by Data Source view for LANs. Different key metrics appear on this view for switches, switchlinks, and WANs; however, the functionality of this view is the same for all data sources. Note: Top conversations are labeled by pairs of hosts.
2-16
To display a Top Hosts by Data Source view:
v On an At-a-Glance chart, click a data source listed in the Name column to

display the Data Source Health view for that data source; then click one of the following tabs:
w w w
Top Talkers Top Listeners Top Conversations
On any of these views you can change the host name display preferences for the listed hosts. By default, the hosts are referred to by friendly name, but you can change this reference to network address. See Selecting Host Name Display Preferences on page 2-33 for details. Where you can go from this view:
v Click a bar on one of the graphs to display the Top Protocols by Host view v Click a tab at the top of the view to display another view. (Note that the
for the corresponding host. See Top Protocols by Host View on page 2-27 for details. graphic shown above is the Top Hosts by Data Source view for a LAN. Other data sources may have fewer or different tabs on this view.) Note: The Traffic Direction Selection Control is available on this view for full-duplex interfaces. See Traffic Direction Selection Control on page 2-14 for details.
2-17
Data Views
Top Protocol View

The Top Protocol view displays a pie chart for each key metric indicating the top protocols for the selected data source over a 24-hour period. The top protocols are identified by color codes in the legends to the left of each pie chart.
The sample screen above is the Top Protocol view for LANs. Different key metrics appear on this view for switches, switchlinks, and WANs; however, the functionality of this view is the same for all data sources. To display a Top Protocol view:

display the Data Source Health view for that data source; then click the Top Protocols tab.
2-18
v Click a slice of pie on one of the pie charts to display the Top Talkers and v Click a tab at the top of the view to display other data views. Note that the
graphic shown above is the key metrics by Top Protocol view for a LAN. Other data sources may have fewer or different tabs on this view. Note: The Traffic Direction Selection Control is available on this view for full-duplex interfaces. See Traffic Direction Selection Control on page 2-14 for details. Listeners view for the corresponding protocol. See Top Talkers and Listeners View on page 2-29 for details.
2-19
Data Views
Errors/Congestion View
The Errors/Congestion view displays a vertical bar graph indicating the distribution of errors over a 24-hour period. The errors are identified by colors to the left of the bar graph.
The sample screen above is the Errors/Congestion view for LANs, showing an Error Distribution graph. The error graph types that can be displayed in this view are:
v Error Distribution (As shown in the example above). The Error Distribuv Frame Relay Congestion This display shows two congestion graphs
tion graph shows error categories for the type of interface being viewed. This could be Ethernet, Token-ring, ATM, or WAN protocols, for example. which are tiled vertically. The top graph shows FECNs and BECNs over 24 hours stacked in a vertical bar graph. The bottom graph shows the ratio (in percentage) of discard eligible frames relative to total frames.
2-20
v ATM Signaling Traffic Error Distribution and Congestion This display v ATM AAL/5 Datalink Traffic Error Distribution and Congestion This
display shows two congestion graphs which are tiled vertically. The top graph shows the 24 hour AAL/5 error distribution. The bottom graph shows the ratio of CLP-marked cells to total cells over 24 hours. shows two congestion graphs which are tiled vertically. The top graph shows the 24 hour ATM error distribution. The bottom graph shows the percentage ratio of CLP-marked cells relative to total cells over 24 hours.

display the Data Source Health view for that data source; then click the Errors/Congestion tab. Where you can go from this view:
To display a Errors/Congestion view:
v Click a tab at the top of the view to display another view. (Note that the
graphic shown above is the Errors/Congestion view for a LAN. Other data sources may have fewer or different tabs on this view.) Note: The Traffic Direction Selection Control is available on this view for full-duplex interfaces. See Traffic Direction Selection Control on page 2-14 for details.
2-21
Data Views
Detailed Statistics View

The Detailed Statistics view displays statistics for the data source, with the most recent value for each statistic.
The sample screen above is the Detailed Statistics view for a LAN. Different statistics appear on this view for switches, switchlinks, and WANs; however, the functionality of this view is the same for all data sources. To display a Detailed Statistics view:

display the Data Source Health view for that data source; then click the Detailed Statistics tab. Where you can go from this view:
v Click a tab at the top of the view to display another view of the same data.
2-22
Utilization by Data Source View

The Utilization by Data Source view displays a horizontal bar graph that represents the:
v Port utilization for a selected switch v PVC utilization for a selected WAN
The sample screen above is the Utilization by Data Source view for switch ports. Different bars may appear on this view for other data sources, however, the functionality of this view is the same for all elements.
v Click Switches or WANs, on the Domain Health Summary view; then click
the name of a data source to display the At-a-Glance chart for that data source; then click the Utilization tab.
To display a Utilization by Data Source view:
2-23
Data Views
Where you can go from this view: data source.
v Click a bar on the bar graph to display the Data Source Health view for that
Note: The Traffic Direction Selection Control is available on this view for full-duplex interfaces. See Traffic Direction Selection Control on page 2-14 for details.
2-24
Zoom Analysis View

The Zoom Analysis view provides a display with two graphs. The top pane displays detailed data about for the selected key metric over a 24-hour period.
Marker indicates the time slot detailed in the lower pane of this view.
2-25
Data Views
The lower pane displays a Top Hosts by Data Source view with tabs for Top Talkers, Top Listeners, Top Conversations, and Top Protocol views. This information is for the time interval indicated by a marker in the graph at the top of this view. See Top Hosts by Data Source View on page 2-16 and Top Protocol View on page 2-18 for more information about these views. The sample screen above is the Zoom Analysis view for LAN utilization. Different bars may appear on this view for other key metrics; however, the functionality of this view is the same for all supported key metrics (utilization, octets, packets/frames, broadcasts, and multicasts). To display a Zoom Analysis view:
v From the Data Source Health view, click a time interval bar for any key metric to display the Zoom Analysis view for that key metric. See Data Source Health View on page 2-13 for more information. Where you can go from this view: a different time interval. another view.
v Click a time interval bar on the top pane of this view to display details about v Click one of the tabs at the top of the lower pane of this view to display v Click a bar on the lower pane of this view to display a Top Protocols by Host
view for the selected key metric. See Top Protocols by Host View on page 2-27 for details.
2-26
Top Protocols by Host View

The Top Protocols by Host view is divided into three panes. The top pane displays a vertical bar graph indicating the top protocol distribution for the selected key metric. Each bar on the graph represents a host. The hosts are identified by colors that appear in the legend to the left of each bar graph.
Marker indicates the host detailed in the lower part of this view
The two lower panes display pie charts for the top network and application protocols for the selected time interval. The sample screen above is the Top Protocols by Host view for LAN utilization. Different graphs may appear on this view for other key metrics; however, the functionality of this view is the same for all key metrics.
2-27
Data Views
Note that the protocol information shown in the pie charts do not necessarily represent 100% of the protocols on your network, but shows the relative proportions of the protocols captured by NetMetrix Performance Center. On this view you can change the display preferences for the listed hosts. By default, the hosts are referred to by friendly name, but you can change this reference to network address. See Selecting Host Name Display Preferences on page 2-33 for details. To display a Top Protocols by Host view: ysis View on page 2-25 for details.
v Click a bar on the lower pane of the Zoom Analysis view. See Zoom Analv Click a bar on the bar graph to display the top protocol distribution for the v Click on a pie slice to display the Top Talkers and Listeners view for the corresponding host. corresponding host. A marker identifies the selected host. Where you can go from this view:
2-28
Top Talkers and Listeners View

The Top Talkers and Listeners view is split into four panes. The top pane displays a pie chart showing the distribution for the selected metric by Data Source. The center pane displays a vertical bar graph indicating the top protocol distribution over a 24-hour period. The two lower panes display vertical bar graphs for the top talkers and top listeners by host with the hosts identified by color in the legend to the left of each bar graph.
The sample screen above is the Top Talkers and Listeners view for LAN utilization. Different bars may appear on this view for other key metrics; however, the functionality of this view is the same for all key metrics. On this view you can change the display preferences for the listed hosts. By default, the hosts are referred to by friendly name, but you can change this reference to network address. See Selecting Host Name Display Preferences on page 2-33 for details.
2-29
Data Views
To display a Top Talkers and Listeners view:
v Click a slice of pie on one of the pie charts in the Top Protocol view. See
Top Protocol View on page 2-18 for details.
v Position the cursor over a slice of the pie in the top pane of this view to display the percentage represented by that slice.
2-30
Most Active Data Source View

The Most Active Data Source view displays a horizontal bar graph of the five most active data sources for the selected metric. The data sources are sorted from the most active to less active among the top five. What are the measurements shown in this view? There are four types of measurement shown in this view. The type of measurement shown depends on the metric. These are:
Metric Latency Utilization and Unavailability Type of measurement shown Absolute value Self-normalized percentage of capacity
Octets and Cells Calculated to show percentage of capacity. See example below. Frame-based measurements (Congestion, Packets, Frames, etc.) Calculated to show percentage of capacity. See example below.
How can certain metrics be expressed as % of Capacity? Certain metrics are calculated based on normalized (rather than absolute) value. These metrics include Congestion, Packets, Frames, Multicasts, and others. The calculation for the values shown in this view for these metrics is:
This calculation is also made for the metric Octets, but with the difference that /nominal packet size is not used in the calculation. Cells are calculated using /bytes per cell instead of /nominal packet size.
2-31
Data Views
The sample screen below is the Most Active Data Source view for WAN Congestion.
To display a Most Active Data Source view:
v Click a key metric link in a radar graph on the Current Health view.
SeeCurrent Health on page 2-11 for details.
v Click on a horizontal bar to go to the Data Source Health View for that data
source. See Data Source Health View on page 2-13 for details.
2-32
Selecting Host Name Display Preferences

You can use the Display Preferences dialog to identify hosts by either friendly host names or network addresses. This choice applies on the Top Hosts views (Top Talkers, Top Listeners, Top Conversations, Top Protocols by Host, or Top Talkers and Listeners). Note: The NetMetrix Performance Center Server resolves IP addresses to friendly names every six hours, so there may be some delay before you see the friendly host names on the Top Hosts views. Also, if there are no friendly names available for the hosts, the IP addresses will persist even if you have requested the display of friendly names.
To change host display preferences: 1 On the toolbar, click the dialog will display: icon in the toolbar. The Display Preferences
2-33
Selecting Host Name Display Preferences
The default selection is Show Host Name. This host name is whatever friendly name you have specified for the hosts. For example:
2 You can select Show Network Address to specify that the hosts are represented by network addresses (such as an IP address). For example:
3 Make your selection and click OK. Note that any display preference you specify will apply on all views that display lists of hosts until you change the preference back again.
2-34
Setting Time Frame and Time Interval for Data Display

NetMetrix Performance Center includes two tools that allow you to control the time frames and time intervals of the data displayed in the views. These tools are described in the following sections.
Selecting a Time Frame for Historical Data

By default, NetMetrix Performance Center displays the most current data. You can reset the application to display historical data using the Select Date and Time dialog. To change the date or time: 1 On the Data Source Health view, click The Select Data and Time dialog opens. on the toolbar.
2 In this dialog, you can:
w w w
Move the Earlier/Later slider to change the date/time axis. Select new numbers in the Month, Day, Year selectors to display data from a specific date. Use the Hour and Minute selectors to select a specific time.
3 Click Apply to display the view ending at the specified time. This dialog remains open. 4 Click OK to apply your latest changes and close the dialog.
2-35
5 Click
to see current data again.
The settings in this dialog apply to the current session only. Note: If you specify a Date and Time that represents data that does not exist in the database, you will receive an error dialog with a message like this one:
If you find that you need to change the discard value for historical data in your database, see Setting Data Storage Policies on page 4-11.
Selecting a Time Interval for Data Collection

The default time interval for data sampling is 30 minutes. You can change this interval to a finer time granularity using the Interval Selection dialog. This will change the data sampling interval for data that appears in the graphs. To access this dialog, click on the toolbar.
2-36
The Interval Selection dialog lists the available time intervals. You can select one of the existing time intervals, create a new interval, or delete one or more intervals from the list. The default time interval (30 minutes) is represented by the word History in the dialog, as shown above. Whenever you wish to return the default time interval, open this dialog, click History, and then click OK. Note that there can be negative consequences for the functioning of the Server if you select a brief data sampling interval. The consequences of changing the data collection interval can be:
v Increased database growth v Increased use of Server and probe resources v Increased SNMP traffic on the network as the polling interval increases
Note: The history interval applies to data that are continuously collected and stored in the database. Data for other intervals are acquired for the current view only. When you close the Data Source Health View or go to another view, NetMetrix Performance Center discontinues data acquisition for intervals other than the history interval. To add a time interval: 1 Open the Interval Selection dialog. 2 Click Add. The Set Interval Time pop-up opens.
3 Enter a time interval. 4 Click OK. You return to the Interval Select dialog, and the new time interval on the intervals list. 5 To apply the new time interval, select it, and click OK.
2-37
To delete an interval, select the interval, and click Delete. Note: You cannot delete the History (default) interval. You can, however, disable collection using the Agent Interface panel. See Managing Agent Interfaces on page 4-25 for details.
2-38
Managing Events in NetMetrix Performance Center

This section describes events generated by the Server when any of the following occurs:
v A configured threshold has been exceeded v An RMON alarm v A data sources or agents status has changed v An informational message is listed v The networks topology has changed (data sources have been added or v A data source is unreachable v The NetMetrix Performance Center license expires
deleted)
Event Viewer Features

The NetMetrix Performance Center event viewer allows you to:
v View events v Acknowledge events v Delete events v Sort events by severity, data, time, source, event type v Filter events by severity and type, time range, and data sources v Add comments to events v Navigate to the Data Source Health view associated with a listed threshold
event
2-39
Using the Event Viewer Dialog

When you click on the toolbar, the Event Viewer dialog appears.
By default, the event viewer lists all events in chronological order. The most recent event appears at the bottom of the list. Note: To sort by any category, click the category heading by which you want to sort the list. Click on a category a second time to reverse the sort order. Categories of Event Information For each event, the event viewer displays the following categories of information:
Ack Acknowledgment check box. Click to mark an event to help you remember which events you have already reviewed. Also can be used as a filtering criterion. An identification number assigned by the event viewer to each event as it is listed. An indication of the severity of the event:
EventID Severity
v Critical v Warning v Information.
Date & Time Source
The date and time of the event. The source of the event (such as a data source name).
2-40
Event Type
The type of the event:
v Status v Threshold
Status events indicate the overall status of a data source (for example, Agent came on-line. Threshold events indicate threshold violations. Messages A brief description of the event.
Right Click Functionality In the Event Viewer, you can select a data source and then right click to access a pop-up menu with these choices:
Select All Select all data sources listed in the Event Viewer.
Acknowledge/ Use with multiple events. You can Select All events and Acknowledge Unacknowledge or Unacknowledge then if you choose. Annotate Details Element Health Delete Events Help Add or change explanatory text for a selected event. Shows event details (including annotation) for a selected event. Navigates to the data source health view that shows the threshold event. Remove a selected event. invokes the online help.
2-41
Filtering Events
By default, the event viewer lists all events, but you can change this default and filter events by specific categories using the Event Selection option buttons:
Click to display only Critical Events. Click to filter event display by Severity and Type, Time Range, and Data Sources; then click Define. It uses the last-defined filter.
When you select Critical, the event viewer displays events with critical severity only. When you click Filter and then Define, the Set Filter for Event Viewer dialog opens. See the following sections for details.
2-42
Filtering by Severity and Type The left-most tab of the Set Filter for Event Viewer, Severity and Type, allows you to set the severity level and the type of event to display in the event viewer:
Match Acknowledgment Match Severity
The default is for the event viewer to display both Acknowledged and Unacknowledged events. You can choose not to display one or the other by clearing the corresponding check box. The default is for the event viewer to display the events with any of the three levels of severity. Clear the check boxes for the levels that you do not wish to display.
Match Event Type
v traps (will always display) v collector status (will always display) v data source status (can be filtered in) v threshold violations (can be filtered in)
The default is for the event viewer to display these four event types:
To limit the display, click Selected Types, and then click the check boxes for the types you wish to display. You can filter in threshold violations and data source status events. Traps and collector status events are always displayed in the event viewer.
2-43
Filtering by Time Range The middle tab of the Set Filter for Event Viewer, Time Range, allows you to filter the events shown in the event viewer by time periods.
Match Latest
The default is to match (display) all events. You can override this default by selecting another time period. For example, you can specify that you want to see only events that have occurred in the last hour. You can specify a time range for displayed events by using the time sliders. Click Received Before or Received After, and then use the slider to select a date and time for before and after.
Match by Time Range
2-44
Filtering by Data Sources The right-most tab of the Set Filter for Event Viewer, Data Sources, allows you to restrict the events displayed to only selected data sources.
To select a data source by which to filter: 1 Click Match Source(s). 2 Select the data sources from the Available panel by clicking the folder icons until you get to the data source. 3 Click the arrow to display the selected data sources in the Selected panel. Events that occur on the selected agents are now the only events that the event viewer displays.
2-45
To delete items from the Selected panel: 1 Click the data source to select it. 2 Right-click the data source. The Delete pop-up appears. 3 Click Delete. Note: The data source is deleted from the Selected panel in the Data Sources filter only. It still exists on your network and is displayed in the data views in NetMetrix Performance Center.
2-46
Interpreting What You See in NetMetrix Performance Center

This chapter describe how to use Agilent NetMetrix Performance Center to monitor your network. It describes several network problem scenarios. Each scenario walks you through the process of isolating a specific network problem. This chapter describes these scenarios:
v High utilization on a WAN v Broadcast storm on a LAN v High WAN latency v High PVC utilization on a WAN v High utilization on a switch port v High utilization on a VLAN on a Switchlink
3-1
High Utilization on a WAN

You notice a utilization peak on your WAN. You want to find out the cause of this activity. In the Current Health view of the Domain Health Summary, there is a red sector on the radar graph for the Utilization and Octets metrics for WANs:
Note the red sector for Utilization for WANs.
1 Click the hot spot for WAN utilization to display the Most Active Data Source view of the busiest WAN interface. 2 In the Most Active Data Source view, look at the Utilization metric:
Note the red bars in the most recent time slots in the graph.
3-2
3 Click on the highest red bar in the Utilization metric graph. This zooms in on the network information for that particular time interval and displays the Zoom Analysis view for the Utilization metric:
This view includes an enlarged metric view, along with tabs for Top Talkers, Top Listeners, Top Conversations, and Top Protocols for that particular time. Take note of the time.
3-3
4 Look through the tabs for high activity hosts, such as Top Talkers. For example, click on the bar for the highest activity Top Talker. The Top Protocols by Host view opens:
Note that the marker indicates which bar in the graph we are working with.
Note the host name of the busiest Top Talker. Now, look at the protocols. In this example the HTTP protocol in the application protocol pie graph has high activity. The HTTP protocol is typically used for web traffic. You want to see the other end of the conversation to find out the Top Listener host for this activity.
3-4
5 Click on the pie slice for the HTTP application protocol. The Top Talkers for the protocol view opens:
Note the time.
This view displays the top application protocols for the Top Talker, and shows the Top 10 Listeners by host. Note the host name of the outstanding listener, and the time of the activity. The listener happened to be a Web server. Since the protocol involved is http and the listener is a Web server, you conclude that the client is downloading Web pages. Example Solution: To solve the problem of peak traffic on the WAN at this time, you configure the client PC to use a web proxy and cache web pages, eliminating the need for a fresh download each time a user requests a web page.
3-5
Broadcast Storm on a LAN

You see a burst of activity on the network that is degrading the networks performance. Broadcast storms originate from a host that is running the application that is the cause of the problem. Your goal in this scenario is to identify the host that is generating the storm. In the History at a Glance view of the Domain Health Summary, you notice that there are several red blocks in the LAN history graph:
High activity indicated here.
1 Click on the LANs link under History at a Glance. The LANs at a Glance view opens:
Red blocks indicating high activity.
This view shows your LANs, with the most active LAN at the top of the list. This LAN shows several blocks of red at intervals, indicating periods of high network activity.
3-6
2 Click on the link for the LAN showing the high activity. This could be a broadcast storm on the LAN. The Most Active Data Source view for the LAN display. Notice the high activity for the Broadcast metric:
Note the red bars showing high activity periods.
3-7
3 Click on one of the red bars. This zooms in the on the network information for that particular time interval. The Zoom Analysis view for the Broadcast metric opens:
This view includes an enlarged metric view, along with tabs for Top Talkers and Top Protocols for that particular time. Note that one host shows significantly higher activity than the others.
3-8
4 Click on the bar for most active host. The Top Protocols by Host view opens:
5 Look at the protocols for this Top Talker host. In this example, the ARP protocol in the network protocol pie graph has high activity. So, the broadcast storm can be specifically identified as an ARP storm. Example Solution: Having identified the host and the type of protocol involved in the broadcast storm, you talk to the administrator for that host machine. She tells you that she has recently installed some new printer server software. This software does auto-discovery and rapidly searches for IP addresses. There is a configuration problem, and she reconfigures the printer server to have a delay between searches. This eliminates the ARP storm.
3-9
High WAN Latency
High WAN Latency

You notice an unexpected peak of WAN latency. You need to characterize the problem by knowing the time that this started occurring so you can tell your service provider. This scenario describes you how to find the time of a high latency period on a WAN. For more information on WAN latency configuration in NetMetrix Performance Center, see Configuring WAN Latency on page 4-38. In the Current Health view of the Domain Health Summary, you notice that there is a red sector on the radar graph for the Latency metric for WANs:
Sector of high activity.
1 Click the hot spot for WAN latency to display the Most Active Data Source view of the busiest WAN interface. 2 In the Most Active Data Source view, look at the Latency metric:
Red bars indicate high activity.
Example Solution: By looking at this graph, you get an idea of the time of the high latency. You call your internet service provider and tell them that the high WAN latency occurred starting at 2:00 pm. The internet service provider explains that at that time, they had lost a terrestrial link and are temporarily using a backup link that goes through a satellite.
3-10
High PVC Utilization on a WAN

You notice that the History at a Glance is indicating high utilization on your WAN.
1 Click on the WANs link. The WANs at a Glance view opens:
You notice a WAN with high activity. 2 Click on the link for that WAN. The interfaces are displayed, but you need to see the activity on the PVCs.
3-11
High PVC Utilization on a WAN
3 Click the Utilization by PVCs tab. The pattern of high use makes you wonder if a specific PVC could be the problem. The Utilization by PVC view opens:
Yellow and red bars indicate threshold violations on the PVC.
Example Solutions: You may want to try to load balance with another PVC, or You confirm that a over-utilized PVC, Palo Alto to Houston, is the problem, and call your service provider. He configures a higher committed information rate (CIR) for that PVC. Once the new CIR takes effect, the high utilization stops.
3-12
High Utilization on a Switch Port

There is consistent high activity on your switches and you decide to find out which switch port is responsible. In the History at a Glance view of the Domain Health Summary, the Switches history graph displays numerous yellow and red blocks, indicating threshold violations have occurred:
1 Click on the Switches link. The Switches at a Glance view opens:
You notice that one switch shows fairly persistent high utilization with threshold violations occurring frequently. You want to see what is going on with that switch. 2 Click on the label for the busy switch. The Switch Ports at a Glance view displays. You want to see activity for individual ports.
3-13
High Utilization on a Switch Port
3 Click the Port Utilization tab. The Utilization by Data Source view for that switch opens:
One port shows high activity. Depending on your needs, there are a few actions you can take to address this: Example Solutions: If the port is a shared media port connecting with multiple nodes, you can move several of the nodes to another switch. This alleviates the high utilization on the busy switch port. You might need to upgrade the port interface to a higher media speed (for example, from 10 mbit to 100 mbit). You might decide that high utilization is acceptable for the busy switch, and elect to increase the thresholds on that device. See Setting Global Thresholds on page 4-13 for details on configuring thresholds. Also, this condition can be an indication of a bad card on the busy port.
3-14
High Utilization on a VLAN on Switchlinks

You notice high utilization for your switchlinks. You need to find out which VLAN is the cause of this condition. In the Current Health view of the Domain Health Summary, there is a red sector on the radar graph for the Utilization and Octets for switchlinks:
1 Click the hot spot for Switchlink Utilization. The Most Active Data Source view of the busiest VLAN opens. 2 Click the Top Conversations tab to see the busiest conversations between hosts.
Note the two hosts that are having the most conversations. Example Solution: Now that you know who the hosts are, you can start to look at the kinds of applications that are on the two machines. You find out that the two machines are servers that are exchanging frequent database updates. To remedy the high utilization between them, you move the connections so that both servers are physically connected to the same switch.
3-15
High Utilization on a VLAN on Switchlinks
3-16
Configuring NetMetrix Performance Center
Overview
This chapter describes Agilent NetMetrix Performance Centers configuration options, including:
v Global Policy Configuration v MLM and Agent Management v Agent Auto-Discovery
Before you make any configuration changes, please read through the next section, Configuration Considerations to determine what kinds of configuration changes you might want to make and when to make those changes.
Configuration Considerations
When you complete the installation of NetMetrix Performance Center you will want to add agents. See Adding Agents on page 4-17 for information on adding individual agents, or see Agent Auto-Discovery on page 4-46 for more information on agent auto-discovery. The default configuration settings for NetMetrix Performance Center have been optimized for typical network considerations and network administrators concerns. However, every network is somewhat different, and from time to time, every network has special circumstances. You might want to change one or more configuration settings now or sometime in the future, or you might want
4-1
Overview
to make some tweaks from time to time or change a setting temporarily. This section calls your attention to a few configuration options you might want to consider changing now, on an on-going basis, or under special circumstances. Immediate Considerations Before you begin using NetMetrix Performance Center, consider the following configuration options:
v Auto-discovering agents w You can configure NetMetrix Performance Center to auto-discover

w
agents. See Agent Auto-Discovery on page 4-46 for instructions. If you want to selectively add agents, see Adding Agents on page 4-17 for instructions. You might want to use this option if you have devices that you do not want to monitor for some reason or if you find you have more devices than the Server can effectively monitor.
v Selecting a security model

w w
If you want to allow any user on your network to view and/or configure NetMetrix Performance Center from a Web browser, select the global security model (the default). The default settings in this model are: Viewing is enabled. Any user on your network can display the NetMetrix Performance Center views in a browser.
Configuration is allowed from the NetMetrix Performance Center Performance Console only (not from a web browser). If you want to restrict access to NetMetrix Performance Center to only one or a few IP addresses, use the access list security model. This model allows you to specify certain IP addresses and then to assign separate viewing and configuration permissions to each IP address individually. See Setting Access Control on page 4-9 for instructions on configuring NetMetrix Performance Center security.
4-2
v Providing friendly names for agents

NetMetrix Performance Center provides practical names for agents and other devices on the network. These names are based on the IP hostname on the system. DNS is used to resolve IP hostnames. If DNS is not available, NetMetrix Performance Center will use a local host table. You might consider changing these assigned names to more meaningful names. The following is a list of names you can change and the section and page number that describes how to change each:
w w w w w
Server name (MLM and Agent Management on page 4-15). MLM means Mid-Level Manager, a key part of the Server which manages the network agents. Agents (Adding Agents on page 4-17, Setting Agent Properties on page 4-21) Agent interface (Managing Agent Interfaces on page 4-25) PVCs (Configuring PVCs on page 4-33) VLAN (Configuring VLANs on page 4-36)
v Determining data to store and how to store it w When deciding on a data discard date, think about how much data you can
w
afford to store, in terms of disk space, and in terms of data availability. For example, the default value is 42 days of data. Will you want more history available than that?
When selecting a database cleanup time, think about other system activity. You may not want this cleanup to occur during a busy time, such as when your system backups are occurring. See Setting Data Storage Policies on page 4-11 for instructions.
4-3
Overview
Periodic Considerations v Adjusting thresholds This is the most common configuration change you might make on an on-going basis. As your network usage changes, you might want to change the thresholds to be sure the NetMetrix Performance Center views are reflecting an accurate picture of your network traffic.
v Adding PVCs to WANs
NetMetrix Performance Center auto-discovery automatically adds PVCs that are already configured on the agent. You may want to add more PVCs after the initial auto-discovery. Note: When you add a PVC, either through auto-discovery or manually, the state of the PVC is Enabled, not Collecting. By default, PVCs are not in the state Collecting until you start collection. See Configuring PVCs on page 4-33 for details. You can add protocols that are not in the default list, and make them available to agents. See Customizing Agent Protocols on page 4-43 for details. Warm or cold start of probes. See Administering Agents on page 4-45 for details. When you add a VLAN, either through auto-discovery or using the Add Agent view, you must also:
v Customizing protocols v Restarting probes
v Adding and Configuring VLANs w w
Use the Agent Interfaces view to change the VLAN management class to Switchlinks. See Managing Agent Interfaces on page 4-25 for more details. Use the VLAN Configuration view to enable data collection on each VLAN. Configuring VLANs on page 4-36 for more details.
4-4
Navigating the Configuration Views

There are several ways for you to navigate through the configuration views. You can go directly to one view and then return to the data views, or you can navigate through a series of configuration views to display or modify the current configurations. This section describes the basic navigational tools in the configuration area. Context Menus Right-clicking on different areas of the configuration screens displays context menus with commands that are specific to the current situation. The following table describes the context menus that are generally available on most configuration views.
Table 1 Configuration Context Menus Right click on... A row of data displayed in the white area of a configuration view The open (gray) area outside of any buttons or data displayed Anywhere on the view except on a button, if there is no open space on the current view To display... A context menu that allow you to view and modify, delete, or make other changes to the selected item (or items, where multiple selection is permitted) A context menu that allow you to add an item to the list or select all items on the list A context menu that combines both menus listed above
Apply, Reset, Set to Defaults Buttons Most views allow you to set or change parameters and then to apply your changes or to revert back to the previous settings. Some views allow you to revert back to the original default settings.
Click... Apply To... Save your changes
4-5
Overview
Click... Reset
To... Return the settings to their previous values when data has been entered Reset the settings to their original default values
Set to Defaults
4-6
Toolbar Buttons The button on the NetMetrix Performance Center toolbar is a link to the configuration views and is available whenever the toolbar is visible. When a configuration view is open, the button is added to the toolbar. When you click this button from any configuration view, the Global Configuration view opens.
The Global Configuration view is the main, or home, configuration view. You can navigate to any other configuration view from this view. Click one of the buttons to display the configuration options in each of the three primary areas:
v Global Policy Configuration v MLM and Agent Management v Agent Auto-Discovery
The remainder of this chapter describes the configuration options available in NetMetrix Performance Center.
4-7
Global Policy Configuration

When you click Global Policy Configuration, the Global Policy Configuration view opens. The Global Policy Configuration view has three tabs, each providing different configuration options:
v Security v Storage v Thresholds
The following sections describe the options on each of the tabs.
4-8
Setting Access Control

When the Global Policy Configuration view first opens, the Security tab appears, displaying the access control configuration options.
You use the Security tab to specify the type of access control you want to impose on the NetMetrix Performance Center system. If you select the Use Global Security Policies radio button (the default), you can enable or disable access from the web browsers as follows:
v Permit Data Viewing from Web Browser allows users on your network v Permit Configuration from Web Browser allows users on your network
to view NetMetrix Performance Center data from a web browser. The default is enabled (checked). to configure NetMetrix Performance Center from a web browser. The default is disabled (unchecked).
4-9
If you select the Use Access List radio button, you can restrict access to particular IP addresses only. For each IP address, you can specify different access levels from consoles and web browsers:
When you select Use Access List, the list of IP addresses with NetMetrix Performance Center access is enabled. You can add IP addresses to the list and change the permissions from each source individually. Right-click an IP address to display a context menu.
v Add New IP Address displays the Add IP Address view. v Change IP Address displays the Change IP Address view. v Delete IP Address deletes the selected IP address.
4-10
When you add an IP address to the list, the access permissions from both the console and a web browser are set to denied, the default. To change a permission setting, right-click on the setting you want to change to display a context menu listing the permission options for that setting.
Select the permission you want from the menu.
Setting Data Storage Policies

You can modify the data storage policies for your history and realtime data. Click the Storage tab on the Global Policy Configuration view to display the data storage configuration options.
4-11
You can access historical data using the Select Date and Time dialog. See Selecting a Time Frame for Historical Data on page 2-35 for details. These are the values that you can change on this screen: cleanup to occur. The default is 02:10:00.
v Database Cleanup Schedule the time at which you would like the database v Discard History Data After the number of days after which NetMetrix v Discard RealTime Data After the number of days after which realtime v Disk Utilization Alarm Threshold the amount of disk space that can be
Factors that can affect database size are: data is discarded. The default is 7 days. Note that data for realtime studies is derived from RMON1 and WAN statistics. used for storage (default is 10,000MB) before an alarm is sent to the Event Viewer. Performance Center discards historical data. The default is 42 days.
v Number of nodes on the network v Number of data sources that are being collected from v Number of RMON2 collections v Number of protocols collected v Number of conversations among nodes v Collection intervals/studies that are specified v Number of realtime collections
4-12
Setting Global Thresholds

Click the Thresholds tab on the Global Policy Configuration view to display the threshold configuration options.
You can use the Thresholds tab to specify the global thresholds for the key metrics available for each media type. The thresholds that are initially displayed for each media type before you change them are the factory thresholds. When you change the factory thresholds, you are establishing new global thresholds. The key metrics correspond to the key metrics displayed for each media type in the Data Source Health views. See Most Active Data Source View on page 2-31 for details on how percentage of capacity is calculated.
4-13
Click the Media Selector down-arrow to display a drop-down list of media types, and select the media type for which you want to set key metric thresholds. The key metrics for the specified media type appear on the Global Thresholds list, with the default thresholds displayed. When you change a threshold setting, the new setting takes effect immediately. However, this new threshold setting only affects data collected in the future, and does not affect pre-existing threshold events. The thresholds for each media type are indicated with red, yellow, and green bars and a number appears on the red and yellow sections to indicate the current threshold setting. To change a setting, position the cursor over the dividing lines between colors, and then click and drag the dividing line right to increase the threshold or left to decrease the threshold. You must always click Apply to save your new settings. After you click Apply to save your changes for one media type, you can select another media type from the Media Selection drop-down list, if desired, and set its thresholds by repeating the steps described above. Be sure to click Apply to save your changes for each media type. Reset will reset the thresholds to the last setting. This works only if you have changed settings and not yet clicked Apply. Set to Defaults resets the thresholds to factory defaults for the selected media type.
4-14
MLM and Agent Management

When you click MLM and Agent Management on the Global Configuration view, the MLM Configuration view opens.
You use the MLM Configuration view to display and modify configuration and policy values as follows: Server monitors the domain for the Palo Also site, you may want to call that MLM (Server) pasite; editable field. able field.
v MLM Name allows you to specify a name for the Server. For example, if a v Host Name displays the Server machine host name or IP address; nonedit-
4-15
v State indicates the current Server state: w Collecting Data: The Server is in the normal operating mode. w Initialization: The Server is performing the boot and initialization prow w w
cess. Shutdown: The Server is executing a shutdown request. Install: The Server is undergoing a network installation or update. Unknown: NetMetrix Performance Center is unable to communicate with the Server or host system, so its state is unknown.
v Software Version indicates the Server software version. v Logging: w Log Directory allows you to view the log files directory and path.
Viewing Agents on page 4-19 for details. page 4-17 for details.
v View Managed Agents displays the MLM Agent Management view. See v Add Agent displays the Add New Agent view. See Adding Agents on
Server automatically generates the log file name and stores them locally.
4-16
Adding Agents
When you click Add Agent on the MLM Configuration view, the Add Agent view displays. This view allows you to manually add an individual agent. You can also use Auto-discovery to add agents. See Agent Auto-Discovery on page 4-46 for more details.
Use the Add Agent view to add new agents (a hardware probe or network switch) as follows:
v Telemetry Address indicates the IP address of the agents telemetry port. v User Defined Name defaults to the host name corresponding to the telemv SNMP Settings: w Community String specifies the community string used when commuw w
nicating with the agent. Default is blank. You must enter a community string with administrative access to the device. The administrative community string for Agilent probes is hp_admin. SNMP Port specifies the SNMP port used when communicating with the agent. Default is 161. Message Size specifies the maximum message size in bytes when communicating with the agent. Default is 1400. etry port address (or to the address itself if no host name is available). This is the name that appears on the views described in Chapter 3. You can change it to a friendlier name, if desired.
4-17
When you finish specifying the information about the new agent, click Finish to add the new agent information and return to the MLM Configuration view. Note: Note that when you add a VLAN you must change the management class for the interface before you complete the configuration for this data source. See Managing Agent Interfaces on page 4-25 for more details on changing the management class.
4-18
Viewing Agents
When you click View Managed Agents on the MLM Configuration view, the MLM Agent Management view opens.
You use the MLM Agent Management view to display all of the MLM agents monitored by NetMetrix Performance Center or those of a specific type. The color of each agent icon indicates the current status of that agent. The Agent Type drop-down list allows you to select the type of agents you want to display. The default setting is All. Click on the toolbar to add an agent.
You can take any of the following actions on this view:
v Double-click an agent icon to display the Agent Properties view for that
agent. See Setting Agent Properties on page 4-21 for details.
4-19
v Right-click on one or more agent icons to display a context menu for that
agent.
w w
Start starts data collection from the selected agent(s). Data collection is started when you add an agent, or when an agent is added through auto-discovery. Stop stops data collection from the selected agent(s). Note that graphs showing time intervals that pass while an agent is stopped will contain no data for that agent. For example, you may want to stop data collection on an agent when you want to take that particular device offline, update firmware on a probe, or change an IP address for a device. Delete Agent stops data collection and deletes the selected agent(s) from the NetMetrix Performance Center system; deletes all stored settings and policies for the selected agent(s); requires confirmation. Properties displays the Agent Properties view for the selected agent; same as double-clicking on an agent icon; disabled when multiple agents are selected. SNMP Settings displays the Agent SNMP Settings view for the selected agent; disabled when multiple agents are selected. See Setting Agent SNMP Values on page 4-23 for details. Interfaces displays the Agent Interface view; disabled when multiple agents are selected. See Managing Agent Interfaces on page 4-25 for details. Protocol Customization displays the Agent Protocol Customization view for the selected agent(s). See Customizing Agent Protocols on page 4-43 for details. Agent Administration displays the Agent Administration view for the selected agent; disabled when multiple agents are selected. See Administering Agents on page 4-45 for details. Firmware Update displays the Firmware update view. See Updating Agent Firmware on page 4-24 for details.
w w w w w w w
4-20
v Right-click anywhere on the MLM Agent Management view except on the

agent icons to display a general context menu.
w w
Add displays the Add Agent dialog. See Adding Agents on page 4-17 for details. Select All selects all agent icons.
Setting Agent Properties When you double-click an agent icon on the MLM Agent Management view, or right-click an agent icon and select Properties from the context menu, the Agent Properties view opens.
4-21
You use the Agent Properties view to view and modify the configuration settings for the selected agent as follows:
v Telemetry Address indicates the IP address of the agents telemetry port. v User Defined Name defaults to the host name corresponding to the telemv Managing MLM displays the name of the managing Server; uneditable. v State displays the current status of the agent; possible values are: w Discovery Server is in the process of discovering agent capabilities. w Collecting Data The agent is collecting data. w Stopped The agent is stopped. w Query Server is attempting to query the agent. w Update The agents firmware is being updated. w Error The agent has experienced an error. w Admin An administration operation is being performed on the agent, v Firmware Revision displays the agent firmware version, if available; v Agent Description displays the type of agent (LAN, WAN, media speed, v Agent Configuration:
These configuration actions can be taken on more than one agent at a time: etc.). uneditable. etry port address (or to the address itself if no host name is available). You can change it to a friendlier name, if desired.
such as restart. Offline The agent is unavailable.
w w w
SNMP Settings displays the Agent SNMP Settings view. See Setting Agent SNMP Values on page 4-23 for details. Interfaces displays the Agent Interface view. See Managing Agent Interfaces on page 4-25 for details.
w w
Agent Admin displays the Agent Administration view for the selected agent; disabled when multiple agents are selected. See Administering Agents on page 4-45 for details. This configuration actions can be done only on one agent at a time because the data being changed will vary: Protocols displays the Agent Protocol Customization view. See Customizing Agent Protocols on page 4-43 for details. FW Update displays the Agent Firmware Update view. See Updating Agent Firmware on page 4-24.
4-22
Setting Agent SNMP Values When you right-click an agent icon in the MLM Agent Management view and select SNMP Settings on the context menu or when you click SNMP Settings on the Agent Properties view, the Agent SNMP Settings view opens.
v Community String specifies the community string used when communicating with the agent. Default is blank. You must enter a community string with administrative access to the device. The administrative community string for Agilent probes is hp_admin. agent. Default is 161.
You use the Agent SNMP Settings view to specify the following settings for the selected agent:
v SNMP Port specifies the SNMP port used when communicating with the v Message Size specifies the maximum message size when communicating
with the agent. Default is 1400.
4-23
Updating Agent Firmware When you right-click on one or more agent icons in the MLM Agent Management view and select Firmware Update on the context menu, the Agent Firmware Update dialog opens.
You use the Agent Firmware Update dialog to update the firmware for a group of agents of the same type.
v Agent Description identifies the type of agent v Agent ID displays the system descriptor (identifier) for the agent. v Selected Agents The list of agents to be updated appears on the right side
of the view. update file. Click Browse to use a standard file system navigation dialog to locate the file. Click Cancel if you want to close this dialog without performing the update. Click OK to close the dialog and initiate the update process. The firmware is downloaded into the memory of the probe. NetMetrix Performance Center requests confirmation that you approve a cold start of the agent.
v Firmware File / Browse allows you to specify the location of the firmware
The update operation might take some time, especially when multiple agents are being updated. The State field on the MLM Agent Management view indicates that an update is in progress for the affected agents. Note: After the firmware is downloaded and updated, the probe will warm start. A warm start allows the probe to retain configuration data, such as agent information configured through Performance Center.
4-24
Managing Agent Interfaces When you right-click an agent icon in the MLM Agent Management view and select Interfaces on the context menu or when you click Interfaces on the Agent Properties view, the Agent Interface view opens.
The Agent Interface view displays a list of all interfaces on the selected agent and the state of and other information about each interface. The interfaces are displayed whether NetMetrix Performance Center is monitoring them or not. Note that devices that are not being monitored will have a blank State.
Additional Steps for VLAN Configuration
Note that when you initially add a VLAN, the management class will show in this view as other than Switchlink. For you to be able to fully configure the VLAN for data collection, you must change the value in the MGMT Class field to Switchlink. To do this: 1 Select the VLAN MGMT Class field. 2 Right click and then select Modify Field.
4-25
3 The MGMT Class dialog will display. Use the pull-down arrow to select Switchlink. The management class value for the VLAN interface you selected will change to Switchlink. 4 To fully enable collection, you must start the collection using the VLAN Configuration view. See Configuring VLANs on page 4-36 for more details. These may be physical interfaces, such as probe interfaces or switch ports, or they may be logical interfaces, such as PVCs on a WAN. If an interface is not named, the Server assigns a default name. To modify the configuration settings for one or more interfaces, right-click any column for one or more interfaces to display a context menu. The commands enabled on this menu reflect the state of the system, the number of interfaces selected, and the row and the column in which you right-click.
v Start/Stop Starts and Stops data collection. This affects the State. Potenw w w
tial states are: Enabled collector active; able to collect data Disabled collector not active; not able to collect data Collecting collector is actively collecting data
v Thresholds displays the Interface Thresholds view for the selected interface. See Setting Global Thresholds on page 4-13 for details.
4-26
v Modify Field opens a dialog specific to the column on which you

right-click, for example:
Enter the appropriate information in this dialog and click OK. The new name replaces the old name. Note: This command is enabled for the If name, IP addr, Def Gtwy, Subnet columns only.
v Alarm Configuration displays the Device Alarm Information view; disv PVC Configuration displays the PVC Information view (WAN probes v VLAN Configuration displays the VLAN Configuration view
only); disabled when multiple interfaces are selected. See Configuring PVCs on page 4-33 for details. (full-duplex Ethernet interfaces designated as Switchlinks only); disabled when multiple interfaces are selected. See Configuring VLANs on page 4-36 for details. probes only); disabled when multiple interfaces are selected. See Configuring WAN Latency on page 4-38 for details. interface; disabled when multiple interfaces are selected. If you right-click on an area of the Agent Interface view that does not contain data, a general context menu appears. abled when multiple interfaces are selected. See Configuring Device Alarm Information on page 4-30 for details.
v WAN Latency displays the WAN Latency Configuration view (WAN
v Data Source Health displays the Data Source Health view for the selected
v Select All selects all interface rows.
4-27
Setting Interface Thresholds You can set new custom thresholds for individual agent interfaces, or for a group of selected interfaces. Note: If you are changing the thresholds for a group of agent interfaces, all of the interfaces must have the same media type. If you have selected multiple interfaces, the Agent Interface Thresholds screen will display the thresholds of the first interface listed. When you right-click an interface on the Agent Interface view and select Thresholds on the context menu, the Agent Interface Thresholds Configuration view opens.
This view displays the current threshold settings for each key metric in the system. Slide the settings bars left or right to adjust the red, yellow, and green thresholds for each key metric.
4-28
If you select Use Global Settings (the default), any changes you make affect all interfaces which have the same media type as the selected interface(s). The global settings are the same thresholds that you set using Setting Global Thresholds on page 4-13 for the media type of a particular data source. If you click Use Custom Settings, any changes you make affect the selected interface(s) only. Note that any interfaces you specify to have custom settings will no longer have global threshold settings. You can always elect to return all to global threshold settings if you chose to do so for any interface. When you click Use Custom Settings, the buttons at the bottom of the screen are enabled.
v Apply applies the changes to the selected interface(s). v Set to Defaults resets the threshold settings to the factory default values for v Reset resets the threshold settings to their most recent values if you have
not yet clicked Apply. the selected interface(s).
4-29
Configuring Device Alarm Information When you right-click the name of an interface on the Agent Interface view and select Alarm Configuration from the context menu, the Device Alarm Information view opens.
You use the Device Alarm Information view to display and modify RMON alarms for an interface or port on an agent. When you right-click on any row in the table, a context menu appears.
v Add New Alarm displays the Add Alarm dialog. See Adding New
Alarms on page 4-31 for details. Note: Alternatively, you can click on the toolbar to add an alarm.
4-30
v View/Modify Alarm displays the View/Modify Alarm dialog. See Viewv Delete Alarm deletes the selected alarm. v Show Agent Log (rising event) displays the Agent Event Log view for the v Show Agent Log (falling event) displays the Agent Event Log view for
the falling event associated with the selected alarm. If there is no falling event configured for the selected alarm, this command is disabled. See Viewing an Agent Event Log on page 4-32 for details. Adding New Alarms When you right-click in the Device Alarm Information view and select Add New Alarm on the context menu, the Add New Alarm dialog opens. Note: Alternatively, you can click on the Device Alarm Informations toolbar to display this dialog. rising event associated with the selected alarm. If there is no rising event configured for the selected alarm, this command is disabled. See Viewing an Agent Event Log on page 4-32 for details. ing/Modifying Alarms on page 4-32 for details.
4-31
v Monitored Variable / Browse allows you to specify the OID string or

MIB variable name of the monitored variable. Click Browse to locate the OID string of the desired statistic from the probe. Note: NetMetrix Performance Center allows MIB variable names for RMON1 and WAN statistics, but no other MIBs are currently supported. For unsupported MIBs, you can explicitly enter an OID string.
v Interval indicates the time interval used to sample the alarm condition in v Sampling indicates whether the event trigger will be an absolute value or a v Thresholds indicates the rising and falling threshold settings. These v Rising/Falling Edge Events allows you to specify rising and falling events
and then to activate (check) or deactivate (uncheck) them. The radio buttons indicate the action the agent is to perform if the event occurs. The text in the Event Description field is the text that appears in the log or event viewer. By default, it describes the event as rising or falling; however, you can modify this text, if desired. Select a trap community from those configured from the selected agent. (The trap is used only if the event is configured to send a trap.) Note that Performance Center will set up the trap community for you. Viewing/Modifying Alarms When you right-click an alarm in the Device Alarm Information view and select View/Modify Alarm on the context menu, the View/Modify Alarm dialog opens and displays the current data associated with the selected alarm. Viewing an Agent Event Log When you right-click an alarm in the Device Alarm Information view and select Show Agent Log (rising event) on the context menu, the Agent Event Log view opens and displays the rising event data. When you right-click an alarm in the Device Alarm Information view and select Show Agent Log (falling event) on the context menu, the Agent Event Log view opens and displays the falling event data. thresholds perform according to the RMON specification. For example, a rising edge event cannot be retriggered until the condition falls below the falling threshold and then rises above the rising threshold. delta value related to the last event of this type. the selected agent.
4-32
You use the Agent Event Log view to view data regarding rising and falling events. No modifications are required or allowed on this view. Configuring PVCs When you right-click the name of an interface on the Agent Interface view and select PVC Configuration from the context menu, the PVC Configuration view opens.
Right-click in the PVC Configuration view to display a context menu.
4-33
v Start/Stop Collection Starts and Stops data collection. This affects the
State. Potential states are:
v Thresholds Displays the Threshold view. v Modify Field Allows you to modify the selected field. The fields that you
can modify are:
w w w
Enabled collector active; able to collect data Disabled collector not active; not able to collect data Collecting collector is actively collecting data
w w
w w w
ifName Near/Far values (names of these fields will vary depending on the type of PVC). If you modify this value, be sure that the value you enter is valid for the probe you are working with. Near Rate must be an integer value Far Rate must be an integer value Encapsulation - select an encapsulation type from the pull-down menu.
v Element Health Displays the Health view for the PVC. v Delete Allows you to delete a selected PVC. v Select All - Selects all PVCs.
Right-click on any open area of the view, and this context menu displays:
v Add displays the Adding a New PVC dialog and allows you to add a PVC. v Select All - selects all PVCs.
Adding a New PVC When you right-click in the PVC Configuration view (in the open grey area and not on any of the listed PVCs) and select Add PVC from the context menu, the Adding a New PVC dialog opens. Note: Alternatively, you can click dialog. on the toolbar to display this
4-34
This is example is for Frame Relay. Other data link protocols have similar but slightly different dialogs.
This is what the dialog will look like if you are adding an AAL5 PVC:
Note: When you add a PVC, either through auto-discovery or manually, the state of the PVC is Enabled, not Collecting. By default, PVCs are not in the state Collecting until you start collection.
4-35
To add a new PVC: 1 Enter the values for the PVC. These will vary depending on the type of PVC you are adding. 2 Select an encapsulation method from the drop-down list. 3 Enter a name for the PVC. 4 Click OK. The new PVC is added to the selected interface. Configuring VLANs When you right-click the name of an interface on the Agent Interface view and select VLAN Configuration from the context menu, the VLAN Configuration view opens.
4-36
You use the VLAN Configuration view to configure VLAN virtual interfaces for probes on switch links. Note: After you add a VLAN, either manually or through auto-discovery, you must use the Agent Interfaces view to change the VLAN management class to Switchlinks before you can perform any further configuration on the VLAN. See Managing Agent Interfaces on page 4-25 for more details. This view lists all VLANs that the selected agent (probe) that are automatically detected or added manually, regardless of whether they are configured for collection or not. Note: The default collection state for a new VLAN is disabled. You must specifically enable collection for any new VLAN. You can change the name of any VLAN listed in the table, if desired, by simply selecting the name and entering a new name. Right-click in the VLAN Configuration view to display a context menu.
v Start/Stop Collection Starts and Stops data collection. Note that the v Thresholds Displays the Threshold view. v Modify Field Allows you to modify the selected field. v Element Health Displays the Health view for the VLAN. v Delete Allows you to delete a selected VLAN. v Select All - Selects all VLANs.
default data collection state is Disabled. You must start the collection for each new VLAN for the data collection to begin.
Right-click on any open area of the view, and this context menu displays:
4-37
v Add displays the Adding a New VLAN dialog and allows you to add a v Select All - selects all VLAN.
Adding a New VLAN When you right-click in the PVC Configuration view and select Add VLAN from the context menu, the Adding a New VLAN dialog opens. Note: Alternatively, you can click dialog. Configuring WAN Latency When you right-click the name of an interface on the Agent Interface view and select WAN Latency Configuration from the context menu, the WAN Latency Configuration view opens. on the toolbar to display this VLAN.
4-38
Use the WAN Latency Configuration view to set up a WAN latency measurement: Note: Note that when a WANProbe is first added to NetMetrix Performance Center, WAN latency measurement is not enabled. The diagram on this view illustrates the WAN link to be measured. The icons indicate the near end and far end devices for the link to be measured for a WAN probe interface (which can be a PVC). To configure WAN Latency: 1 Enter the IP addresses for the WAN link in the Near End IP Address and Far End IP Address fields. Typically, these are the near-end and far-end routers on the WAN link being measured. 2 Click the Enable Latency Measurement check box. You can uncheck this if you wish to stop the latency measurement, but retain the IP addresses you have entered. 3 Click Apply.
WAN Latency Measurement Methodology
In NetMetrix Performance Center, WAN latency measurement uses ICMP echo, and therefore can only be used on circuits that can carry IP traffic It can also only be used on datalink and PVC logical interfaces. The ICMP packet comes from the telemetry port of the probe. Therefore, the telemetry IP address of the selected probe interface appears at the top of WAN Latency Configuration view for your reference.The WAN latency measurement is based on a differential ICMP echo round-trip delay time measurement originating from the probes telemetry port. It measures the delay difference between the near and far-end IP addresses that you specify. The telemetry port of the WAN probe is used for sending ICMP datagrams, since the WAN monitor ports are passive and therefore do not generate traffic. The following requirements must be met for the WAN latency measurement to be possible:
v the logical interface in question must support ICMP (and therefore IP) v there must be a route for ICMP packets coming from the telemetry port of the
WAN probe to get to the near-end, far-end, and back again.
4-39
For an accurate WAN latency measurement, the following considerations apply: 1 The route from the WAN probe telemetry port to the near-end and back needs to be well-behaved, having a delay variation that is small compared to the round-trip delay of the WAN link.
In most cases, but not all, the round-trip delay of the WAN link will be large enough that this will not be a problem unless there are:
w w
multiple router hops between the telemetry port and the near-end and/or over-utilized ports or segments in the path.
4-40
2 The route from the telemetry port to the far-end should contain the route from the telemetry port to the near-end. This should be true for both forward and return traffic. The differential measurement relies on being able to factor out the common part of the path. 3 If near and far-end routers are heavily loaded and handle ICMP traffic at a lower priority than other traffic, accuracy can be degraded. This effect may be confirmed by manually pinging the routers at low and high traffic volumes to see if a significant degradation is taking place.
Choice of near end and far-end IP addresses
Most WAN configurations involve routers at the near and far ends of the link. In these cases, you can use the router IP address for the near and far end IP addresses in the WAN Latency configuration view. Some WANs use bridges rather than routers, which do not have IP addresses associated with their interfaces, unless they provide a management agent. In such cases, you can use an IP address of a near-by device (for example, attached to the same LAN segment) as long as the routes are the same as if the near and far ends used routers. Since LAN delays are usually insignificant compared to WAN delays, this approach will usually not introduce much inaccuracy to the measurement. If the WAN probe telemetry port is very close (at least in terms of delay time) to the near-end, it is even possible for you to use the telemetry ports own IP address as the near-end address. This method may not be as accurate as using a near-end router IP address.
4-41
Configuring WAN latency Measurement on datalink versus PVC logical interfaces
If a WAN consists of a single physical far-end destination, you may decide to configure a WAN latency measurement for the datalink traffic, even if there are multiple PVCs.
On the other hand, if the WAN interface contains PVCs that are routed to physically different far-end destinations, it will not make sense to configure the a WAN latency measurement for the overall datalink traffic.
Instead, each PVC should be configured with its own WAN latency measurement. In this case, each PVC should have a unique far-end IP address, but can use the same near-end IP address.
4-42
Customizing Agent Protocols When you right-click an agent icon in the MLM Agent Management view and select Protocol Customization on the context menu, the Agent Protocol Customization view opens.
The Agent Protocol Customization view displays a list of all configured protocols and the associated port, if applicable, and owner of each. You can add protocols for agents that support user-defined protocols. You can delete user-defined protocols but not those defined by agents. Right-click a protocol to display the protocol context menu. Note that you must have selected UDP or TCP in order to be able to access this context menu.
v Add Protocol displays the Add Protocol view.
4-43
v Delete Protocol deletes the protocol, if it is user-defined or if the agent

supports deletion of agent-defined protocols. In general, you will only be able to delete protocols that have an Owner of User.
Adding Protocols
When you right-click on a TCP, for example, on the Agent Protocol Customization view and select Add Protocol on the context menu, the Add Protocol dialog opens. Note: You cannot add custom protocols to ports for the following probes: QuadEthernet, Cisco 5500, LAN III Ethernet, Agilent Procurve 2400M, or for any switch.
To add a protocol: 1 Enter a name for the protocol. 2 Enter the port number to be used by the protocol. 3 Click OK.
4-44
Administering Agents When you right-click an agent icon in the MLM Agent Management view and select Agent Administration on the context menu, the Agent Administration view opens.
v Warm Start performs a warm boot of the agent. A warm boot retains
much of an agents configuration information. basic configuration information from the agent.
You use the Agent Administration view to restart an agent with a warm or cold start.
v Cold Start performs a cold boot of the agent. A cold boot removes all but
Refer also to probe documentation for complete information regarding warm and cold boots and the exact information retained for each device.
4-45
Agent Auto-Discovery
When you click Agent Import and Discovery on the Global Configuration view, the Agent Auto-Discovery view opens. Use the Agent Auto-Discovery view to set parameters for the auto-discovery process. Auto-discovery automatically detects agents on your network. These RMON agents are the LAN probes, WAN probes, and Switches that will be used for data collection. When an agent is auto-discovered successfully, the agent will be added to the agent icons shown on the Managed Agents view. See Viewing Agents on page 4-19 for information on agent management. Auto-discovery runs in the background, and eventually discovers new devices that are added to network. The discovery engine uses Address Resolution Protocol (ARP) caches to map devices to IP addresses. If the device in question has not recently communicated on the network, its IP address will not appear in an ARP cache, and will not be discovered. Devices that are not eligible for auto-discovery can be added manually added. See Adding Agents on page 4-17 for more details. Note: Using auto-discovery does not preclude manually adding or deleting agents. In order for NetMetrix Performance Center to be able to detect an agent using auto-discovery, you must:
v Install the device and configure it with an IP address v If a community string other than hp_admin or public is used, know this community string for the device and specify it To configure agent auto-discovery: 1 Specify a host IP address in the Seed Address list. Routers are usually the best choice. You must specify at least one seed address. The auto-discovery engine will look in the ARP caches (described above) of the hosts you specify as seed addresses. You may specify more than one seed address to widen the search. 2 If your routers or RMON devices use community strings other than public or hp_admin, specify these in the Community Strings list.
4-46
3 Generally, you may leave the Networks to search list blank. By default, the networks in which the seed addresses reside are the ones searched. You can include additional networks in the search by specifying them in the Networks to search list. Otherwise, leave this list blank. 4 Specify the number of network routing hops you would like to have occur during the search. The number of hops you specify is dependant on the overall size of your network: the more hops you specify, the larger area of your network will be explored for agents to discover. However, the more hops that the application has to take to discover agents implies that the overall discovery will take more time.The default is one hop. 5 Select the Internal radio button at the top of the view. 6 Click Apply. Note: You will have to start data collection for newly-discovered VLANs.
4-47
v Be able to successfully perform a ping test to the device
v Select data on the view and right click to display a context menu:
You can take any of the following actions on this view. Note that changes do not take effect until you click Apply.
w w w
Add add a new community string, seed IP address, or network for auto-discovery Modify change a community string, seed IP address, or network Delete delete a community string, seed IP address, or network
v Internal uses the auto-discovery process in NetMetrix Performance Center

to discover agents. Default auto-discovery behavior.
4-48
v Discovery Disabled stops the agent auto-discovery process.

Note: Once you have stopped auto-discovery, you restart it by clicking the Internal radio button and clicking Apply.
v Max hops allows you to specify the number of hops (levels of network
routing to be explored during the auto-discovery). Default value is 1 hop. Note: Specifying many hops on a large network could make the auto-discovery a time-consuming process.
v Community Strings (optional) specifies a list of community strings to be v Seed Addresses specifies the host used to as a starting point for auto-distried when communicating with the agent. You must specify the community string only if a string other than a default string (hp_admin or public) is used. covery. Note that you must add at least one seed address for the auto-discovery to work. It is recommended (but not required) that you use routers as seed devices. Note that a successful auto-discovery depends on the specified seed device having a correct subnet mask configuration. If the subnet mask is configured incorrectly, the auto-discovery conducted by NetMetrix Performance Center may have unexpected results. works to be searched in addition to the network specified by the Seed IP Addresses. No entry is required unless you need to discover networks for which no seed address is specified. For example, if you have a private network that you will be testing (and which is accessible from your production network) you could specify the seed address for a router in your production network and then add the private network to the Networks to search list. When you have added, changed, or deleted agent auto-discovery parameters, use the buttons on the bottom of the screen:
v Networks to Search (optional) specifies the network address(es) for net-
v Apply applies the changes to the auto-discovery parameters. v Reset returns the parameters to previous settings (if you have not yet
clicked Apply).
v Clear Discovery Table Removes all data from the lists in the view, and
clears the data out of the discovery table in the NetMetrix Performance Center database.
4-49
To limit the search to specific subnets: 1 Specify the Hops to be 0 (zero). 2 Specify a Seed Address that is contained in each subnet you wish to search. For example, if your network address is 10.0.0.0, and you want to search three specific subnets: 10.1.3.0, 10.1.5.0, and 10.1.7.0. Identify a router interface that serves each of the three subnets. In this example, these router interface addresses could be 10.1.3.1, 10.1.5.7, 10.1.7.99. Once you determine these router interface addresses, specify them as the Seed Addresses.
4-50
Exporting Data from the NetMetrix Performance Center Database
Exporting Data from the Database

This chapter describes how to export data from the Agilent NetMetrix Performance Center database to Microsoft Excel. To export data to a spreadsheet: 1 First, access the application database by specifying the ODBC driver. If you wish to use the ODBC driver for reporting purposes, you can obtain this driver by installing the NetMetrix Performance Center Performance Console. 2 Once you have specified the driver, you can retrieve database data into Microsoft Excel. The following sections describe how to perform these tasks. Note: You must have Microsoft Query (which comes with Excel) installed to be able to perform this task. If you chose the Typical installation option during Excels Setup, Query will not be installed. Use the Microsoft Excel Setup program and choose the Custom installation option to install Query.
5-1
Accessing the NetMetrix Performance Center Database

1 Click , and select Control Panel on the Settings menu. .
2 On the Control Panel, double-click
The ODBC Data Source Administrator dialog opens and displays the User DSN tab.
3 Click Add. The Create New Data Source dialog opens. 4 Select SOLID ODBC Driver 3.0. This driver is installed when you install the NetMetrix Performance Center Performance Console. 5 Click Finish. The SOLID Server ODBC Setup dialog opens. 6 Enter the Data Source Name, which is a friendly name that represents the database. This name is for your convenience.
5-2
7 Enter an optional description. This information does not appear anywhere but in this dialog. Use a description that will help you remember what retrieval this data source was for. 8 Enter the Network Name. This name is made up of three parts: tcp database_server port
tcp
database_ server
TCP identifier (always use TCP) Name of the machine where the NetMetrix Performance Center Server has been installed. This will be the location of the database. Port identifier. This value (and the database server value) resides in the file c:\Program Files\NetMetrix Performance Center\solid\solid.ini under the [Com] category. For example,
port
[Com] Listen=Solid, tcp localhost 1326

The network name for server; the protocol and name that SOLID Server uses when starting to listen to the network.
9 Click OK. NetMetrix Performance Center returns you to the ODBC Data Source Administrator dialog, which displays your newly created Data Source. 10Click OK to exit.
Retrieving Database Data into Excel

To retrieve data from your SOLID database into Excel: 1 Start Microsoft Excel. 2 From the Data menu, select Get External Data, and then select Create New Query (or New Database Query) from the cascading menu. The Choose Data Source dialog opens. 3 Double-click New Data Source. The Create New Data Source dialog opens.
5-3
4 In Field 1, enter the data source name. Choose a name that reminds you of the type of data you extract for this query. You might want to use the name you chose earlier for you database. 5 On the drop-down list in Field 2, select SOLID Server 3.0. 6 For Field 3, click .
The SOLID Server Login dialog opens.
Server name:
This is the same as the Data Source Name you entered in step 6 of Accessing the NetMetrix Performance Center Database on page 5-2. In this example, the name is database. Enter your provided username: partner (use this
Username: Password:
username)
Enter your provided password: dataexport (use this
username)
7 Click OK.
5-4
8 Select a database schema table from the drop-down list: Domain Lists attributes of a domain. Agent Lists the attributes of an agent. Port Lists port identifiers. Interface Lists each interface to an agent. Data Source Lists interfaces that are measuring network traffic. StatMIB MIB statistics. Collection Measurable metrics collected from a data source over a period. Interval Discrete interval that contains one or more distinct measurable data. StatValue Statistical data from data sources; an entry for each variable read from the data source. Protocol Distribution Maps the protocols SDConversions Tracks source to destination conversions. See Database Schema on page 5-7 for a full description of the database schema tables. 9 Select the Data Source Name and click OK. The Solid Server Dialog screen re-displays. 10Click OK. Field 4 is enabled. 11 Click OK. The new data source is listed in the Choose Data Source dialog:
5-5
12Double-click on the data source (in this example database). The Query Wizard - Choose Columns dialog opens.
13Select the desired columns, and then click
The selected columns appear on the Columns in your query list. 14Click to display the next screen.
There are screens that allow you to filter and sort the information. 15When you finish making selections on these screens, close the Query screen and the Returning External Data to Microsoft Excel dialog displays.
16Click OK. The data from the database columns appears on the worksheet. Now you can use the spreadsheet programs functionality to manipulate the data as you wish.
5-6
Database Schema
The following are the database schema tables for NetMetrix Performance Center. This figure shows the hierarchy of data in the database:
Domain
A domain is a single security boundary of a network monitoring. In the world of TCP/IP, it is usually a subnet or an area of IP addressing. A domain group is made up of one or more domains. The enterprise network is made up of one or more domains and or Domain Groups. A domain is designated as a master within a domain group. The master domain is the aggregation point for network data for all its children. All children domains in a domain group propagate the respective domain health information and the events to the domain master. This allows an administrator to get the overall health status of a domain group by connecting to the master domain.
5-7
Database Schema
Internally, a domain represents a Solid database server. When an application is connected to a domain, it is connected to the database server and retrieves the stored information from that server. Domain Table
Table 5-1Domain Table Attribute domain_id Data type CHAR(76) Description Domain identifier. This unique value identifies an entry in the table. Domain name. This field is mandatory. Host address of the domain. This is the host where the database server is running. The connect string to connect to this domain from a JDBC program. The connect string to connect to this domain from a ODBC program. Creation timestamp. Readable domain information. Domain status. Valid values are: CollectingData = 1 Initialization = 2 Shutdown = 3 Install = 4 Unknown = 5 owner VARCHAR(128) Domain Owner.
name
VARCHAR
ip_address
VARCHAR(32)
jdbc_connect_string
VARCHAR
odbc_connect_string
VARCHAR
cts description
TIMESTAMP LONG VARCHAR
status
INTEGER
5-8
Table 5-1Domain Table (continued) Attribute master Data type INTEGER Description If set, indicates master domain entry. If set, indicates local domain. If set, indicates domain out of reach. Normalized value (between 0.0 and 3.0). This field is updated every history interval (i.e., 30 minutes) and represents the overall domain health. This value is the worst normalized metric value in the latest interval.
local
INTEGER
down
INTEGER
nvalue
FLOAT
Agent
An agent object represents a managed element. Examples of agents are probes and switches. An agent object consists of one or more ports that can be attached to a subnetwork to monitor the network traffic. Each port is uniquely identified by an port index. A port in turn consists of one or more logical interfaces. In most cases, there is a one to one correspondence between a port and an interface, but a WAN port may contain multiple logical interfaces such as signaling, datalink, and PVC interfaces. A Data Source is a source of data identified by an interface index (ifIndex) on a device. It represents a set of data collected from a source in the network. For example, an embedded RMON agent in a switch is a source of data. A set of selected ports redirected to a monitor port is a source of data. A trunk between switches (for example, ISL link) and routers monitored by a probe are a source
5-9
Database Schema
of data. From users point of view, the Data Source can be (traffic data collected from) a network switch, a combination of slot number and port number, or a VC identifier for PVCs. Not all interfaces are datasource objects. An agent may have interfaces that are not used for data collection. Examples are serial interfaces or a LAN interface on a WAN probe. Agent Table
Table 5-2Agent Table Attribute domain_id agent_id Data Type CHAR(76) CHAR(76) Description The domain the agent belongs to. Agent identifier. The Agent identifier is unique within a domain. This is the index to the table. Friendly name. IP address for the telemetry port. Agent management class. Valid values are: LAN = 1 SWITCH = 2 WAN = 4 The above values are defined in the MgmtClass table. port message_size sys_contact sys_descriptior sys_location sys_name INTEGER INTEGER Port number.
name ip_address mgmt_class
VARCHAR VARCHAR INTEGER
5-10
Table 5-2Agent Table (continued) Attribute sys_object_id sys_services community firmware cts state VARCHAR VARCHAR VARCHAR INTEGER Read/write community string. Firmware version. Creation timestamp. Agent state. Valid values are: Discovery = 1 Error = 2 CollectingData = 3 Stopped = 4 Deleted = 5 Admin = 6 The above values are defined in the AgentState table. Data Type Description
Port Table
Table 5-3Port Table Attribute port_id Data type CHAR(76) Description Port identifier. The Port identifier is unique within a domain. This is the primary key to this table. The Agent that the port belongs to. The port index. This is the same as interface index. Friendly name. IP address for the telemetry port.
agent_id If_index
CHAR(76) INTEGER
name ip_address
VARCHAR VARCHAR
5-11
Database Schema
Table 5-3Port Table (continued) Attribute mgmt_class Data type INTEGER Description Agent management class. Valid values are: LAN = 1 SWITCH = 2 WAN = 4 The above values are defined in the MgmtClass table. If_caps INTEGER Port capabilities. Valid values are: MONITOR_ONLY = 1 TELEMETRY = 2 MONITOR_TRANSMIT = 3 if_speed INTEGER Media speed.
Interface Table This table contains an entry for all the interfaces in a port.
Table 5-4Interface Table Attribute interface_id Data type INTEGER Description Interface identifier. The Interface identifier is unique within a domain. This is the primary key to this table. The port it belongs to. IP address. Interface index. Interface description. Interface MAC address. Interface type as defined in RFC1213 and RFC1573.
port_id device_ip if_index if_description if_mac if_type
CHAR(76) VARCHAR(32) INTEGER VARCHAR VARCHAR(32) INTEGER
5-12
Table 5-4Interface Table (continued) Attribute if_mtu Data type INTEGER Description The size of the largest datagram which can be sent/received on the interface. Media speed. Friendly name. Further differentiates the interface, e.g., full duplex, fast ethernet, etc. The complete list of all possible combination of if_type and if_sub_type is provided in the if_type table. Not used. Not used. Switch slot number. Used only if this is a switch port entry. Switch port number. Used only if this is a switch port entry. Default gateway. Subnet mask. Identifies PVC entry.
if_speed name if_sub_type
INTEGER VARCHAR INTEGER
espan_address espan_if_index slot_number
VARCHAR(32) INTEGER INTEGER
port_number
INTEGER
def_geteway subnet_mask id pvc_near_id pvc_far_id pvc_cir pvc_reverse_cir encapsulation ds_oid
VARCHAR(32) VARCHAR(32) INTEGER INTEGER INTEGER INTEGER INTEGER INTEGER VARCHAR
The datasource OID to be used in the rmon control table.
5-13
Database Schema
Table 5-4Interface Table (continued) Attribute user_defined Data type TINYINT Description If set, this is a user-defined interface. This is true in cases of PVC added by an user. Only user-defined interfaces can be deleted by the user. Interface state. Valid values are: UNDEFINED = 0 VALID = 1 DELETED = 2 cts parent_if_id TIMESTAMP CHAR(76) Creation time stamp. Parent interface identifier. This field will be mostly null except in cases of PVCs where it will set to the corresponding datalink interface.
state
INTEGER
Data Source Table This table has an entry for only those interfaces that are measuring network traffic data.
Table 5-5Data Source Table Attribute datasource_id Data type CHAR(76) Description Datasource identifier. The Datasource identifier is unique within a domain. This is the primary key to this table. Datasource description. Datasource type. This is mainly used for GUI purposes. This is for internal use. Media type. The media type is used to apply the appropriate threshold settings on the metrics. This is for internal use.
description ds_type
VARCHAR INTEGER
media_type
VARCHAR(32)
5-14
Table 5-5Data Source Table (continued) Attribute counter_type Data type INTEGER Description Counter type. This is used by the data collectors to identify the appropriate mib variables for supported statistics. This is for internal use. If set, indicates that the datasource supports RMON2 mib. The current state of the datasource. Valid values are: UNDEFINED = 0 ENABLED = 1 DISABLED = 2 COLLECTING = 3 DELETED = 4 collection_id INTEGER The next collection id to be used for this datasource. This is used by the data collector to create a Collection entry. The interface represented by the datasource. Creation time stamp.
rmon2
TINYINT
state
INTEGER
interface_id
INTEGER
cts
TIMESTAMP
Statistics Variables
In order to implement an extensible schema that can support collection of statistics data from any probe a new table was added instead of extending columns to the StatValue table. This allows the software to easily support statistics collection from new probes without additional programming. What is required is to make appropriate entries in the StatMib table. The primary key is the counter type that is associated with all data sources. The counter type variable identifies the set of MIB variables that should be used by the data collectors to collect metric data.
5-15
Database Schema
StatMib Table
Table 5-6StatMib Table Attribute counter_type Data type TINYINT Description Counter type. Possible values were enumerated in the Datasource table above. MIB variable as it appears on the mib file. Unique identifier used internally to associate a value measured with the metric. Text label to be used for display purposes. If set, indicates important stat, in which case the normalized value has to be calculated. If set, indicates the stat is derived from other stats, e.g., Error. Stat direction. Valid values are: NONE = 0 IN = 1 OUT = 2 The above values are defined in the StatDirection table. datatype TINYINT Stat data type. This is used by the data collector to use the appropriate variable to extract the metric from the mib variable. Valid values are: Integer = 1 Counter32 = 2 counter64 = 3 timeticks = 4 The above values are defined in the StatDataType table. oid VARCHAR Object identifier for this variable.
mib_var stat_id
CHAR(64) INTEGER
label key_stat
VARCHAR TINYINT
derived
TINYINT
direction
TINYINT
5-16
Collection
Collection is a set of measurable metrics collected from a data source over a period. A collection provides intervals. One of the important attributes of the collection table is the collection interval length. There will be a separate entry for collections of different interval. However, there will be only one entry for a collection of a specific interval. If a collection was stopped and later started, the existing collection id will be used rather than creating a new one. This will result in holes in the collections where the network data will be missing for the stopped duration. Collection Table
Table 5-7Collection Table Attribute datasource_id Data type CHAR(76) Description Datasource identifier. The combination of datasource_id and interval_length forms the primary key to this table. Unique collection id for this datasource and a specific interval. Collection start time. Collection end time. Null, if it is still active. Interval length in seconds. Total intervals in this collection so far. Number of clients currently using this entry. Reason why the collection was stopped. A value of 0 indicates active collection.
collection_id
INTEGER
start_time end_time interval_length interval_total user_count reason_end
TIMESTAMP TIMESTAMP INTEGER INTEGER INTEGER INTEGER
5-17
Database Schema
Interval
An Interval represents a discrete interval that contains one or more distinct measurable data that were collected for that interval. By default, an interval spans 30 minutes. A starting and an ending timestamps mark the interval boundary. This Interval contains multiple rows of data. Each data row identifies a monitored interface and contains the metrics collected during that interval. Interval Table
Table 5-8Interval Table Attribute datasource_id Data type CHAR(76) Description Datasource identifier. The combination of datasource _id and collection_id forms the primary key to this table. Unique collection id for this datasource and a specific interval. Unique interval id over all collection. This field is used as a key to all the metrics table. Interval start time. Interval end time. Zoom tables updated in this interval. A value of -1 indicates a collection error. If set, the interval data has been processed.
collection_id
INTEGER
interval_id
INTEGER
start_time end_time zoom_types
TIMESTAMP TIMESTAMP INTEGER
normalized
INTEGER
Counters
This first type of zoom table maintains media-level statistics over a defined period with a defined granularity. Media-level statistics depend on the type of media of the specified network interface.
5-18
Media-level statistics will be primarily supplied from the RMON Statistics group, in particular the etherStatsTable. For WAN probes, the relevant statistics are supplied from a private Agilent mib. There will be an entry made at every interval for each of the active data sources. The counters to be collected are identified by the entries in the StatMIB table. This provides a flexible scheme to extend the supported metrics. StatValue Table This table contains the stat data entry from the datasources. An entry is made for each variable read from the datasource. The statistics are entered every interval and is identified by the interval id.
Table 5-9StatValue Table Attribute interval_id stat_id value nvalue pofc red yellow red_actual yellow_actual Data type INTEGER INTEGER DOUBLE FLOAT FLOAT FLOAT FLOAT FLOAT FLOAT Description Unique interval id. Identifies the Stat being referenced. Actual value read from the mib variable. Normalized value between 0 and 3. Percent of capacity. Red threshold value in percentage. Yellow threshold value in percentage. Red threshold value in octets. Yellow threshold value in octets.
5-19
Database Schema
Protocol Distribution
This table maintains a distribution of statistics over a set of protocols. These statistics are provided by any data source which supports the Protocol Directory and Protocol Distribution groups of RMON-2, in particular the protocolDirTable, protocolDistControlTable and protocolDistStatsTable. Protocol Distribution Table
Table 5-10Protocol Distribution Table Attribute interval_id protocol_id protocol_name packets octets Data type INTEGER VARCHAR VARCHAR DOUBLE DOUBLE Description Unique interval id. Protocol id as defined in the RFC. Protocol name. Total packet count for the interval. Total octet count for the interval.
Application and MAC Host

These tables maintain a distribution of statistics over a set of application-level and MAC-level host addresses. Application-level statistics are provided by any data source which supports the Protocol Directory, Network Layer Host and Application Layer Host groups of RMON-2, in particular the protocolDirTable, alHostControlTable, and alHostTable. MAC level statistics are provided by data source that supports only the RMON-1 Host group, in particular the hostControlTable and hostTable. For this release, the metrics will be collected only from the NlHost table. The AlHost data can be derived from the entries in the Application conversation entries.
5-20
NlHost Table
Table 5-11NlHost Attribute interval_id host_ip protocol_id_nl protocol_name_nl protocol_id_al protocol_name_al in_packets Data type INTEGER VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR DOUBLE Description Unique interval id. Host being tracked. Network layer protocol id. Network layer protocol name. Application layer protocol id. Application layer protocol name. Total count of incoming packets for the interval. Total count of outgoing packets for the interval. Total count of incoming octets for the interval. Total count of outgoing octets for the interval. Total count of non unicast packets.
out_packets
DOUBLE
in_octets
DOUBLE
out_octets
DOUBLE
non_unicast
DOUBLE
Application and MAC Conversation

This zoom table maintains a distribution of statistics over a set of application-level conversations and MAC-level matrix. Application-level statistics are provided by any data source which supports the Protocol Directory, Network Layer Matrix and Application Layer Matrix groups of RMON-2, in particular the protocolDirTable, hlMatrixControlTable, nlMatrixSDTable, nlMatrixD-
5-21
Database Schema
STable, alMatrixSDTable and alMatrixDSTable. MAC-level statistics are provided by data source which only supports RMON-1 matrix group, in particular the matrixControlTable, matrixSDTable, and matrixDSTable. For this release, the metrics will be collected only from the AlMatrix table. The NlMatrix data can be derived from the entries in the AlMatrix table. The AlMatrix table is divided into two portions, one for each direction. We will be collecting only from the SDConversations table. SDConversations Table This table tracks the Source to Destination conversations.
Table 5-12SDConversations Table Attribute interval_id host1_ip host2_ip protocol_id_nl protocol_name_nl protocol_id_al protocol_name_al packets octets Data type INTEGER VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR DOUBLE DOUBLE Description Unique interval id for this collection. One end of the conversation. The other end of the conversation. Network layer protocol id. Network layer protocol name. Application layer protocol id. Application layer protocol name. Total packet count for the interval. Total octet count for the interval.
5-22
Glossary
A
Agent The SNMP agent of an RMON/RMON2 device on the network. In this document, the term agent refers to the measurement device. An agent might include multiple data sources. For example, a quad probe is an agent with four data sources (interfaces). Aggregation A technique by which Agilent NetMetrix Performance Center derives a summary (higher-level) status for the network conditions from a set of lower-level statuses. In general, when a set of statuses are aggregated, the worst-level status is propagated to the higher levels. For example, when the redyellow-green (RYG) status of multiple segments is aggregated into a single RYG block on an At-a-Glance view, the top view color turns red if any individual segment status turns red. At-a-Glance Graphs A summary view of network status over 24 hours. These graphs contain a threshold-based, color-coded block for each data point representing a 30-minute status.
D
Data Source An individual point of measurement under an agent. For example, each interface on a probe is a data source. Similarly, each port on a switch is a data source. Delta The incremental gain or increase in a variable. Domain The management scope of a single Agilent NetMetrix Performance Center Server. The domain contains all of the network elements managed by the Server.
Glossary-1
E
Exception Network conditions that may be responsible for serious network performance degradation at a particular time. Agilent NetMetrix Performance Center isolates these conditions from other events for exception-driven troubleshooting.
H
Historical Views Views that present network performance data over 24 hours with data collected at 30-minute intervals. The historical data is stored in the repository, so past data can be scrolled back in time.
K
Key Metrics Metrics that represent measurements of certain aspects of network activity for the various network elements. Examples of key metrics are Utilization, Errors, Packets, Octets, Unavailability. The key metrics displayed can vary depending on the network element you are working with.
N
Network Element This term indicates the type of network component being measured or managed. For example, a LAN segment is a network element when monitored by a probe. Examples of other network elements are WANs, and switches. A network element may contain multiple data sources managed through a single agent.
P
Probe A media-specific hardware device that monitor the traffic on the network media. These devices can analyze the packets and collect RMON/ RMON2 statistics. PVC Permanent Virtual Circuit. PVCs provide a way to subdivide bandwidth on a WAN interface. Each PVC can have its own quality of service, run its own protocol, have its own far end destination in the WAN cloud, and so on.
R
Real-Time View Views that present network performance data based on intervals other than the default 30-minute historical collection interval. By default, a 30-second interval study is provided in each managed RMON device,
Glossary-2
Glossary
and you can configure additional studies. Real-time views have some limitations compared to historical views in that the data is not stored in the Server database, the data is not measured against a threshold, and the graph does not support zoom navigation and cannot be scrolled back in time. RMON/RMON2 The standard remote network monitoring MIBs for SNMPbased monitoring and control of network devices. RMON is the original standard and the RMON2 is a relatively recent addition to the original RMON standard.
S
Segment A section of the network media shared by a number of hosts. The network is separated into segments using switches and routers. Server The repository and computation engine of the product. The Server sits between the user interface and the data sources making measurements. The Server contains a database which forms the middle tier of the three-tier architecture. SNMP Simple Network Management Protocol. A standard method for managing and monitoring network devices and more (servers, applications, and so on). Switch A multi-port, layer 2 or layer 3 network devices used to partition the network into segments and to isolate traffic into domains.
T
Thresholds Values that specify the normal, warning, and critical ranges for key traffic metrics on different network elements. Default thresholds for key metrics, which you can change, are provided for each media type.
Z
Zoom Navigation A technique by which Agilent NetMetrix Performance Center allows the user to navigate across context selections. You can refine the data being viewed by refining the context selection.
Glossary-3
Glossary-4
Index
A
access control, Global Policy Configuration view 4-9 accessing, NetMetrix Performance Center database 5-2 adding agents 4-17 alarms 4-31 protocols 4-44 PVCs 4-34 PVCs to WANs 4-4 time intervals 2-37 VLANs 4-38 adding VLANs 4-4 addresses, telemetry 4-17 adjusting thresholds 4-4 administrating agents 4-45 Agent Administration view 4-45 Agent Event Log view 4-32 Agent Interface view 4-25 Agent Properties view 4-21 Agent Protocol Customization view 4-43 agents 1-9, Glossary-1 adding 4-17 adding protocols 4-44 administrating 4-45 auto-discovering 4-2, 4-46 configuration 4-22 customizing protocols 4-43 deleting 4-20 firmware revision 4-22 naming 4-3 option menus 4-20, 4-21 selecting interface thresholds 4-28 selecting types 4-19 settings 4-21 SNMP values 4-23 specifications 4-17 starting/stopping data collection 4-20 states 4-22 updating firmware 4-24 viewing 4-19 viewing interfaces 4-25 warm or cold starts 4-45 aggregation 1-6, 2-10, Glossary-1 alarms adding 4-31 configuring information 4-30 setting options 4-32 viewing/modifying 4-32 application protocols supported 1-4 application server 1-9 Apply button 4-5 architecture, NetMetrix Performance Center 1-8 At-a-Glance charts 2-12 auto-discovering agents 4-2, 4-46
B
broadcast storms 3-6 buttons, apply, reset, set to default 4-5
C
capturing events 1-7 changing time and date 2-35 coding, color 1-6 cold starts, agents 4-45 collecting data, intervals 1-6 colors aggregate status 2-10 coding 1-6 hot spots 2-11 configuration views context menus 4-5 double-clicking 4-5 home page 4-7 navigating 4-5 configuring agents 4-22 device alarm information 4-30 interfaces 4-26 NetMetrix Performance Center 4-1
Index-1
Index
options 4-2 PVCs 4-33 WAN latency 4-38 content area 2-6 context menus 4-5 Current Health view 2-11 customizing agent protocols 4-43 protocols 4-4
D
data collection intervals 1-6 collectors 1-9 color indications 2-10 display area 2-6 displaying summaries 2-12 exporting to Excel 5-1 historical, selecting time/date 2-35 retrieving into Excel 5-3 selecting for storage 4-3 source, filtering events by 2-45 sources 1-9, Glossary-1 starting/stopping collection 4-20 storage policies 4-11 types contained in graphs 1-4 viewing from web browsers 4-9 Data Source Health view 2-13 database accessing 5-2 exporting data 5-1 schema 5-7 server 1-9 SOLID 5-3 dates changing 2-35 selecting for historical data 2-35 defaults access control 4-9 data storage policies 4-12 event listings 2-42 history interval 2-38 PVC states 4-35 security model 4-2 time interval 2-37 deleting agents 4-20 delta, definition Glossary-1 Detailed Statistics view 2-22 Device Alarm Information view 4-30 devices
configuring alarm information 4-30 naming 4-3 display preferences (showing hosts by host name or network address) 2-33 displaying At-a-Glance charts 2-12 Data Health Source views 2-14 Detailed Statistics view 2-22 Domain Health Summary view 2-9 Errors/Congestion view 2-21 network address 2-34 Top Hosts by Data Source view 2-17 Top Protocol views 2-18 Top Protocols by Host view 2-28 Top Talkers and Listeners 2-30, 2-32 Utilization by Data Source view 2-23 Zoom Analysis view 2-26 displaying hostname 2-33 Domain Health Summary view 2-7 domains definition Glossary-1 description 1-2 Server role 1-2 double-clicking, configuration views 4-5
E
Errors/Congestion view 2-20 event viewer Event Viewer dialog 2-40 features 2-39 information categories 2-40 sorting information 2-40 events capturing 1-7 data source, filtering by 2-45 filtering 2-42 to 2-46 managing in NetMetrix Performance Center 2-39 severity and type, filtering by 2-43 time range, filtering by 2-44 Excel exporting data to 5-1 retrieving data from SOLID database 5-3 exceptions, definition Glossary-2 exporting data 5-1
F
file manager, see navigation tree filtering by date source 2-45
Index-2
Index
by severity and type 2-43 by time range 2-44 events 2-42 to 2-46 firmware, updating for agents 4-24 folders, working with 2-4
specifying access 4-2 telemetry port 4-17
K
key metrics 2-11, Glossary-2
G
getting started 2-2 Global Configuration view 4-7, 4-46 Global Policy Configuration access control 4-9 view 4-8 global thresholds, setting 4-13 graphs At-a-Glance, definition Glossary-1 hierarchy 1-5 radar 2-11 source 1-2 types contained in views 1-4 types of data contained in 1-4
L
LANs, broadcast storm 3-6 latency, WANs 3-10, 4-38 log settings 4-16
M
main panel, NetMetrix Performance Center 2-2 managing events 2-39 menus agent options 4-20, 4-21 agent protocols 4-43 context 4-5 PVC configuration 4-33 VLAN configuration 4-37 MLM Properties view 4-15 modifying alarms 4-32 monitoring your network 3-1 Most Active Data Source view 2-31
H
hierarchy graphs 1-5 views 1-5 historical data collection 1-6 selecting time/date 2-35 hops 4-49 hostname displaying 2-33 hot spots 2-11
N
names agents and devices 4-3 navigating configuration views 4-5 navigation tree 2-3 resizing 2-4 NetMetrix Performance Center accessing database 5-2 architecture 1-8 configuration 4-1 integrating with Network Node Manager 1-9 main panel 2-2 navigation tree 2-3 overview 1-1 restricting access 4-2 network configuring from web browsers 4-9 domains, see domains monitoring 3-1 protocols, supported 1-4 tracking activity 2-9 network address
I
ICMP echo 4-39 In+Out Traffic view 2-15 interfaces agent 4-25 modifying configuration 4-26 selecting thresholds 4-28 user 1-8 Interval Selection dialog 2-37 intervals adding 2-37 selecting 2-36 time 1-6 IP addresses changing settings 4-10 seed 4-49
Index-3
Index
displaying 2-34 network elements definition Glossary-2 displaying data 2-12 Network Node Manager, integrating 1-9
P
permissions, IP address access 4-10 port utilization 2-23 probes definition Glossary-2 restarting 4-4 properties, setting agent 4-21 protocols adding 4-44 agent 4-43 application 1-4 customizing 4-4 network 1-4 PVC Configuration view 4-33 PVCs adding 4-34 adding to WANs 4-4 configuring 4-33 default states 4-35 definition Glossary-2 states 4-34 utilization 2-23, 3-11 WAN probe interfaces 4-39
Q
quad probes, definition Glossary-1
R
radar graphs 2-11 realtime monitoring 1-6 real-time views, definition Glossary-2 repository, definition Glossary-2 Reset button 4-5 resizing navigation tree 2-4 restarting probes 4-4 restricting access to NetMetrix Perfomance Center 4-2 RMON alarm modification 4-30 definition Glossary-3
S
scenarios, network problems 3-1
security models, selecting 4-2 segments, definition Glossary-3 Select Time and Date dialog 2-35 selecting a security model 4-2 agent types 4-19 thresholds for interfaces 4-28 time intervals 2-36 Server adding agents 4-17 components 1-9 current state 4-16 definition Glossary-3 events 2-39 functions 1-2 log settings 4-16 software version 4-16 Set to Defaults button 4-5 setting agent properties 4-21 data storage policies 4-11 global thresholds 4-13 time intervals 2-35 settings IP address access 4-10 log 4-16 SNMP 4-17 shortcut buttons 2-5 showing hosts by host name or network address 2-33 SNMP definition Glossary-3 setting values, agents 4-23 settings 4-17 software version, determining 4-16 sorting information in event viewer 2-40 sources, data 1-9, Glossary-1 starting data collection 4-20 state, Server 4-16 status bar 2-6 stopping data collection 4-20 storage policies, data 4-11 storing data 4-3 storms, broadcast 3-6 support, web browser 1-9 switch ports, high utilization 3-13 switches definition Glossary-3 port utilization 2-23 switchlinks high utilization on a VLAN 3-15
Index-4
Index
WANs PVC utilization 2-23
T
telemetry addresses 4-17 thresholds adjusting 4-4 alarms 4-32 definition Glossary-3 global, setting 4-13 selecting for interfaces 4-28 time adding intervals 2-37 changing 2-35 filtering events by 2-44 importance in NetMetrix Performance Center 1-6 selecting for historical data 2-35 selecting intervals 2-36 tools for setting intervals 2-35 toolbar buttons 4-7 main 2-5 Top Hosts by Data Source view 2-16 Top Protocol view 2-18 Top Protocols by Host view 2-27 Top Talkers and Listeners view 2-29 Traffic Direction Selection Control 2-14 troubleshooting network 2-9 network problem scenarios 3-1
Current Health 2-11 Data Source Health 2-13 Detailed Statistics 2-22 Device Alarm Information 4-30 direction of traffic 2-14 Domain Health Summary 2-7 Errors/Congestion 2-20 example 1-3 Global Configuration 4-7, 4-46 Global Policy Configuration 4-8 hierarchy 1-5 historical, definition Glossary-2 In+Out Traffic 2-15 initial 2-7 MLM Properties 4-15 Most Active Data Source 2-31 PVC Configuration 4-33 real-time, definition Glossary-2 Top Hosts by Data Source 2-16 Top Protocol 2-18 Top Protocols by Host 2-27 Top Talkers and Listeners 2-29 types of graphs 1-4 Utilization by Data Source 2-23 WAN Latency Configuration 4-38 Zoom Analysis 2-25 VLANs adding 4-38 adding and configuring 4-4 high utilization 3-15
U
updating agent firmware 4-24 user interface 1-8 Utilization by Data Source view 2-23
W
WAN Latency Configuration view 4-38 WANs adding PVCs 4-4 alarms 4-30 configuring latency 4-38 high latency 3-10 high PVC utilization 3-11 high utilization 3-2 warm starts, agents 4-45 web browsers configuring network from 4-9 permitting data viewing from 4-9 support 1-9 web server 1-9
V
viewing agent event logs 4-32 agent interfaces 4-25 agents 4-19 alarms 4-32 views 1-3 to 1-5, 2-7 Agent Administration 4-45 Agent Event Log 4-32 Agent Interface 4-25 Agent Properties 4-21 Agent Protocol Customization 4-43 configuration, navigating 4-5
Z
Zoom Analysis view 2-25
Index-5
Index
zoom navigation Glossary-3
Index-6
Copyright Agilent Technologies 1999-2000 All Rights Reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws.
Software License Agreement

ATTENTION: USE OF THE SOFTWARE IS SUBJECT TO THE AGILENT SOFTWARE LICENSE TERMS SET FORTH BELOW. USING THE SOFTWARE INDICATES YOUR ACCEPTANCE OF THESE LICENSE TERMS. IF YOU DO NOT ACCEPT THESE LICENSE TERMS, YOU MUST RETURN THE SOFTWARE FOR A FULL REFUND. IF THE SOFTWARE IS SUPPLIED WITH ANOTHER PRODUCT, YOU MAY RETURN THE ENTIRE UNUSED PRODUCT FOR A FULL REFUND.
Manual Part No. 5969-4269 Second edition, March 2000

Printed in USA Supersedes 5967-9476
Agilent Software License Terms The following License Terms govern your use of the accompanying Software unless you have a separate written agreement with Agilent . Definitions and License Grant. Use means storing, loading, installing, executing or displaying the Software. For products other than those designated as Agent products, Agilent grants to you a license to Use the software set forth in your Entitlement Certificate for concurrent use on one processor. For Agent products, for each copy licensed you may Use the software on only a single processor. You may not modify the Software or disable any licensing or control features of the Software. Ownership. The Software is owned and copyrighted by Agilent or its third party suppliers. Your license confers no title or ownership in the Software and is not a sale of any rights in the Software. Agilent s third party suppliers may protect their rights in the event of any violation of these License Terms. Copies and Adaptations. You may only make copies or adaptations of the Software for archival purposes or when copying or adaptation is an essential step in the authorized Use of the Software. You must reproduce all copyright notices in the original Software on all copies or adaptations. You may not copy the Software onto any bulletin board or similar system. No Disassembly or Decryption. You may not disassemble, decompile or decrypt the Software unless Agilent s prior written consent is obtained. In some jurisdictions, Agilent s consent may not be required for disassembly or decompilation. Upon request, you will provide Agilent with reasonably detailed information regarding any disassembly or decompilation. Transfer. Your license will automatically terminate upon any transfer of the Software. Upon transfer, you must deliver the Software, including any copies and related documentation, to the transferee. The transferee must accept these License Terms as a condition to the transfer. Termination. Agilent may terminate your license upon notice for failure to comply with any of these License Terms. Upon termination, you must immediately destroy the Software, together with all copies, adaptations and merged portions in any form. Export Requirements. You may not export or re-export the Software or any copy or adaptation in violation of any applicable laws or regulations. U.S. Government Restricted Rights. The Software and documentation have been developed entirely at private expense and are provided as Commercial Computer Software or restricted computer software. Use, duplication or disclosure by the U.S. Government or a U.S. Government subcontractor is subject to the restrictions set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clauses in DFARS 252.227-7013 or as set forth in subparagraph (c) (1) and (2) of the Commercial Computer Software Restricted Rights clauses at FAR 52.22719, as applicable. The Contractor is Agilent Technologies, 395 Page Mill Road, Palo Alto, California 94306.
Warranty The information contained in this document is subject to change without notice. Agilent makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties or merchantability and fitness for a particular purpose. Agilent shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. NetMetrix Division Agilent Technologies 5301 Stevens Creek Blvd Santa Clara, CA 95051 http://www.agilent.com/comms/netmetrix
Sales/Support Contacts USA: (888) 699-7280 Outside the USA: Visit http://www.agilent.com/go/support to find contact information for your area. Trademark Acknowledgments. Microsoft is a U.S. registered trademark of Microsoft Corp. Netscape and Netscape Navigator are U.S. trademarks of Netscape Communications Corporation.

Agilent NetMetrix PC

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Agilent NetMetrix PC

Încărcat de

Drepturi de autor:

Formate disponibile

Agilent NetMetrix Performance Center

Introduction to NetMetrix Performance Center

Introduction to NetMetrix Performance Center

Introduction to NetMetrix Performance Center

NetMetrix Performance Center Users Guide

Introduction to NetMetrix Performance Center

What are the Views?

Introduction to NetMetrix Performance Center

Data Sources for the Graphs

v Application protocols - Supported application protocols include: HTTP,

v Network protocols - Supported network protocols include: IP, IPX, DEC-

LAN WAN Switch Switchlink

Yes Yes Yes Yes

Yes Yes No Yes

NetMetrix Performance Center Users Guide

Introduction to NetMetrix Performance Center

The Hierarchy of Views

Wider visibility; less detail

Narrower visibility; more detail

Introduction to NetMetrix Performance Center

The Function of Time

Note the time intervals in the bottom axis.

Color Coding and Aggregation

Introduction to NetMetrix Performance Center

Introduction to NetMetrix Performance Center

NetMetrix Performance Center Architecture

NetMetrix Performance Center Users Guide

Introduction to NetMetrix Performance Center

Integration with HP OpenView Network Node Manager

Web Browser Support

NetMetrix Performance Center Users Guide

NetMetrix Performance Center Interface and Navigation

NetMetrix Performance Center Domain Health Summary

NetMetrix Performance Center Domain Health Summary

NetMetrix Performance Center Users Guide

NetMetrix Performance Center Interface and Navigation

The right pane is divided into three areas: Center

NetMetrix Performance Center Domain Health Summary

v Configuration views v Event Viewer v Online help system

NetMetrix Performance Center Users Guide

NetMetrix Performance Center Interface and Navigation

NetMetrix Performance Center Domain Health Summary

Allows you to navigate to the Device Alarm Information panel.

NetMetrix Performance Center Users Guide

NetMetrix Performance Center Interface and Navigation

Each of the following sections provides:

Domain Health Summary View

NetMetrix Performance Center Users Guide

NetMetrix Performance Center Interface and Navigation

v History At-a-Glance v Current Health

These panes are described in the following sections.

To display a Domain Health Summary view:

Where you can go from this view:

NetMetrix Performance Center Users Guide

NetMetrix Performance Center Interface and Navigation

Where you can go from this view:

NetMetrix Performance Center Users Guide

NetMetrix Performance Center Interface and Navigation

v Click an item listed in the Name column to display a more specific

Where you can go from this view:

Data Source Health View

To display a Data Source Health view:

Where you can go from this view: