Handbook of Local Area Networks, 1998 Edition:LAN Management Click Here! Search the site:   ITLibrary ITKnowledge EXPERT SEARCH Programming Languages Databases Security Web Services Network Services Middleware Components Operating Systems User Interfaces Groupware & Collaboration Content Management Productivity Applications Hardware Fun & Games EarthWeb sites Crossnodes Datamation Developer.com DICE EarthWeb.com EarthWeb Direct ERP Hub Gamelan GoCertify.com HTMLGoodies Intranet Journal IT Knowledge IT Library JavaGoodies JARS JavaScripts.com open source IT RoadCoders Y2K Info Previous Table of Contents Next TOKEN RING RMON MIB Because of the popularity of the Ethernet RMON standard, several Token Ring vendors established the RFC 1513 Internet standard. Four of the categories established integrate the statistics and history groups with Token Ring parameters (see Exhibit 7-1-4). The Token Ring media access control (MAC) level and promiscuous statistics categories make up the Token-Ring specific categories within statistics and history. The other four categories address the inherent management functionality within the Token Ring standard. For example, the Token Ring standard designates an active monitor for each ring that notes behavior on the overall ring. The IEEE 802.5 standard also provides for a beacon frame that detects errors on the ring. Ring Station Control Table. This category serves as the keeper of status information for each ring being monitored. It looks at the ring state, active monitor, and number of active stations. Ring Station Table. This category gathers information for each station (e.g., error statistics ) on a local ring. Because the token circulates around the ring constantly, it is necessary to monitor the health of each station. This category tracks beaconing stations and the active monitor. Ring Station Order. This category collects information in logical ring order sequence. It is, therefore, critical to providing information about the performance of a particular ring. Ring Station Configuration Control. This category collects station configuration information. It examines: •  The station’s MAC address. •  The physical location of the node. Using this information, the probe may actively remove any station on the monitored ring. This category provides fault and configuration information to network administrators. Source Routing. This category measures source routing statistics. Source routing enables the determination of a fixed route between the source ring and the final destination ring. It provides data on the number of hops between rings and whether the packet originated on the ring or is on its way to the final destination. THE FUTURE OF RMON RMON has been quite successful, and RMON2 is currently in draft form and scheduled for approval in late 1996. RMON2, unlike many other standards, is interoperable with RMON. RMON2 adds several new groups and provides a more efficient software product. Exhibit 7-1-5 shows a tree diagram for RMON2. Exhibit 7-1-5.  RMON2 New Groups in RMON2 Following is a list of the new groups in RMON2 and their functions: •  Protocol Directory. This group provides a list of protocols that the RMON agent is capable of decoding and counting. •  Protocol Distribution. This group represents the traffic amount for the protocols defined in the protocol directory. •  Address Map. This group maps network layer addresses to physical addresses of the interface. •  Network Layer Host. This group characterizes network layer traffic to and from a specific network node. •  Network Layer Matrix. This group characterizes network layer traffic between two addresses and allows tracking number of packets sent between two hosts. •  Application Layer Host. This group characterizes application layer traffic to and from a specific network node and tracks which host sends packets of a specific application, such as Lotus Notes or SAP’s R/3. •  Application Layer Matrix. This group characterizes application layer traffic between two addresses and tracks which two hosts sent packets of a particular application. •  User History. This group represents a historical study of user-defined variables. •  Probe Configuration. This group represents a configuration of agent addresses, traps, serial ports, and software and provides standard configuration parameters for probes and therefore eases interoperability between RMON and RMON2 probes. Previous Table of Contents Next Use of this site is subject certain Terms & Conditions. Copyright (c) 1996-1999 EarthWeb, Inc.. All rights reserved. Reproduction in whole or in part in any form or medium without express written permission of EarthWeb is prohibited. Please read our privacy policy for details.