® Management Module Guide for Standard RMON
Notice Cabletron Systems reserves the right to make changes in specifications and other information contained in this document without prior notice. The reader should in all cases consult Cabletron Systems to determine whether any such changes have been made. The hardware, firmware, or software described in this manual is subject to change without notice.
Virus Disclaimer Cabletron Systems makes no representations or warranties to the effect that the Licensed Software is virus-free. Cabletron has tested its software with current virus checking technologies. However, because no anti-virus system is 100% reliable, we strongly caution you to write protect and then verify that the Licensed Software, prior to installing it, is virus-free with an anti-virus system in which you have confidence.
Contents Preface Who Should Read This Manual ...........................................................................................xi How This Manual Is Organized ...........................................................................................xi Related Reading.................................................................................................................. xii Questions about SPECTRUM Documentation .................................................................
Chapter 4 Icons and Icon Components The RMONApp Icon............................................................................................................4-1 RMONApp Icon Subviews............................................................................................4-2 The RMON Ethernet Probe Icon ........................................................................................4-4 RMONEProbe Icon Subviews ...................................................................................
Chapter 6 Configuring RMON Alarms and Events RMON Alarms .................................................................................................................... 6-1 Creating an Alarm ....................................................................................................... 6-2 Modifying and Enabling an Alarm Under Creation................................................... 6-5 Modifying a Valid Alarm ................................................................................
Appendix B Token Ring Fields and Statistics Mac-Layer Statistics Table ................................................................................................ B-1 Mac-Layer Statistics Detail View ............................................................................... B-2 Isolating Errors Chart .......................................................................................... B-2 Non-Isolating Errors Chart ............................................................................
Appendix E Object Identifiers (OIDs) etherStats............................................................................................................................E-1 historyControl .....................................................................................................................E-2 etherHistory ........................................................................................................................E-2 hostControl...................................................
Figures Chapter 1 Figure 1-1. Chapter 2 Figure 2-1. Figure 2-2. Figure 2-3. Figure 2-4. Chapter 3 Figure 3-1. Figure 3-2. Chapter 4 Figure 4-1. Figure 4-2. Figure 4-3. Figure 4-4. Figure 4-5. Figure 4-6. Introduction Sample RMON Model Configuration ................................................................... 1-3 Modeling RMON in SPECTRUM Example of an EMME Model Configuration ....................................................... 2-6 EMME DevTop View ............................................
Chapter 5 Figure 5-1. Figure 5-2. Figure 5-3. Figure 5-4. Figure 5-5. Figure 5-6. Figure 5-7. Figure 5-8. Figure 5-9. Figure 5-10. Figure 5-11. Figure 5-12. Figure 5-13. Figure 5-14. Chapter 6 Figure 6-1. Figure 6-2. Figure 6-3. Figure 6-4. Figure 6-5. Figure 6-6. Chapter 7 Figure 7-1. Figure 7-2. Figure 7-3. Figure 7-4. Figure 7-5. Figure 7-6. ix Using RMON Views Ethernet Statistics Table ......................................................................................
Tables Chapter 2 Table 2-1. Modeling RMON in SPECTRUM SPECTRUM Model Type Designations ................................................................
Preface This manual describes the RMON Management Module, which allows you to collect, manage, and monitor information about a remote LAN segment. Who Should Read This Manual Read this manual if you are going to use the RMON Management Module to analyze networks that have been modeled in SPECTRUM. Before reading this document, you should be familiar with SPECTRUM’s functions as described in the SPECTRUM System User’s Guide and the SPECTRUM System Administrator’s Guide.
Related Reading • Appendix D—Provides sample profiles for Ethernet and Token Ring. • Appendix E—Provides object IDs (OIDs) that you supply during alarm creation. • Appendix F—Describes the Report Information Block (.rib) files included with the RMON Management Module. Related Reading The following documents contain more information about remote monitoring, SPECTRUM, and TCP/IP-based networks. SPMA Tools User’s Guide, Cabletron Systems, Inc.
Chapter 1 Introduction This chapter provides an introduction to the RMON Management Module and its model types. RMON Management Module A management module is a C++ coded software emulation of a physical device or software agent. The management module uses icons based on X Windows/ OSF Motif to represent this device in the user interface.
SPECTRUM and RMON device icon, select View > Utilities > Applications. Within the Applications dialogue box, click on the RMON Suite button. For additional information about SPMA for RMON, refer to SPMA for Remote Network Monitoring User’s Guide. SPECTRUM and RMON Remote Network Monitoring, or RMON, was developed by the Internet Engineering Task Force (IETF) as a means of monitoring remote networks using the SNMP protocol.
RMON Models distinct network segments, which are then internally bridged or routed within the EMME. An RMON agent running on a network device collects and maintains RMON data for each interface on the device. The RMON Management Module supports three types of models to represent the RMON agent and its supported applications and interfaces. When you use SPECTRUM to model a device that supports RMON, RMON models are created automatically within SPECTRUM’s Application View.
Major Software Application Models Major Software Application Models When a device is modeled, SPECTRUM automatically creates a model for each major software application (such as the RMONApp) that is present on the device. Major software application models appear in SPECTRUM’s Application View in the first tier beneath the device model; black lines connect each major model directly to the device model.
RMON Groups RMON Groups • The RMON MIB, which is based on RFC 1271 (Ethernet) and RFC 1513 (Token Ring), is divided into the following groups: • Statistics • History • Alarm • Host • HostTopN • Matrix • Filter • Packet Capture • Event • Token Ring Each group defines a set of objects to be monitored. In addition, each group stores data and statistics collected by the agent on the device, which may have multiple network interfaces.
RMON Groups Unsupported RMON Groups Event Controls the generation and notification of events from the monitoring agent. Token Ring These subgroups provide monitoring functions for Token Ring: • Ring Station Group—Provides information about each station on the ring, as well as each ring being monitored. • Ring Station Order Group—Provides the order of stations on the monitored ring. • Ring Station Configuration Group—Actively manages stations on the ring.
Chapter 2 Modeling RMON in SPECTRUM This chapter describes the SPECTRUM views that contain RMON models, how to model and configure devices that implement an RMON agent, and how to set up RMON as a network monitor point.
Creating a Device Model That Supports RMON 4. Select a model type that supports RMON from the Select Model Type dialog box. The following table lists RMON devices and their model type designations in SPECTRUM. If your device supports RMON but does not have a model type designation in SPECTRUM, use the GnSNMPDev model type. Table 2-1.
Enabling RMON for a Cabletron Device • • • • • • • Community Name—The Community Name assigned locally to this device. The default value is public. See your network administrator to verify that the Community Name has not been changed from public to another access policy name before modeling this device. Location—The location where the device is installed. This field is optional. Contact—The contact person or group who can provide troubleshooting help. This field is optional.
Enabling RMON for a Cabletron Device Follow these steps to enable the MIB components and set the community names: 1. Click on Configuration in the device’s Icon Subviews menu. The Device Configuration View appears. 2. Click on Component Table. 3. Deselect any preselected components in the Component Table. NOTE When you enable any of the RMON components, you may need to upgrade your device’s memory requirements to improve overall system performance.
Configuring RMON as a Network Monitor Point Configuring RMON as a Network Monitor Point When you work with RMON, you have the option of configuring an RMON probe model as a network monitor point for the given segment or ring. A monitor point is a device within a network group model (such as a LAN_802_3 or LAN_802_5 network) that provides the statistics that are used to calculate network activity in the network group model’s Performance View.
Configuring RMON as a Network Monitor Point Associating an RMON Probe Model with a Network Interface Associating an RMON Probe Model with a Network Interface The first step in making RMON a network monitor point is to associate the probe model with a network interface. An RMON probe model that monitors a network interface can be a monitor point only for the network connected to that interface.
Configuring RMON as a Network Monitor Point Associating an RMON Probe Model with a Network Interface Figure 2-2. EMME DevTop View Network Network Interface Channel In Figure 2-2, three of the EMME’s network interfaces are associated with a network model at that interface. For example, interface 2 is associated with the Design network model.
Configuring RMON as a Network Monitor Point Copying RMON Probes into Network Models Copying RMON Probes into Network Models To designate an RMON probe model as a monitor point, copy the RMON probe model from the device’s Application View and paste it into the corresponding 802.3 or 802.5 network model. The RMON Probe becomes a monitor point device within that segment. Follow these steps: 1. Open the Application View for the device you modeled. 2. Select Edit from the File Menu. 3.
Configuring RMON as a Network Monitor Point Verifying the Monitor Point Verifying the Monitor Point The last step in the monitor point process is to verify that the RMON Probe is selected as the monitor point for the LAN. If you configure the RMON Probe to be the monitor point device, RMON segment performance data is presented in the Performance View of the network model.
Configuring RMON as a Network Monitor Point Verifying the Monitor Point Figure 2-4. LAN Information View E Probe 01 CSIRptr Ch1 45 EProbe E Probe1 01 RMONEthProbe Available monitor points Selected monitor point To select a monitor point, or to modify an existing one, follow these steps: 1. Highlight the desired monitor point from the Select Monitor Point list and click OK. 2. Verify that the selected monitor point is now displayed in the Monitor Point Model Name field.
Chapter 3 Loading and Unloading Profiles This chapter describes how to set up, load, and unload profiles. What is a Profile Default control table instances of each RMON group are created on the device when the agent is started. In addition to these instances, you can download customized instances by using information stored in an ASCII file called a profile. Each profile specifies the control table characteristics you want to view.
Checking Your Agent Configuration To access the Profile Load/Unload View, select Profile Load/Unload from the RMONApp model’s Icon Subviews menu. The Profile Load/Unload View shown in Figure 3-1 appears. Figure 3-1. RMON Profile Load/Unload View Supported and enabled groups Check Configuration Reset View button Checking Your Agent Configuration The Profile Load/Unload View allows you to check which RMON groups are supported and enabled on the agent.
Creating Custom Profiles Creating Custom Profiles Cabletron provides starter files that you can use to create your own custom profiles. The starter files are located in the directory /Spectrum_install_area/ SS/CsResource/RMON_Profiles. Note that the files are intended only as starter files; their configuration may not match your supported RMON groups or suit your needs. See Appendix D for examples and descriptions of the format and syntax of profiles.
Loading Profiles Loading Profiles When you load a profile, the load process uses the resource_file_path parameter in your ss/.vnmrc file as the root path in its search for the specified profile. By default, this parameter is set to the //SS/ CsResource directory. Cabletron supplies an RMON_Profiles directory in this area, where you can find sample profiles and also store your custom profiles. To load a profile, follow these steps: 1.
Loading Profiles Problems When Loading Profiles Problems When Loading Profiles When an error occurs while a profile is being loaded, the Profile Load/Unload parsing mechanism aborts the profile loading process, generates a parser error message that corresponds to the error, and records an error log entry in the error log file that you specified when you loaded the profile.
Unloading Profiles Unloading Profiles Use the Profile Unload feature to remove default or user-configured instances from the agent Control Table and thereby free up resources on the device allocated to those instances. When you remove profile information, you specify what to remove according to the owner of the instance. Therefore, the removal process is not group-specific; all instances in all groups associated with the specified owner will be removed. To remove profile information, follow these steps: 1.
Chapter 4 Icons and Icon Components This chapter describes the RMON models and discusses how you can use the icons (the RMONApp icon, the RMON Ethernet probe icon, and the RMON Token Ring probe icon) to obtain network performance data. The RMONApp Icon The RMONApp icon ( Figure 4-1) serves as a central gathering point for network device information and allows you to easily access data collected from multiple interfaces on the device.
The RMONApp Icon RMONApp Icon Subviews RMONApp Icon Subviews Icon subviews provide detailed information about the RMONApp model. To access the Icon Subviews menu, click the middle mouse button anywhere on the icon. As an alternative, you can click on the RMONApp icon to highlight it and then select Icon Subviews from SPECTRUM’s View menu. Figure 4-2.
The RMONApp Icon RMONApp Icon Subviews The following list briefly describes menu selections for the Ethernet and Token Ring RMONApp icons. Note that some menu selections describe options that are topology-specific; for example, menu selections for Ethernet are not available on a Token Ring network and vice versa. Chapter 5 describes the menu selections in more detail. Appendices A and B provide additional information about the statistics displayed by the menu selections.
The RMON Ethernet Probe Icon The RMON Ethernet Probe Icon The RMON Ethernet probe (RMONEProbe) gathers statistics from a single interface on an Ethernet device. The RMONEProbe icon ( Figure 4-3) contains labels that provide access to detailed information about the model. For quick access to the information, double click on the label, using the left mouse button. (You can also access this same information through the Icon Subviews menu.) Figure 4-3.
The RMON Ethernet Probe Icon RMONEProbe Icon Subviews RMONEProbe Icon Subviews Click the middle mouse button anywhere on the RMONEProbe icon to access the Icon Subviews menu, shown in Figure 4-4. As an alternative, you can click on the RMONEProbe icon to highlight it and then select Icon Subviews from SPECTRUM’s View menu. Figure 4-4. RMONEProbe Icon Subviews Menu Close the Subviews Menu Move to a Topology View higher or lower in the topology hierarchy.
The RMON Token Ring Probe Icon The RMON Token Ring Probe Icon The RMON Token Ring probe (RMONTProbe) gathers statistics from a single interface on a Token Ring device. The RMONTProbe icon ( Figure 4-5) contains labels that provide quick access to detailed information about the model. For quick access to the information, double click on the label, using the left mouse button. (You can also access this same information through the Icon Subviews menu.) Figure 4-5.
The RMON Token Ring Probe Icon RMONTProbe Icon Subviews RMONTProbe Icon Subviews Click the middle mouse button anywhere on the RMONTProbe icon to access the Icon Subviews menu, shown in Figure 4-6. As an alternative, you can click on the RMONTProbe icon to highlight it and then select Icon Subviews from SPECTRUM’s View menu. Figure 4-6. RMONTProbe Icon Subviews Menu Close the Icon Subviews Menu. Move to a Topology View higher or lower in the topology hierarchy.
The RMON Token Ring Probe Icon RMONTProbe Icon Subviews Icons and Icon Components 4-8 Standard RMON Management Module Guide
Chapter 5 Using RMON Views This chapter describes the RMON views that are available from the Icon Subviews menu. It also describes how you can tailor many of the views to suit your needs. Views Unique to RMON This chapter describes the views that are unique to the RMON management module. To access the RMON views, highlight the RMONApp or RMON probe icon. Then click the middle mouse button anywhere on the icon; the Icon Subviews menu appears. As an alternative, click on View New View Icon Subviews.
Views Unique to RMON The following table lists views that are unique to RMON. These views are described later in this chapter. Note, however, that the Profile Load/Unload view is described fully in Chapter 3 while the RMON Alarms/Events are described in Chapter 6. The table indicates the network topology that supports each view and also identifies the RMON group on which the view is based. Note that some views appear only on an Ethernet network, while others appear only on a Token Ring network.
Customizing the RMON Tables Customizing the RMON Tables Many RMON tables share a common format and have identical options that you can use to customize the information output. The customization options are described in the following table. Click on... To... The popup menu next to Sort ON Sort table contents incrementally according to the entry type. The default is No Sort. Popup menu choices differ for each RMON table.
Accessing Ethernet Views Ethernet Statistics Ethernet Statistics From the Icon Subviews menu, click on Ethernet Statistics. The Ethernet Statistics Table shown in Figure 5-1 presents the RMON Statistics data in tabular form. Figure 5-1. Ethernet Statistics Table The RMON Statistics group consists of 17 parameters measured at the monitored network interface (data source) of the device.
Accessing Ethernet Views Ethernet Statistics • • • • • Fragments—Total packets received that were not an integral number of octets in length or that had a bad FCS, and were less than 64 octets in length. Jabbers—Total packets received, longer than 1518 octets, and not an integral number of octets in length or with a bad FCS. Oversize—Total packets received, longer than 1518 octets, otherwise well-formed. Undersize—Total packets received, less than 64 octets long, otherwise well-formed.
Accessing Ethernet Views Ethernet Statistics Viewing Statistics with the Details Button Click the Details button in the Performance View for more diagnostic detail. The Statistics Detail View appears; it presents a graphical breakdown of the frame size distribution and error statistics which are updated and presented as totals or deltas. Note that this view is dynamically updated.
Accessing Ethernet Views Ethernet History Ethernet History From the Icon Subviews menu, click on Ethernet History. The Ethernet History Table presents the RMON History data in tabular form. The RMON History group records data from the Statistics group over user-defined intervals and stores it for later retrieval, allowing you to perform trend analysis of a statistic over time or to isolate periods of time during which a network event may have occurred. Figure 5-2.
Accessing Ethernet Views Hosts Control Viewing the History Table Double click any History Control Table entry to display the data for that instance. The History Table shows the past performance measured at the monitored network interface (data source) of the device. Appendix A contains detailed descriptions of the fields found in the History Table. Hosts Control From the Icon Subviews menu, click on Hosts Control. The Hosts Control Table presents the RMON Host data in tabular form.
Accessing Ethernet Views Hosts Control The Host Control Table (shown in Figure 5-3) presents the configuration of each Host instance running on the network interface. Each instance features the following fields: • • • • • Data Source—The interface being monitored. Size—The number of host entries in the table. Last Deleted—The time that the oldest entry was deleted and replaced by the newest entry. Owner—The individual or entity that configured this entry. Status—The status of this control table entry.
Accessing Ethernet Views Hosts Control Viewing the Host Table Double click on any instance in the Host Control Table to open the Host Table View. The Host Table, shown in Figure 5-4, displays per-host traffic statistics measured at the monitored network interface (data source) of the device. Appendix A contains detailed descriptions of the fields found in the Host Table. Figure 5-4. Host Table View 132.177.00.
Accessing Ethernet Views Matrix Control Matrix Control From the Icon Subviews menu, click on Matrix Control. The Matrix Control Table presents the RMON Matrix data in tabular form. The RMON Matrix group provides a breakdown of traffic statistics according to the communication pairs it identifies on the segment by using the source and destination MAC address fields contained in a transmitted packet.
Accessing Ethernet Views Matrix Control oldest entry is deleted and replaced by the newest entry; the time this occurs is indicated by the column Last Deleted. Viewing the Matrix Table Double click on any instance in the Matrix Control Table to open the Matrix Table View. The Matrix Table View, shown in Figure 5-6, displays traffic statistics for each host pair, measured at the monitored network interface. Figure 5-6. Matrix Table View 132.177.00.
Accessing Ethernet Views HostTopN Control HostTopN Control From the Icon Subviews menu, click on HostTopN Control. The HostTopN Control Table ( Figure 5-7) presents the RMON HostTopN data in tabular form. The RMON HostTopN group allows you to select one of the seven Host group statistics and determine an arbitrary number of hosts on the segment with the greatest value for that parameter.
Accessing Ethernet Views HostTopN Control Viewing or Configuring the Top Hosts To configure an instance of Top Hosts or to view the result of an instance or one in progress, double click on an instance listed in the HostTopN Control Table. The Top Hosts view (shown in Figure 5-8) appears, where you specify the measurement parameters and view the results of the completed sample.
Accessing Token Ring Views Accessing Token Ring Views The following sections describe RMON views that appear on Token Ring icons. Refer to Appendix B, Token Ring Fields and Statistics, for detailed descriptions of statistics that appear in Token Ring views. Mac-Layer Statistics From the Icon Subviews menu, click on Mac-Layer Statistics. The Mac-Layer Statistics Table (Figure 5-9) presents the RMON statistics in tabular form. Figure 5-9. Mac-Layer Statistics Table 132.177.00.
Accessing Token Ring Views Mac-Layer Statistics during this sampling interval. Viewing Performance Statistics on the Segment Double click on any instance (row or interface) in the Mac-Layer Statistics Table to view the RMON data presented in SPECTRUM Performance View format. This allows you to view current percentage calculations and a time graph of the interface activity, rather than the absolute numbers of the Statistics Table. Note that this view is dynamically updated.
Accessing Token Ring Views Promiscuous Statistics Promiscuous Statistics From the Icon Subviews menu, click on Promiscuous Statistics. The Promiscuous Statistics Table (Figure 5-10) presents the RMON statistics in tabular form. Figure 5-10. Promiscuous Statistics Table 132.177.00.00 The RMON Statistics group consists of the following 7 parameters measured at the monitored network interface (data source) of the device.
Accessing Token Ring Views Promiscuous Statistics Viewing Performance Statistics on the Segment Double click on any instance (row or interface) in the Promiscuous Statistics Table to view the RMON data presented in SPECTRUM Performance View format. This allows you to view current percentage calculations and a time graph of the interface activity, rather than the absolute numbers of the Statistics Table. Note that this view is dynamically updated.
Accessing Token Ring Views Mac-Layer History Mac-Layer History From the Icon Subviews menu, click on Mac-Layer History. The Mac-Layer History Table presents the RMON Mac-layer data in tabular form. The RMON History group records data from the Statistics group over user-defined intervals and stores it for later retrieval, allowing you to perform trend analysis of a statistic over time or to isolate periods of time during which a network event may have occurred. Figure 5-11.
Accessing Token Ring Views Promiscuous History Viewing the History Table Double click any Mac-Layer History Control Table entry to display the data for that instance. The History Table shows the past performance measured at the monitored network interface (data source) of the device. Appendix B contains detailed descriptions of the fields found in the History Table. Promiscuous History From the Icon Subviews menu, click on Promiscuous History.
Accessing Token Ring Views Promiscuous History The History Control Table (Figure 5-12) presents the configuration of each History instance running on the network interface. By default, the RMON standard specifies 2 instances, having intervals of 1800 seconds and 30 seconds. Each instance features the following fields: • • • • • • Data Source—Interface being monitored. Interval—The sample collection interval.
Accessing Token Ring Views Ring Station Ring Station From the Icon Subviews Menu, click on Ring Station. The menu selection is available only from the RMONTRProbe model. When you click on the Ring Station selection, the Ring Station Control View (Figure 5-13) appears. This Token Ring View includes the Ring Station and Ring Station Order Groups. The Ring Station group provides status information for the ring being monitored.
Accessing Token Ring Views Ring Station Viewing the Station Order Click on the Station Order button to view the Station Order Table which shows a screen similar to the following. Figure 5-14. Station Order The following fields appear in the Station Order Table. Field 9031280 E4 Description Order The location of this station with respect to other stations on the ring when the RMON probe gets the value one. Mac Address The physical address of this station.
Accessing Token Ring Views Ring Station Viewing Non-Isolating Errors Click on the Non-Isolating Errors button to view data about non-isolating errors that occur on the network. Fields include: • • • • • • • • • Address—The physical address of this station. Token—Total token errors reported in error reporting packets detected by the probe. Duplicates—The number of times the station experienced a duplicate address error.
Accessing RMON Alarms/Events Other RMON Views Other RMON Views All other RMON views that appear on Token Ring icons also appear on Ethernet icons. Refer to the preceding section on Ethernet Views for information on the following views: • • • Hosts Control Matrix Control HostTopN Control Accessing RMON Alarms/Events The RMON Alarms/Events group monitors statistics, compares them to thresholds you set, and specifies the action that should be taken when a threshold is met.
Accessing RMON Alarms/Events Using RMON Views 5-26 Standard RMON Management Module Guide
Chapter 6 Configuring RMON Alarms and Events This chapter describes the RMON Alarms and Events tables and how to create, modify, and delete RMON alarms and events. RMON Alarms An alarm is triggered when a threshold for a specified network activity, or monitored object, is crossed in a particular direction. You can set an alarm to be triggered when a monitored object goes above an indicated value (a rising threshold) or when it drops below an indicated value (a falling threshold).
RMON Alarms Creating an Alarm Creating an Alarm Creating an alarm is a two-step process. The first step is to create an instance of a new alarm. The next step is to make the alarm Valid, thus enabling the alarm. NOTE In the configuration views for RMON Alarms and Events, some attribute fields are outlined in red. This is normal; it occurs when you define a new alarm or event because a value for the attribute does not yet exist. After you enter a value, the attribute outline changes to white.
RMON Alarms Creating an Alarm 5. Click on the Status button and select createRequest from the Status menu. 6. Click on the Start-up Alarm button and select the type of threshold that will trigger this alarm. Threshold types are: • • • Rising—The value for the monitored object rises above the threshold Falling—The value for the monitored object falls below the threshold Rising_or_Falling—The value for the monitored object rises above or falls below the threshold 7.
RMON Alarms Creating an Alarm to control the type of notification you want. See the steps outlined in RMON Events. 10. Click in the Rising Threshold field and enter the high threshold for the sampled statistic. A single alarm is generated for the object if either of the following conditions is met: • The current sampled value is greater than or equal to this threshold and the value at the last sampling interval was less than this threshold.
RMON Alarms Modifying and Enabling an Alarm Under Creation 15. To see the alarm instance you created, click Update in the Alarm Table. The new alarm definition appears in the table, the Status field reads underCreation, and the alarm’s values appear. Now that you have created the alarm, you must change the alarm’s status to Valid. Note that Cabletron RMON agents on the device will delete an alarm whose status remains underCreation for an extended period of time.
RMON Alarms Modifying a Valid Alarm 2. You can modify the following fields. For a description of these fields see the previous section, Creating an Alarm. • • • • • Owner Start-up Alarm Variable Threshold Information Sampling Information 3. To enable the alarm, click on the Status button (located above the Description Information box) and select valid. Remember that Cabletron’s RMON agent will delete the alarm if you neglect to change the status to valid. 4.
RMON Events Removing an Alarm Removing an Alarm To remove an alarm from the table, follow these steps: 1. Double click on the alarm in the Alarm Table to access the Alarm Set Up View. 2. Click on the Status button and select invalid from the menu. 3. Click the right mouse button, or select Save All Changes from the File menu, and click OK in the dialog box that appears. The alarm will now be removed from the Alarm Table. Dismiss the Alarm Set Up View window. 4.
RMON Events Creating an Event To create an event, access the Event Set UpView, where you supply values for the parameters that define the event. Follow these steps: 1. Click on RMON Alarms/Events in the RMONApp’s Icon Subviews menu. The Alarm/Event Table View appears. Adjust the vertical slide bar to see the Event Table (shown in Figure 6-3). Figure 6-3. Event Table View 2. In the Event Table, click on the New Event button to access the Event Set Up View, shown in Figure 6-4. Figure 6-4.
RMON Events 4. In the Index field, enter a number that represents this event definition. Make sure the Index number you choose is not already assigned to an existing event definition. The event indexes in use need not be consecutively numbered. 5. Click in the Community Name field and enter a text string that identifies the SNMP community to which an SNMP trap will be sent. See the section entitled Traps for details. 6. Click on the Action button and select the action required in response to an alarm.
RMON Events Modifying and Enabling an Event Under Creation Now that you have created the event, you must change the status to valid. Note that Cabletron RMON agents on the device will delete an event whose status remains underCreation for an extended period of time. (RMON agents produced by other companies might not delete events that are under creation.) To change the status of the new event to valid, follow the steps outlined in Modifying and Enabling an Event underCreation.
RMON Events Modifying a Valid Event Modifying a Valid Event To modify an event which is in the valid state, you must first return the event to the underCreation state. After making your changes, return the Event to the valid state. To modify an existing event definition in the Event Table, follow these steps: 1. Double click on the event entry you want to change. The Event Setup View appears. 2. Click on the Status button and select underCreation. 3.
Traps Viewing the Event Log Viewing the Event Log In the Event Table, click on the View Event Log button to view the Event Log Table, which contains detailed descriptions of all recorded events. Figure 6-5. Event Log Table View L a nP r ob e wa r m - s ta r t in g. L a nP r ob e wa r m - s ta r t in g. L a nP r ob e wa r m S ta r t . The following fields appear in the Event Log Table: • • • • Event—The index number of the event which was logged. No.—Entry sequence per defined event (index number).
Traps SPMA Trap Table Tool If you plan to define RMON events which will send SNMP traps, you must first configure both the RMON agent and your management station to handle them. This section describes that process. SPMA Trap Table Tool The SPECTRUM Portable Management Application Trap Table Tool is part of the SPMA Tools which are available from Cabletron as part of the SPMA core product.
Traps RMON Agent RMON Agent When an SNMP device on the network generates a trap as a result of some condition on that device, the device must know where to send the trap (the trap destination). For Cabletron devices such as an EMME, there is a Trap Destination Table which is user-configurable and accessed through local management via the front panel console port on the EMME or remotely with the SPMA Trap Table Tool.
Traps RMON Agent Accessing the Trap Table Screen To access the Trap Table Screen from the Features Selection Screen, use the arrow keys to highlight the Component Trap Table option and press the Return key (or F8). The Trap Table Screen, shown in Figure 6-6, appears. Figure 6-6. Trap Table Screen EMME LOCAL MANAGEMENT Cabletron EMME Revision 0.00.00 TRAP TABLE SNMP Community Name ctron public Traps N N N N N N N N Trap IP Address 134.141.9.6 134.141.6.1 0.0.0.0 0.0.0.
Traps RMON Agent Note that this is not a community name of the destination management station itself, which typically is not a factor in receiving traps. However, this event community name is embedded in the trap message and can be accessed by applications at the destination to allow an application to decide whether the trap is of interest. This is the second purpose of the community name in the Trap Destination Table, and currently neither SPECTRUM nor any of its applications make use of it.
Chapter 7 Creating IndirectRMON Models This chapter describes how to set up IndirectRMON models. IndirectRMON Models The IndirectRMON Model Type was designed to take advantage of additional network monitoring possibilities made available by data contained in the Host Table. A number of hosts on the network, whose MAC addresses are in the Host Table, may not be using SNMP as a management protocol or otherwise may not be supported by SPECTRUM, yet their traffic statistics are visible to RMON.
Creating an IndirectRMON Model Creating an IndirectRMON Model You create an IndirectRMON model from within the RMON Host Table View. To create an IndirectRMON model, follow these steps: 1. Select the Hosts Control menu item from the Icon Subviews menu. 2. Double click on an instance within the Host Control Table. The Host Table View appears. 3. In the Host Table, choose the device you want to model and double click on the row containing the chosen MAC address. The Host Table Detail view appears. 4.
Placing an IndirectRMON Model into a View 10. Click OK to create the model. The IndirectRMON Creation View disappears and the newly created IndirectRMON model icon is placed into the Lost & Found view. The following section describes how to move the Indirect RMON icon from the Lost & Found view to its proper location in a LAN segment. Placing an IndirectRMON Model into a View To place an IndirectRMON model into a SPECTRUM view, follow these steps: 1.
The IndirectRMON Icon The IndirectRMON Icon Figure 7-2. IndirectRMON Icon 89 IndirectRMON Host Performance label IndirectRMON Information View labels 0.0.C.5.B8.C7 The IndirectRMON icon features three labels that provide visual status and quick access to detailed information about the model: • The IndirectRMON Information View label (at the top of the icon) displays the default or user-defined model name.
The IndirectRMON Icon IndirectRMON Information View Label IndirectRMON Information View Label Double click on the IndirectRMON icon’s Information View label to open the IndirectRMON Information View (Figure 7-3). Figure 7-3. IndirectRMON Information View The following fields appear in the Information View: • • • • • • • • 9031280 E4 Model Name—The model name for the IndirectRMON model. MAC Address—The MAC address for the IndirectRMON model.
The IndirectRMON Icon IndirectRMON Host Performance Label IndirectRMON Host Performance Label The IndirectRMON icon’s Host Performance label provides a representative image of the IndirectRMON model type, as well as visual contact status. Double click on the question mark in the center of the icon to access the IndirectRMON Host Performance view (Figure 7-4). This view contains traffic data attributes for the host modeled by the IndirectRMON model.
The IndirectRMON Icon IndirectRMON Host Performance Label • • Broadcast Packets—The total number of good packets transmitted by this address that were directed to the broadcast address since this host was added to the Host Table. Multicast Packets—The total number of good packets transmitted by this address that were directed to a local or global multicast or functional address since this host was added to the Host Table.
The Off-Page Reference Icon The Off-Page Reference Icon The Off-Page Reference Icon (Figure 7-6) represents a device that is directly connected to the current level of view but which was modeled from another view. The icon features two areas (the IndirectRMON Information View label and the IndirectRMON Host Performance View label) that you can double click to access informational views about the device.
Appendix A Ethernet Fields and Statistics This appendix describes the Ethernet fields and statistics that appear in the RMON Management Module views. Ethernet Statistics Table Listed below is a description of the fields found on the Ethernet Statistics Table. Field Description Data Source The source of the data that this entry is configured to analyze. The source can be any Ethernet interface on this device.
Ethernet Statistics Table Ethernet Statistics Detail View Field Description Collisions The best estimate of the total number of collisions on this Ethernet segment. Fragments The total number of packets received that were not an integral number of octets in length or that had a bad FCS, and were less than 64 octets in length (excluding framing bits but including FCS octets).
Ethernet Statistics Table Ethernet Statistics Detail View Field 64 Bytes Description The total number of packets, including error packets, that were 64 bytes in length. 65 to 127 Bytes The total number of packets, including error packets, that were between 65 and 127 bytes in length inclusive. 128 to 255 Bytes The total number of packets, including error packets, that were between 128 and 255 bytes in length inclusive.
Ethernet History Control Table Field Description Jabbers The total number of packets received that were longer than 1518 bytes and were not an integral number of octets in length or had a bad Frame Check Sequence. Total The total number of packets received. Ethernet History Control Table The following fields appear in the Ethernet History Control Table.
Ethernet History Control Table History Table Field 9031280 E4 Description Created The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of the time of day, it starts the first sample when the next hour of the day begins. Utilization The best estimate of the mean physical layer network utilization on this interface during this interval in hundredths of a percent.
Hosts Control Table Hosts Control Table The following fields appear in the Hosts Control Table. Field Description Data Source The source of the data for this instance of the host function. The source can be any interface on the device. Size The number of host entries in the table. Last Deleted The value of sysUpTime when the last entry was deleted from the portion of the table associated with this entry. Owner The entity that configured this entry and is using the resources assigned to it.
Hosts Control Table Host Table Host Table The following fields appear in the Host Table. Field 9031280 E4 Description Index The set of collected host statistics of which this entry is a part. Address The physical address of this host. Order An index that defines the relative ordering of the creation time of hosts captured for a particular hostControlEntry. In Packets The number of packets without errors transmitted to this host since it was added to the Host Table.
Hosts Control Table Host Table Detail Host Table Detail The following fields appear in the Host Table Detail view. Field Description MAC Address The physical address of this device. Out Octets The number of octets transmitted by this address since it was added to the Host Table (excluding framing bits but including FCS octets) including those octets in packets that contained errors.
Matrix Control Table Matrix Control Table The following fields appear in the Matrix Control Table. Field Description Data Source The source of the data from which this entry creates a traffic matrix. The source can be any interface on the device. Size The number of matrix entries in the table for this interface. Last Deleted The value of sysUpTime when the last entry was deleted from the portion of the matrixSDTable or matrixDSTable associated with this entry.
HostTopN Control Table HostTopN Control Table The following fields appear in the HostTopN Control Table. Field Description Data Source The source of the data. This source can be any interface on the device. Report The HostTopN Control Table report of which this entry is a part. ReqSize The maximum number of hosts requested for the HostTopN Control Table. Size The maximum number of hosts in the table.
HostTopN Control Table Top Hosts View Top Hosts View The following fields appear in the Top Hosts view. Field 9031280 E4 Description Top Hosts The maximum number of hosts requested for the table. The default is 10. Sample Interval The number of seconds that this report has collected during the last sampling interval or, if this report is currently being collected, the number of seconds that this report is being collected during this sampling interval.
HostTopN Control Table Top Hosts View Ethernet Fields and Statistics A-12 Standard RMON Management Module Guide
Appendix B Token Ring Fields and Statistics This appendix describes the Token Ring fields and statistics that appear in the RMON Management Module. The fields and statistics are listed according to the RMON table or view on which they are found. Mac-Layer Statistics Table This table provides a list of Mac-Layer Token Ring statistic entries. Field Description Data Source The source of the data that this entry is configured to analyze. The source can be any Token Ring interface on this device.
Mac-Layer Statistics Table Mac-Layer Statistics Detail View Mac-Layer Statistics Detail View The following fields appear on the Mac-Layer Statistics detail view. Isolating Errors Chart The following fields appear in the Isolating Errors Chart. Field Description Line The total number of line errors reported in error reporting packets detected by the probe. Burst The total number of burst errors reported in error reporting packets detected by the probe.
Mac-Layer Statistics Table Mac-Layer Statistics Detail View Field Description Frequency The total number of frequency errors reported in error reporting packets detected by the probe. Total The total number of errors reported. Event Breakdown Chart The following fields appear in the Event Breakdown Chart. Field 9031280 E4 Description Drop Events The total number of events in which packets were dropped by the probe due to lack of resources.
Mac-Layer History Control Table Mac-Layer History Control Table The following fields appear on the Mac-Layer History Control Table. Field Description Data Source The source of the data for which historical data was collected and placed in a media-specific table on behalf of this entry. The source can be any interface on the device. Interval The interval in seconds over which the data is sampled for each bucket in the part of the media-specific table associated with this history control entry.
Mac-Layer History Control Table Mac-Layer History Table Field 9031280 E4 Description PrgePkts The total number of ring purge MAC packets detected by the probe during this sampling interval. ClmTkPkts The total number of claim token MAC packets detected by the probe during this sampling interval. BecnPckts The total number of beacon MAC packets detected by the probe during this sampling interval.
Mac-Layer History Control Table Mac-Layer History Table Field Description PurgeEvnts The total number of times that the ring entered the ring purge state from normal ring state during this sampling interval. DropEvnts The total number of events in which packets were dropped by the probe due to lack of resources during this sampling interval. ClmTkEvnts The total number of times that the ring enters the claim token state from normal ring state or ring purge state during this sampling interval.
Promiscuous Statistics Table Promiscuous Statistics Table This table provides a list of Promiscuous Token Ring Statistic entries. Field 9031280 E4 Description Data Source The source of the data that this entry is configured to analyze. The source can be any Token Ring interface on this device. Octets The total number of octets of data in good frames received on the network (excluding framing bits, but including FCS octets) in nonMAC packets.
Promiscuous Statistics Table Promiscuous Statistics Detail View Promiscuous Statistics Detail View The following fields appear on the Promiscuous Statistics detail view. Frame Size Breakdown The following fields appear in the Frame Size Breakdown Chart. Field Description 18-63 The total number of good Non-MAC frames received that were between 18 and 63 octets in length inclusive, excluding framing bits but including FCS octets.
Promiscuous History Control Table Promiscuous History Control Table The following fields appear on the Promiscuous History Control Table. Field Description Data Source The source of the data for which historical data was collected and placed in a media-specific table on behalf of this entry. The source can be any interface on the device. Interval The interval in seconds over which the data is sampled for each bucket in the part of the media-specific table associated with this history control entry.
Promiscuous History Control Table Promiscuous History Table Field Description Broadcasts The total number of good non-MAC frames received that were directed to an LCC braodcast address (0XFFFFFFFFFFFF) or (0XC000FFFFFFFF) Multicasts The total number of good non-MAC frames directed to a local or global multicast or functional address (not including broadcast address). Drop Events The total number of events in which packets were dropped by the probe due to lack of resources.
Hosts Tables Hosts Tables Refer to Appendix A for a description of the fields that appear in the Hosts Control Table, the Host Table, and the Host Table Detail. Matrix Tables Refer to Appendix A for a description of the fields that appear in the Matrix Control Table and the Matrix Table. HostTopN Tables Refer to Appendix A for a description of the fields that appear in the HostTopN Control Table and the Top Hosts View.
Ring Station Control View Station Order Table Field Description Last NAUN The physical address of the last known NAUN of this station. Last Entered The value of sysUpTime at the time this station last entered the ring. Last Exited The value of sysUpTime at the time the probe detected that this station last exited the ring. Status The status of this station on the ring. Station Order Table The following fields appear on the Station Order Table.
Ring Station Control View Isolating Errors Field Description Copy Frame The total number of frame copied errors reported by this station in error reporting packets detected by the probe. Frequency The total number of frequency errors reported by this station in error reporting packets detected by the probe. Insertion The number of times the probe detected this station inserting onto the ring. In Beacon The total number of beacon frames sent by this station and detected by the probe.
Ring Station Control View Isolating Errors Field Description Internal The total number of adapter internal errors reported by this station in error reporting packets detected by the probe. Congestion The total number of receive congestion errors reported by this station in error reporting packets detected by the probe.
Appendix C SpectroWATCH This appendix contains information on using SpectroWATCH with the RMON Management Module. Watches The RMON Management Module uses SpectroWATCH to perform various calculations on the parameters of the RMON Statistics Groups. These calculations are specified as Watches for the RMONEthProbe and RMONTRProbe model types. The calculations provide aggregate information such as segment performance information as well as individual rate calculations for each Statistic Group parameter.
Modifying or Creating Watches For information on how to make a Probe model a Monitor Point, and thus enable its RMON Watches, see section 2.4, Configuring RMON as a Network Monitor Point. NOTE In the following sections, for information on how to Create, Modify or Log a Watch, please refer to the SpectroWATCH Users Guide. Modifying or Creating Watches A user may modify any of the supplied watches or create new ones.
Logging Watches Logging Watches The user may enable logging on any of the Watch attributes as detailed in the SpectroWATCH Users Guide.
Ethernet Watches mp_MonBroadPkts= INTEGER(((COUNTER_DELTA (mp_ethStsBroadPkts) *100)/ COUNTER_DELTA(mp_ethStsPkts))) -----------------------------------------------------------------mp_MonMultiPkts= INTEGER(((COUNTER_DELTA (mp_ethStsMultiPkts) *100)/ COUNTER_DELTA(mp_ethStsPkts))) -----------------------------------------------------------------mp_MonCRCAlgnErrs= INTEGER(((COUNTER_DELTA (mp_ethStsCRCAlgnErr) *100)/ COUNTER_DELTA(mp_ethStsPkts))) ----------------------------------------------------------
Token Ring Watches mp_MonPkts512to1023= INTEGER(((COUNTER_DELTA (mp_ethStsPkts512to1023) *100)/ COUNTER_DELTA(mp_ethStsPkts))) -----------------------------------------------------------------mp_MonPkts1024to1518= INTEGER(((COUNTER_DELTA (mp_ethStsPkts1024to 1518)*100) COUNTER_DELTA(mp_ethStsPkts))) ------------------------------------------------------------------ Token Ring Watches The following watches are provided for the RMONTRProbe model type: MonSystemUptime= Mem_Sys_Up_Time --------------------
Token Ring Watches TR_Mon_Isol_Err_Count= INTEGER (((((COUNTER_DELTA (mp_mlayStsLineErrs) +COUNTER_DELTA(mp_mlayStsInternErrs)) +COUNTER_DELTA(mp_mlayStsBurstErrs)) +COUNTER_DELTA(mp_mlayStsAbortErrs)) +COUNTER_DELTA(mp_mlayStsACErrs))) -----------------------------------------------------------------TR_Mon_Non_Isol_Err_Count= INTEGER(((((COUNTER_DELTA (mp_mlayStsFrmCpyErrs) +COUNTER_DELTA(mp_mlayStsLstFrmErrs)) +COUNTER_DELTA(mp_mlayStsTokenErrs)) +COUNTER_DELTA(mp_mlayStsFreqErrs)) +COUNTER_DELTA(mp_mla
Appendix D Sample Profiles This appendix provides samples of properly formatted profiles for Ethernet and Token Ring. Ethernet Profile The following example shows an Ethernet profile for an agent or a device (such as an EMME) that has 4 network interfaces. [OwnerString] csi-defaults [EnetStats] 1 2 3 4 [History] 1, 120, 30 2, 120, 30 [Host] 1 2 3 [Matrix} 1 2 3 [HostTopN] 1, 10, 3600 2, 25, 30 END.
Ethernet Profile Ethernet Profile Field Descriptions Ethernet Profile Field Descriptions In this enhanced version of Sample A, descriptions have been added for all fields in the profile. [OwnerString] Field identifier for the owner string specifier which follows. This must appear exactly as shown. csi-defaults The owner string. Assign a meaningful name, without spaces. [EnetStats] Field identifier for the Statistics Group specifiers which follow. This must appear exactly as shown.
Ethernet Profile Ethernet Profile Field Descriptions 1 2 Host Group specifiers. This example creates an instance of Host for 3 of the network interfaces of the EMME. 3 [Matrix} Field identifier for the Matrix Group specifiers which follow. This must appear exactly as shown. An instance of the Matrix Group may be configured for each network interface monitored by the RMON agent. 1 2 Matrix Group specifiers. This example creates an instance of Matrix for 3 of the network interfaces of the EMME.
Ethernet Profile Token Ring Profile Token Ring Profile The following example shows a sample profile for Token Ring for an agent or a device (such as a TRMM) that has 4 network interfaces. [OwnerString] csi-defaults [MacStats] 1 2 3 4 [ProStats] 1 2 [History] 1, 120, 30 2, 120, 30 [Host] 1 2 3 [Matrix] 1 2 3 [HostTopN] 1, 10, 3600 2, 25, 30 END.
Ethernet Profile Token Ring Field Descriptions Token Ring Field Descriptions In this enhanced version of Sample B, descriptions have been added for all fields in the profile. [OwnerString] Field identifier for the owner string specifier which follows. This must appear exactly as shown. csi-defaults The owner string. Assign a meaningful name, without spaces. [MacStats] Field identifier for the Mac-Layer Statistics Group specifiers which follow. This must appear exactly as shown.
Ethernet Profile Token Ring Field Descriptions [Host] Field identifier for the Host Group specifiers which follow. This must appear exactly as shown. An instance of the Host Group may be configured for each network interface monitored by the RMON agent. 1 2 3 [Matrix} Host Group specifiers. This example creates an instance of Host for 3 of the network interfaces of the TRMM. Field identifier for the Matrix Group specifiers which follow. This must appear exactly as shown.
Using a Wildcard to Specify All Network Interfaces Using a Wildcard to Specify All Network Interfaces If you want to specify that all interfaces should be included in a sample, substitute an asterisk where you would normally specify the network interface, as shown in the following example. [EnetStats] * [History] *, 120, 30 *, 120, 1800 This example creates an instance of Statistics for all network interfaces monitored by the RMON agent.
Using a Wildcard to Specify All Network Interfaces Sample Profiles D-8 Standard RMON Management Module Guide
Appendix E Object Identifiers (OIDs) This chapter describes object identifiers (OIDs) of RMON objects that you can monitor, using the RMON Alarms feature. See Configuring RMON Alarms and Events for detailed information about using OIDs with alarms. etherStats OID Object Name 1.3.6.1.2.1.16.1.1.1.1 etherStatsIndex 1.3.6.1.2.1.16.1.1.1.2 etherStatsDataSource 1.3.6.1.2.1.16.1.1.1.3 etherStatsDropEvents 1.3.6.1.2.1.16.1.1.1.4 etherStatsOctets 1.3.6.1.2.1.16.1.1.1.5 etherStatsPkts 1.3.6.1.2.1.16.1.
historyControl historyControl OID Object Name 1.3.6.1.2.1.16.2.1.1.1 historyControlIndex 1.3.6.1.2.1.16.2.1.1.2 historyControlDataSource 1.3.6.1.2.1.16.2.1.1.3 historyControlBucketsRequested 1.3.6.1.2.1.16.2.1.1.4 historyControlBucketsGranted 1.3.6.1.2.1.16.2.1.1.5 historyControlInterval 1.3.6.1.2.1.16.2.1.1.6 historyControlOwner 1.3.6.1.2.1.16.2.1.1.7 historyControlStatus etherHistory OID Object Name 1.3.6.1.2.1.16.2.2.1.1 etherHistoryIndex 1.3.6.1.2.1.16.2.2.1.
hostControl OID 1.3.6.1.2.1.16.4.1.1.
host host OID Object Name 1.3.6.1.2.1.16.4.2.1.1 hostAddress 1.3.6.1.2.1.16.4.2.1.2 hostCreationOrder 1.3.6.1.2.1.16.4.2.1.3 hostIndex 1.3.6.1.2.1.16.4.2.1.4 hostInPkts 1.3.6.1.2.1.16.4.2.1.5 hostOutPkts 1.3.6.1.2.1.16.4.2.1.6 hostInOctets 1.3.6.1.2.1.16.4.2.1.7 hostOutOctets 1.3.6.1.2.1.16.4.2.1.8 hostOutErrors 1.3.6.1.2.1.16.4.2.1.9 hostOutBroadcastPkts 1.3.6.1.2.1.16.4.2.1.10 hostOutMulticastPkts hostTime OID Object Name 1.3.6.1.2.1.16.4.3.1.1 hostTimeAddress 1.3.6.1.2.1.16.4.
matrixSD matrixSD OID Object Name 1.3.6.1.2.1.16.6.2.1.1 matrixSDSourceAddress 1.3.6.1.2.1.16.6.2.1.2 matrixSDDestAddress 1.3.6.1.2.1.16.6.2.1.3 matrixSDIndex 1.3.6.1.2.1.16.6.2.1.4 matrixSDPkts 1.3.6.1.2.1.16.6.2.1.5 matrixSDOctets 1.3.6.1.2.1.16.6.2.1.6 matrixSDErrors matrixDS OID Object Name 1.3.6.1.2.1.16.6.3.1.1 matrixDSSourceAddress 1.3.6.1.2.1.16.6.3.1.2 matrixDSDestAddress 1.3.6.1.2.1.16.6.3.1.3 matrixDSIndex 1.3.6.1.2.1.16.6.3.1.4 matrixDSPkts 1.3.6.1.2.1.16.6.3.1.
hostTopN hostTopN OID Object Name 1.3.6.1.2.1.16.5.2.1.1 hostTopNReport 1.3.6.1.2.1.16.5.2.1.2 hostTopNIndex 1.3.6.1.2.1.16.5.2.1.3 hostTopNAddress 1.3.6.1.2.1.16.5.2.1.4 hostTopNRate alarm OID Object Name 1.3.6.1.2.16.3.1.1.1 alarmIndex 1.3.6.1.2.16.3.1.1.2 alarmInterval 1.3.6.1.2.16.3.1.1.3 alarmVariable 1.3.6.1.2.16.3.1.1.4 alarmSampleType 1.3.6.1.2.16.3.1.1.5 alarmValue 1.3.6.1.2.16.3.1.1.6 alarmStartupAlarm 1.3.6.1.2.16.3.1.1.7 alarmRisingThreshold 1.3.6.1.2.16.3.1.1.
log log OID Object Name 1.3.6.1.2.1.16.9.2.1.1 logEventIndex 1.3.6.1.2.1.16.9.2.1.2 logIndex 1.3.6.1.2.1.16.9.2.1.3 logTime 1.3.6.1.2.1.16.9.2.1.4 logDescription tokenRingMLStats OID 9031280 E4 Object Name 1.3.6.1.2.1.16.1.2.1.1 tokenRingMLStatsIndex 1.3.6.1.2.1.16.1.2.1.2 tokenRingMLStatsDataSource 1.3.6.1.2.1.16.1.2.1.3 tokenRingMLStatsDropEvents 1.3.6.1.2.1.16.1.2.1.4 tokenRingMLStatsMacOctets 1.3.6.1.2.1.16.1.2.1.5 tokenRingMLStatsMacPkts 1.3.6.1.2.1.16.1.2.1.
tokenRingPStats tokenRingPStats OID 1.3.6.1.2.1.16.1.3.1.1 Object Name tokenRingPStatsIndex 1.3.6.1.2.1.16.1.3.1.2 tokenRingPStatsDataSource 1.3.6.1.2.1.16.1.3.1.3 tokenRingPStatsDropEvents 1.3.6.1.2.1.16.1.3.1.4 tokenRingPStatsDataOctets 1.3.6.1.2.1.16.1.3.1.5 tokenRingPStatsDataPkts 1.3.6.1.2.1.16.1.3.1.6 tokenRingPStatsDataBroadcastPkts 1.3.6.1.2.1.16.1.3.1.7 tokenRingPStatsDataMulticastPkts 1.3.6.1.2.1.16.1.3.1.8 tokenRingPStatsDataPkts18to63Octets 1.3.6.1.2.1.16.1.3.1.
tokenRingPHistory OID Object Name 1.3.6.1.2.1.16.2.3.1.15 tokenRingMLHistoryLineErrors 1.3.6.1.2.1.16.2.3.1.16 tokenRingMLHistoryInternalErrors 1.3.6.1.2.1.16.2.3.1.17 tokenRingMLHistoryBurstErrors 1.3.6.1.2.1.16.2.3.1.18 tokenRingMLHistoryACErrors 1.3.6.1.2.1.16.2.3.1.19 tokenRingMLHistoryAbortErrors 1.3.6.1.2.1.16.2.3.1.20 tokenRingMLHistoryLostFrameErrors 1.3.6.1.2.1.16.2.3.1.21 tokenRingMLHistoryCongestionErrors 1.3.6.1.2.1.16.2.3.1.22 tokenRingMLHistoryFrameCopiedErrors 1.3.6.1.2.1.
ringStationControl ringStationControl OID Object Name 1.3.6.1.2.1.16.10.1.1.1 ringStationControlIfIndex 1.3.6.1.2.1.16.10.1.1.2 ringStationControlTableSize 1.3.6.1.2.1.16.10.1.1.3 ringStationControlActiveStations 1.3.6.1.2.1.16.10.1.1.4 ringStationControlRingState 1.3.6.1.2.1.16.10.1.1.5 ringStationControlBeaconSender 1.3.6.1.2.1.16.10.1.1.6 ringStationControlBeaconNAUN 1.3.6.1.2.1.16.10.1.1.7 ringStationControlActiveMonitor 1.3.6.1.2.1.16.10.1.1.8 ringStationControlOrderChanges 1.3.6.1.
ringStationOrder ringStationOrder OID 1.3.6.1.2.1.16.10.3.1.1 Object Name ringStationOrderIfIndex 1.3.6.1.2.1.16.10.3.1.2 ringStationOrderOrderIndex 1.3.6.1.2.1.16.10.3.1.3 ringStationOrderMacAddress ringStationConfigControl OID 1.3.6.1.2.1.16.10.4.1.1 Object Name ringStationConfigControlIfIndex 1.3.6.1.2.1.16.10.4.1.2 ringStationConfigControlMacAddress 1.3.6.1.2.1.16.10.4.1.3 ringStationConfigControlRemove 1.3.6.1.2.1.16.10.4.1.
sourceRoutingStats sourceRoutingStats OID Object Name 1.3.6.1.2.1.16.10.6.1.1 sourceRoutingStatsIfIndex 1.3.6.1.2.1.16.10.6.1.2 sourceRoutingStatsRingNumber 1.3.6.1.2.1.16.10.6.1.3 sourceRoutingStatsInFrames 1.3.6.1.2.1.16.10.6.1.4 sourceRoutingStatsOutFrames 1.3.6.1.2.1.16.10.6.1.5 sourceRoutingStatsThroughFrames 1.3.6.1.2.1.16.10.6.1.6 sourceRoutingStatsAllRoutesBroadcastFrames 1.3.6.1.2.1.16.10.6.1.7 sourceRoutingStatsSingleRouteBroadcastFrames 1.3.6.1.2.1.16.10.6.1.
Appendix F Reports This appendix describes the Report Information Block (.rib) files included with the RMON Management Module. The .rib files allow you to generate reports that display segment activity using RMON data from your probe device. Report Description RMON reports are run for a network segment using an RMON Probe model which is a Monitor Point for that segment. The data reported is RMON data from the Statistics Groups of your probe device.
SetUp Statistical Reports SetUp Monitor Point Only a Probe model which has been copied into the corresponding Network model as a Monitor Point can be used to run RMON Reports for that network segment. It is not necessary that the Probe model be selected as the current Monitor Point, only that it has been copied in as a candidate. For information on how to make a Probe model a Monitor Point, please refer to Section 2.4, Configuring RMON as a Network Monitor Point.
SetUp Statistical Reports Standard Reports Two report generation (rib) files are provided with the RMON management module, one for Ethernet and one for Token Ring. These report the segment performance data seen in the Spectrum Performance View of a Network model when the Probe model is the Monitor Point. .../CsRib/RMONEthProbe/EProbePerf.rib Performance View LabelAttributeAttributeID LoadMonUtilization0x10207 Frame RateMonPacketRate0x10093 % ErrorsMonErrorRate0x10094 % CollisionsMonCollisionRate0x1024c ..
SetUp Sample Statistical Report Output File 4. Select Statistical as the Report type. The main window shows the selections for a Statistical Report. This information needs to be completed based on the Report Generator User’s Guide. 5. Click Generate. You will be prompted to specify report time frame parameters and a report output filename. When the report completes, it is placed in the SpectroGRAPH (SG) directory. The statistical report file is in the CsRib/ directory.
Index Symbols “Profile processing completed” 3-4, 3-6 Numerics 802.
I P In Octets A-7 In Packets A-7 Insertion B-13 interface B-11 internal errors 5-24, B-2 parsing mechanism 3-5 Poll Log Ratio 7-5 Polling (time) Interval 7-5 Profile Load/Unload error conditions 3-5 J R Jabbers A-4 receive congestion errors B-14 Remote Network Monitoring 1-2 Reports F-1 ReqSize A-10 Restricted Rights Notice ii, iv ring poll events B-3, B-5 ring purge MAC packets B-5 RMON Alarms/Events 4-3 RMONApp 1-4 L line errors B-5 lost frame errors B-5 lost frames 5-24, B-2 M Matrix Control 4-3
