Avaya RMON, RMON2 User Manual

Download

Page 1

Configuring RMON and RMON2

BayRS Version 13.0 0 Site Manager Software Version 7.00

BCC Version 5.04

Part No. 303539-A Rev 00 October 1998

Page 2

4401 Great America Parkway 8 Federal Street Santa Clara, CA 95054 Billerica, MA 01821

and recomm endations in this docum ent are believed to be accurate and reliable, but are presented without express or implied warranty. U sers must take full respons ibility for their applications of any products specified in this do cum ent. The information in this document is proprietary to Bay Networks, Inc.

The software described in this document is furnished under a license agreement and may only be used in accordance with the te rms of that license. A summary of the Soft w are License is include d in this docum ent.

Trademarks

ACE, AFN, AN, BCN, BLN, BN, BNX, CN, FRE, LN, Optivity, PPX, Quick2Config, and Bay Networks are registered tradema rks and Advanced Remote Node, ANH, ARN, ASN, BayRS, BaySecure, BayStack , BayStr eam, BCC, BCNX, BLNX, EZ Install, EZ Internetwork, EZ LAN, FN, IPAutoLearn, PathMan, RouterMan, SN, SPEX, Switch Node, System 5000, and the Bay Netw orks logo are trademarks of Bay Networks, Inc.

Microsoft , MS, MS-DOS, Win32, Windows, and Windows NT ar e registered trade m arks of Micro soft Corporation. All other trademarks and registered trademarks are the property of their respective owners .

Restricted Rights Legend

Use, duplication, or disclosure by the United States Government is subject to restrict ions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.

Notwithstanding any other license agreement th at may pertain to, or accompany the delivery of, this computer software, the ri ghts of the Un ited States Gove rnment re garding its use, reproduction, and disclosure are as set forth in the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.

Statement of Conditions

In the interest of improving internal design, operational function, and/or reliability, Bay Networks, Inc. reserves the right to make changes to the products described in this document without notice.

Bay Networks, Inc. does not assume an y liability that may occur due to the use or applic ation of the product(s) or circuit layout(s) described herein.

Portions of the code in this software product may be Copyright © 1988, Regents of the University of California. All rights reserve d. Redistribution and use in source and binary forms of such portions are permitted, provided that the above copyright notice and this paragrap h are duplicated in all su ch forms and th at any docume ntation, adverti sing materials, and other materials related to such distribution and use acknowledge that such portions of the software were deve loped by th e U niversity of California, Berkeley. The nam e of the University may not be used to endorse or promote products derived from such portions of the software without specific prior written permission.

SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIE D WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

In additi on, the program and information contained herein are li censed only pursuant to a license agreement that contains restrictions on use and disclosu re (that may incorporate by reference cert ain limitations and not ices imposed by thir d pa rt ie s).

303539-A Rev 00

Page 3

Bay Networks, Inc. Software License Agreement

NOTICE: Please carefully read this license agreement before copying or using the acco m p anying software or instal ling the hardware unit with pre-enabled software (e ach of which is referred to as “Softw are” in this Agreement). BY COPYING OR USING THE SOFTWARE, YOU ACCEPT ALL OF THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT. THE TERMS EXPRESSED IN THIS AGREEMENT ARE THE ONLY TERMS UNDER WHICH BAY NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE. If you do not accept these terms and conditions, return the product, unused and in the o riginal shipping container, within 30 days of purchas e to obtain a credit for the full purchase price.

1. License Grant. Bay Networks, Inc. (“Bay Networks”) gra nts the end user of the Software (“Lice nsee”) a personal, nonexcl usive, nontransferable license: a) to use the Software either on a single computer or, if applicable, on a single authori zed de vi ce ide ntified by host ID, fo r whi ch it was origi nal ly acq uired ; b) to cop y th e Softw ar e so le ly fo r bac kup purposes in support of authorized us e of the Software; and c) to use and copy the associat ed user manual solely in support of authorized use of the Soft w are by Licensee. This li cense applies to the Software only and does not extend to Bay Networks Agent software or other Bay Networks softw are products. Bay Networks Agent software or other Bay Networks software products are licensed for use under the terms of the applicable Bay Networks, Inc. Software License Agreement that accompanies such software and upon payment b y the end user of the applicable licen se fees for such software.

2. Restrictions on use; reservation of rights. The Software and user manuals are prote cted under copyright laws. Bay Networks and/or its licensors retain all title and ownership in both the Software and user manuals, including any revis ions made by Bay Networks or its licensors. The copyright notice must be reproduced and included wi th any copy of any por tion of the Sof tw are or use r manua ls . Licens ee may not modif y, translate, dec ompi le , disas se mble , use for any compe ti ti v e an al ysis, r e v erse e ngi ne er , dis tr ib ute , o r c rea te der i vative work s f ro m the Softw are or u se r man ual s or any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or transfer the Softw are or user man uals, in whole or in part. The Software and user manuals embody Bay Ne tworks’ and its licenso rs’ confidential and proprietary intell ectual property. Licensee shall not sublicense, assig n, or otherwise disclos e to any third party the Software, or any information about the ope ration, design, performance, or implementation of the Software and user manuals that is confidential to Bay Networks and its li censors; howe ver, Licensee m ay grant permission to its consul tants, subcontractors, and agents to use the Software at Licensee’ s facility, provided they have agreed to use the Software only in accordance with the terms of t his license.

3. Limited warranty. Bay Networks warrants each item of Software, as delivered by Bay Network s and properly installed and operated on Bay Networks hardware or other equipment it is original ly licensed for, to function substantially as described in i ts accompan ying user manual during its warranty period, wh ich begins on the date Softwar e is fi r st shi pped to Licen see . If any it em of Soft war e fai ls to so func ti on du ring i ts warr anty pe ri od, as t he so le remedy Bay Ne tworks will at its discretion provide a suitable fix, pat ch, or worka round for the problem tha t m ay be included in a future Software release. Bay Networks further warrants to Licensee that the media on which the Softwar e is provided will be fr ee from defects in materials and workmanship under normal use for a period of 90 days from the date Software is first shipped to Licensee. Bay Networks will replace defective media at no charge if it is returned to Bay Netw orks during the warranty per iod along with proof of the date of shipmen t. This warran ty does not apply i f the media has been damaged as a result of acci dent, misuse, or abuse. The Licensee assumes all re sponsibility for selection of the Software to achieve Licensee’s intended results and for the installation, use, and results obtained from the Software. Bay Networks does not warrant a) that the functions cont ained in the software w ill meet the Licensee ’s requirements, b) that the Software will operate in the har dw are or software combinat ions that the License e may select, c) that the operati on of the Softw are will be uninterrupted or error free, or d) that all defects in the operati on of the Software wi ll be corrected. Bay Networks is not ob ligated to remedy any Software defect that cannot be repro duced with the latest Software release. These warranties do not apply to the Sof tware if it has been (i) a ltered, except by Bay Networks or in accordance with its instructions; (ii) used in conjunction with another vendor’s product, resulting in the defect; or (iii) damaged by im proper environment, abuse, misuse, accident , or neglige n ce. THE FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of

303539-A Rev 00

iii

Page 4

its own data and information and for maint aining adequate procedures apart from the Software to reconstr uct lost or altered files, data, or programs.

4. Limitati on of liabili ty. IN NO EVENT WILL BAY NETWORKS OR ITS LICENSORS BE LIABLE FOR ANY COST OF SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ; OR ANY DAMAGES RESULTING FROM INACCURATE OR LOST DATA OR LOSS OF USE OR PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN IF BAY NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT SHALL THE LIABILITY OF BAY NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT EXCEED THE PRICE PAID TO BAY NETW ORKS FOR THE SOFTWARE LICENSE.

5. Governmen t L icensees. This provision applies to all Softw are and documentation acquired directly o r indirectly by or on behalf of the United States Government. The Software and documentation are commercial products, licensed on the open market at market prices, and were developed entirely at private expense and without the use of any U.S. Government funds. The licens e to the U.S. Government is granted only with restricted rights, and use, duplication, or disclos ure by the U.S. Gover n m ent is subject to the restrictions set forth in subparagraph (c)(1) of the Com m ercial Computer So ftware––Restricted Rights clause of FAR 52.227-19 and the limitations set out in this license for civilian agencies , and subparagraph (c) (1)(ii) of the Rights in Technical Data and Computer Software clause of DFARS

252.227-7013, for agencies of t he D e partment of Defense or their suc cessors, whiche ver is applicable.

6. Use of Software in the European Communi ty. This provision applies to all Software acquired for use within the European Comm unity. If Lice nsee uses the Software within a countr y in the European Community, the Softwar e Directive enacted by the Counc il of European Communities Directive dated 14 May, 1991, will apply to the examination of the Software to facilitate interoperability. License e agrees to notify Bay Networks of any such intended examination of the Software and may procure support and assistance from Bay Networks.

7. Term and termination. This license is effective until terminated; however, all of the restrictions with respect to Bay Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the Bay Networks copyright; those r estrictions relating to use and disclosure of Bay N etworks’ confidential information shall continue in effect. Licensee may terminate this license at any time. The license will automatically terminate if Licensee fails to co m ply with any of the terms and conditions of the license. Upon terminat ion for any reason, Licensee will immediately destroy or return to Bay Networks the Software, user manuals, and all copies. Bay Networks is not liable to Licensee for damages in any form solely by reason of the termination of this license.

8. Export and Re-export. Licensee agrees not to export, directly or indirectly, the Software or related technical data or information without first obtaining any required export licenses or other governmental approvals. Without limiting the fore going, Licensee, on behalf of itself and its subsidiaries and affiliates, agrees that i t will not, without first obtaining all export licenses and appro vals required by the U.S. Government: (i) export , re-export, trans fer, or diver t any such Sof tware or technical data, or any direct product thereof, to any coun try to which such exports or re-exports are rest ricted or embargoed under United States ex port control laws a nd regulations, or to any national or resident of such rest ricted or embargoed countries; or (ii) provide the Software or related technical data or inf ormation to any military end user or for any military end use, including the design, development, or prod uction of any chemical, nuclear, or biological weapons.

9. General. If any provision of this Agreement is held to be invalid or unenforceable by a court of competent jurisdiction, the remainder of the provisions of this Agreement shall remain in full force and effect. This Agreement will be governed by the laws of the state of California.

Should you have any questions concerning this Agreement, contact Bay Networks, Inc., 440 1 G reat America Parkway, P.O. Box 58185, Santa Clara, Californi a 95054-8185.

LICENSEE ACKNOW LEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FUR THER AGREES THAT THIS AGREEMENT IS THE ENTIRE AND EXCLUSIVE AGREEMENT BETWEEN BAY NETWORKS AND LICENSEE, WHICH SUPERSEDES ALL PRIOR ORAL AND WRITTEN AGREEMENTS AND COMMUNICATIONS BETWEEN THE PARTIES PERTAINING TO THE SUBJECT MATTER OF THIS AGREEMENT. NO DIFFERENT OR ADDITIONAL TERMS WILL BE ENFORCEABLE AGAINST BAY NETWORKS UNLESS BAY NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT , INCLUDING AN EXPRESS WAIVER OF THE TERMS OF THIS AGREEMENT.

303539-A Rev 00

Page 5

Preface

Before You Begin ............................................................................................................. xiii

Text Conventions .................................... ....................................................................... ..x iv

Acronyms ......................................................................................................................... xv

Bay Networks Technical Publications ..............................................................................xvi

How to Get Help ..............................................................................................................xvi

Chapter 1 RMON and RMON2 Overview

RMON MIB .....................................................................................................................1-1

RMON2 MIB ...................................................................................................................1-3

RMON and RMON2 Support on Bay Networks Routers ................................................ 1-8

RMON and RMON2 Architecture ...................................................................................1-9

Data Collection Module (DCM) ..............................................................................1-11

DCM Agent Software ......................... ..... .. ..... ..... ..... .... ..... ..... .. ..... .. ..... .. ..... ..... .. ....1-11

DCM Middleware (DCMMW) ............ ........................................... ...........................1-11

RMON Agent Software ...........................................................................................1-11

RMON Network Management Software ................................................................. 1-12

Optivity Analysis for UNIX ................................................................................1-12

Optivity LAN .....................................................................................................1-15

Optivity Analysis for Windows NT ....................................................................1-16

Chapter 2 Starting RMON and RMON2 on AN/ANH and ARN Routers

Router Hardware and Software Prerequisites ................................................................2-2

Starting Configuration Tools ...........................................................................................2-4

303539-A Rev 00

Page 6

Starting RMON and RMON2 ..........................................................................................2-4

Preparing a Configuration File .................................................................................2-4

Configuring an Ethernet DCM for AN/ANH Routers .................................................2-5

Configuring an Ethernet DCM for ARN Routers ....................................................... 2-7

Customizing the Ethernet DCM ...................................................................................... 2-9

Chapter 3 Configuring Mini-RMON on an ARN 100 Router

Configuration Considerations .........................................................................................3-2

Starting Mini-RMON .......................................................................................................3-2

Preparing a Configuration File .................................................................................3-3

Enabling Mini-RMON Data Collection ......................................................................3-3

Disabling Mini-RMON Data Collection ............................................................................ 3-5

Chapter 4 Customizing a DCM for RMON and RMON2

Disabling the Ethernet DCM ...........................................................................................4-2

Specifying RMON or RMON2 Data Collection ...............................................................4-3

Specifying the Configuration Mode .................................................................................4-6

Saving the Config uration Infor mation .............................................................................4-7

Configuring the DCM Image on the Router ....................................................................4-9

Modifying Default RMON MIB Group Parameters ........................................................4-12

Specifying the Maximum Number of RMO N Hosts ................................................4-12

Enabling and Disabling the RMON Host Control Table ..........................................4 -14

Enabling and Disabling the RMON Matrix Control Table ........................................4-16

Rebooting the Ethernet DCM .......................................................................................4 -18

Deleting the Ethernet DCM Software Subsystem ......................................................... 4 -19

Using the Technician Interface to Manage a DCM ....................................................... 4 -20

Appendix A Monitoring the DCM Using the BCC show Command

show rmon dcm ............................................................................................................. A-2

303539-A Re v 00

Page 7

Appendix B Ethernet DCM Parameters

Appendix C RMON and RMON2 MIB Groups

RMON MIB Groups .......................................................................................................C-1

RMON MIB Group Controls and Functi ons .............................................................C-2

Statistics Group .......................................................................................................C-2

History Group ...................................................... ....................................................C-2

Host Group ..............................................................................................................C-3

HostTopN Group .....................................................................................................C-3

Matrix Group .......................................................................... ....... .. ....... .......... .......C-3

Filter Group .............................................................................................................C-3

Capture Group .............................................................................. .. ....... .......... .......C-4

Alarm Group .......................................................................................................... ..C-4

Event Group ............................................................................................................C-5

Event Trap Considerations ................................................................................C-6

RMON2 MIB Groups .....................................................................................................C-6

Protocol Directory Group .................................................. ....... ....... ..... ....... ....... .....C-7

Protocol Distribution Group .................................................................... .......... .. .....C-8

Address Mapping Group ...................................................................... ....... ....... .....C-9

Network Layer Host Group ......................................................................................C-9

Application Layer Host Group .................................................................................C-9

Network Layer Matrix Group ........................................ .......... ....... ....... .. .......... .......C-9

Application Layer Matrix Group .............................................................................C-10

Memory Requirements for RMON Groups . .................................................................C-11

Statistics Group .....................................................................................................C-12

History Group ...................................................... ..................................................C-12

Host Group ............................................................................................................C-13

HostTopN Group ...................................................................................................C-14

Matrix Group .......................................................................... ....... .. ....... .......... .....C-14

Filter and Capture Groups .....................................................................................C-15

Alarm and Event Gr oup s .................... ...................................................................C-16

303539-A Rev 00

vii

Page 8

Appendix D Upgrading the DCM Software Image

Verifying Minimum DCM Requirements .........................................................................D-1

Upgrading the DCM Software Image .............................................................................D-2

Using Site Manager .................................................................................................D-3

Using the Technician Interface ................................................................................D-5

Sample Display: dcmload.bat ...........................................................................D-7

Index

viii

303539-A Re v 00

Page 9

Figures

Figure 1 -1. RMON and RMON2 in the OSI Model .....................................................1-4

Figure 1-2. RMON/RMON2 MIB Tree ......................................................................... 1-7

Figure 1-3. RMON/RMON2 Archite cture ..................................................................1-10

Figure C-1. Protocol Directory Statistics ....................................................................C-7

Figure C-2. Protocol Distribution Statistics ................................................................C-8

Figure C-3. Application Layer Matrix Statisti cs ........................................................ C-10

Figure D-1. Choosing DCMMW Global Configuration Parameters ............................D-3

Figure D-2. Edit Base Module DCM Parameters Window ...................... .. ..... ..... .. .....D-4

303539-A Rev 00

Page 10

Page 11

Tables

Table 1-1. RMON MIB Groups ..................................................................................1-2

Table 1-2. RMON2 MIB Groups ............................................................................... 1-5

Table 1-3. Summary of RMON and RMON2 Support ............................................... 1-8

Table 1-4. Optivity Analysis for UNIX RMON-Based Tools ....................................1-13

Table 2-1. AN/ANH Requirements for Using RMON and RMON2 ............................2-2

Table 2-2. ARN Requirements for Using RMON and RMON2 .................................2-3

Table C-1. DRAM and RMON Memory Size .........................................................C-11

Table C-2. Maximum Number of Hosts .................................................................. C-13

Table C-3. Default Si ze for Captu re Buffer .............................................................C-15

303539-A Rev 00

Page 12

Page 13

Preface

This guide describes configuring and managing an Ethernet remote monitoring (RMON) data colle ction module (DCM) in a Bay Networks BayStack™ router. The BayStack family of routers includes the following platforms:

• Access Node (AN

• Access Node Hub (ANH

• Advanced Remote Node

)

™

)

™

(ARN™)

You can use the Bay Command Console (BCC RMON and RMON2 on a router. In this guid e, you will f i nd instructio ns for using both the BCC and Site Manager.

Before You Begin

Before using this guide, you must complete the following procedure s. For a new router:

• Install the router (re fer t o the installation guide that came with your router).

• Connect the route r to the net work a nd create a pilot configuration file (refer to Quick-Starting Routers or Configuring BayStack Remote Access).

Make sure tha t you are running the latest version of Bay Networks BayRS Site Manager software. For information about upgrading BayRS and Site Manager, see the upgr ading guide for your version of B ayRS.

™

) or Site Manager to configure

™

and

303539-A Rev 00

xiii

Page 14

Configuring RMON and RMON2

Text Conventions

This guide use s the following text conventions:

angle brackets (< >) Indicate that you choose the text to enter based on the

description inside the brackets. Do not type the brackets when entering the command. Example: If the command syntax is:

bold text

<ip_address>

ping ping 192.32.10.12

Indicates text tha t you need to enter and command

, you enter:

names and options. Example: Enter

Example: Use the

show ip {alerts | routes

command.

dinfo

}

italic text Indicates file and directory names, new terms, book

titles, and variables in command syntax descriptions. Where a variable is two or more words, the words are connected by an underscore. Example: If the command syntax is:

show at

valid_route

valid_route>

is one va riable and you subs titu te one value

for it.

screen text Indicates system output , fo r exa mple, prompts and

system messages. Example:

Set Ba y Netw orks Tr ap Mo nito r Fil ters

separator ( > ) Shows menu paths.

Example: Protocol s > IP identifies the IP option on the Protocols menu.

xiv

vertical line (

) Separates choices for command keywords and

arguments. Enter only one of the choices. Do not type the vertical line when entering the command. Example: If the command syntax is:

, you enter either:

show ip {alerts | rou tes show ip alerts

}

show ip routes

, but not both.

303539-A Re v 00

Page 15

Acronyms

Preface

ASN.1 abstract syntax nota tion CMIP Common Management Information Prot oc ol DCM data collection modu le DCMMW data collection modu le middleware DLCI data link control int erface DRAM dynamic random access memory FDDI Fiber Distributed Data Interface IP Internet Protocol LRU least recently used MAC media access c ontrol MIB management information base NVRAM nonvolatile random acce s s memo r y

303539-A Rev 00

PDU protocol data unit PVC permanent virtual circuit RFC Request for Comments RIP Routing Informati on Protocol RMON remote monitoring SNMP Simple Network Management P rotocol TFTP Trivial File Transfer Protocol UDP User Datagram Protocol WAN wide area network

Page 16

Configuring RMON and RMON2

Bay Netwo rks Technical Publicati o ns

You can now print Bay Networks technical manuals and release notes free, directly from the Int ernet. Go to support.bayn etworks.com/libr ary/tpubs/. Fi nd the Bay Networks product for which you need doc umenta tion. Then locate the specific category and model or version for your hardwa re or software product. Using Adobe Acrobat Reader, you can open the manuals and release notes, search for the sections you need, and print them on most standard printers. You can download Acrobat Reader free from the Adobe Systems Web site, www.adobe.com.

You can purchase Bay Networks documentation sets, CDs, and selected technic al publications through the Bay Networks Collateral Catalog. The catalog is located on the World Wide Web at support.baynetworks.c om/catalog. html and is divided into sections arran ged alpha betically:

• The “CD ROMs” section lists available CDs.

• The “Guides/Boo ks” section lists books on technical topi cs.

• The “Technical Manuals” section lists available printed documentation sets.

Make a note of the part num bers and prices of the items that you want to order. Use the “Marketing Collateral Catalog description” link to place an order and to print the order form.

How to Get Help

For product assista nce, support contracts, or information about educational services, go to the following URL:

http://www.baynetworks.com/corporate/contacts/

Or telephone the Bay Networks Technical Solutions Center at: 800-2LANWAN

xvi

303539-A Re v 00

Page 17

Chapter 1

RMON and RMON2 Overview

RMON and RMON2 are MIB standards develop ed to provide powerful remo te troubleshooting and monitoring within a LAN segment and across an enterprise network. This chapter includes the following inf ormation:

T opic Page

RMON MIB

RMON MIB RMON2 MIB 1-3 RMON and RMON2 Support on Bay Networks Routers 1-8 RMON and RMON2 Architecture 1-9

RMON is a standard MIB that defines current and histor ical statistics and control objects at th e media acce ss cont rol (MAC) layer, allo win g you to ca pture r eal-ti me information across the enti re network. The RMON standard is an SNMP MIB definit ion described in RFC 1757 (formerly 1271) for Ethernet .

The RMON MIB provides a standard method for monitor ing the basic operations of the Ethernet network, providing interopera bility between Simple Network Management (SNMP) management stati ons and monitor ing agents. RMON also provides a powe rful alarm and eve nt mechanism for setting thresholds and for notifying you of changes in network behavior.

You can use RMON to analyze and monitor network traffic data within remote LAN segments from a central location, enabling you to detect, isolate , diagnose, and report potential and actual ne twork problems before they escalate to crisis situations. For example, the Ethernet DCM can identify the hosts on a network that generate the most traffic or errors.

1-1

303539-A Rev 00

1-1

Page 18

Configuring RMON and RMON2

RMON allows you to set up automatic histories, which the RMON agent collects over a period of ti me, pr oviding trending data on such basic statistics as utilization , coll isions, a nd so f orth. Using a netw ork manage ment appli cati on such as Optivity LAN network usage patte rns . Bec ause RMON automates this data collection and provides b etter data to the pla nning process, the process is easier and the outcome more accurate.

Bay Networks implements se v en RMON MIB groups in its RMON agent, and the alarm and ev ent groups in its base module for BayStack AN/ANH and ARN routers. Table 1-1 about the RMON MIB groups, see Appendix C, “

Groups.”

Table 1-1. RMON MIB Groups

Group Lets You

Statistics Analyze the operational effectiveness of your network. Statistics

History Analyze traf fic trends based on hist ori cal data. Host Collect information for each host on the segment. HostTopN Reduce net work overhead by looking at the most active nodes. Matrix Report on traffic and errors between any host pair. Filter Define criteria for capturing specific infor mation. Capture Copy packets for analysis. Alarm Report on changes i n netwo rk ch aract eristi cs bas ed on thre sholds f o r

Event Log events based on thres holds that you define. You can use these

™

or Optivity Analysis™, you can retrieve histories to understand

summarizes the RMON MIB groups. For detailed information

RMON and RMON2 MIB

include pac k ets, octets , br oadca sts, multi casts , dropped pa c kets , sof t errors, and packet size distribution.

any MIB variable of interest.

statistics to initiate functions such as data capture or instance counts to isolate specific portions of your network.

1-2

303539-A Re v 00

Page 19

RMON2 MIB

RMON2 is a standard MIB that extends the scope of the RMON MIB beyond the MAC layer to pro vide statistics on network and applic ation layer traffic (layers 3 through 7 of the OSI model). By monitoring higher-layer protocols, you can get an internetwork or enterprise-wide view of network traffic, enabling you to:

• Identify whic h systems are communicating with which serv ers a nd what

• Identify whic h devices are sending and receiving which types of traffic.

Using this knowl edge of traffi c patterns, you can strateg ic ally place users and resources in the correct loc ation on the network to optimize performance and reduce costs.

Figure 1-1 shows the level of vi sibility that RMON and RMON2 provide within a

LAN segment and within a network at each layer of the OSI model.

RMON and RMON2 Overview

applications the y are using.

303539-A Rev 00

1-3

Page 20

Configuring RMON and RMON2

Layer 4-7

Layer 3

RMON2

Application layer

RMON2

Network layer

E-mail

Lotus Notes

WWW

Layer 2

Layer 1

RMON

MAC layer

Hub

Physical layer

Key

C1 = client 1 C2 = client 2 C3 = client 3

S1 = server 1 S2 = server 2 S3 = server 3

Figure 1-1. RMON and RMON2 in the OSI Model

Other nets

Router

C1 C2 C3

RMN0003A

1-4

303539-A Re v 00

Page 21

RMON and RMON2 Overview

With RMON2, you can also trouble shoot network problems faster and more accurately using statistics from the network layer matrix table, which shows the protocol-specific traffic between communicating pairs of systems.

For example, with RMON, you can learn that a particular server is inactive because it fails to transm it packets. W ith RMON2, you can diagnose the more diff icult problem that occurs when the syste m is active but a particular protocol stack is malfunctioni ng.

RMON2 provides address translation capabilities tha t bind MAC-layer addresses to network-layer addresses, making all addresses easier to read a nd remember. You can detect duplicate addresses, whic h help s to solve a common problem that disrupts network r outers and virtual LANs.

RMON2 allows you to collect the hist orical data of any counter in the system, rather than only a predef ined set of statistics. For example, you can collect historical da ta on a specific file server or a specific router-to-router connection.

RMON2 also lets you configure more flexible and efficient filters to support higher-layer protocols.

303539-A Rev 00

Bay Networks implements seven RMON2 MIB groups in its RMON2 agent for BayStack AN/ANH and ARN routers. Table 1-2

summarizes the RMON2 MIB groups. For more detailed information about the RMON2 MIB groups, see

Appendix C, “

Table 1-2. RMON2 MIB Groups

Group Lets You

Protocol Directory Compile a master dir ectory of all protocols tha t the

Protocol Distrib ution Aggregate statistics on the amoun t of traffic

Address Mapping Connect port numbers, MAC addresses, and

Network Laye r Host Obtain statist ics on the traffi c of specific hosts

RMON and RMON2 MIB Groups.”

Ethernet DCM can interpret.

generated by each protocol, per LAN segment, or for each la yer in the protocol stack.

network addresses.

(in/out, packets, octets, and so forth) based on the network layer address.

(continued)

1-5

Page 22

Configuring RMON and RMON2

Table 1-2. RMON2 MIB Groups

Group Lets You

Application Layer Host Obtain statistics on the traffic of specific hosts

Network Layer Matrix Obtain statistics on the traffic betwee n pairs of hosts

Application Layer Matrix Obtain statistics on the traffic between pairs of hosts

(continued)

(in/out, packets, octets, and so forth) based on the network layer address.

(in/out, packets, octets, and so forth) based on the application layer address.

For more information about RMON2 MIB groups, see Appe ndix C, “RMON and

RMON2 MIB Groups.” Figure 1-2

illustrates the RMON/RMON2 MIB tr ee, showing RMON and

RMON2 MIB groups.

1-6

303539-A Re v 00

Page 23

RMON OID Tree

RMON and RMON2 Overview

MIB

Mib 1

Event

Org

MIB

Capture

Mgmt

ISO

Internet

Root

Private

DoD

alMatrix

alHost

RMON

nlMatrix

nlHost

addressMap

protocolDist

Filter

HostTopN

Host

Key

RMON RMON2

Figure 1-2. RMON/RMON2 MIB Tree

303539-A Rev 00

History

AlarmMatrix

Statistics

protocolDir

RMN0002A

1-7

Page 24

Configuring RMON and RMON2

RMON and RMON2 Support on Bay Networks Routers

Table 1-3 summarizes the three levels of RMON and RMON2 support that Bay

Networks off ers and describes how Bay Networ ks impl ements this support.

T able 1-3. Summary of RMON and RMON2 Support

RMON Support Router Model Configurati on Tasks

RMON alarm and event groups only

Mini-RMON, which includes bui lt-in RMON capability f or the f ollowing RMON MIB groups:

• Statistics

•History

•Alarm

• Event Complete support for all

nine RMON groups and for seven RMON2 groups

All routers (no Ethernet DCM)

ARN 100 (no Ethernet DCM)

• AN/ANH and ARN with Ethernet DCM

• ARN 100 with Ethernet expansion module and Ethernet DCM

You must enable the RMON alarm and event subagent (RAESA) on the router using Technician I nterface commands (see

After yo u enab le a larm and e v ent g roup s on the r out er, you can configure the Threshold Manager in Optivity LAN to set alarms on any integer-based object in the MIB tree. Then you can config ure the F a ult Corr elato r tool in Optiv ity LAN to receive traps when the threshold is exceeded.

Use Site Manager to enable RMON statistics on the ARN 100 base module (see Chapter 3 RMONstat subagent, which contains bot h the statistics and history groups . It also loads the RAESA subagent, which contains the alarm and event groups.

Use Optivity Analysis RMON tools (see Table 1-4 configure, retrieve, and view these RMON st atistics.

Using Site Manager or t he BCC, you must enable the Ethernet DCM (see Chapter 2 foll owing subagents on the router:

• Ethernet DCM

• DCM middleware (DCMMW)

• RAESA Use RMON tools in Optivity Analysis for Windows NT

configure, retrieve, and view RMON and RMON2 statistics .

Using Technician Interface Software

). This action loads the

) to

). This action enables the

1-8

For more information about configuring DCM-enabled RMON, see Chapter2

, “Starting RMON and RMON2 on AN/ANH and ARN Routers.” For inform ation about configur ing mini-RMON on an ARN 100 router, see Chapter 3

“Configuring Mini -RMON on an ARN 100 Router.”

303539-A Re v 00

Page 25

RMON and RMON2 Architecture

The Bay Networks RMON and RMON2 ar chitecture consists of the fol lowing components:

• AN/ANH and ARN base modules and ARN Ethernet expansion modules,

which reside on the router

• DCM, which physically attaches to the router’s base module and contains its

own flash memory module

• DCM agent software , whic h opera tes on the Ethernet DCM

• Data collection module middlewa re (DCMMW), which operates on the

router’s base module

• RMON agent software , whic h opera tes on the router’s base module

• Network manag em en t soft w are, which resides on an RMON network

management station

RMON and RMON2 Overview

The RMON network management station sends SNMP

set

and

commands

get

requesting inf ormation from the DCM agent that resides on the Ethernet DCM on the router. The RMON agent sends the requested infor mation to the network management station, which then processes and displays this infor mation on its console.

Figure 1-3

illustra tes the components of this architecture. The sections that follow

describe them in more detail.

303539-A Rev 00

1-9

Page 26

Configuring RMON and RMON2

RMON Agent

Optivity Enterprise or management software application

DCMMW

Base module

2.0

1.5

1.0

0.5

0.8

0.6

0.4

0.2

0.0

Ethernet LAN

DCM

agent

DCM Flash memory

Ethernet DCM

Network management station

Workstation

Router

segment

WAN

Workstation

Router

1-10

Ethernet LAN

segment

Figure 1-3. RMON/RMON2 Architecture

RMON

data

collection

module

(DCM)

SNM0013A

303539-A Re v 00

Page 27

Data Collection Module (DCM)

The Ethernet DCM, which runs the DCM agent software, physically connects to the BayStack router base module and the ARN Ethernet expansion module. The Ethernet DCM contains a flash memory module for its own boot image and configura tion files.

DCM Agent Software

The DCM agent software resides on a DCM installed on an AN/ANH or ARN router. The DCM agent continually collec ts and analyzes Ethernet data in real time on a single LAN segment (RMON), on groups of LANs (RMON), or on an enterprise network (RMON2). The DCM agent stores the data locally in the Ethernet DCM according to t he RMON specif i cation, defined in RFC 1757, or the RMON2 MIB specificatio n, in compliance with RFC 2021.

You can enable multiple DCM agents running on different segments of the network, with a single network management station controlling and a ccessing them.

RMON and RMON2 Overview

DCM Middleware (DCMMW)

To communicate with the DCM software on the Ethernet DCM, the router uses a software subsys tem, the DCM middleware (DCMMW). This software subs ystem enables and configures an installed Ethernet DCM and allows you to modify the Ethernet DCM configur ation, boot the Ethernet DCM, download the DCM image from the base module to the Ethernet DCM, and disable the Ethe rn et DCM using Site Manager or the BCC. You can use an SNMP-based network management application that suppor ts RMON to view RMON and RMON2 statistics.

RMON Agent Software

The RMON agent software resides on the router’s base module and supports the alarm and ev ent groups on all Bay Networks routers. The RMON agent softwar e also supports the stati stic s and history groups on the ARN 100 router and communicates with the DCMMW software subsystem to access RMON and RMON2 data collected by the Ethernet DCM.

303539-A Rev 00

1-11

Page 28

Configuring RMON and RMON2

RMON Network Management Software

An RMON net wor k m anag em en t softw are application, also known as a client, runs on a network management station, which can be a workstatio n or PC running UNIX or Windo ws®. Many RMON clients located at va rious locations can simultaneously r etrieve information from an AN/ANH or ARN rout er locat ed on a specific LAN segment within an internetwork. Optivity Analysis for Windows NT® is an example of an RMON network management application.

After you enable the Ethernet DCM on a r outer and the Ethernet DCM is collecting stat istics, you can use the followi ng network management application s to view, analyze, and monitor network RMON and RMON2 statistics:

• Opti vity Analy sis for UNIX and Opti vity LAN app licat ions, whic h are part of

the Optivity Ente rprise

• Opti vity Analysis for Windows NT

Optivity Analysis for UNIX

Optivit y Analysis for UNIX is a set of graphical network management applications bas ed on RMON. These Optivity® applications of fer powerful RMON-based tools that let you view statistics for an enterpri se-wide internetwor k, for specific LAN segments within an internetwork, or for hosts on a LAN segment.

™

network management suite

1-12

Each RMON tool is a complete application that represents an intelligent implementation of the RMON and RMON2 MIB groups. After the tool requests and receives information from the network management station, it processes the information and displa ys a graph ical summary of network traffic. Each tool is configura ble, so you can obtain exactly the type of information you need.

303539-A Re v 00

Page 29

RMON and RMON2 Overview

In Optivity Anal ysis, the RMON tools provide methods for collecting data for all RMON and RMON2 MIB groups. Table 1-4 summarizes the RMON-based tools and lists the correspon ding RMON MIB groups that they use to collect and display traf fic statistics.

Table 1-4. Optivity Analysis for UNIX RMON-Based Tools

Tool Name Purpose Possible Uses Special Features

RMON MIB Group

Segment Statistics

Host Statistics Display traffic

Host Matrix Present statistics on

Display and rec ord information from th e RMON statistics gr oup. This infor m a t io n includes raw packet counts and bandwidth utilization .

summaries fo r each host on a selected segment.

Provide a HostTopN filter that allows you to concentrate on onl y the most active ho st s on the network.

conversations between host pairs on a select ed segment.

Plan bandwidth-intensive tasks.

Baseline individual segment traffi c characterist ics.

Determine which hosts ar e generating spec ific types of traffic.

Isolate sources of broadcasts, errors, and so forth.

Locate workgroups for segmentation.

Ability to view mult iple sessions

Automati c u til iz at io n calculation bas ed on available bandwidth

History collection Filter for viewing

TopN hosts Link packet capture

Sparse matrix display

Quick view of graphic coding of information

Lev el 3 support for conversations by protocol

Statistics

Host Table and HostTopN

Matrix

303539-A Rev 00

(continued)

1-13

Page 30

Configuring RMON and RMON2

Table 1-4. Optivity Analysis for UNIX RMON-Based Tools

Tool Name Purpose Possible Uses Special Features

Filter/Capture Define channels and

filters.

Activate channels for captures.

DecodeMan Decode and display

captured packet content.

Alarm Editor View thresholds for

segment.

Run Learning Tool locally.

Alarm Monitor Continually monitor all

segments.

Capture packets for analysis of a specific problem or to pro vide selective traffic statistics.

Troubleshoot problems by pinpointing the source.

Modify individual normative models.

Run Learning Tool with local configuration for specific segment.

Proactive maintenance Monitors all

(continued)

Flexib le chan nel and filter edit ors

Real-time display of counters

Automatic capture activation from other tools

Full seven-layer decode

Quick search index

Quick configuration of RMON probes for standalone operation

Editin g of in di v id ual thresholds and hysteresi s values interac ti vely

segments at once

RMON MIB Group

Filter and Capture

Ancillary to Alarm and Event

Alarm and Event

Protocol Distribution (RMON2)

1-14

Provide breakdo wn by protocol type

Analyze protoc ols and applications co ntrib ut ing t o the overall traffic levels on the network.

Quick filte r by segment or alar m type

Link to Filter /Capture and DecodeMan

N/A Protocol

Distribution

(continued)

303539-A Re v 00

Page 31

RMON and RMON2 Overview

Table 1-4. Optivity Analysis for UNIX RMON-Based Tools

Tool Name Purpose Possible Uses Special Features

Network Layer Matrix (RMON2)

Learning Tool Automatically “learn”

TrafficMan Graphically represent

View conversation pairs across router boundaries.

normal network behavior on all segments.

the relations hip be tween end stations, including relative traffic volumes and the primary network layer protocol used.

Analyze traf fi c flow to predict bottlenecks and plan for growth.

Create normative model comprising thre shold values for all segments.

Identify hosts or conversations that require attention.

View statistics for specific hosts and conversations.

Start other RMON tools directly from TrafficMan map.

(continued)

Shows statistics on traffic between pairs of hosts (in/out, packets, octets, and so forth)

Learns automatically

Flexible samp le

Builds model statistically

Filters TrafficMan map on a variety of features, includin g upper-layer protocols such as FTP and HTTP

RMON MIB Group

Network Lay er Matri x

Ancillary to Alarm and Event

N/A

303539-A Rev 00

For detailed inf ormation about how to install, configure, and custom ize the RMON-based tools for use with RMON and RMON2, see Using Optivity Analysis 8.x.

Optivity L A N

Optivity LAN offers two tools you can use to monitor network statistics col lected by the RMON agent: Threshold Manager and Fault Correlator. These tools allow you to set thresholds on inte ger-based objects and display t rap infor mation whe n a threshold is exceeded.

Threshold Manager

After you establish a level of performance that you cons ider normal for your network, you can configure your system to generate response s whe never your network perfor mance becom es abnormal.

1-15

Page 32

Configuring RMON and RMON2

You can also set thresholds that initia te alarms whenever specified network conditions occur. Whenever a threshold is met or exce eded, the specified event occurs and the alarm is triggered. You can set thresholds specific to a slot or port.

For detailed inf ormation about installing the Threshold Manager tool, see Using Optivity LAN 7.1 for U NIX.

Fault Correlator

After you set alarm thresholds on integer-based variables using the Threshold Manager, you can use the Fault Correlator tool to decode the traps that are sent to the RMON network management station.

The Fault Correlat or generates fault report s and calcula tes the current state of network objects and devices. Optivity LAN automatically stores this information in the Optivity f ault database.

For detailed inf ormation about using the Fault Correlator tool, see Using Optivity

LAN 7.1 for UNIX.

Optivity Analysis for Windows NT

1-16

Optivit y Analysis for Windo ws NT monitors the performance of heterogeneous LANs to help you i dentif y and so lv e networ k probl ems qui ckly be fore t hey lead to network failure.

Optivit y Analysis for Windo ws NT supports the RMON and RMON2 MIBs and provides a powerful interface that allows you to poll the RMON devices (pr obe s, routers, and switches) on your network. You can poll a device and inquire about errors, bandwidth, and so fort h.

Optivit y Analysis for Windo ws NT can monitor hundreds or even thousands of LAN segments by dividing large, complex networks into more manageable domains. Optivity Analysis for Windows NT allows you to view traffic statistics generated from a single LAN, groups of LANs, or an enterprise network.

With Optivity Analysis for Windows NT, you can establish and report on net work trends over extended periods and create baselines that set alarms so that an accurate picture of the networ k can be portrayed.

For more information about using Optivity Analysis for Windows NT, see Using Optivity Analysis for Windows NT Version 1.x.

303539-A Re v 00

Page 33

Chapter 2

Starting RMON and RMON2

on AN/ANH and ARN Routers

This chapter lists the requirements for starting RMON and RMON2 using Site Manager and the BCC. It also inc ludes th e proced ures for con fi guring RMON and RMON2 on AN/ANH and ARN routers using the default configuration values .

If you want to configure the built-in version of RMON on an ARN 100

Note:

router with no Ethernet DCM using Site Manager, go to Chapter 3, “Configuring Mini -RMON on an ARN 100 Router.”

303539-A Rev 00

This chapter contains the following information:

T opic Page

Router Hardware and Software Prerequisites Starting Configuration Tools 2-4 Starting RMON and RMON2 2-4 Customizing the Ethernet DCM 2-9

For detailed inf ormation about RMON and RMON2 and the Bay Networks implementation of RMON and RMON2, see Chapter 1, “RMON and RMON2

Overview.”

2-2

2-1

Page 34

Configuring RMON and RMON2

Router Hardware and Software Prerequisites

Before you can use the full RMON and RMON2 functionality on BayStack AN/ANH, ARN, and ARN 100 routers, your router must meet specific hardware and software requirements.

To ensure a successful implementation of RMON and RMON2, complete the following ta sks:

Install an Eth erne t DCM module in each Ba y St ac k AN/ANH or ARN

router from whi ch you want to collect RMON and RMON2 statistics.

For complete installation instructions, see one of the following guides:

• Installing an N11 Data Collection Module (DCM) in a BayStack AN

• Installing an N11 Data Collection Module (DCM) in an 8-Port ANH

• Installing an Ethernet RMON DCM in a BayStack ARN Router

Upgrade the memory on the Ethernet DCM. The minimum memory

requirements are as follows:

• RMON: 4 MB

2-2

• RMON2: 8 MB To determine how much memory you need to configure RMON MIB groups

and to stor e the data for these groups, see “Memory Requirements for RMON

Groups” on page C-11.

Review the recommended software and hardware requirements for

RMON and RMON2 operation.

Table 2-1

lists the software and har dware requirements for RMON and

RMON2 operation on BayStack AN/ANH routers.

Table 2-1. AN/ANH Requirements for Using RMON and RMON2

Software/Hardware Recommended Version

DCM hardware Revision E Boot PROM Version 9.00c ( Diagnostic PROM Version v7.30 ( BayRS BayRS Version 12.20 ( DCM agent software DCM Agent Softwar e Version 2.00.1 (

anboot.exe andiag.exe

an.exe

v9.00c) or later

v7.30) or later

v12.20) or later

in_2.00.1. obj

303539-A Re v 00

)

Page 35

Starting RMON and RMON2 on AN/ANH and ARN Routers

Table 2-2 lists the software and hardware requirements for RMON and

RMON2 operation on BayStack ARN routers.

Table 2-2. ARN Requirements for Using RMON and RMON2

Software/Hardware Recommended Version

DCM hardware Revision E Boot PROM Version 1.19 ( Diagnostic PROM Version 2.00 ( BayR S Version 12 .20 ( DCM agent software Version 2.00. 1 (

arnboot.exe arndiag.exe

arn.exe

v12.20) or later

in_2.00.1. obj

v1.19) or later

v2.00) or later

)

Caution:

Enabling an Ethernet DCM with DCM agent software earlier than Version 2.00.1 generates a warning log messa ge , whic h prevents the Ethernet DCM from booting successfully.

Verify minimum DCM requirements to determine whether you need to

upgrade the DCM software image on the router.

For instruct ions, see Appendix D, “

Configure an Ethernet interface for each LAN segment you want to

Upgrading the DCM Software Image.”

monitor. Install and configure on your network management station one of these

network management applications to view and analyze RMON and RMON2 statistics generated by the Ethernet DCM:

• Opti vity Enterprise (contai ns Optivity Analysis for UNIX and Optivity LAN)

• Opti vity Analysis for Windows NT

303539-A Rev 00

2-3

Page 36

Configuring RMON and RMON2

Starting Configuration Tools

Before configuring RMON and RMON2, see the appropriate user guide for instructions on how to start and use the Bay Networks confi guration tool of your choice.

Configuration Tool User Guide

Bay Command Console (B CC Site Manager

™

These guides also describe generally how to create and modify a device configuration.

Starting RMON and RMON2

To begin using RMON and RMON2 for data collection on BayStack routers, you must enable the Ethernet DCM using the default configuration.

Using the Bay Command Console

)

Configuring and Managing Routers with Site Manager

To start RMON and RMON2 on Ethernet DCM-enabled AN/ANH and ARN routers using the BCC or Site Manager, perform the following tasks:

• Prepare a configuration file.

• Configure the Ethernet DCM.

Preparing a Configuration File

To create a configuration file using Site Manager, comple te the following steps:

You do this System responds

1. From the Site Manager main menu, choose

2. Choose

2-4

Tools.

Configuration Manager.

Site Manager Procedure

The Tools menu opens.

The Configuration Manager window opens.

(continued)

303539-A Re v 00

Page 37

Starting RMON and RMON2 on AN/ANH and ARN Routers

Site Manager Procedur e

You do this System responds

3. Choose

Dynamic.

4. Select the configuration file and click on

Local File, Remote File

, or

(continued)

Site Manager prompts you to choose a configuration file.

The Configuration Manager window opens, displaying the router models.

For infor mation about Site Manager and ho w to work with configura tion files, see Configuring and Managing Routers with Site Manager.

Configuring an Ethernet DCM for AN/ANH Routers

Before you can configure an Ethernet DC M on an AN/ANH router, you must configure IP and SNMP on the router (see Configuring SNMP, BootP, DHCP, and RARP Services.)

When you configure the Ethernet DCM for an AN/ANH router, you create the DCM middleware (DCMMW) conf igur ation using the default paramete r values. For informatio n about modifying the default v al ues, see Chapter 4

a DCM for RMON and RMON2.”

For an AN/ANH router, you can only configure a DCM base module.

, “Customizing

Using the BCC

303539-A Rev 00

To configure an Ethernet DCM for an AN/ANH router:

Navigate to the root (box) level and enter RMON configu ration mode:

rmon

Set the module type for the DCM that you want to configure by entering:

dcm dcm-id

Module

is either ba se-module or expansion-module.

2-5

Page 38

Configuring RMON and RMON2

For example, the following command line conf igures the DCM base-module on an AN router:

Using Site Manager

To configure an Ethernet DCM for an AN/ANH router, comple te the following steps:

You do this System responds

1. In the Configuration M anager window, cho os e the A N router m o del.

2. Click on

3. Choose a net module for the DCM, for example, 8pt. EHub/3S/N11/DCM, then click o n OK.

4. Choose the link or net module connector on which you are configuring the Ethernet DCM, for exampl e, XCVR, then clic k on

5. Choose

6. Click on OK. You return to the Configuration Manager

7. Choose

8. Choose

9. Choose

10.Click on OK to accept the default configuration parameters.

rmon# dcm/ba se-module#

dcm dcm-id ba se-modul e

The following command line configures the DCM expansion-module on an ARN router:

rmon# dcm/ex pansion-module#

dcm dcm-id ex pa n s io n-m odule

Site Manager Procedure

Confirm.

The Select Protocols window opens.

, then click on OK. The IP Configuration window opens.

window.

Platform DCM 11.0 and later Create Base Modul e DCM

. The Platform menu opens.

. The DCM 11.0 and later menu opens.

. The Edit Base Module DCM Par am eters

window opens. You return to the Configuration Manager

window.

2-6

303539-A Re v 00

Page 39

Starting RMON and RMON2 on AN/ANH and ARN Routers

When you enable the Ethernet DCM, the RMON Object Support parameter is set to RMON2 by default, allowing the Ethernet DCM to collect both RMON and RMON2 statistics. You can use Optivit y Analysis for UNIX or Optivity Analysis for Wind ows NT to view and analyze RMON and RMON2 statistics.

Configuring an Ethernet DCM for ARN Routers

Before you can configure an Ethernet DC M on an ARN router, you must configure IP and SNMP on the router (see Configuring SNMP, BootP, DHCP, and RARP Services).

When you configure the Ether ne t DCM for an ARN router, you create the DCM middleware (DCMMW) configuration using the default parameter values . F or information about modifying the default values, see Chapter 4

DCM for RMON and RMON2.”

For an ARN router, you can configure up to two DCMs: one on the router’s base module and one on the router’s expansion module. You must configure each module separately.

, “Customizing a

Using the BCC

303539-A Rev 00

To configure an Ethernet DCM for an ARN router:

Navigate to the root (box) level and enter RMON configu ration mode:

rmon

Set the module type for the DCM that you want to configure by entering:

dcm dcm-id <

Module_type

module_type>

is either ba se-module or expansion-module.

For example, the following command sequence con figures one DCM on an ARN router base module and another DCM on an ARN router expansion module:

rmon# dcm/ba se-module# dcm/ex pansion-module#

dcm dcm-id ba se-modul e

dcm dcm-id e xpa n s i on-m odule

2-7

Page 40

Configuring RMON and RMON2

Using Site Manager

To configure an Ethernet DCM for an ARN router, complete the following steps:

You do this System responds

1. In the Configuration M anager window, choose an ARN router model.

2. Click on

3. Choose the base, expansion, or adapter module you want to configure for the ARN router. You must choose each module sep arate ly. For example:

Confirm.

Site Manager Procedure

• For a base module, choose

• For an expansion module, choose

Ethernet DCM

• For an adapter module, choose

ISDN ‘V.’

4. Click on OK.

5. Choose a net or link module f or the ARN router.

6. Choose the link or net module connector on which you are configuring the Ethernet DCM.

7. Accept the default circuit name or modify it, then click on

8. Choose

9. Click on OK. You return to the Configuration Manager

10.Choose

11.Choose

12.Choose

Create Expansion Module DCM

You can enable a DCM on both an Ethernet base module and an Ethernet ex pansion module with an installed DCM.

13.Click on OK to accept the default configuration parameters.

, then click on OK. The IP Configuration window opens.

Platform DCM 11.0 and later Create Base Modul e DCM or

. The Platform menu opens.

Ethernet

. The DCM 11.0 and later menu opens.

The Add Circuit window opens.

The Select Protocols window opens.

window.

The Edit Base Module DCM Par am eters

window or t he Edit Expansion Module DCM Parameters window opens.

You return to the Configuration Manager window.

2-8

303539-A Re v 00

Page 41

Starting RMON and RMON2 on AN/ANH and ARN Routers

Customizing the Ethernet DCM

For informatio n about customizing the DCMMW configuration para mete rs, see Chapter 4, “Customizing a DCM for RMON and RMON2.”

303539-A Rev 00

2-9

Page 42

Page 43

Chapter 3

Configuring Mini-RMON on an ARN 100 Router

On the ARN 100 router, Bay Networks provides a condensed version of the RMON MIB standard, called mini-RMON. Mini-RMON supports the following four RMON MIB groups:

• Statist ics

• History

• Alarm

• Event Unlike the AN/ANH and ARN routers, which use an installed Ethernet DCM to

collect RMON statistics, the ARN 100 router contains built- in RMON capability on the router’s base module. Using Site Manager to configure the ARN 100 base module, you can enable the ARN 100 to collect RMON statisti cs.

After you c onfigure the ARN 100 route r to collect RMON statistics, you can view these statistic s using the RMON tools in Optivity Analysis for UNIX or Optivity Analysis for Windows NT. For information about using these RMON tools, see “RMON Network Management Software

” on page 1-12.

303539-A Rev 00

3-1

Page 44

Configuring RMON and RMON2

Configuration Considerations

If you choose, you can upgrade an ARN 100 router to collect complete RMON and RMON2 statistics by insta lling an Ethernet expansion modu le on the router’s base module and attaching the Ethe rnet DCM to it. You can collect full RMON/RMON2 statistic s only from the segment attached to t he router’s Ethernet expansion module .

You cannot collect RMON statistics from both the base module and the Ether net DCM (full RMON/RMON2). This restriction is enf orced in the following way for ARN 100 routers:

• If you enable the DCMMW subsystem on an ARN 100 router and then configure mini-RMON on the AR N 100 base module, the DCMMW subsystem is disabled. (DCMMW is unloaded and its load mask is cleared.)

• If you enable mini-RMON on the base module and you the n configure the DCMMW subsystem, mini-RMON is disabled. (Mini-RMON is unloaded and its load mask is cleared.)

For information about installing an Ethernet DCM on an Ethernet expansion module in an AR N router, see Installing an Ethernet RMON DCM in a BayStack ARN Router . F or information about starting RMON and RMON2 on an ARN 100 router with an installe d Etherne t DCM, se e Chapter 2

RMON2 on AN/ANH and ARN Routers.”

, “Starting RMON and

Starting Mini-RMON

To start RMON data collection on an ARN 100 base module, use Site Manager to perform the following tasks:

• Prepare a configuration file.

• Enable the base module a nd RMON data collection.

3-2

303539-A Re v 00

Page 45

Preparing a Configuration File

To create a configuration file, c omplete the following steps:

You do this System responds

Configuring Mini-RMON on an ARN 100 Router

Site Manager Procedure

1. From the Site Manager main window, choose

2. Choose

3. Choose

Dynamic.

4. Select the configuration file and click on

Tools.

Configuration Manager.

Local File, Remote File

For infor mation about Site Manager and ho w to work with configura tion files, see Configuring and Managing Routers with Site Manager.

Enabling Mini-RMON Data Collection

To begin collecting mini-RMON statistic s on the ARN 100 base module, you enable the base module and then enable RMON by completing the following steps:

Site Manager Procedure

You do this System responds

, or

The Tools menu opens.

The Configuration Manager window opens.

Site Manager prompts you to choose a configuration file.

The Configuration Manager window opens, displaying the router models.

303539-A Rev 00

1. In the Configuration M anager window, cho os e the A R N route r m o del.

2. Click on

3. Choose the 10/100BASE-TX Ethernet or the 100BASE-FX Ethernet net or link module for the ARN 100 router.

4. Click on

Confirm.

OK.

(continued)

3-3

Page 46

Configuring RMON and RMON2

Site Manager Procedur e

You do this System responds

5. Choose the link or net module connector on which you ar e ena bli ng mini -RMON, f o r example, XTRCV.

6. Accept the default circuit name or modify it, then click on OK.

7. Choose

8. Set the following parameters:

IP Address

•

Subnet Mask

•

T ransmit Bcast Addr

•

UnNumbered Assoc Addres s

• Click on

Services

9. Click on OK. You return to the Configuration Manager

10.Choose

11.Choose

12.Choose

Stats.

RIP,

and

Help

for parameter descriptions.

Platform

RMON Stats 12.10 and later.

Enable Base Module RMON

then click on OK.

or see

Configuring IP

. The Platf orm menu opens.

(continued)

The Add Circuit window opens.

The Select Protocols window opens.

window.

The RMON Stats 12.10 and later menu opens.

The Enable Base Module RMON Stats menu opens, indi cating that you have enabled the base module for RMON data collecti on.

3-4

303539-A Re v 00

Page 47

Configuring Mini-RMON on an ARN 100 Router

Disabling Mini-RMON Data Collection

To stop collecting mini-RMON statistics on the Ethernet, you must delete the RMON Stats base module on the ARN 100 router.

To delete the RMON Stats base module on the ARN 100 router, complete the following ste ps:

Site Manager Procedure

You do this System responds

1. In the Configuration M anager window, choose

2. Choose

3. Choose

Stats

Platform

RMON Stats 12.10 and later.

Delete Base Module RMON

The Platform menu opens.

The RMON Stats 12.10 and Later menu opens.

The Configur ation Manage r dis ab les da ta collection b y del eti ng the base m odule on the ARN 100.

303539-A Rev 00

3-5

Page 48

Page 49

Chapter 4

Customizing a DCM for RMON and RMON2

This chapter describes h o w to customize th e conf igur atio n of a n Etherne t DCM b y editing the DCMMW parameters. It contai ns the following information:

Topic Page

Disabling the Ethernet DCM Specifying RMON or RMON2 Data Collecti on 4-3 Specifying the Configuration Mode 4-6 Saving the Configuration Infor m ation 4-7 Configuring the DCM Image on the Router 4-9 Modifying Default RMON MIB Group Parameters 4-12 Rebooting the Ethernet DCM 4-18 Deleting the Ethernet DCM Software Subsystem 4-19 Using the Technician Interface to Manage a DCM 4-20

4-2

For detailed inf ormation about RMON and RMON2 and the Bay Networks implementation of RMON and RMON2, see Chapter 1

, “RMON and RMON2

Overview.” For a description of all Ethernet DCM parameters, see Appen dix B, “Ethernet D CM Param et ers .”

303539-A Rev 00

4-1

Page 50

Configuring RMON and RMON2

Disabling the Ethernet DCM

By default, DCM data collection is enabled on the router. Before you can modify DCMMW configuration parameters for an installed Ethernet D CM, you must temporarily disab le the Ethe rnet DCM from collecting data. When you finish modifying the DCMMW configurat ion parameters, you must reenable the Ethernet DCM for these changes to take effect.

Using the BCC

To temporarily disable the DCM from collecting data, nav igate to the dcm/base-module context or the dcm/expansion-module context (for example,

state disabled

For example, the following command line disable s DCM data collection on the base-module of an AN/ANH router:

box; dcm/base-modul e

) and enter:

dcm/base-module# dcm/base-module#

state disabled

The following command line disables DCM data collection on the expansion-mo dule of an ARN router:

dcm/expansion-module# dcm/expansion-module#

state disabled

4-2

303539-A Re v 00

Page 51

Using Site Manager

To temporarily disable the DCM from collecting data, complete the following steps:

You do this System responds

Customizing a DCM for RMON and RMON2

Site Manager Procedure

1. In the Configuration M anager window, choose

2. Choose

3. Choose

4. Choose one of the following options:

• Base Module DCM

• Expansion Module DCM

5. Set the

Disable

parameter descri pti on on pageB-2

6. Click on OK. You return to the Configuration Manager

Platform

DCM 11.0 and later Global

Enable/Disable

. Click on

. The DCM 11.0 and later menu opens.

. The Global menu open s.

parameter to

Help

or see the

The Platform menu opens.

If you choose Edit Base Module DCM Parameters window opens.

If you choose for an ARN router, the Edit Expansion Module DCM Parameters window opens.

window.

Specifying RMON or RMON2 Data Collection

When you enable one Ethe rnet DCM using S ite Mana ger default v alue s, the DCM collects RMON2 and RMON statistics from the AN/ANH or ARN router. Although the ARN router suppor ts two Etherne t DCMs, it cannot c ollec t RMON2 statistics from more than one Etherne t DCM simultaneously.

Base Module DCM,

Expansion Module DCM

the

303539-A Rev 00

When you enable one Etherne t DCM using BCC default v alu es, the DCM collects only RMON statistics. You can configur e the DCM to collect both RMON and RMON2 statistics, but only on one DCM.

Y ou c an specify which Ethernet DCM you want to collect RMON2 statistics from; any additional Ethernet DCMs automatically d efault to RMON.

4-3

Page 52

Configuring RMON and RMON2

Using the BCC

To specify the Ethernet DCM from which you want to collect RMON and RMON2 statistics or just RMON statistics, navigate to the rmon-control context (for exampl e,

box; rmon/dcm dcm-id base-module/rmon-control

) and enter:

rmon2 level

Statistics

is either r mon or rmon2.

For example, the following command sequence spe cifies the Ethernet DCM that collects RMON2 sta tistics and displays the object support level:

rmon-control/base-module# rmon2/ base-module# level rm on2

info

rmon2 level rmon2

The following command sequence specifies that the Ethernet DCM collects both RMON and RMON2 statistics and display the object support level:

rmon2/base-module# rmon2/ base-module# level rm on

rmon2 level rmon info

4-4

303539-A Re v 00

Page 53

Using Site Manager

To specify the Ethernet DCM from which you want to collect RMON2 statistics, complete the following steps :

You do this System responds

Customizing a DCM for RMON and RMON2

Site Manager Procedure

1. In the Configuration M anager window, choose

2. Choose

3. Choose

4. Choose

Expansion Module DCM.

5. Set the

Disable

parameter descri pti on on pageB-2

6. Click on OK. You return to the Configuration Manager

7. Repeat steps 1 through 4; then go to step 8.The Edit Base Module DCM Parameters

8. Se t th e parameter. Click on parameter descri pti on on pageB-6

9. Set the

Enable.

parameter descri pti on on pageB-2

10.Click on OK. You return to the Configuration Manager

Platform

DCM 11.0 and later Global. Base Module DCM

Enable/Disable

. Click on

RMON Object Support

Enable/Disable

Click on

Help

or see the

. The DCM 11.0 and later menu opens.

parameter to

or see the

parameter to

The Platform menu opens.

The Global menu open s. The Edit Base Module DCM Parameters

window or t he Edit Expansion Module DCM Parameters window opens.

window.

window or t he Edit Expansion Module DCM Parameters window opens.

window.

303539-A Rev 00

4-5

Page 54

Configuring RMON and RMON2

Specifying the Configuration Mode

By default, the Ethernet DCM uses the configuration file in its own local flash memory. If you want to use the confi guration information in the DCM DRAM, written b y DCMMW from the Bay Stack route r’s file system, set t he Conf igu rati on Mode parameter to shared mem o ry. Shared memo ry is the are a on t he Eth ern e t DCM through which the router’s base module and the Ethernet DCM exchange information.

Using the BCC

T o s pecif y whet her you wa nt to use the configuration information in DCM DRAM or in DCM flash memory, navigate to the dcm/base-module context or the dcm/expansi on-module context (for example,

bo x; dcm/base- m odule

) and enter:

config-mode <

Mode_type

mode_type>

is either probe-memory (local) or shared-memory.

For example, the following command lets you acces s the configuration information in DCM DRAM:

dcm/base-module# dcm/base-module#

config-mode shared-memory

The following command lets you access the configuration information in DCM flash memory:

dcm/base-module# dcm/base-module#

config-mode probe-memory

4-6

303539-A Re v 00

Page 55

Using Site Manager

To specify the configurat ion mode, complete the following steps:

You do this System responds

Customizing a DCM for RMON and RMON2

Site Manager Procedure

1. In the Configuration M anager window, choose

2. Choose

3. Choose

4. Choose

Expansion Module DCM

5. Set the

Disable

parameter descri pti on on pageB-2

6. Click on OK. You return to the Configuration Manager

7. Repeat steps 1 through 4; then go to step 8.The Edit Base Module DCM Parameters

8. Set the Click on description on page B-4

9. Set the

Enable

10.Click on OK. You return to the Configuration Manager

Platform

DCM 11.0 and later Global. Base Module DCM

Enable/Disable

. Click on

Configuration Mode

Help

Enable/Disable

. Click o n

parameter to

Help

or see the

or see the parameter

. parameter to

Help

or see page B-2

. The DCM 11.0 and later menu opens.

parameter.

The Platform menu opens.

The Global menu open s. The Edit Base Module DCM Par am eters

window or t he Edit Expansion Module DCM Parameters window opens.

window.

window or t he Edit Expansion Module DCM Parameters window opens.

window.

Saving the Configuration Information

By default, the DCM saves the configuration information in DRAM to its local DCM flash memory (overwr iting the existing configuration file). If you do not want to overwrite the DCM configuration file in flash memory, configure the DCM so that it does not save the configur ation information.

303539-A Rev 00

4-7

Page 56

Configuring RMON and RMON2

Using the BCC

To set the save mode for the configuration information, navigate to the dcm/base-module or expa nsion-module context (for example,

box; dcm/base-module

) and enter:

save-mode <

Mode

For example, the following command line speci fies that the DCM uses the configuration file in its local flash memory but does not save the configuration information in its loca l flash memory:

dcm/base-module# dcm/base-module#

The following command specifies that the DCM uses the configuration file in DCM DRAM and saves the conf iguration information in DRAM to its loc al flash memory:

dcm/base-module# dcm/base-module#

Using Site Manager

To set the save mode for the configuration information, complete the following steps:

You do this System responds

mode>

is either sa ve (default) or no-sa ve.

config-mode probe-memory save-mode no-save

config-mode shared-memory save-mode save

Site Manager Procedure

4-8

1. In the Configuration M anager window, choose

2. Choose

3. Choose

4. Choose

Expansion Module DCM

5. Set the

Disable

parameter descri pti on on pageB-2

Platform

DCM 11.0 and later Global. Base Module DCM

Enable/Disable

. Click on

Help

parameter to

or see the

. The DCM 11.0 and later menu opens.

The Platform menu opens.

The Global menu open s. The Edit Base Module DCM Par am eters

window or t he Edit Expansion Module DCM Parameters window opens.

(continued)

303539-A Re v 00

Page 57

Customizing a DCM for RMON and RMON2

Site Manager Procedur e

You do this System responds

6. Click on OK. You return to the Configuration Manager

7. Repeat steps 1 through 4; then go to step 8.The Edit Base Module DCM Parameters

8. Set the Click on description on page B-4

9. Set the parameter. Click on parameter descri pti on on pageB-4

10.Set the

Enable

parameter descri pti on on pageB-2

11.Click on OK. You return to the Configuration Manager

Configuration Mode

Help

or see the parameter

Save Configurat ion Info

Help

Enable/Disable

. Click o n

Help

parameter.

or see the

parameter to

or see the

(continued)

window.

window or t he Edit Expansion Module DCM Parameters window opens.

window.

Configuring the DCM Image on the Router

You configure the DCM image on the router by specifying the follo wing required parameters:

303539-A Rev 00

• By defa ult, the DCM uses the im age f il e in its local flash memory a s t he DCM boot image. The boot image option, which specifies whether the DCM boots with the image file in its local flash memory (local) or with a boot im age copied from the router’s flash memory card (download).

• The router v olume and file name for the image you want the DCM to boot. The boot image name cannot exceed 255 characters.

• The image save mode, which specifie s whether or not the DCM saves the active DCM image to its loca l flash mem o ry.

By default, the DCM saves the boot image file in DRAM to its local flash memory (overwr iting the existing image file). You can choose not to save the DCM boot image file (the image remains in DRAM until the next tim e the DCM boots).

4-9

Page 58

Configuring RMON and RMON2

Using the BCC

Before you can configure the DCM boot image on the router, make sure that the

config-mode

parameter is se t to shared-memory. Then configure the DCM boot

image by spe cifying an explicit value for the following required parameters:

image-name, boot-option

T o co nfi gure the DCM boot image on the rout er , na vig ate to the dc m/base-modul e or dcm/expansion- module context (for exa mple, and enter the follo wing required parameters:

, and

save-mode

box; dcm/expans i on-modul e

)

image image-name save-mode

Vol ume _number:filename

want the DCM to boot.

Option Mode

For exa mple, the following command sequence sets the config-mode para meter to shared-memory, then specifies that th e DCM boots with the image f ile 11_140.obj on volume 1 of the router’s flash memory ( in the DCM flash mem o ry:

image/ base-module#

save-mode

image/base-module#

save

Using Site Manager

To configure the DCM boot image on the router, comple te the tasks in the following ta ble:

<volume_number:filenam e>

boot-opt io n

<mode>

is the volume and the fi le name of the image that you

is either local or do wnload.

is either sav e or no-save.

download

image image-name 1:11_140.obj boot-option download

Site Manager Procedure

) and save s the DCM ima g e

4-10

You do this System responds

1. In the Configuration M anager window, choose

2. Choose

3. Choose

Platform

DCM 11.0 and later Global.

. The DCM 11.0 and later menu opens.

The Platform menu opens.

The Global menu open s.

(continued)

303539-A Re v 00

Page 59

Customizing a DCM for RMON and RMON2

Site Manager Procedur e

You do this System responds

4. Choose

Expansion Module DCM

5. Set the

Disable

parameter descri pti on on pageB-2

6. Click on OK. You return to the Configuration Manager

7. Repeat steps 1 through 4; then go to step 8.The Edit Base Module DCM Parameters

8. Set the

Help

page B-2

9. Se t th e Click on description on page B-3

10.Set the Click on description on page B-3

11.Set the

Enable

parameter descri pti on on pageB-2

12.Click on OK. You return to the Configuration Manager

Base Module DCM

Enable/Disable

. Click on

Boot Option

or see the parameter description on

Image Name

Help

Image Save Mode

Help

Enable/Disable

. Click o n

Help

parameter. Click on

or see the parameter

Help

parameter to

or see the

parameter.

. parameter to

or see the

(continued)

The Edit Base Module DCM Par am eters window or t he Edit Expansion Module DCM Parameters window opens.

window.

window or t he Edit Expansion Module DCM Parameters window opens.

window.

303539-A Rev 00

4-11

Page 60

Configuring RMON and RMON2

Modifying Default RMON MIB Group Parameters

If necessary, you can change the default values for the following R MON MIB group parameters:

• Maximum number of host addresse s col lected in each RMON host control table

• Whether the DCM creates the RMON host control tab le when it boots

• Whether the DCM creates the RMON matrix control table when it boots

For more information a bout the RMON host contr ol and matrix cont rol tables , see “RMON MIB Group Controls and Functions

Go to the sections that follow to set these RMON MIB group parameters.

Specifying the Maximum Number of RMON Hosts

You can specify the maximum number of host addresses to be collected in each RMON host control table. The maximum limit depends on the amount of flash memory available in the DCM. When the host control table reaches the m aximum value, the DCM deletes entries based on an LRU (least recently used) algorithm.

” on page C-2.

Using the BCC

4-12

To specify the maximum number of host addresses to be collected in the RMON matrix control table, navigate to the rmon-control/base-module or rmon-control/expansion-module context (for example,

base-module max-hosts <

Integer

is the maximum number of host addresses that the DCM collects and

) and enter:

integer>

box; rmon-control/

stores in the RMON host control table. Host addresses range from 100 through

8128.

For example, the following command line sets the maximum number of hosts in the RMON control table to 300:

rmon-control/base-module# rmon-control/base-module#

max-hosts 300

303539-A Re v 00

Page 61

Using Site Manager

To specify the maximum number of RMON hosts, complete the following ste ps:

You do this System responds

Customizing a DCM for RMON and RMON2

Site Manager Procedure

1. In the Configuration M anager window, choose

2. Choose

3. Choose

4. Choose

Expansion Module DCM

5. Set the

Disable

parameter descri pti on on pageB-2

6. Click on OK. You return to the Configuration Manager

7. Repeat steps 1 through 4; then go to step 8.The Edit Base Module DCM Parameters

8. Set the

Shared Memory

parameter descri pti on on pageB-4

9. Set the Click on description on page B-5

10.Set the

Enable

parameter descri pti on on pageB-2

11.Click on OK. You return to the Configuration Manager

Platform

DCM 11.0 and later Global. Base Module DCM

Enable/Disable

. Click on

Configuration Mode

RMON Max Host

Help

Enable/Disable

. Click o n

parameter to

Help

or see the

. Click on

parameter.

or see the parameter

. parameter to

Help

or see the

. The DCM 11.0 and later menu opens.

parame ter to

Help

or see the

The Platform menu opens.

The Global menu open s. The Edit Base Module DCM Par am eters

window opens or the Edit Expansion Module DCM Parameters window opens.

window.

window opens or the Edit Expansion Module DCM Parameters window opens.

window.

303539-A Rev 00

To verify the number of hosts configured, chec k the MIB object wfDCMmsRMONHost using the Site Manager Statistics tool.

4-13

Page 62

Configuring RMON and RMON2

Enabling and Disabling the RMON Host Control Table

By default, the DCM does not create the RMON host control ta ble when it boots. If your RMON network management application does not enable and disable its own host configuration during normal operation, you may need to enable the DCM to create it.

The DCM allows only one instance of the host cont rol table.

Using the BCC

To enable the creation of the RMON host control table, navigate to the rmon-control/ba se-module or rmon-control/exp ansion-module context (for exampl e,

host-control enabled

box; rmon-control/expansion-module

For exa mple, the following command line enables the creation of the RMON host control table, allowing the DCM to create default host e ntries in this table:

) and enter:

rmon-control/expansion-module# rmon-control/expansion-module#

host-control enabled

To disable the creation of the RMON host control ta ble, navigate to the rmon-control/ba se-module or rmon-control/exp ansion-module context (for example,

host-control disabled

box; rmon/rmon-control/expansion-module

) and enter:

For example, the following command line disable s the RMON host control table, preventing the DCM from creating default host entries in thi s table:

rmon-control/expansion-module# rmon-control/expansion-module#

host-control disabled

4-14

303539-A Re v 00

Page 63

Using Site Manager

To enable or disable the creation of the RMON host c ontrol table, complete the following steps:

You do this System responds

Customizing a DCM for RMON and RMON2

Site Manager Procedure

1. In the Configuration M anager window, choose

2. Choose

3. Choose

4. Choose

Expansion Module DCM

5. Set the

Disable

parameter descri pti on on pageB-2

6. Click on OK. You return to the Configuration Manager

7. Repeat steps 1 through 4; then go to step 8.The Edit Base Module DCM Parameters

8. Set the

Shared Memory

parameter descri pti on on pageB-4

9. Set the Click on description on page B-5

10.Set the

Enable

parameter descri pti on on pageB-2

11.Click on OK. You return to the Configuration Manager

Platform

DCM 11.0 and later Global. Base Module DCM

Enable/Disable

. Click on

Configuration Mode

RMON Default Host

Help

Enable/Disable

. Click o n

parameter to

Help

or see the

. Click on

or see the parameter

. parameter to

Help

or see the

. The DCM 11.0 and later menu opens.

parame ter to

Help

or see the

parameter.

The Platform menu opens.

The Global menu open s. The Edit Base Module DCM Par am eters

window or t he Edit Expansion Module DCM Parameters window opens.

window.

window or t he Edit Expansion Module DCM Parameters window opens.

window.

303539-A Rev 00

4-15

Page 64

Configuring RMON and RMON2

Enabling and Disabling the RMON Matrix Control Table

By default, the DCM does not create the RMON matrix control table when it boots. If your RMON network management application does not enable and disable its own matrix configuration during normal operation, you may need to enable the DC M to cre at e it.

The DCM allows only one instance of the matri x control table.

Using the BCC

To enable the creation of the RMON matrix control table, naviga te to the rmon-control/ba se-module or rmon-control/exp ansion-module context (for exampl e,

matrix-control enabled

box; rmon-control/expansion-module

For example, the following command line enabl es the cre ation of the RMON matrix control table, allowing the DCM to create default matrix en tries in this table:

) and enter:

rmon-control/expansion-module# rmon-control/expansion-module#

matrix-control enabled

To disable the creation of the RMON matrix control ta ble, navigate to the rmon-control context and ente r:

matrix-control disabled

For example, the following command line disable s the creation of the RMON matrix control table, preventing the DCM from creating default matrix entries in this table:

rmon-control/expansion-module# rmon-control/expansion-module#

matrix-control disabled

4-16

303539-A Re v 00

Page 65

Using Site Manager

To enable or disable the creation of the RMON matrix control table, complete the following steps:

You do this System responds

Customizing a DCM for RMON and RMON2

Site Manager Procedure

1. In the Configuration M anager window, choose

2. Choose

3. Choose

4. Choose

Expansion Module DCM

5. Set the

Disable

parameter descri pti on on pageB-2

6. Click on OK. You return to the Configuration Manager

7. Repeat steps 1 through 4; then go to step 8.The Edit Base Module DCM Parameters

8. Set the

Shared Memory

parameter descri pti on on pageB-4

9. Set the Click on description on page B-6

10.Set the

Enable

parameter descri pti on on pageB-2

11.Click on OK. You return to the Configuration Manager

Platform

DCM 11.0 and later Global. Base Module DCM

Enable/Disable

. Click on

Configuration Mode

RMON Default Matrix

Help

Enable/Disable

. Click o n

parameter to

Help

or see the

. Click on

or see the parameter

Help

. parameter to

or see the

. The DCM 11.0 and later menu opens.

parame ter to

or see the

parameter.

The Platform menu opens.

The Global menu open s. The Edit Base Module DCM Par am eters

window or t he Edit Expansion Module DCM Parameters window opens.

window.

window or t he Edit Expansion Module DCM Parameters window opens.

window.

303539-A Rev 00

4-17

Page 66

Configuring RMON and RMON2

Rebooting the Ethernet DCM

After you finis h modifying Ethernet DCM configurat ion para meters, you must reboot the Ethernet DCM for these changes to take effect. You do this by reenabling the Etherne t DCM.

Using the BCC

To reenable the DCM for data collection, navigate to the dcm/bas e-module or dcm/expansi on-module context (for example,

state enabled

For example, the following command line reena bles a DCM to begin collecting data:

bo x; dcm/base- m odule

) and enter:

dcm/base-module# dcm/base-module#

Using Site Manager

To reboot the Ethernet DCM, complete the following steps:

You do this System responds

1. In the Configuration M anager window, choose

2. Choose

3. Choose

4. Choose

Expansion Module DCM

5. Set the

Enable

parameter descri pti on on pageB-2

6. Click on OK. You return to the Configuration Manager

state enabled

Platform

DCM 11.0 and later Global. Base Module DCM

Enable/Disable

. Click o n

Help

or see the

parameter to

Site Manager Procedure

The Platform menu opens.

. The DCM 11.0 and Later menu opens.

The Global menu open s.

The Edit Base Module DCM Par am eters window or t he Edit Expansion Module DCM Parameters window opens.

window.

4-18

303539-A Re v 00

Page 67

Customizing a DCM for RMON and RMON2

Deleting the Ethernet DCM Software Su bsystem

The router requires the DCMMW software to communicate with the Ethernet DCM. Deleting DCMMW deactivates the Ethernet DCM.

Before you delete the DCMMW, always try disabling the Ethernet

Note:

DCM first.

Using the BCC

To deactivate the Ethernet DCM, navigate to the dcm/base-module or expansion-mo dule context (for exampl e,

delete

For example, the following command deactivates the Ethernet DCM on a router:

box; dcm/base-module

) and enter:

dcm/base-module# rmon#

Using Site Manager

To deactivate the Ethernet DCM, complete the following steps:

You do this System responds

1. In the Configuration M anager window, choose

2. Choose

3. Choose

delete

Platform

DCM 11.0 and later Delete DCM.

Site Manager Procedure

The Platform menu opens.

. The DCM 11.0 and later menu opens.

The Delete DCM menu opens.

(continued)

303539-A Rev 00

4-19

Page 68

Configuring RMON and RMON2

Site Manager Procedur e

You do this System responds

4. Choose one of the following options:

Base Module DCM only

•

• Expansion Module DCM only

All DCMs

•

Base Module DCM only

DCMMW from the bas e module on t he curr ent platform.

Expansion Module DCM only

DCMMW from the ARN Ethernet expansion module.

All DCMs

modules on the current plat form.

5. Click on OK. Site Manager co mp letely deactivates all

remove s the DCMM W from all

removes the

(continued)

Site Manager displays a confirmation prompt.

Ethernet DCMs.

If you need to react ivate the Ethernet DCM after del et ing the DCMMW, see “Starting RMON and RMON2” on page 2-4.

Using the Technician Interface to Manage a DCM

You can use Technician Interface commands to:

• Download a new Ethernet DCM software image. , “Upgrading the DCM Softwar e Image.”

set, get,

and

commit

commands with the MIB object ID.

4-20

See Appendix D

• Display or modify DCMMW configuration parameters.

See Using T echnician Interface Software for infor mation about accessing the DCM MIB using

Caution:

The Technician Interface does not verify tha t the value you enter fo r

a parameter is valid. Entering an invalid value can corrupt your configur ation.

303539-A Re v 00

Page 69

Customizing a DCM for RMON and RMON2

• Enable, disa ble, and reboot the Ethernet DCM.

See Using T echnician Interface Software for infor mation about using the

enable/disable dcmmw

scripts.

Caution:

Avoid running scripts that continually issue Technician Interface commands while you are running another RMON network management application. This combination can cause the SNMP agent to fill the system buffers with RMON data, causing a system restart.

303539-A Rev 00

4-21

Page 70

Page 71

Appendix A

Monitoring the DCM

Using the BCC show Command

This appendix describes how to use the BCC configura tion, interface, and statistical information from the management information base (MIB). The type and amount of data displa yed depend on the specific DCM settings you want to view.

This chapter includes descriptions of the

Enter all commands using lowercase letters.

Note:

show rmon dc m

command to obtain DCM

show

command.

303539-A Rev 00

A-1

Page 72

Configuring RMON and RMON2

show rmon dcm

summary

Displays configuration and statistical information about all Ethernet DCMs configured on the router.

The output inc ludes the following information:

Data Collection Module # Number that corresponds to either a base module (1) or an

DCM State Stat e of the D C M : enabl e d or disa bled. Operational Status Indicates the status of the DCM: up or down. RMON Object Support Indicates whether the E thernet DCM is collect ing RM ON or RMON2

Module Type Type of circuit to which the DCM is attached on the AN/ANH o r ARN

Memory Size Total size of available memory on the DCM. Hardware Revision Revision number associated with the DCM hardware. Firmware Revision Revision number associated with t he DCM firmware. Agent Image Version Version number of the DCM agent software. Boot Option Indicates whet her the DCM uses the image file in its o w n fl ash

Image Name Name of the image file on the AN/ANH or ARN router’s flash

The

show rmon dcm

command displays configur ation, status, and

statistical information about the DCM configured on an AN/ANH or ARN router. The

show rmon dcm

command supports the following subcommand options

• summary

• image

• dcmconfig

• rmonconfig

expansion module (2).

statisti cs .

router base module or ARN expansion module. The only module type supported by the DCM is Ethernet.

memory (local) f or boot ing or a boot imag e copi ed fro m the AN/ANH or ARN router’s flash memory card to DCM shared memory (download).

memory card.

A-2

303539-A Re v 00

Page 73

Monitoring the DCM Using the BCC show Command

Image Sav e Mo de Indicates that the DCM saves the active image to it s local flash

memory (save) or that th e DCM does not save the DCM boot image (no sav e), if the save mode is no save.

Config Source Indicates t hat the DCM uses the default configuration information in

the DCM local flash memory (local ) or the router’s flash memory, stored in DCM DRAM (shared).

Config Save Mode Indicates that the DCM sa ves the configuration information to its

local flash memory (sav e) or that the DCM does not sav e the DCM configurat ion information (no save).

Max hosts per entry Maximum number of host addr esses to be collec ted in eac h entry of

the RMON host control ta ble. Addresses range from 100 throug h

8128.

Configured hosts per entry Configured n umber of hos ts i n eac h RMON hos t cont ro l ent ry on the

DCM.

Create Host Control Table Indicates whether the creation of the RMON host control table is

enabl ed or di sa bled.

Create Matrix Control Table Indicates whether the creation of the RMON matrix control table is

enabl ed or di sa bled.

image

Displays information a bout the DCM image for all Ethernet DCMs configured on the AN/ANH or ARN router, including agent im age version, boot option, image name, and image save mode.

The output inc ludes the following information:

Data Collection Module # Number that corresponds to either a base module (1) or an

Agent Image Version Version number of the DCM agent software. Boot Option Indicates th at t he DCM uses the i ma ge file in its own flash mem ory

Image Name Name of the image file on the AN/ANH or ARN router’s flash

Image Sav e Mo de Indicates that the DCM saves the act ive image to its local flash

303539-A Rev 00

expansion module (2).

(local) for booting or a boot image copied from the AN/ANH and ARN router’s flash memory card to DCM shared memory (download).

memory card.

memory (save) or that th e DCM does not save the DCM boot image (no save, if the save mode is nosave.

A-3

Page 74

Configuring RMON and RMON2

dcmconfig

Displays configuration information about a ll Ethernet DCMs configured on the AN/ANH or ARN router, including the state of the DCM, its operational status, its hard ware and firmware revisions, and so forth.

The output inc ludes the following information:

Data Collection Module # Number that corresponds to either a base module (1) or an

DCM State Stat e of the D C M : enabl e d or disa bled. Operational Status Indicates the operational status of the DCM: up or down. Module Type Type of circuit to which the DCM is attached on the AN/ANH o r ARN

Memory Size Total memory size of the DCM software. Hardware Revision Revision number associated with the DCM hardware. Firmware Revision Revision number associated with t he DCM firmware. Config Source Indicates t hat the DCM uses the default configuration information in

Config Save Mode Indicates whether the DCM saves the configuration information to

expansion module (2).

router base module or ARN expansion module. The only module type supported by the DCM is Ethernet.

the DCM local flash memory (local ) or the router’s flash memory, stored in DCM DRAM (shared).

its local flash memory (save) or that the DCM does not save the DCM configuration information (no save).

dcm rmon co n fig

Displays information spe cific to the RMON default conf iguration, including maximum number of hosts per entr y, configured number of hosts per entry, and the status of the host control table and matrix control table.

A-4

303539-A Re v 00

Page 75

Monitoring the DCM Using the BCC show Command

The output inc ludes the following information:

Data Collection Module # Number that corresponds to either a base module (1) or an

expansion module (2).

RMON Object Support Indicates whether the Ethernet DCM is collect ing RM ON or RMON2

statisti cs .

Max hosts per entry Maximu m number of host addresses collected in eac h entry of t he

RMON host cont rol table.

Configured hosts per entry Configured n umber of hos ts i n eac h RMON hos t cont ro l ent ry on the

DCM.

Create Host Control Table Indicates whether the creation of the RMON host control table is

enabl ed or di sa bled.

Create Matrix Control Table Indicates whether the creation of the RMON matrix control table is

enabl ed or di sa bled.

Config Save Mode Indicates whether creation of the DCM saves the configurat ion

informati on to i ts local flash memory (sav e) or that the DCM does not save the DCM configuration information (n o save).

303539-A Rev 00

A-5

Page 76

Page 77

Appendix B

Ethernet DCM Parameters

This appendix contains reference information a bout customizing the parameters for the Ethernet DCM to support RMON and RMON2. For each parameter, this appendix provide s the following information:

• Parameter name

• Conf iguration Manager menu path

• Default se tting

• Valid parameter options

303539-A Rev 00

• Parameter function

• Instructions for setting the parameter

• Management infor mation base (MIB) object ID The Technician Interface allows you to modify parameters by issuing

commit

modifying parameters using Site Manager. For more information about using the T echnician Interface to access the MIB, refer to Using Technician Interface Software.

Caution:

parameter va lues. Entering an invalid value can corrupt your configur ation.

commands with the MIB object ID. This process is equi valent to

The Technician Interface does not verify the validity of your

set

and

B-1

Page 78

Configuring RMON and RMON2

Parameter: Enable/Disable

Path: Configuration Manager > Platform > DCM 11.0 a nd later > Global > B ase

Module DCM (or Expansion Module DCM)

Default: Enable

Options: Enable

Function: Enables or disables DCMMW (the DCM software subsystem) and therefor e the

DCM.

Instructions: To disable the DCM, select Disable. To reenable the DCM, select Enable. Use

this parameter to reboot the DCM by disabling, then reenabling, DCMMW.

MIB Object ID: 1.3.6.1.4.1.18.3.3.2.16.2.1.3

Parameter: Boot Option

Path: Configuration Manager > Platform > DCM 11.0 a nd later > Global > B ase

Module DCM (or Expansion Module DCM)

Default: Local

Options: Local

Function: Specifies whether the DCM uses the image file in its own flash memory for

booting or a boot image copied from the BayStack router’s flash memory card to DCM shared memory.

Instructions: Select Local to specify the image file in DCM local flash memory as the DCM

boot image. Select Download to specify an image file on the BayStack router’s flash memory as the DCM boot image. You specify the downloaded image using the Image Name parameter.

MIB Object ID: 1.3.6.1.4.1.18.3.3.2.16.2.1.8

Disable

Download

B-2

303539-A Re v 00

Page 79

Ethernet DCM Parameters

Parameter: Image Name

Path: Configuration Manager > Platform > DCM 11.0 a nd later > Global > B ase

Module DCM (or Expansion Module DCM)

Default: None, but you must specify an image name when the Boot Option parameter is

set to Download

Options: An ASCII text string up to 255 characters

Function : Specifies an im age file on the BayStack rou te r’s flash memory card . The im ag e

name must be a fully qualified file name, including both the volume and file name.

Instructions: Enter the volume and f ile name of the image that you want the DCM to boot,

using the format

<volume_number:filename>

, for example,

1:dcm_image

MIB Object ID: 1.3.6.1.4.1.18.3.3.2.16.2.1.7

Parameter: Image Save Mode

Path: Configuration Manager > Platform > DCM 11.0 a nd later > Global > B ase

Module DCM (or Expansion Module DCM)

Default: Save

Options: Save

No Save

Functio n : Sp e cifies w heth e r the DCM saves th e active imag e to its local flash memory.

Instructions: To save the active DCM boot image file to the DCM local flash memory

(overwrit ing the ex isti ng sa v ed image) , se lect Sav e. Select No Sa ve if you do not want to save the DCM boot image file . The image remains in DRAM until the next time the DCM boots.

MIB Object ID: 1.3.6.1.4.1.18.3.3.2.16.2.1.9

303539-A Rev 00

B-3

Page 80

Configuring RMON and RMON2

Parameter: Configuration Mode

Path: Configuration Manager > Platform > DCM 11.0 a nd later > Global > B ase

Module DCM (or Expansion Module DCM)

Default: Local

Options: Local

Function: Specifies whether t o use the configuration information in DCM shared memory

Instructions: Select Local to use the defaul t con fi gurati on informatio n in the DCM local flash

MIB Object ID: 1.3.6.1.4.1.18.3.3.2.16.2.1.10

Parameter: Save Conf iguration Info

Path: Configuration Manager > Platform > DCM 11.0 a nd later > Global > B ase

Default: Save

Options: Save

Function: Specifies whether to save the configuration information in DRAM to the DCM

Instructions: Select Save to save the configuration information in DRAM to the DCM flash

MIB Object ID: 1.3.6.1.4.1.18.3.3.2.16.2.1.11

Shared Memory

(DRAM) or the configuration information saved on the DCM’s flash memory.

memory. Select Shared Memory to use the configuration information from the BayStack router’s flash memory, stored in DCM DRAM.

Module DCM (or Expansion Module DCM)

No Save

flash memo ry.

memory (overwrit ing the existing configuration fil e). Select No Save to av oid overwriting the DCM configuration file.

B-4

303539-A Re v 00

Page 81

Ethernet DCM Parameters

Parameter: RMON Max Host

Path: Configuration Manager > Platform > DCM 11.0 a nd later > Global > B ase

Module DCM (or Expansion Module DCM)

Default: 500

Options: 100 to 8128

Function: Indicates the maximum number of host addresses to be collected in each entry

of the RMON host control t able. The maximum limit depends on the amount of flash memory available in the DCM. When the host control table reaches this maximum value, the DCM delet es entri es based on an LR U ( least rec ently us ed) algorithm.

Instructions: Recommended values, based on DCM memory configurations, a re

-- 2 to 4 MB: 2048

-- 8 MB: 4096

-- 16 MB: 8128 T o verify the number of configured hosts, check the MIB object

wfDCMmwRMONHost using the Site Manager Statistics tool

MIB Object ID: 1.3.6.1.4.1.18.3.3.2.16.2.1.12

Parameter : RMON Defa u lt Ho st

Path: Configuration Manager > Platform > DCM 11.0 a nd later > Global > B ase

Module DCM (or Expansion Module DCM)

Default: Disable

Options: Enable

Disable

Function : Specifies wh eth er to crea t e the RM O N host control table at every boot. Some

RMON network management applications e xpect the DCM to set up a host configurati on; others enable and disable their own host configurations during normal operations.

Note that the DCM allows only one instance of the host control table.

Instructions: Select Enable to create the RMON host control table a t the next (and every

subsequent) reboot. Sel ect Disa ble to disable defa ult creation of the RMON hos t control table at boot time.

MIB Object ID: 1.3.6.1.4.1.18.3.3.2.16.2.1.13

303539-A Rev 00

B-5

Page 82

Configuring RMON and RMON2

Parameter : RMON Defa u lt Matr ix

Path: Configuration Manager > Platform > DCM 11.0 a nd later > Global > B ase

Module DCM (or Expansion Module DCM)

Default: Disable

Options: Enable

Function: Specifies whether to create the RMON matrix control table at every boot. Some

RMON network management applications e xpect the DCM to set up a matrix configurati on; others enable and disable the ir own matrix configurations during normal operations.

Instructions: Select Enable to create the RMON matrix control table at the next (and every

subsequent) reboot. Select Disable to disable default creation of the RMON matrix control table at boot time.

MIB Object ID: 1.3.6.1.4.1.18.3.3.2.16.2.1.14

Parameter : RMON Ob jec t Support

Path: Configuration Manager > Platform > DCM 11.0 a nd later > Global > B ase

Module DCM (or Expansion Module DCM)

Default: RMON2

Options: RMON2

Function: Determines the Ethernet DCM from which you want to collect RMON2

statistics. You use this parameter only when you have multiple Ethernet DCMs on a network runni ng RMON2 and you need to choose which Ethe rnet DCM to collect RMON2 information from.

Instructions: Choose RMON2 to collect RMON2 statistics for the Ethernet DCM. Any other

Ethernet DCMs default to RMON.

MIB Object ID: 1.3.6.1.4.1.18.3.3.2.16.2.1.15

Disable

RMON

B-6

303539-A Re v 00

Page 83

Appendix C

RMON and RMON2 MIB Groups

This appendix defines the RMON and RMON2 MIB groups and pr ovides information about RMON memory usage and interoperability issues. RMON functions are d escribed without referring to the low-level details of the RMON MIB, which are described in RFC 1757 and RFC 2021.

This appendix contains the f ollowing information:

Topic Page

RMON MIB Groups RMON2 MIB Groups C-6 Memory Requirements for RMON Groups C-11

RMON MIB Groups

RMON provides i nformation about laye rs 1 and 2 of the seven-layer OSI network model. You can monitor information on an Ethernet netw or k through nine differ ent MIB groups that comprise the RMON specificati on. RFC 1757 def ines the function a nd organization of the RMON MIB groups.

Bay Networks implements the f ollowing MIB groups in its RMON agent for BayStack AN/ANH and ARN routers:

• Statistics

• History

• Host

• HostTopN

• Matrix

303539-A Rev 00

C-1

Page 84

Configuring RMON and RMON2

• Filter

•Capture The router base module supports the foll owing groups:

• Alarm

• Event

RMON MIB Group Controls and Functions

Several of the RMON groups in the MIB contain control and data tables. Control tables contain contr ol parameters that specify which stat istics you want to access and collect. You can view and change many entrie s in a control table. Data tables contain statistic s the agent collects; usually you can only view entries in these tables.

The followin g sections describe the function of each group and the tables that each group defines. Refer to RFC 1757 for the following information:

• A list of all the parameters that appear in a control ta ble

• The read/write status of a control parameter

• The defa ult values for control parameters with read/write status

• A list of all the objects that appear in a data table

Statistics Group

The statistics grou p records da ta that the Ethernet DCM measures on network interfaces. The Ethernet DCM creates one entry for each Ethernet interface it monitors and places the entry in the EtherS tatsTable. The EtherStatsTable also contains control parameters for this group.

History Group

The history group contains a contr ol an d data collection function. The control function manages the periodic statistical sampling of data from networks and specifies control parameters, such as the frequency of data sampling, in the historyControlTable.

C-2

303539-A Re v 00

Page 85

The data collection func tion records periodic statistical samples from Ethernet networks, for example, interval start time and number of packets. This function places the statistic al samples in the etherHistoryTable.

Host Group

The host group identif ies hosts on the network by recording the source and destination MAC addresses in good packets, and places the information in the hostTable. This group also records the time it discovered a host on the network in the hostTimeTable. The hostControlTable specifies control parameters, such as which monitoring operat ions the Ethernet DCM performs, and contains some information about the monitoring process.

HostTopN Group

The HostTopN group ranks hosts according to a statistic type. For example, you can rank the hosts by the number of errors they generate. Control para mete rs for this group are stored in the hostTopNControlTable, and data this group generates is stored in the hostTopNTable. To use the HostTopN group, you must set up the host group.

RMON and RMON2 MIB Groups

Matrix Group

The matrix group stores statistics for an interchange between hosts a t different addresses. This group’s control parameter s, such as number of hosts, are stored in the matrixContr olTable. When the matrix group receiv es information from a good packet, it places data in both the matrixSDTable and the matrixDST a ble.

Filter Group

The filter group specifies the types of packe ts the Ethernet DCM can capture. Filter cont rol parameters, such as the mini mum length of those packets, a re stored in the filterTable. Associated with each filter is a channel (a specific path al ong which data flows). Control parameters in the channelTable define how and where the filtered packets flow.

303539-A Rev 00

C-3

Page 86

Configuring RMON and RMON2

Capture Group

The capture group enables the capture of packets that satisfy the f ilter group control parameters for a particular channel. Control parameters in the buff erControlTable specify how to transfer data from the chann elTable to the captureBuf ferTable. For example, you can spe cify the maximum number of octets from each packet that the group can store in the captureBufferTable. To use the capture group, you must set up the filter group.

Alarm Group

The alarm group allows you to se t an alarm thre shold and a sampling interva l to enable the RMON agent to generate alarms on any network segment it monitors. Alarm thresholds can be based on absolute or delta values, so that you can be notifie d of rapid spikes or drops in a monitored val ue.

Each alarm is l inked t o an e ve nt in the e v ent gr oup. An e v ent defi nes an actio n that is triggered when the alarm threshold is exceeded.

The alarm group periodical ly tak es statistical samples from variables in the Ethernet DCM and compares them to previously configured thresholds. The Alarm Table stores configuration entries that define a var iable, a polling period, and threshold parameters. If the RMON agent determines that a sample crosses the threshold values, it generates an event. The RMON agent monitors any variables that resolve to an ASN.1 primitive type of integer (integer, counter, gauge, or TimeTick).

C-4

You can specify risi ng or fa lli ng threshol ds, indicating net work fa ult s such as s lo w throughput or other networ k-related performance problems. You specify rising thresholds when you want to be notified that an alarm has risen abov e the threshold you specified. You specify falling thresholds when you wa nt to be notifie d that the network is behaving normal ly ag ain. For example, you might specify a falli ng threshold of 30 collisions per second to indicate a return to acceptable beha vior.

When you configure an alarm condition, you must define the following values:

• The monitoring inte rval over which data is sampled

• The va riable to be sampled

• Rising and falling thresholds to detect when network trouble starts and ends

303539-A Re v 00

Page 87

Event Group

RMON and RMON2 MIB Groups

• The ev ent that takes place when a rising thr eshold is crossed

• The ev ent that takes place when a fall ing threshold is crossed

The event gr oup allows for the generation of an SNMP trap, a log entry, or both, for any ev ent you choose. An event can occur when the sample variable e xceeds the alarm thr eshold or exceeds a channel match event generated on an Ethernet DCM. Traps can be delivered by the RMON agent to multiple management stations. For information about setting trap destina tions, see Configuring SNMP, BootP, DHCP, and RARP Services.

You can set up events to either record the monitoring information or to notify the network management station. The event group includes an event table and a log table. The event table defines the notification that takes place when an eve nt is triggered.

Each entry in the ev ent table identi f ies an e ve nt that can be trigge red and indicat es an action. The event can trigger any of the following actions:

303539-A Rev 00

• The system sends an SNMP trap to the network management station.

• The management station is notified immediately. The management station

determines how to rea ct to the SNMP trap.

• The system logs the event in the log table in the agent system.

• The system sends an SNMP trap and logs the event in the log table. The log table is a read-only data table for the network management station. It

records each e vent that needs to be logged, including the event number, an index that distinguishe s occurrences of the same ev ent , the time at which the event occurred, and the event description. You are not required to configure the log table.

The management station can retrieve the information stored in the log table for further analysis. For example, the information collected can be used to select proper threshold values.

C-5

Page 88

Configuring RMON and RMON2

Event Trap Considerations

To allow RMON to generate trap events, you must set up the SNMP manager table. In the SNMP manager table, you a dd the SNMP community names that you configure d for the network management application ( for example, Optivity Analysis for Windows NT) and for the hosts on which you are running applications. If you do not make these changes, the router will be unable to send trap eve nts to the network management station. See Configuring SNMP, BootP, DHCP, and RARP Services for inst ructions on how to set up an SNMP manager table.

When you set up the SNMP manager table, you can do one of the following: use the SNMP community names that the network management application uses and modify the tr ap-receiving tables on the r outer to use these names; or configure the router to use specific SNMP community names and modify the network management softwa re to use these names.

When configuri ng SNMP community managers, you must assign each manager a specific IP address; you cannot specify a wildcard for the community manager address. Also, you must configure community managers to receive all traps, not just generic tra ps. You do this by changing the Tr ap Types parameter in the SNMP Manager window from Generic (the default) to All. For more information about changing communitie s and community manager parameters, see C onfiguring SNMP, BootP, DHCP, and RARP Services.

RMON2 MIB Groups

With RMON2, you can vie w traffic statistics by protocol and by appl ication within the protocol to obtain an enterpris e vie w of the network. RFC 2021 def ines the function a nd organization of the RMON2 MIB groups.

Bay Networks implements the f ollowing seven groups in its RMON2 agent for BayStack AN/ANH and ARN routers:

• Protocol Dir ectory

• Protocol Distr ibution

• Address Mapping

• Network Layer Host

• Applicat ion Layer Host

C-6

303539-A Re v 00

Page 89

• Network Layer Matrix

• Applicat ion Layer Matrix

Protocol Directory Group

The Protocol Directory group lists the protocols that the Ethernet DCM can monitor. These protocols represent different network layer, transport lay er, and higher-layer protocols.

RMON and RMON2 MIB Groups

Figure C-1

shows the statistics collected for the Protocol Directory group using

the Threshold Manager tool in the Optivity Analysis application.

303539-A Rev 00

Figure C-1. Protoc ol Directory Stati st ics

C-7

Page 90

Configuring RMON and RMON2

Protocol Distribution Group

The Protocol Distribution group collects the relative numbers of octets and packets for the different protocols detected on a network segment. An RMON application can use thi s tabl e to quickly determine bandwidth allocat ion used by differ ent protoc ols. An e ntry is made in the tabl e for e v ery pr otocol in th e Protocol Directory table that has been seen in at least one packet. Counters are updated in this table for e ver y protocol type that is encount ered when pa rsing a pa cke t, bu t no counters are updated for packets with MAC-layer errors.

Figure C-2

shows the statistics c olle cted for the Protocol Distribution group using

the Optivity Analysis for Windows NT application.

C-8

Figure C-2. Protocol Distribution Statistics

303539-A Re v 00

Page 91

Address Mapping Group

The Address Mapping group maps network layer addresses to MAC layer addresses dis cov ered b y t he Ethe rnet DCM. Th e netw ork manage ment appl icati on can correlate these networ k layer addresses to names via DNS or another naming utility. The Ethernet DCM creates entries in this table for all protocols that it understands. If it cannot perform address mapping for the protocol, or if this protocol is not a network layer protocol, then it does not interpret the addresses.

Network Layer Host Group

The Network La yer Host g rou p records the a mount of traffic sent to and fr om each network layer address discovered by the Ethernet DCM. These entries enable the collection of the netw ork and application layer host tables indexed by network addresses. Entries in the network layer host table are crea te d on behalf of each entry in this table. Additionally, if the Ethernet DCM implements the application layer host table, entri es in that table are created on behalf of this table.

Application Layer Host Group

RMON and RMON2 MIB Groups

The Application La yer Host group records the amount of traffic, by protocol, sent from and to each network layer address discovered b y the Ethernet DCM.

To implement this group, you must first implement the Network Layer Host group. The Ethernet DCM adds all addresses seen as the source or destination address in all packets with no MAC errors to the application layer host table, and increments octet and packet counts for all packets with no MAC errors.

Network Layer Matrix Group

The Network Layer Matrix group provides a table of traffic matrix entries that collect statistics for c onversations between two ne twork layer addresses. This table is indexe d first by the source add ress and then by the destination address to make it con venient to collect all conversations from a particular address . The Ethernet DCM adds all pairs of addresses seen in all packets with no MAC errors to this table, and increments octet and packet counts for all packets with no MAC errors.

303539-A Rev 00

C-9

Page 92

Configuring RMON and RMON2

Application Layer Matrix Group

The Application Layer Matrix group provide s a table of application layer tr affic matrix entries, which colle ct statistics for conversations of a particular protocol between two ne twork layer addresses. This table is indexe d first by the source address and then by the destina tion address to make it con venient to collect all conve rsations from a particular address. The Ethernet DCM adds all pairs of addresses seen in all packe ts with no MAC errors to this tabl e, and increments octet and packet counts f or all pa ckets with no MAC errors. To implement this group, you must first implement the Network Layer Matrix group.

Figure C-3

shows the statistics collected for the Application Layer Matrix group

using the Optivity Analysis for Windows NT application.

C-10

Figure C-3. Application Layer Matrix Statistics

303539-A Re v 00

Page 93

Memory Re quireme nts fo r RMON Gr oups

To optimize the use of your network management applications (such as Optivity Analysis for W indo ws NT), you need to unders tand each RMON group’s memory requirements.

The total amount of av ailable RMON and RMON2 memory depends on the DRAM avail able on the Ethernet DCM (Table C-1

Table C-1. DRAM and RMON Memory Size

Installed DRAM (MB) Available RMON Memory in Bytes

4 2,077,330 8 5,222,034 16 12,561,042

If the RMON memory pool is full or if the RMON agent r eaches an

Note:

implementation limi t, the agent responds to an SNMP RMON control table entry with an SNMP GEN-ERROR.

RMON and RMON2 MIB Groups

command on an

set

303539-A Rev 00

The followin g sections describe how much memory you need to:

• Configure an RMON group (for example, the matrix group or the filter and

capture groups).

• Store the data for an RMON group (for exa mple, the packets on Ethernet

DCM captu res).

In the following se ctions, the term configuration means the set of control table s for a group. For example, a matrix configuration includes only the matrixControlTable. Note that you can create more than one configuration for some RMON groups. For example, you can create more than one history configuration, allowing you to specify different intervals for sampling statistics.

C-11

Page 94

Configuring RMON and RMON2

Statistics Group

When you enable the Ethernet DCM, the RMON agent automatically creates a statistics configuration that records dat a for each netw ork interface. Through your RMON network management application, you can create as many statistics configura tions as memory permits, up to the RMON limit of 65,535 configura tions.

If you create multiple configurations, it is possible to collect the same set of statistics for the same interface in multiple data tables. The absolute values of those statist ics may v ary fr om table to tabl e, beca use the baseli ne of e ach stati stics counter occurs when you create a configuration. You may prefer, however, to use only one statistics con figuration, to conserve memory for other RMON groups.

You need 200 bytes of memory for each statistics configuration.

History Group

When you enable the Ethernet DCM, the RMON agent automatically creates a history configuration tha t collects history da ta at two intervals. The first configura tion provides short-term history by sampling stati stics every 30 seconds and holding up to 50 sa mples (called buckets). The second configuration pr ovides long-term history by sampling statistics every 30 minutes and holding up to 50 buckets.

Warning:

configurations as memory pe rmits, up to the RMON limit of 65,535 configurations. You can also set the number of bucke ts for a particular history conf iguration to as many as available memory allows. If you request more buckets than memo ry allows, the agent allocate s enough buckets to fill ava ilable memory.

C-12

Through your RMON netwo rk mana gement a pplication , y ou can create as many history

You need 504 bytes of memory for each history configuration ( 252 bytes each for the short-term and long- term history configurati ons).

The history data requires 52 bytes of memory per bucket. You calculate the total memory (in bytes) you need to store the data as follows:

number of buckets * 52 * 2 history configur ations This calcula tion shows that you need appr oximately 5.1 KB for the default se tti ng

of 50 buckets.

303539-A Re v 00

Page 95

Host Group

RMON and RMON2 MIB Groups

When you enable the Ethernet DCM, the default setting for the RMON Default Host parameter is Disable, meaning tha t no host configuration is c reated. T o create a host configuration, set the RMON Default Host pa rameter to Enable (see “Modifying Default RMON MIB Group Parameters” on page 4-12).

Some RMON network management applicati ons e xpect the Ethernet DCM to set up a host configuration, but others set up their own configurations.

The RMON agent allows you to create only one host configuration.

Note:

Make sure to set the RMON Default Host parameter according to the expectati ons of the RMON network management application.

The host configur ation requires 148 bytes. The host data requires 105 bytes of memory per host address that the Ethernet DCM detects on a segment.

You specify the maximum number of host addresses that appear in the host configura tion by setting the RMON Max Host parameter. If there is not enough memory for the number of hosts you request, the RMON agent sets the RMON Max Host parameter to the highest possible value. The number of addresses can range from 100 to 8,128 hosts, depending on the Etherne t DCM memory configura tion. TableC-2

shows recommended va lue s for this parameter.

303539-A Rev 00

Table C-2. Maximum Number of Hosts

Installed DRAM (MB) Maximum Hosts

2-4 2,048 5-8 4,096 9-16 8,128

You calculate the total memory (in bytes) you need fo r the host data as follows: 105 * value of the RMON Max Host parameter

C-13

Page 96

Configuring RMON and RMON2

HostTopN Group

To save memory and increase performance, there is no default configuration for the HostTopN group. You must create HostTopN configurations through your RMON network management application. You can create as many HostTopN configura tions as memory permits, up to the RMON limit of 65,535 configura tions.

Before you create a HostTopN configuration, you must create a host

Note:

configuration.

Each HostTopN configuratio n requires 164 byte s. The HostTopN data requires 10 bytes of memory per host address that the Ethernet DCM detects on a segment.

You calculate the total memory (in bytes) you need fo r the HostTopN data as follows:

10 * value of the RMON Max Host parameter For information about setting the RMON Max Host parameter, see “Modifying

Default RMON MIB Group Parameters” on page 4-12.

Matrix Group

When you enable the Ethernet DCM, the default setting for the RMON Default Matrix parameter is Disable. To create a matrix configuration, set the RMON Default Matrix par ameter to Enable (see “Modifying Default RMON MI B Gro u p

Parameters ” on page 4-12).

Some RMON network management applicati ons e xpect the DCM to set up a matrix configur ation, but others set up their own configura tions.

Note:

Make sure to set the RMON Default Matrix paramete r according to the expectati ons of the RMON network management application.

The matrix config uration requires 212 bytes. The matrix data requires approximately 178 bytes of memory per source/destination pair that the Ethernet DCM detects on a segment.

C-14

The RMON agent allows you to create only one matrix configuration.

303539-A Re v 00

Page 97

Filter and Capture Groups

RMON and RMON2 MIB Groups

Caution:

The memory you need for a filter/capture configuration and for storing captured packets can easily exhaust all the available memory on an Ethernet DCM, particularly if the filters are not sel ective.

You must create filter and capture configurations through your RMON network management application. You can create as many filters and capture buffers as memory permits, up to the RMON limit of 65,535 configurations.

Memory requirements v ary greatly according to the si ze and number of the filters and the size of the capture buffer. In most cases, you need 3 to 5 KB of memory for the filt er and capt ure configuration.

The size of the captu re buffer determ i nes the amount of memory you need for the data. Y ou can request the largest buffer size available by specifying a buffer size of

-1 through your RMON network management application. When you specify -1 for the capture buffer size, the agent attempts to allocate a default buffer, depending on the DRAM in the Ethernet DCM (Table C-3)

Table C-3. Default Size for Capture Buffer

Installed DRAM (MB) Default Buffer Size (KB)

464 8256 16 512

303539-A Rev 00

You can also request a larger buffer size up to 15 MB. In any case, if there is not enough memory currently available to satisfy the r equest, the agent will provide a buff er that uses all ava ilable memory.

You can determine the maximum number of packets that an agent can capture in a buffer as follows:

buff er size/(packet slic e size + 20 bytes)

C-15

Page 98

Configuring RMON and RMON2

Example

You specify a buff er size of 32 KB and a packet sli ce size of 1 KB. After checking the av ailable memory, the RMON agent allocates the buffer size you requested. The buf fer can hold a maximum of 32,768 / (1024 + 20), or 31 packets.

The RMON agent allocates the full amount of memory you specify for

Note:

the packet slice size to each packet, even if the packet size is smaller than this amount. For this reason, Bay Networks recommends that you set the packet slice size to the smallest size possible. The maximum packet size is 2 KB.

Alarm and Event Groups

When you enable the Ethernet DCM, the router does not create defa ult a larm or eve nt entries. Bay Networks recommends that you create alarm and event entries using a network management appl ic ation, such as Optivity Analysis for Windows NT.

You can create as many alarm and event entries as memory permits, up to the RMON limit of 65,535 entrie s. The memory limita tion for al arm and e v ent groups is based on the memory resource s al located on the router base module rathe r than on the Ethernet DCM. The RMON alarm and event groups are maintained by the router base module. All other RMON groups are supported on the Ethernet DCM.

C-16

Each alarm entry requires 232 bytes. Each event entry requires 542 bytes. The log table can accommodate up to 65,535 entrie s. Ea ch entry in the log table

requires 267 bytes. You cannot delete log entry rows. Therefore, as events are triggered and the event type specifies logging, the log table incre as es in size. Although there is no way to delete a specific log entry, all log entries in the log table correspondi ng to a singl e event entry are deleted when the event entry is deleted.

303539-A Re v 00

Page 99

Appendix D

Upgrading the DCM Software Image

This appendix describes how to upgrade the DCM software image on BayStack routers using Site Manager or the T e chnician Interface. This appendix includes the following inf ormation:

T opic Page

Verifying Minimum DCM Requirements Upgrading the DCM Software Image D-2

Verifying Minimum DCM Requirements

To verify the minimum DCM hardware and software requirements:

Establish a Technician Interface session on the router.

Verify the correct DCM hardware revision by entering the following

command:

[1:TN]$ get wfDCMEntry.wfDCMhwRev.*

The Technician Interface displays information similar to the following:

wfDCMEntry.wfDCMhwRev.1 = "E" wfDCMEntry.wfDCMhwRev.2 = "E"

If the Hardware Revision line indicates “C” or earlier, you must upgrade to DCM Hardware Revision E.

D-1

303539-A Rev 00

D-1

Page 100

Configuring RMON and RMON2

Display the current version of DCM agent software.

Your version of router software determines which command you enter:

• For a router running Router Software Version 11.0 or later, enter the following c ommand to display the DCM agent software version:

[1:1]$ get wfDCMEntry.wfDCM ag entImageVersion.*

The Technician Interface displays information similar to the following:

wfDCMmw.wfDCMagentImageVersion.1 = ”V1.4.2“

(There are two e ntries if there a re two DCMs installed on an ARN router.)

• For an AN or ANH router running Router Software Version 9.0 or 10.0x, enter the following command:

[1:TN]$ get wfDCMmw.wfDCMAgentImageVersion.0

The Technician Interface displays information similar to the following:

wfDCMmw.wfDCMAgentImageVersion.0 = ”V1.4.2“

If the Agent Image Version line does not indicate “V1.4.1” or “V1.4.2,” go to the next section to upgrade the DCM agent software.

Upgrading the DCM Software Image

Upgrading the DCM software image in BaySta ck route rs involves the following tasks:

• T ransferring the DCM software image from CD to your PC or UNIX workstation

• T ransferring the DCM software image from your PC or UNIX workstation to the router’s flash memor y ca rd

• T ransferring the DCM software image from the route r’s flash memory to the DCM’s f lash memory

D-2

303539-A Re v 00

Avaya RMON, RMON2 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Configuring RMON and RMON2

Contents

Figures

Tables

Preface

Before You Begin

Text Conventions

Acronyms

Bay Netwo rks Technical Publicati o ns

How to Get Help

RMON MIB

RMON2 MIB

RMON and RMON2 Support on Bay Networks Routers

RMON and RMON2 Architecture

Data Collection Module (DCM)

DCM Agent Software

DCM Middleware (DCMMW)

RMON Agent Software

RMON Network Management Software

Optivity Analysis for UNIX

Optivity L A N

Optivity Analysis for Windows NT

Router Hardware and Software Prerequisites

Starting Configuration Tools

Starting RMON and RMON2

Preparing a Configuration File

Configuring an Ethernet DCM for AN/ANH Routers

Configuring an Ethernet DCM for ARN Routers

Customizing the Ethernet DCM

Configuration Considerations

Starting Mini-RMON

Preparing a Configuration File

Enabling Mini-RMON Data Collection

Disabling Mini-RMON Data Collection

Disabling the Ethernet DCM

Specifying RMON or RMON2 Data Collection

Specifying the Configuration Mode

Saving the Configuration Information

Configuring the DCM Image on the Router

Modifying Default RMON MIB Group Parameters

Specifying the Maximum Number of RMON Hosts

Enabling and Disabling the RMON Host Control Table

Enabling and Disabling the RMON Matrix Control Table

Rebooting the Ethernet DCM

Deleting the Ethernet DCM Software Su bsystem

Using the Technician Interface to Manage a DCM

show rmon dcm

RMON MIB Groups

RMON MIB Group Controls and Functions

Statistics Group

History Group

Host Group

HostTopN Group

Matrix Group

Filter Group

Capture Group

Alarm Group

Event Group

Event Trap Considerations

RMON2 MIB Groups

Protocol Directory Group

Protocol Distribution Group

Address Mapping Group

Network Layer Host Group

Application Layer Host Group

Network Layer Matrix Group

Application Layer Matrix Group

Memory Re quireme nts fo r RMON Gr oups

Statistics Group

History Group

Host Group

HostTopN Group

Matrix Group

Filter and Capture Groups

Alarm and Event Groups

Verifying Minimum DCM Requirements