SMC Networks EliteView 6.20 User Manual

MANAGEMENT GUIDE

EliteViewTM 6.20

SNMP-Based
Network Management Softwarefor Windows™

EliteView™
User Guide

SNMP-Based Network Management Software for Windows™

20 Mason
Irvine, CA 92618
Phone: [phone]

May 2008

Pub. # 149100039100A

E052008-DG-R6.20

Information furnished by SMC Networks, Inc. (SMC) is believed to be accurate and reliable. However, no responsibility is
assumed by SMC for its use, nor for any infringements of patents or other rights of third parties which may result from its
use. No license is granted by implication or otherwise under any patent or patent rights of SMC. SMC reserves the right to
change specifications at any time without notice.

Copyright © 2008 by

SMC Networks, Inc.

20 Mason

Irvine, CA 92618

All rights reserved.

Trademarks:

SMC is a registered trademark; and EliteView, EZ Switch, TigerStack and TigerSwitch are trademarks of SMC Networks, Inc. Other product and company names are
trademarks or registered trademarks of their respective holders.

Licence Agreement

The Purchaser MUST read this agreement before using the software provided in this package. As used in this Agreement the terms “You”,
“Your”, “LICENSEE”, and “Purchaser” refer to the licensee of the SOFTWARE and accompanying written materials in this package, as
described below. If you do not agree to the terms of this License Agreement, return the package, unused, to the point of purchase for a refund
of any license fee which you paid.

1. Grant of license

SMC Networks, Inc. (SMC) grants to you a non-exclusive right to use one copy of the program (hereinafter the “SOFTWARE”). The
SOFTWARE is provided by SMC on CD-ROM. SMC also grants to you a non-exclusive right to use the programs on the enclosed CD-ROM
(hereinafter the “SOFTWARE”) on one local area network. SMC reserves all rights not expressly granted to the LICENSEE.

2. Ownership of license

All SOFTWARE, and each copy thereof, remains the property of SMC and/or one or more of its licensors. This license is not a sale of any

SOFTWARE, or of any copy. You disclaim forever any rights of ownership in any SOFTWARE, or in any copy. The only rights that you obtain
with respect to any SOFTWARE are those expressly set forth in this License Agreement.

3. Copy restriction

You acknowledge that the SOFTWARE and accompanying written materials are copyrighted and entitled to protection under the copyright
laws of nations where the SOFTWARE is installed, and under international conventions. Except for the copying of SOFTWARE as expressly

permitted in the next sentence, you may not copy any SOFTWARE or accompanying written materials, or any portion of any of them, or
remove any copyright or proprietary notice from any of them; and you agree not to allow any other person or entity to do so. Subject to these

restrictions, you may make copies of the SOFTWARE solely for backup purposes.

4. Use restriction

As the LICENSEE, you may physically transfer the SOFTWARE from one computer to another within a licensed local area network. You may

not distribute copies of the SOFTWARE or accompanying written materials to others. Furthermore, the LICENSEE is not permitted to mod-

ify, disassemble, reverse or de-engineer, or create any derivative works based on the SOFTWARE.

5. Transfer restrictions

This SOFTWARE is licensed only to you, the LICENSEE, and may not be transferred to anyone without prior written consent of SMC. Any

authorized transferee of the SOFTWARE shall be bound by the terms and conditions of this Agreement. In no event may you transfer, assign,
rent, lease, sell or otherwise dispose of the SOFTWARE on a temporary or permanent basis except as expressly provided herein.

6. Termination

This license agreement is effective until terminated by SMC. This license may be terminated without notice by SMC if the LICENSEE fails to
comply with any provision of this license. Upon termination, it is the LICENSEE’s obligation to destroy the written materials and all copies of

the SOFTWARE. Further use of the SOFTWARE components will be in violation of this license.

Limited Warranty

The Warranty Period for the media on which the SOFTWARE is recorded is for 5 years from the date of its delivery to the original user as evi­denced by a receipt.

You must give SMC prompt written notice within the Warranty Period of any warranty claim. Conditioned on your providing prompt written

notice to SMC within the Warranty Period, SMC shall, as your sole and exclusive remedy, repair or replace media not conforming to this war­ranty, or accept return of any such nonconforming media. The election of whether to repair, replace, or refund shall be SMC’s, in its sole discre-

tion.

i

EXCEPT FOR THE EXPRESS WARRANTY SET FORTH ABOVE IN THIS LIMITED WARRANTY SECTION, THERE ARE NO
WARRANTIES, EITHER EXPRESS OR IMPLIED. THE SOFTWARE IS PROVIDED AS IS, WITH ALL FAULTS. SMC DISCLAIMS
AND EXCLUDES ANY AND ALL WARRANTIES, INCLUDING WITHOUT LIMITATION ANY AND ALL IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AGAINST INFRINGEMENT AND THE
LIKE, AND ANY AND ALL WARRANTIES ARISING FROM ANY COURSE OF DEALING OR USAGE OF TRADE. YOU
ACKNOWLEDGE THAT YOU ARE NOT RELYING ON SMC’S SKILL OR JUDGEMENT TO SELECT OR FURNISH SUITABLE
GOODS.

PRODUCTS AND SERVICES PROVIDED BY SMC ARE NOT DESIGNED, INTENDED OR AUTHORIZED FOR USE IN ANY
LIFE SUPPORT OR OTHER APPLICATION WHERE PRODUCT FAILURE COULD CAUSE OR CONTRIBUTE TO PERSONAL

INJURY OR SUBSTANTIAL PROPERTY DAMAGE. IF YOU APPLY ANY PRODUCT OR SERVICE PURCHASED OR LICENSED

FROM SMC TO ANY SUCH UNINTENDED OR UNAUTHORIZED USE, YOU SHALL INDEMNIFY AND HOLD SMC, ITS
AFFILIATES AND THEIR RESPECTIVE SUPPLIERS, HARMLESS AGAINST ALL CLAIMS, COSTS, DAMAGES AND EXPENSES

ARISING, DIRECTLY OR INDIRECTLY, OUT OF ANY SUCH UNINTENDED OR UNAUTHORIZED USE, EVEN IF SUCH
CLAIM ALLEGES THAT SMC OR ANY OTHER PERSON OR ENTITY WAS NEGLIGENT IN DESIGNING OR MANUFACTUR-

ING THE PRODUCT.

Limitation of Liability and Damages

IN NO EVENT SHALL SMC BE LIABLE FOR INCIDENTAL, INDIRECT, SPECIAL, PUNITIVE, OR CONSEQUENTIAL DAM-

AGES; OR FOR LOST PROFITS, SAVINGS OR REVENUES OF ANY KIND; OR FOR ANY ACTUAL DAMAGES IN EXCESS OF
$100,000; REGARDLESS OF THE FORM OF ACTION, WHETHER BASED ON CONTRACT; TORT; NEGLIGENCE OF SMC OR

OTHERS; STRICT LIABILITY; BREACH OF WARRANTY; OR OTHERWISE; WHETHER OR NOT ANY REMEDY IS HELD TO

HAVE FAILED OF ITS ESSENTIAL PURPOSE, AND WHETHER OR NOT SMC HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.

Copyright © 2008 by

SMC Networks, Inc.

20 Mason

Irvine, CA 92618

ii

A

BOUT THIS GUIDE

About This Guide

Welcome to EliteView network management software. This guide describes the procedures for installing and using

this program. Detailed instructions on how to use every module and practical examples make it easy for you opti-

mize the performance and efficiency of your network.

General Manual Coverage

This manual is your guide to using EliteView to manage all your network resources. It covers the following topics:

Introduction to EliteView Chapter 1

Software Installation Chapter 2

Getting Started Chapter 3

Mapping Out Your Network Chapter 4

Basic Management Tools Chapter 5

SNMP MIB Management Chapter 6

Logging Network Statistics Chapter 7

Managing Events Chapter 8

Using RMON Chapter 9

Conventions Used in this Manual

This manual uses a variety of editorial and typographical conventions to help you locate and interpret information

easily. These conventions are:

italics Italicized words refer to keyboard keys you have to press, menu options you have to select to

invoke an action, or a section in this manual or another manual you can consult for reference.

For example: <Enter>, Reboot

Courier New Words shown in Courier New typeface are used to represent screen displays, filenames, or

commands you must enter to initiate an action.

Additional References

System Help

Help files may be accessed directly from EliteView via on-line help. To get help, select Help from the menu bar and
then click on Index. Last-minute information regarding EliteView has been recorded in the README.TXT file.

iii

iv

C

ONTENTS

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Management Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Application Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Features of EliteView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

Installation for EliteView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Using SETUP to Install EliteView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

3 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Event-Driven, Modular Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

EliteView Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Alive Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

BatchUp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

BOOTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Device Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

EliteView Main Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Event Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Log Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

MIB Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

MIB Compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

MIB-2 Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Name Database Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

RMON Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Trap Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

WUR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Data Logging and Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

How the Event Manager Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Starting EliteView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Using the Main EliteView Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

4 Defining the Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

v

C

ONTENTS

Quick Guide to Map Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Using Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Name Database Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Adding a New Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Deleting Device Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Updating Device Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Searching for Device Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Creating Network Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Menu Description for Map Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Editing Map Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

5 Network Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1

Setting Addresses with the BOOTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

The BOOTP Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Starting the BOOTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Adding and Modifying Node Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Adding Filename Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Default Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Probing Devices with the Alive Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Problem Solving with the Alive Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Downloading Files with the TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Starting the TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Using the TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Viewing the TFTP Process List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Fetching Files from Other Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Telneting to Other Computers on the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Where You Are (WUR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

File Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Device Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Option Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Batch Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

File Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Utilities Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Edit Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

Options Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

File Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Utilities Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

Options Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

vi

C

ONTENTS

6 SNMP MIB Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1

MIB Compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Starting the MIB Compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

MIB-2 Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

MIB-2 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

Interface Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

Interface Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9

MIB Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

Basic Functions of MIB Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

Menu Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12

Accessing Device Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13

Using the Output Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18

Viewing Output Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18

7 Collecting Data with Log Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Editing a Log Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

Adding a New Log Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log Controls 7-5

Viewing Log Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

Using the Log Database Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Defining Filter Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

Filter Formula . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

Filter Formula syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Defining Threshold Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

Threshold vs. Filter Formula . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

Threshold Formula . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11

Threshold Formula Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11

Chart Manager Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

Basic Functions of Chart Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

Menu Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

Creating Log Charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15

Editing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15

Summarizing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16

Displaying Graphic Charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17

Graph Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18

vii

C

ONTENTS

8 Managing Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-1

Understanding the Event Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Starting the Event Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Defining Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Pre-Defined “System” Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Defining “User” Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Defining Event Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Event Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

Receiving SNMP Traps with the Trap Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

Limitations of Trap Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

Trap Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

Trap Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

Posting Messages to the Report Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7

Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8

9 Using RMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

A Brief Description of RMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Starting the RMON Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

RMON Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4

Statistics Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

Viewing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

History Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10

Alarm and Event Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13

Host Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15

Host Top N Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18

Matrix Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20

Filter and Capture Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22

A Typical EliteView Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Adding a New MIB Using the MIB Compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Managing a Third-Party Device Using the MIB Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Using the Log and Event Managers to Monitor the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Customizing EliteView to Receive Third-Party Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6

Exporting Logged Data to Other Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

B Customizing EliteView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

EliteView’s Initialization Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

Inside the NETMGR.INI File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

Description of Sections in NETMGR.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

Changing Parameters in NETMGR.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2

viii

C

ONTENTS

The [system] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3

The [device] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3

The [tools] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-5

The [bitmaps] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-6

The [util] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-8

The [tftp] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-9

The [startup] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-9

The [discover] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-10

Inside the TRAP.INI File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-11

The [generic] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-12

The [enterprise] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-13

Specific Trap Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-14

C SNMP Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

SNMP Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-1

Managing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-1

Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-2

table.index notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-2

iso origin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-3

Branches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-4

D Technical References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

RFC Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Managing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

RFC Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

Industry-Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3

E Performance Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Optimize Your Computer System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Minimize Unnecessary Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Other Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2

Managing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2

RFC Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2

Industry-Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-4

F Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1

Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1

G CodeBase 6.0 DLL
Sub-License Agreement G-1

ix

C

ONTENTS

H Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H-1

I Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-1

EliteView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-1

BOOTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-4

BOOTP.DLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-5

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovery I-8

Event Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-12

ICMP.DLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-12

IPX.DLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-15

Log Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-15

MESSAGE.DLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-16

MIB Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-17

MIB Compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-19

MIB.DLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-22

Mib-2 Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-23

Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-24

TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-25

TFTP.DLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-26

Trap Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-29

J Product Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-1

Technical Support Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-1

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-1

x

Glossary

Index

T

ABLES

Table 3-1 EliteView Program Menu Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Table 3-2 EliteView Program Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Table 4-1 Creating a Network Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Table 4-2 Discovery Menu Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Table 4-3 Field Description for Discovery Setup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Table 4-4 Name Database Manger – Editing Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Table 4-5 Menu Description for Map Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Table 4-6 Map Editing Toolbar Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Table 4-7 Map Generic Device Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Table 4-8 Map Add New Object Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Table 5-1 BOOTP Server Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Table 5-2 Adding a Node to the BOOTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Table 5-3 Alive Test Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Table 5-4 Field Description for Discovery Setup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Table 5-5 TFTP Process List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Table 5-6 TFTP Read File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Table 6-1 MIB Compiler Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Table 6-2 MIB-2 Viewer Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

Table 6-3 Field Descriptions for System Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

Table 6-4 Field Description for Interface Admin Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

Table 6-5 Field Description for Interface Statistics Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9

Table 6-6 MIB Browser Menu Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12

Table 6-7 MIB Variable Textual Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14

Table 7-1 Field Description for Log Manager/Information Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

Table 7-2 Elements of Filter Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

Table 7-3 Elements of Threshold Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Table 7-4 Chart Manager Menu Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

Table 7-5 Log Chart Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15

Table 7-6 Chart Manager - Graph Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18

Table 8-1 Event Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Table 8-2 Event Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Table 8-3 Report Window Menu Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7

Table 9-1 RMON Manager Probe Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Table 9-2 RMON Manger Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Table 9-3 RMON Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4

Table 9-4 Statistics Group Control Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

Table 9-5 SMC6724L3 1 Interface Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

Table 9-6 Statistics Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8

Table 9-7 Statistics Parameter Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9

Table 9-8 Statistics Menu and Tool Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10

xiii

T

ABLES

Table 9-9 Statistics Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10

Table 9-10 History Control Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11

Table 9-11 Alarm Control Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13

Table 9-12 Event Control Table Index Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15

Table 9-13 Host Control Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16

Table 9-14 Host Control Table Menu and Tool Bar Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-17

Table 9-15 Host Top N Menu and Tool Bar Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19

Table 9-16 Matrix Control Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20

Table 9-17 Matrix Menu and Tool Bar Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22

Table 9-18 Channel and Buffer Control Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23

Table 9-19 Filter Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25

Table 9-20 Channel and Buffer Add/Edit Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27

Table 9-21 Separate Control Tables: Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-29

Table 9-22 Separate Control Tables: Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-30

Table 9-23 Separate Control Tables: Buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-31

Table 9-24 Buffer Menu and Toolbar Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-33

Table A-1 Log and Event Manager Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

Table A-2 Port Packet Reception Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5

Table A-3 Target Device Packet Reception Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6

Table B-1 Description of Sections in NETMGR.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

Table B-2 Description of Parameters in NETMGR.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3

Table B-3 Parameter Definitions for the [device] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-4

Table B-4 Parameter Definitions for the [tools] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-5

Table B-5 Identifying Particular Tools for a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-6

Table B-6 Enumerating Graphic Bitmaps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-7

Table B-7 Parameter Definitions for the [util] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-8

Table B-8 Parameter Definitions for the [startup] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-10

Table B-9 Parameter Definitions for the [discover] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-11

Table B-10 Description of Sections in TRAP.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-11

Table B-11 Elements of a Trap Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-12

Table B-12 Parameters of the [generic] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-12

Table B-13 Parameters of the [enterprise] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-13

Table B-14 Trap Message Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-14

Table B-15 Trigger Event Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-15

Table C-1 Branches to the iso Origin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-4

Table D-1 RFC Reports: Networking Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

Table E-1 RFC Reports: Managing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2

Table F-1 Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .F-1

Table J-1 Technical Support Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-1

xiv

C

HAPTER

I

NTRODUCTION

EliteView provides a user-friendly interface for managing SMC Networks, Edgecore and third-party network
devices. This software is specifically designed to support the efforts of the MIS manager, system administrator(s),
technical staff responsible for network management and maintenance, and network operators who use the system
on a daily basis.

EliteView provides all the tools you need to manage nearly any kind of network. You can readily monitor the
traffic load throughout the network and make the changes required to avoid major crises ahead of time. This
software is designed around an event-driven architecture, which allows you to define event-handling routines that
can automatically manage a wide variety of common network tasks.

General Description

EliteView is based on the industry standard Simple Network Management Protocol (SNMP), and provides
protocol support for UDP/IP and IPX. EliteView is a Windows-based application used to manage nearly every
component in your network, from internetworking devices down to end-node computer resources.

1

EliteView manages network devices using the comprehensive Management Information Base. This MIB consists
of various MIB modules which define basic system parameters for both general and specific device types.

EliteView is based on a sophisticated graphical interface that permits it to manage any network device that
supports SNMP. By opening your network map and clicking on various objects, specific management interfaces
and system information can be readily accessed.

Interface statistics and traffic load can be illustrated by line charts. This information can be automatically recorded
by the Log Manager to maintain historical records. A powerful reporting feature is also provided for recording
significant information from any management window. Reports can be edited, saved and retrieved again during a
later session for subsequent analysis or comparison.

Event management is a key feature of EliteView. By defining specific data filters and thresholds, you can activate
event-handling routines that help you keep the network functioning. You can easily shut down malfunctioning
ports, switch to backup systems, or reconfigure network connections; and then restore system parameters back to
normal values after component problems have been resolved or the traffic falls off.

1-1

I

NTRODUCTION

Management Functions

EliteView is a Windows-based software package. It provides state-of-the-art utilities which allow you to perform
the following network management tasks:

• Generate a detailed hierarchical map of your entire network configuration. These maps display the current

status of network nodes, and provide a hot link to the management module for each device.

• Maintain centralized boot services that provide network addresses and information on system files to

download. Boot services are used to quickly reassign network addresses, and fetch filenames required for
downloading frequently modified system software for test devices.

• Monitor and log significant events and statistics. EliteView provides access to common MIB variables, as well

as specific parameters for SMC devices. Network statistics can then be displayed in tabular or graphic form.

• Automatically respond to network problems with a variety of actions. By defining thresholds for parameters

based on device-specific criteria or traffic loading, you can invoke event handling routines designed to warn the
network manager of potential system problems or automatically take corrective action.

• Quickly fetch or set MIB variables for network devices. Data in the Management Information Base

(e.g., RFC 1213 for generic internetworking devices) can be managed on an item-by-item basis.

• Remotely manage or reconfigure network devices. SMC provides a wide variety of intelligent networking

devices, including hubs and switches, which can be remotely managed via an SNMP agent. Software modules
based on an advanced graphic user interface are provided to manage every aspect of these devices. Using the
MIB Browser, extensive management functions are also provided for third-party devices.

Application Interface

EliteView runs on a personal computer attached to the network you want to manage. Management actions
normally occur via the network map, through which you can activate the appropriate software module simply by
double-clicking on the concerned device or by selecting a target device and then invoking the appropriate module
from the menus. By sending commands across the network, EliteView can directly manage a wide variety of
SNMP-based devices.

Using this powerful management tool, you can generate a device map of a complete view of the network, where
each device is represented as an icon. Network devices can be added or deleted manually, or located using
Discovery. Device icons can be placed anywhere within a map using simple drag and drop. Object attributes can
also be easily changed.

1-2

A full hierarchical representation can be generated by creating submaps that
expand to a more detailed view when selected. Moreover, multiple submaps
can be opened simultaneously. Each device included in the map can be
checked periodically to verify that it is still attached to the network. When any
device loses its network connection, its icon will change to indicate device
state, and an alarm may be generated.

The standard method of starting EliteView is to double-click
on the EliteView icon, open your network map, select a target device, and
then invoke the required management module. However, you can directly
invoke any of the modules displayed below.

The EliteView program group includes over twenty different modules. The
main program, labeled EliteView Platform, serves as the platform through
which you display the network map, manage the network, and access any of
the other management modules.

Features of EliteView

EliteView includes the following features:

F

EATURES OF ELITEVIEW

• Windows-based SNMP network management.

• Manages unlimited number of network devices running SNMP agent

software.

• Provides detailed information on device parameters, such as statistics for

the overall SNMP agent, device component status, and network interface configuration/statistics.

• Management controls are displayed with graphic and text-oriented windows, which can be accessed via the

network map, or from a pull-down menu, for better functional grouping and a more intuitive user interface.

• Hierarchical, interactive network management map with unlimited devices and network levels.

• Displays real-time graphical statistics for various counters including network traffic. Monitors the status and

traffic load of each attached device, e.g., displaying the number of incoming, outgoing and discarded frames.

• Flexible event management allows you to log relevant factors on device status and traffic.

1-3

I

NTRODUCTION

1-4

C

HAPTER

I

NSTALLATION

This chapter describes setup procedures for EliteView network management software. EliteView can manage any
of SMC’s network devices via standard and private MIB definitions; and also manage any third-party device that
has a resident SNMP agent via standard MIB definitions. Installation of EliteView software designed to manage
specific devices is covered in the corresponding manuals.
(Refer to “Additional References” on page iii.)

Installation for EliteView

EliteView can be readily installed on most Windows-compatible personal computers. The EliteView setup
program will guide you through a step-by-step procedure.

System Requirements

Before installing EliteView, please review these minimum computer and network system requirements for a
“dedicated” network management system (NMS).

2

Hardware:

• PC with 1.6 GHz Pentium IV or better

• Minimum 256MB memory

• Hard disk with a minimum of 200 MB free disk space

• SVGA adapter and display

•Mouse

• 10/100/1000Mpbs Network adapter

Software:

• Microsoft Windows 95

• Microsoft Windows 98

• Microsoft Windows NT 4.0

• Microsoft Windows 2000

• Microsoft Windows XP

2-1

I

NSTALLATION

Using SETUP to Install EliteView

The SETUP program will install EliteView from the distribution CD-ROM. This program decompresses files and
copies them to a location you specify on your hard disk.

To Start SETUP:

1. Start Windows.

2. Insert the EliteView installation CD-ROM in your drive.

3. The CD will auto-run and display the installation screen.

4. If the CD does not auto-run, please select the Setup file on the CD.

5. Follow the on-screen instructions to install the software.

2-2

C

HAPTER

G

ETTING

Welcome to the EliteView network management program for Microsoft Windows. EliteView is a powerful
network management product that provides detailed device management functions, together with a sophisticated
graphical interface. The complete package is marketed as EliteView, which includes the main EliteView program
and over twenty core program modules. This chapter provides an overview of the structure, and explains how the
various EliteView modules are related.

S

TARTED

Overview

EliteView is a flexible network management system based on international and industry standards.
It is a Windows-based program that runs on an inexpensive PC platform. This full-featured network management
software allows management of SMC or third-party network devices. In addition, it supports an open platform for
the development of any kind of management application.

EliteView can manage various SMC network devices and examine the management information base in third-party
devices.

3

Network Interface

EliteView can function on various network protocol stacks for greater flexibility and efficiency. In the Windows
environment, EliteView can be configured to run on a Windows TCP/IP package with a standard WINSOCKET
interface. At the application level, network devices are managed via SNMP over IP or IPX.

Event-Driven, Modular Architecture

Designed around an event-driven, multi-tasking architecture, EliteView consists of the main program and
supplementary modules. Each module works independently or in conjunction with other modules. Running any
module is as easy as invoking it from the main EliteView program, or by simply double-clicking on the
corresponding icon from the EliteView program group.

3-1

G

ETTING STARTED

EliteView Modules

EliteView includes support for many SMC products, including the EZ Stack, TigerStack, and TigerSwitch, series.
This section briefly describes the basic support modules included in EliteView. The modules for specific SMC
products are described in the on-line help files.

Alive Test

This module tests the connection to any network node with ICMP messages. It sends an echo request
to the specified network node and gathers replies to determine device existence, round trip delay time,
and the ratio of successfully returned packets.

Backup

Backup is a tool that used to backup the latest version of the configuration file on a network device. It
replaces the conventional way used to backup files by setting SNMP commands. Backup can load
devices from a Map file (Created by EliteView) or an exported file (*.dbf), discover and collect lots of

networking devices located in different places. Users can use simply Drag and Drop operations to
configure backup information. After clicking the Backup or Start Schedule speed button (or using the Utilities
menu) the program will automatically process these devices in turn.

BatchUp

This module is used for downloading operating code files into switches located on the local network or

on remote networks. Use the Broadcast and Search features to find devices on the network. These

devices can then be added to the Backup List and have their configuration file backed up. Use the

Backup feature to backup the configuration files for network devices. Create a backup schedule using
the Start Schedule and Stop Schedule features.

BOOTP Server

The BOOTP Server maintains a database of network addresses and a list of corresponding boot files.

BOOTP protocol runs on the UDP/IP stack. It is used by network devices to find out their own IP

address and device initialization file(s) to download.

Device Manager

Each of these modules supports advanced management functions for the corresponding device.

On-line help is provided for each of these devices. EliteView currently includes device management

modules for the EZ stack, TigerStack and TigerSwitch series.

3-2

E

Discovery

This module is used to automatically detect active devices on the network by polling within a specified

network address range or community. Discovery sends commands out to the network and waits for

responses. When a device responds, EliteView queries its functionality. If it responds correctly, a

corresponding bitmap icon is added to the Discovery window.

EliteView Main Program

The main EliteView program provides the primary interface to all EliteView modules. The Tools and

Utilities menus provide access to nearly every module under EliteView. The main program also provides

all the tools you need to generate a detailed map of your network via menus and tool buttons. Moreover,

it supports MDI (Multiple Document Interface) which allows you to simultaneously manage several
submaps. After locating the required device on your map, simply double-click on it to invoke the relevant
management application.

Event Manager

This module serves as the management center for all events generated under the main EliteView

program, Log Manager and Trap Manager. In response to input from these modules, the Event

Manager can define and dispatch responses in various forms. Actions may range from sounding an

audible signal, displaying an on-screen message, logging the event into the report window, running a
user-specified program such as a beeper, fax, pager, email, etc., or logging the event into a database for later
analysis.

LITEVIEW MODULES

Log Utilities

The Log Manager can collect the current value of SNMP MIB variables at a specified interval. A wide

range of parameters on device status and network traffic can be sampled for selected nodes and stored

in the database for long-term analysis. This information is displayed with the Log Database Manager in

numeric form (including date, time and data).

MIB Browser

This module is a generic SNMP management tool used to browse device MIBs. By browsing MIBs, you

can send commands to get or set information defined in the MIB.

Information to be recorded into the Log Manager can be selected directly from the MIB. Moreover, the
MIB Browser also provides a convenient editing tool which can be used to quickly extract information from the
MIB and store it for future reference or prepare it as a technical report.

3-3

G

ETTING STARTED

MIB Compiler

This application compiles textual MIB files into database files specifically formatted for EliteView,

which allows relevant EliteView modules to access required information.

MIB-2 Viewer

This module provides an easy-to-use windowed interface to the MIB II (RFC 1213) management

information database. MIB II is maintained by each device that includes a resident SNMP agent. The

traditional approach displays information directly from the MIB, which requires a good understanding
of the overall hierarchical tree structure to locate the variables you need. The MIB-2 Viewer, on the other hand,
organizes this information in a set of commonly referenced items which are displayed in a convenient and easily
understood format.

Name Database Manager

This module provides a convenient means to map an easily remembered mnemonic name to each

device in the network. These names are then used in many other EliteView modules, which allows you

to conveniently specify any network device or view data using the name associated with each device.

Report

This module displays any system events or user-defined events specified in the Event Manager. The

report window shows all network alarm messages in chronological order. Each entity is stamped with a

time and date.

RMON Manager

Remote Network Monitoring allows you to instruct a remote device to collect information or respond

to specified events on an independent basis. An RMON-capable device can independently perform a

wide range of tasks, significantly reducing network management traffic. It can continuously run

diagnostics and log network performance. If an event is triggered, the remote device can automatically
notify the network administrator of a failure and provide historical information about the event. If the remote
device cannot connect to the management agent, it will continue to perform any specified tasks and pass data back
to the management station the next time it contacts the remote device.

3-4

TFTP Server

Trap Manager

WUR

E

LITEVIEW MODULES

This module is used to download agent software to the requesting device. It can be used to download

software to any EZ Stack, TigerStack, and TigerSwitch management module. For all other SMC devices,

downloading is performed via out-of band mode. The TFTP server is also used to perform file transfers

between any two stations running EliteView.

Trap Manager has no tangible user interface. It is only used to pass events to the Event Manager. This

module receives trap messages and converts them into events. By default, the Trap Manager generates a

“Trap” event and outputs a text message to the Event Manager according to the pattern specified in

TRAP.INI. These events are then handled according to the options selected in the Event Manager.

Where You Are is a tool that is used to locate which port on the switch and port to which a remote host

is connected. You only need to input the IP address or MAC address of the remote host; then either

enter a broadcast domain or enter a particular IP range to search for switches, then click Go. Where You

Are will then display the port and the switch that the remote host is connected to.

3-5

G

ETTING STARTED

Data Logging and Event Management

The Log Manager and Event Manager modules play a key role in network management. The following diagrams
depict how they work.

Log Data Manager

EliteView
Application

Database

Filter

Log Manager

Threshold

send request

Trigger Event

get reply

Network

The Log Manager periodically sends requests to target devices according to a fixed polling interval. The target
device receives the requests and sends replies to the Log Manager.

The Log Manager then processes data in two different ways:

• Data passes through the filter you set; it may be saved in the database depending on the condition specified in

the filter.

• Data is checked against a threshold formula. If conditions are satisfied, the Log Manager automatically triggers

the event associated with the log process.

3-6

How the Event Manager Works

D

ATA LOGGING AND EVENT MANAGEMENT

EliteView Application

trigger event

Event Manager

database
management

Run
Program

The Event Manager receives input from EliteView applications such as the main EliteView program, the log
Manager and the Trap Manager. Any named event may be triggered simply by satisfying the user-defined threshold
formula. Any triggered event is passed on to the Event Manager, which activates the proper response, such as
running a program, sounding an audible alarm, displaying a message on screen, displaying a message in the Report
window, or writing to the event database.

Beep

Action

Message
Box

Display Message
in Report Window

3-7

G

ETTING STARTED

Starting EliteView

The main EliteView program provides an
intuitive interface to other program modules.
You can invoke specific management
applications (by clicking on the appropriate
device icon in the network map), verify current
network connections with Discovery, check
device response (via broadcast/search) with
the Alive Test, or fetch information about
selected devices using the MIB browser.

Each module is closely integrated with the
main EliteView program, and can be quickly
invoked by selecting the required function from the Utilities menus. For certain device-specific applications, first
select a target device from the network map and then select the required function from the Tools menu. The
overall relationship between the main EliteView program and its submodules is depicted below.

3-8

Using the Main EliteView Program

To invoke the main EliteView program click on the EliteView icon. Many functions under the main

program provide support for network mapping. These functions include most of the toolbar buttons,

along with the File, Edit and Windows menus. Network mapping is described in the next chapter,

Defining the Network Configuration. After you map out your network, you will want to use the other
functions listed below.

S

TARTING ELITEVIEW

Alive Test

Bootp Server

TFTP Server

Discovery

Telnet

TigerSwitch 8

TigerSwitch 100

EliteView

Platform

EZ Stack 10

TigerStack II

Log Manager

Log Database

Event Manager

Trap Manager

MIB Browser

MIB-2 ViewerMIB-2 Viewer

Report

3-9

G

ETTING STARTED

The menu items and tool buttons used on a regular basis are described below. The items used to construct and
maintain your network map are described in the next chapter.

Table 3-1 EliteView Program Menu Definitions

Menu Label Description

Tools • Zoom – Opens the management module for the selected device.

• Alive Test – Opens the Alive Test for the selected device.

• MIB Browser – Opens the MIB Browser for the selected device.

• MIB-2 Viewer – Opens the MIB-2 Viewer for the selected device.

• Telnet - Opens a connection to another computer on the network
through which you can execute programs or access data as though
attached locally.

• RMON Manager – Provides access to to all nine RMON groups
for recent SMC products that support RMON.

Window • Cascade – Arranges all open EliteView windows in cascaded

fashion.

• Tile – Arranges all currently open EliteView windows in tiled
fashion.

• Arrange Icons – Arranges all EliteView icons on the screen.

• select window – Switches to the selected EliteView window.

3-10

Utilities Accesses most EliteView modules.

S

TARTING ELITEVIEW

Table 3-1 EliteView Program Menu Definitions

Menu Label Description

Options • Change Settings – Allows you to define the default map, SNMP

community, polling interval, default timeout, default retries, and
whether or not to save the desktop when EliteView is closed.

• Change Password – Changes the password required to display
the map.

• Map Information – Displays all user-defined parameters for each
device included in the current map.

• Search Object – Searches for a network device by address or label
(the later of which must be defined in the network map).

• Toolbar & Status Bar – toggle buttons to display or hide these
items.

• Config Toolbar – Utility used to specify toolbar layout.

(not shown here) Floating By clicking anywhere in the background of the EliteView program

you can open a menu that includes various functions relevant to the
current module.

Many of the items included in the menu bar are also provided in the toolbar. The following table describes a few of
the buttons found in the main EliteView program. The other buttons, which are used for creating network maps,

are described in the following chapter.

Table 3-2 EliteView Program Toolbar

Button Label Description

Exit Shuts down the main EliteView program and all subordinate modules.

About Displays the version number for this module.

Help Provides on-line help for this module.

3-11

G

ETTING STARTED

Configuring Polling Parameters

Before directly accessing devices from the network map, you should specify
the default settings. These defaults are provided as a convenience for you,
and are used by both the Add Object command and the device management
modules. Open the Default Settings dialog box by selecting Change Settings
from the Options menu. Set an SNMP community name and polling
parameters which are applicable for your particular network environment.
Depending on your current configuration, you may need to provide any of
the following information.

1. Define a Community describing the administrative relationship between
SNMP entities.

2. Specify the Polling Interval between sending requests, the Default
Timeout to wait for a response, and number of Default Retries to make contact. The settings displayed here
(i.e., 5, 3, 3) should be suitable for most environments.

Status Bar

The Status Bar serves two basic functions. It displays the status of any currently executing command, and indicates
the function of selected toolbar buttons. To display the description for any toolbar button (in the status bar at the
bottom of the screen), position your mouse over the toolbar button, and hold down the left mouse button. After
viewing the description, slide your mouse off the interface button (without releasing the mouse button). Note that
descriptions for toolbar buttons are also provided in relevant sections throughout this manual.

Configuring the Toolbar

The main program and other modules include an option that allows you to
modify the toolbar layout to suit your specific needs. Simply drag the icons
you want from the Available Tools list into the required position in the Tool
Bar list.

Select any object from the Available Tools list on the left and drag it into
position in the Tool Bar layout on the right.

3-12

D

EFINING THE

Before running any EliteView device management tools, first define the device interconnection
hierarchy, network addresses, and mnemonic names for each network node. If you do not already have
this information mapped out, then use Discovery to help identify each device in your network. This
technique may also be used periodically to incorporate changes in the network configuration.

After identifying the basic network configuration, use the Name Database Manager to assign easily
remembered names to each network device. And finally, in the last step, create a detailed network map
including all intermediate network hierarchy and subordinate devices. This map can then be used to
quickly open relevant device management tools by simply double-clicking on a map object.

All the tools and techniques required to define your network configuration are described in this chapter.

N

ETWORK

Quick Guide to Map Building

The simplest approach to creating a network map is listed below:

C

HAPTER

C

ONFIGURATION

4

Table 4-1 Creating a Network Map

Command Menu

Discovery Utilities

Add Object(s) to Name Database

Get Objects Edit

Add Object Edit

Modify Object Edit

Draw Network Connection

Save Map As File

4-1

D

EFINING THE NETWORK CONFIGURATION

1. Use Discovery to locate network devices.

2. Move selected objects from Discovery onto the map by either of the following methods:

• Drag objects directly onto the appropriate map.

• Use the Get Objects command to fetch objects based on protocol type from the queue of discovered

devices.

3. Use the Add Object command to define additional symbolic objects, such as a LAN Segment or Submap.

4. Draw in network connections using the toolbar in the EliteView Platform program.

5. Save your map under an appropriate filename.

Discovery

EliteView can automatically discover any device using a specified protocol (i.e., SNMP over UDP/IP
or IPX) by polling within a specified network community or address range.

EliteView’s Discovery module sends commands out to the network and waits for responses. Devices
are classified based on whether or not they have a resident SNMP agent. When a device responds, EliteView
queries for SNMP functionality. If a device has no resident SNMP agent, EliteView adds a generic bitmap (to the
window for discovered devices) based on protocol type. However, if a device has an agent then EliteView tries to
identify the device type. If the device is recognized, it adds an object icon based on device type, otherwise it adds a
generic bitmap to indicate that the object has an SNMP agent and to show the associated protocol type.

Using Discovery

Use Discovery to build your initial network map or to locate a specific
device. After you have located the concerned devices, drag them onto a
network map where they can be used to conveniently monitor your
network.

You can select Discovery from the Utilities menu in the main EliteView
program, or activate it by clicking on the Discovery icon in the EliteView
program group. Specify the required protocol and then use Broadcast or
Search to locate attached devices.

Using Discovery, EliteView can automatically identify responding devices
and label them with the correct address (based on the selected protocol).
This indicates the status of current network connections, and also serves to
validate the accessibility of devices for subsequent management. Once a
device has been found, simply drag it onto a map and then initiate the
relevant management module by clicking on the device icon.

4-2

1. Select the appropriate network protocol.

2. Broadcast or Search for attached devices.

3. Drag key devices onto the configuration
map for later use.

D

ISCOVERY

When looking for devices using Broadcast, you may need to press the Broadcast button several times to ensure that
all attached devices have responded. For nodes that do not respond to broadcast queries, use the Search function.
In general, it may be necessary to search for devices not located in the same network with the EliteView
management station.

Menu Description

The menus provided for Discovery are briefly introduced below. Toolbar buttons are also described in this section.

Menu Definitions

Table 4-2 Discovery Menu Definitions

Menu Label Description

File Exit current module – Closes the Discovery window and exits to the

calling program (i.e., EliteView platform or Windows Program Manager)

Protocol Protocol selection and advanced settings

Select the devices to display based on network protocol:

UDP/IP – IP & ICMP, SNMP over UDP/IP agent

IPX – IPX, SNMP over IPX agent

Setup menu – Toggles display of devices without an SNMP agent; also sets
the scan rate and retry count.

Name Name database management – Provides editing functions for the name

database, including adding or modifying object data. You can also dump all
the information gathered by Discovery into the Name database.

Tools Alive Test – The Alive Test is used to directly test device response.

Help Help and Version information – Provides detailed on-line help and

displays the version number for this software module.

4-3

D

EFINING THE NETWORK CONFIGURATION

To automatically discover devices:

1. From the Edit menu, choose Discovery.

2. Choose the appropriate network protocol.

3. If you need to change the search criteria for devices,
open the Setup dialog box using the toolbar.

Field Description for Discovery Setup Menu

Table 4-3 Field Description for Discovery Setup Menu

Field Description

Display IP Node Display IP Nodes without an SNMP agent.

Display IPX Node Display IPX Nodes without an SNMP agent.

Display Novell Server Display Novell Servers.

Scan Rate The scan rate between broadcast requests.

Retry The number of times to query for device response.

Auto Set as default when
Protocol changes

For TCP/IP Nodes

Save the current setup as default when restarting Discovery.

• Broadcast within same network.

• Search for nodes across routers.

• Many IP nodes without SNMP can respond to ICMP queries.

For IPX Nodes

• Broadcast is sufficient.

• Search is not available.

• NetWare Servers use IPX protocol.

4. Click on Broadcast to transmit a query message and wait for responses from the local network. Broadcast is also
adequate for gathering global responses from IPX or Ethernet nodes located on different networks.
However, to find IP nodes on other networks, use the Search command and
provide a specific address range. If you are only interested in a specific range
of stations or need to search for stations that are difficult to reach, then click
on the Search button, specify the address range, and adjust the scan rate if
required. Discovery will search for devices within the specified range.

5. The status line at the bottom of the Discovery window shows the status of
the search. To temporarily halt the process, press the Pause button; press
Resume to continue.

4-4

6. The message End of Search will appear when the discovery
process is completed.

7. Move selected objects from Discovery onto the map by either of
the following methods:

• Drag objects directly onto the appropriate map.

•Use the Get Objects command (under the Edit menu) to fetch

objects based on protocol type from the queue of discovered
devices.

8. Draw in the existing connections and save the updated map.
(Refer to Creating Network Maps for detailed information on
building a network map.)

Adding Community Strings to Discovery

Discovery will search for devices within the specified communities.

To include any communities other than “public,” add the appropriate name to the
Community dialog box. You can include all the communities defined for your
network in a broadcast or search command. However, be aware that a blind search
creates excess traffic. Using a more conservative search will have less impact on
network performance.

D

ISCOVERY

Insert access control string for
authorized community

To automatically discover devices in a community:

1. Click on Community to display a list of community strings.

2. To add or modify a community string, click on an entry in the list and edit the
entry in the Edit field. Click OK to continue or Cancel to abandon the new entry.

3. Click on Broadcast to begin searching for devices.

Updating the Name Database

You can enter information directly from Discovery into the name
database. (Refer to the following section for a detailed description of
the Name Database Manager and its applications.) After the search
process has completed, you can use the Discovery toolbar to add
information for selected objects into the database, change information
for a selected object, or dump all the object data directly into the
database.

To add a device into the name database or to edit the description for a
pre-existing device, select an object with the mouse, click on the Add or Change button, and fill in the pertinent
information, including a name that will display beneath the object in the network map and notes for management
reference.

4-5

D

EFINING THE NETWORK CONFIGURATION

Exiting Discovery

To close this module:

1. From the File menu, choose Exit.

2. The Discovery program will be closed.

Name Database Manager

Device names assigned with the Name Database Manager are used in many other EliteView modules
to help you readily select or identify network devices. The Name Database Manager can be opened
from the Utilities menu under the main EliteView program, or directly from the EliteView group
window by double-clicking on the icon shown here.

Also refer to the discussion on Updating the Name Database under the section on Discovery.

You can store information about network devices in the
name database, including a name, network address, physical
address, network protocol, device type, and informal notes.
For normal maintenance, we recommend updating this
information via Discovery. However, when you need to view
the entire database, you can use the Name Database
Manager.

All items included in the menu bar (under the File, Control
and Help menus) are also provided in the toolbar.

4-6

This table describes the basic editing tools.

Table 4-4 Name Database Manger – Editing Tools

Button Label Description

Add Record Adds a new entry into the name database.

N

AME DATABASE MANAGER

Delete
Record

Update
Record

Search
Records

Deletes an entry from the name database.

Updates a current entry in the name
database.

Searches for specified record(s) in the name
database.

Adding a New Entry

Click on the Add Record button to open this dialog box. Enter a suitable mnemonic
name, the network address (UDP/IP or IPX), the physical device address, the
network protocol (IP or IPX), the functional device type, and any informal notes.
Remember to indicate specific device types for SMC network devices and generic
designations for all other network devices. (Also note that the Get MAC function is
only enabled for the UDP/IP protocol under Windows 98, Windows NT 4.0
Service Pack 4 or later, Windows 2000 and Windows XP.)

Deleting Device Entries

Use your mouse to highlight the entries you want to delete and press the delete button. (Note that the same
conventions are followed for selecting multiple items as those used by the Windows File Manager.)

Updating Device Entries

Use your mouse to highlight the entry you want to update. Then change any of fields
in the dialog box as described above under Adding a New Entry. Note that when
device information is dumped from Discovery, the Name field is automatically filled
in using the network address. Therefore, you should update each entry to include a
meaningful name for these devices. You can do this directly from Discovery, but it
may be easier using the Name Database Manager, where the entire list of devices is
readily available for reference.

4-7

D

EFINING THE NETWORK CONFIGURATION

Searching for Device Entries

You can easily display all device entries that meet your specified search criteria. Simply click on the Search button
and fill in the following parameters:

•Search Mode – ALL or MATCHED

• Sort Key – Device Type, MAC address, Name or Protocol

• Sort Order – Ascending or Descending

• Search Keys – Name, Address, MAC Address, Protocol and Device type

If you select a search mode of ALL, then the search keys are disabled and all entries in the name database will be
displayed. If you select MATCHED search mode, you should include the device name, network address, physical
MAC address, protocol type, or device type, or any combination of these. Also remember that the search for
device name is case sensitive.

Creating Network Maps

Network maps are like road maps, they visually depict the entire network hierarchy. Network
administrators use them to trace out the connections between various network devices, and to quickly
activate dedicated management tools for a selected device. These maps describe the status of network
devices, their physical location, and their logical organization. This section describes how to create,

maintain and use network maps.

You can organize
network maps using
any number of
hierarchal levels.

The main EliteView program is used as the primary interface to most of the EliteView modules. However, this is
also where you create and edit network maps. The following menus are used for map functions.

4-8

C

REATING NETWORK MAPS

Menu Description for Map Functions

Many of the items included in the menu bar are also provided in the toolbar. The following table describes these
basic tools.

Table 4-5 Menu Description for Map Functions

Menu Label Description

File New Map – Initializes required parameters to create a new network

Edit Add Object – Adds a new object based on a textual description to

map.

Open Map – Opens an existing network map.

Save Map – Saves the current map along with any changes.

Save Map As – Saves the current map under a new name.

Exit – Exits EliteView, closing all subordinate modules.

the map.

Modify Object – Allows you to modify any parameters for a map
object.

Delete Object – Deletes the selected map object.

Duplicate Object – Copies the selected object, after which you

should reposition it on the map and modify any required parameters.

Connect – Draws in a device connection from the currently selected
object to the next object you click on.

Disconnect – Removes a connection from the currently selected
object to the next object you click on.

Lock – Prevents any changes from being made to the current map.

Unlock – Allows changes to be made to the current map.

Background Bitmap – Selects a bitmap file to use for the map

background.

Text – Allows you to edit text that will be displayed on the map.

Arrange Objects – Orders objects in the map according to your

specifications.

Get Objects – Moves objects from queue of devices (found by
Discovery) onto the network map based on selected protocol type or
network identifier.

4-9

D

EFINING THE NETWORK CONFIGURATION

Menu Label Description

Table 4-5 Menu Description for Map Functions

Options Change Settings – Allows you to define the default map which will

be automatically displayed every time you open the main EliteView
program.

Change Password – Changes password required to display the
current map.

Map Information – Displays all user-defined parameters for each
device included in the current map by means of the Report Program.

Search Object – Locates specified object within map based on label
or address.

For information on menu items or buttons that appear under the main EliteView module but are not described in
this section, refer to “Using the Main EliteView Program” on page 3-9.

Table 4-6 Map Editing Toolbar Buttons

Button Label Description

Add New Object Adds a new object to the current map.

Delete Object Deletes an object from the current map.

Modify Object Modifies the description for an object.

4-10

Connect Object Connects the selected object to another

object.

Disconnect Object Disconnects the selected object from

another object.

C

REATING NETWORK MAPS

Editing Map Objects

The Edit menu provides all the tools you need to compose a full-scale hierarchical map of your entire network.
You may add or modify object descriptions, draw in physical connections, specify a bitmap to display as the
background image for your map, edit any labels or legends required for the map, and then lock it to prevent further
modification.

Adding a Map Object

The best approach to adding a map object is to first locate the target device using Discovery, drag the object onto
your network map, and then enter the additional information using the Modify Object function. However, you may
also add a new object based entirely on the textual description provided under the Add New Object dialog box.

1. Click on the Add New Object button (or press <Insert>).

2. Select an object type. Specific types are provided for SMC network devices. EZ Stack, TigerStack and
TigerSwitch devices are SMC products. For all other network entities, select the appropriate generic device type
as described below.

Table 4-7 Map Generic Device Types

Device Type Description

IP Node Any device connected via IP network protocol.

LAN Segment A network backbone (i.e., view-only object).

SNMP Node Any network device that supports general SNMP/UDP/

IP or functions.

Submap A “hot link” to a submap.

3. Fill in the dialog box with the object attributes described below.

Table 4-8 Map Add New Object Dialog Box

Attribute Description Example

Label Enter up to 16 characters. This label appears below the device icon. Mktg001, Bldg1020,

Hub42.32

Address The network address of the device. Enter in IP or IPX address notation,

depending on selected protocol type, where:

IP – Internet address and IPX – network number: node number.

Community The community string used to access the device. This text string must

match the community string stored in the device. (An incorrect
community string will prevent access to the device.)

IP: 192.72.24.05

IPX: 000ACC01:

000000000001

public

4-11

D

EFINING THE NETWORK CONFIGURATION

Attribute Description Example

Protocol The network protocol of UDP/IP or IPX. UDP

Table 4-8 Map Add New Object Dialog Box

Polling Interval The interval between polling (in seconds). Setting a low value (2 seconds

or less) will generate excessive network traffic and make EliteView seem
very slow and unresponsive. While a very high value will make EliteView
insensitive to changes in device status.

Timeout After sending an SNMP request, EliteView will wait for an appropriate

response (in seconds). If the device does not respond before the
specified timeout, EliteView will assume that the device is no longer
accessible.

Retries When a device does not respond within the Retries limit, the device is

assumed to be off-line. The event “Connection Lost” is announced and
the icon turns red. EliteView will continue polling for responses (unless
Monitor is turned off, as described for the next parameter).

Monitor If this box is checked, then it will be polled at the specified time interval.

If this box is not checked, then polling is disabled. Note that the
resources of the network management station may become overtaxed if
you attempt to monitor an excessively large number of stations.

Sample Configuration

For large networks, you should break the map up into several pieces that
can be opened independently. The following figure shows an example of
the network map for our offices in Europe. The submap icons are logical
links to other maps. In larger networks, you can represent the overall
configuration as logical network segments. To view a subordinate map,
double-click on the corresponding submap icon. The display shows the
path name for the selected submap in the title bar.

5

3 (values greater than
3 are supported, but
not recommended)

10

Yes (checked)

Submaps may also be used to view different maps of the same network.
For example, you might use several maps showing -

• “\Network” as the physical view

• “\Organization” as the logical network hierarchy

• “\Offices” as the network organized by offices

At the next lower level you can depict the network backbone for the selected network. A LAN Segment is a special
kind of view-only object that is designed to show a common backbone on a network. The LAN segment is also
commonly used to depict various networks based on different protocols (e.g., UDP/IP or IPX) connected to a
common backbone.

4-12

C

REATING NETWORK MAPS

At the lowest level, place the actual network devices and draw in all interconnections. This gives you an accurate
picture of the network and also lets you activate applicable management software modules. For SMC’s network
devices, the corresponding device management module will be activated when you double-click on the device icon.

Modifying Objects

1. Select a network device by clicking on its corresponding icon.

2. Click on the Modify Object button.

3. Modify any of the required parameters. Refer to the table “Map Add New
Object Dialog Box” on page 4-11. Be sure to follow the guidelines in this
table when setting the Polling Interval or Timeout.

4. Press OK to continue, or Cancel to abort any changes.

Deleting Objects

1. Select any map object by clicking on its icon.

2. Click on the Delete Object button, or press the Delete key on your keyboard.

Duplicating Objects

1. Select any map object by clicking on its icon.

2. From the Edit menu, choose Duplicate Object. A copy of the object appears in the
upper left corner of your map.

3. Drag the duplicate object to its new location and draw in any corresponding
network connections.

4. For most applications, you will want to modify the object definition. Therefore,
click on the Edit Object button and modify field parameters such as Label and
Address.

Moving Objects

Use “drag and drop” to move an object. Select any map object by clicking on its icon. Holding the left mouse
button down, move the outline of the device icon to its new location, and release the mouse button. If an icon
cannot be moved, the map view has been locked. From the Edit menu, choose Unlock and try again.

Tip: When creating multiple views of the same network, use Duplicate Object to make copies of objects, use

the mouse to “drag and drop” icons to a new location or another submap, and then use Edit Object to
modify the object’s description.

4-13

D

EFINING THE NETWORK CONFIGURATION

Object Status

When an object is first added to the map, the device is “offline.” If an object's monitor flag is enabled, EliteView
will begin polling the device immediately. When the object first responds, device status changes to “online” and a
“device up” event is generated. If an object fails to respond within the specified timeout and retry limits, device
status changes to “offline” and a “connection lost” event is generated. Changes in the status of objects at lower
hierarchal levels in the network map are also reflected in the icons at higher levels (i.e., submap icons change color
to reflect changes in subordinate devices).

Note: To post changes in object status to the Report window, specify Device Up or Connection Lost in the Action

list for the Event Manager. For more information on defining event responses, see Managing Events,
Chapter 8.

Map Limitations

EliteView maps are designed without any arbitrary program limitations. Practical limits are set by the available
system resources.

4-14

C

HAPTER

N

ETWORK

EliteView supports a wide range of network tools that can be accessed directly from the device maps
(see “Creating Network Maps,” Chapter 4) or from the Window’s Program Manager. This chapter describes
utilities designed to allow a device to identify its own IP address, to help the network manager verify the existence
of a device in the network, and to update device software over the network.

T

Setting Addresses with the BOOTP Server

BOOTP is a protocol (running on the UDP/IP stack) used by network devices to find out their own IP address
and identify files which are to be subsequently downloaded to the client device. Typically, IP addresses are assigned
manually by the network administrator and recorded in the device’s permanent storage for ready reference.

For many network sites, managing IP addresses can be a chore. The network manager needs a convenient way to
access every device and dynamically assign its logical address from a central location. Since every device has a
distinct physical network address, a server can run a special network protocol that lets each device lookup its own
IP address based upon its physical address. Although there are many different address assignment protocols,
BOOTP is one of the most popular ones.

5

OOLS

The BOOTP Protocol

The complete BOOTP protocol provides a wide variety of information services. However, EliteView’s BOOTP
Server only provides an IP address for device recognition and a filename for subsequent downloading.

Once a request is received, the BOOTP server uses the client station’s physical address as a key to find the client
station’s IP address. It replies with the corresponding IP address and a path/filename for a generic or specific
device initialization file.

How EliteView’s BOOTP protocol works:

1. A client station needs its IP address or filename information.

2. The client station sends a BOOTP request. Since it may not know its own IP address at this time, it may send
out a request via broadcast.

3. The EliteView BOOTP Server receives the request and uses the client station’s physical address as a key to
lookup the client station’s IP address. Next, the BOOTP Server looks up the filename for the client station.

5-1

N

ETWORK TOOLS

4. The BOOTP Server sends a reply message back to the MAC address initially provided by the client.

A client station may frequently lookup a filename with BOOTP. For example, a filename may be needed by the
client station to download operating system software from a dedicated file server using another protocol
(e.g., TFTP). Since EliteView also provides a TFTP Server, the service request can be completed entirely via
EliteView.

If the client station provides a generic name, such as “unix” or “hubware,” the BOOTP Server will reply with the
corresponding filename in the server. This allows multiple file download services for many kinds of devices. If the
client station does not provide a generic name, the BOOTP server returns the DEFAULT generic filename.

Starting the BOOTP Server

To open the BOOTP Database:

Choose BOOTP Server from the Utilities menu in the
main EliteView program, or directly from the EliteView
program group.

The dialog box for the BOOTP Server will display.

The screen has two parts. The upper half is the list of
address mappings, while the lower half is the list of file
mappings. Each client station has the following
attributes:

5-2

Table 5-1 BOOTP Server Dialog Box

Parameter Description Example

Name Node name. This value is not used by BOOTP, but is useful for the

network manager.List of filename mappings.

MAC Address Physical address of this node. 0000e80a3e9c

IP Address IP network address. 192.219.74.32

Subnet Mask This mask identifies the host address bits used for routing to specific

subnets.

Default Gateway The gateway must be defined if the device is not located in the same IP

segment as the BOOTP server.

Note A short memo field. SNMPDRV2.BIN

Boot File Mappings Generic names map to an actual filenames.

NetWareSV2

255.255.0.0

10.1.0.254

S

ETTING ADDRESSES WITH THE

BOOTP S

Select an entry in the node list to display the Note and filename mapping for the selected node.

Each node in the BOOTP Server can have its own filename mapping list. This provides maximum flexibility for
the network administrator. Default mapping is also provided, where in most cases per-node special mapping is not
required. Click on the DEFAULT name to set both the IP and MAC addresses to zero; this represents the default
file mapping list.

To exit the BOOTP server, click on the Exit button.

Adding and Modifying Node Information

The BOOTP Server starts with a single entry called DEFAULT. No file mapping is
initially defined for this entry. To provide BOOTP service based on generic
information, add the entries you require to the file map for the DEFAULT node. To
service specific nodes, enter data for each node.

To add a new node:

1. Click the Add Node button in the BOOTP Server dialog box. This will bring up
the Add Record dialog box.

2. Enter the following information in the record fields.

ERVER

Table 5-2 Adding a Node to the BOOTP Server

Parameter Description Example

Name Node name; enter up to 14 characters. NetWareServer2

Note: The name cannot contain
space characters.

MAC Address Physical address of the device. 000E80A301

IP Address IP Network Address. 192.255.74.32

Subnet Mask This mask identifies the host address bits used for routing to

specific subnets.

Default Gateway The gateway must be defined if the device is not in the same

segment as the BOOTP server.

Note Enter a note of 100 characters or less. Backup file at Bldg 100-34.5

255.255.0.0

10.1.0.254

3. Click OK to accept the changes or Cancel to abort them. New node information appears in the node address list.

5-3

N

ETWORK TOOLS

To modify a node:

1. Click on the required node in the node address list.

2. Click the Edit Node button.

3. Make any changes to the current information.

4. Click on OK to accept the changes.

To delete a node:

1. Select a node entry by clicking on its address entry.

2. Click on the Del Node button.

The node entry and all associated file mappings are removed.

Adding Filename Mappings

The file mapping list shows every node defined.

To add a filename mapping:

1. Click on an entry in the node address list.

2. Click the Add... button in the File Mappings field to insert a new file map entry.

– The Add File Mapping dialog box will appear.

3. Input the generic name and filename, including the path.

4. Click OK to store the new mapping.
– The new entry will appear in the file mappings list.

To view the note and file mapping(s) for a node, click on the required entry in the address list.

To change filename mappings:

1. Select the file mapping.

2. Click on the Edit button.

3. Change information in the Edit File Mapping dialog box.

4. Click OK to accept changes.

To delete a file mapping:

1. Select the file mapping.

2. Click on Delete.

The filename mapping will be removed.

5-4

D

EFAULT INFORMATION

Default Information

EliteView’s BOOTP Server provides flexible filename mapping. However, you may find it most convenient to
establish a common default for most nodes on the network.

To define a default address with IP and physical addresses:

1. Select the “default” address (0.0.0.0).

2. Define file mappings applicable to all nodes on the network.

Every BOOTP request to lookup a filename will be checked in this priority:

1. Consult the specific node address.

2. If no address is found for the specified node, consult the default file mappings.

In addition to the explicit default file mappings, the BOOTP Server also provides implicit default file mapping.
When a node is included in the address list and the client station provides no generic filename, it is asking for a
default file mapping that you must provide. A DEFAULT filename must be defined for all stations requiring this
type of mapping. If a DEFAULT generic name is not defined, the request is ignored.

Probing Devices with the Alive Test

The Alive Test serves as a basic network monitor. It determines link status by sending packets between
the network management station (i.e., your PC) and the target node (e.g., gateway, hub or node). This
test can be initiated from the Tools menu in the main EliteView program, from the Discovery module,
or directly from the EliteView program group.

The Alive Test can be used with any IP or IPX device – including devices that do not support SNMP (like
gateways). It cannot be used with the Ethernet protocol. To discover the existence of a device, the Alive Test uses
“ICMP echo” for UDP/IP networks, and the IPX Diagnostic command for IPX nodes. If a device responds
correctly, it returns the message to the sender. When the echoed message is received by the sender, it can
determine:

• Existence of the target device

• Round trip delay time

• Relative network throughput (transmission speed, etc.)

• Return ratio (percentage of packets correctly returned)

5-5

N

ETWORK TOOLS

To select a target device:

If you open the Alive Test from the EliteView program group or from the Discovery
module, select the network protocol as UDP/IP or IPX. Then specify the target
address and polling interval.

Initialization window
displayed when opening the
Alive Test from the
EliteView program group or
from Discovery.

However, if you activate the Alive Test from within the main EliteView program
follow these steps:

1. Open a map containing the target device.

2. Select the device with your mouse.

3. From the Tools menu, select Alive Test.

Note that network protocol, target address, and polling interval default to the object
description as defined in the EliteView map.

In a few seconds, a dialog box opens showing device status.

To adjust parameters for the Alive Test:

• Adjust the Time Interval by clicking the up/down arrow to increase or decrease its value. Time interval is the

duration (in seconds) between the transmission of query messages from your PC, the network management
station (NMS).

• Click Pause to halt the Alive Test temporarily.

• Click Resume to re-start the Alive Test.

• Click Reset to clear all the statistics.

• Click Set to specify a gateway for the target device.

• To exit the Alive Test, click on Exit.

The Alive Test collects a number of statistics. These include:

Table 5-3 Alive Test Statistics

Statistics Description Example

Packets Sent Number of messages sent by Alive Test. 7

Packets Received Number of echoed messages received by Alive Test. 6

Received Percentage Ratio of messages received to messages sent. 85%

Average Round Trip Average time interval between the original message sent and the echoed

message received.

5-6

900 ms

D

OWNLOADING FILES WITH THE

Problem Solving with the Alive Test

The Alive Test helps determine a number of network conditions:

1. Symptom: No response with the Alive Test.

Condition:

No response is ever received during an Alive Test.
(packets received is 0).

Possible Cause:

The device does not exist or there is a cabling problem between your network management station and the
target device.

2. Symptom: No response with EliteView (main program), but responds to the Alive Test.

Condition:
A device responds to Alive Test (packets received is not 0).

Possible Causes:
a. The target device does not support SNMP.
b. The community string for the target device does not match the setting for the object in the EliteView map.

Downloading Files with the TFTP Server

TFTP S

ERVER

Network devices frequently include embedded firmware (software stored in ROM or flash memory)
required for their operation. For example, SMC’s EZ family of manageable devices
(e.g., the EZ Stack 10) all include memory for an SNMP agent.

The trivial file transfer protocol (TFTP) is the most common standard for downloading files to network devices.
SMC uses TFTP to download files for most of its manageable networking products.

Starting the TFTP Server

To start the TFTP Server, choose TFTP Server from the Utilities menu in the main EliteView program or directly
from the EliteView program group.

Using the TFTP Server

EliteView’s TFTP Server provides a public directory for general downloading. The default directory is
C:\EV50\PUBLIC. Only files in this directory can be downloaded to a target device or transferred to another
server.

5-7

N

ETWORK TOOLS

To configure the TFTP server, choose Setup from the File menu. The
TFTP Setup dialog box will open, displaying options for the download
directory, the default timeout to wait for a service response, and the default
number of retries before terminating a connection attempt as described
below.

Field Description for Discovery Setup Menu

Table 5-4 Field Description for Discovery Setup Menu

Field Description Example

Public Read Directory Default directory for all files for public downloading. C:\EV50\PUBLIC

Default Timeout Maximum elapsed time (in seconds) TFTP will wait until it gets a

response from a target device. The optimal value depends on your
specific network

Default Retries Maximum number of attempts TFTP will try to get a response

from the target device before declaring that the session has failed.

Viewing the TFTP Process List

When the TFTP server receives a file transfer
request, an entry appears in the process list window.
For each entry, the following parameters are
displayed:

Table 5-5 TFTP Process List

Parameter Description Example

Target Node The IP address of the device that initiates the TFTP file transfer

session.

Role Indicates whether the TFTP server is acting as a server or a

client.

Action Indicates file download or simple transfer. SEND

5 seconds

3

192.74.255.74

Server

5-8

Filename The file being accessed. SNMPDRV.BIN

Progress Current status of the file transfer (based on a percentage of the

file that has already been transferred).

10%

Fetching Files from Other Servers

You can use the TFTP server as a client to receive files from other
TFTP servers.

To start a transfer session:

1. Choose Read File From... from the Service menu.

2. A dialog box will appear requesting additional information.
Check the box Keep File Upon Failure to save a partial file transfer.

The required parameters are defined below.

Table 5-6 TFTP Read File

Parameter Description Example

Target Node IP address of the target TFTP server. This is the source of the original

file.

T

ELNETING TO OTHER COMPUTERS ON THE NETWORK

192.74.255.74

Remote Filename The file you want from the TFTP server. The path is restricted to the

EliteView public directory for security reasons.

Local Filename Name of the file after it has been received. SNMPDRV.BIN

Keep File Upon Failure Click on this check box to save partial results when file transfer fails.

SNMPDRV.BIN

Telneting to Other Computers on the Network

Telnet is a TCP/IP application protocol that allows you to access a remote computer system (e.g., a UNIX or SUN
workstation) as though you were attached locally via a serial terminal. As long as you have a user account on the
target system and the necessary user privilege, you can execute any text command.

If you require frequent access to a particular workstation, you may want to include it in your network map as an IP
Node.

To telnet into a workstation using your network map:

1. Select the appropriate IP node from the network map with your mouse.

2. Open the Tools menu under the main EliteView window and click on Telnet.

3. Log into the remote workstation.

5-9

N

ETWORK TOOLS

Where You Are (WUR)

Where You Are is a tool that is used to locate which port on the switch and port to which a remote host is
connected. You only need to input the IP address or MAC address of the remote host; then either enter a
broadcast domain or enter a particular IP range to search for switches, then click Go. Where You Are will then
display the port and the switch that the remote host is connected to.

File Menu Commands

Load Profile

Loads a saved profile.

Saving a Profile

Saves information on switches discovered by Where You Are by using either Search or Broadcast. The information
includes the switch IP address, MAC address, community string, and the SNMP version used by Where You Are.
This information is automatically written into the switch.ini file in the Program File folder in your PC's file
directory. When Where You Are is subsequently booted up it will automatically read the information previously
written into the switch.ini file and display this information in the main Where You Are screen.

Community

The broadcast function uses a list of SNMP community strings when searching for devices. A device can only
respond to frames with the correct community string. Where You Are can obtain information from switches with
known community strings that have been set to read/write or read- only access mode via the Web interface or the
CLI. You must know the community strings used by devices in your network and enter them in the "Community
Strings" list in the "Community" dialog box (this is one of the security features of the SNMP protocol). Follow the
instructions below to enter the read/write community strings of the Where You Are supported devices from
which you wish to obtain information.
Select Utilities>Community from the Utilities Menu to open the "Community" dialog box. The first time that you
do so, the only string that will be displayed is the default string "public." (This string has read-only access.)

To add or modify a community string, click on an entry in the list, type known existing community strings in the
"Edit" field then click OK to continue or Cancel to abandon the new entry.

Broadcast

Use the Utilities>Broadcast command in the Utilities Menu to transmit a query message and wait for responses
from the local network.

Broadcast follows two steps:

5-10

W

HERE YOU ARE

1. SNMP packets are sent to find switches on the local network. The IP address and MAC address of these
switches are discovered and saved.

2. ICMP packets are sent to all switches on the local network to provide them with the MAC addresses of remote
hosts. These addresses can then be learned and stored in the switches' dynamic address tables.

Parameters

• IP Address: The IP address of the switch.

• MAC Address: The MAC address of the switch.

(WUR)

Search

To find IP nodes on other networks, select Utilities>Search in the Utilities Menu. If you are only interested in a
specific range of devices or need to search for devices that are difficult to reach, then in the Search Range dialog
box, specify the address range, and adjust the scan rate if required. After clicking OK button, Where You Are will
send SNMP packets and ICMP packets to the specific range of devices.

Remove All

Remove all clears all data and returns the application to its original status.

Exit

Closes the WUR application.

Device Menu Commands

Address

Before using the Address function you must first go through the procedures explained in Broadcast or in Search.
Then select Device> Address from the Device menu, enter the IP address or the MAC address of remote host and
click OK. This will result in Where You Are carrying out three functions:

1. Determining the content of the dynamic address tables for all ports on all located switches.

2. Identifying the MAC addresses of all ports on all identified switches

3. Identifying the port number, MAC address and IP address of the port to which the remote host is connected.

If you enter the IP address, Where You Are will automatically convert it to a MAC address and display the MAC
address in the Where You Are title bar.
After you have entered either a MAC Address or an IP Address Where You Are will then carry out the series of
actions listed below.

1. Where You Are will interrogate the dynamic address tables of all previously located switches on the network.

5-11

N

ETWORK TOOLS

2. Where You Are will then copy these dynamic address tables to your PC and display them in a list in the lower
part of the Where You Are dialog box under the heading "Building host table."

3. After completing the copying of dynamic address tables, Where You Are will identify the MAC addresses of all
ports on the located switches and record these in the form of "self address tables."

4. These self address tables will then be displayed beneath the list of dynamic address tables.

5. Where You Are will then identify the port number of the port to which the remote host is connecte, and also
the IP address and MAC address of this port. This information will be displayed below the list of self address
tables.

If Where You Are cannot determine the switch port to which the remote host is connected, it will display a "Not
found" message.
The reasons for Where You Are not determining the switch port to which the remote host is connected are listed
below.

1. The remote host is not connected to any of the previously located switches.

2. All of the switches on the network are unmanaged.

3. The dynamic address table does not record the MAC address of the remote host.

Learn Table

To display the contents of the dynamic address tables (see Device Menu Commands ) for a specific switch, select
the switch and then click on the Learn tab at the bottom of the Where You Are dialog box.

Self Table

To display the contents of the self address tables (see Device Menu Commands ) for a specific switch, select the
switch and then click on the Self tab at the bottom of the Where You Are dialog box.

Option Menu Commands

Setup

Before sending packets to the devices on the local network, you should specify the default settings.

1. Select Options>Setup from the Option Menu.

2. In the Setup dialog box, set polling parameters that are applicable for your particular network environment.

Parameters

• Default Polling: This is the number of times per second that Where You Are will issue SNMP query

messages (see Broadcast.)

•Default Timeout:Maximum elapsed time (in seconds) Where You Are will wait for a response from a target

device. The optimal value depends on your specific network. Default: 5 seconds

•Default Retries: Maximum number of attempts Where You Are will try to get a response from the target

device before declaring that the session has failed. Default: 3

5-12

B

• Auto broadcast on startup: If this box is checked, Where You Are will automatically transmit a broadcast

message on startup.

Output

When you click on the Output tab, the history of actions carried out by Where You Are (as described in Device
Menu Commands) will be displayed.

Batch Upgrade

Batch Upgrade is used for downloading op-code files into switches located on the local network or on remote
networks. The functions included in the File, Utilities, Edit, and Options menus are explained below.

File Menu Commands

Exit

Closes the Batch Upgrade application.

Utilities Menu Commands

ATCH UPGRADE

Community

Click on Community to display a list of community strings.

Broadcast uses a list of community names when searching for devices. A device can only respond to frames with
the correct community name. You must know the community names used by devices in your network and specify
them in the community list. This is one of the security features of the SNMP protocol.

To add or modify a community string, click on an entry in the list and edit the entry in the Edit field. Click OK to
continue or Cancel to abandon the new entry.

Broadcast

Click on Broadcast to transmit a query message and wait for responses from the local network. Broadcast follows
two steps:

1. An SNMP packet is sent to find devices that Batch Upgrade supports.

2. The SNMP packet is sent to specified switches to obtain the information that follows below.

5-13

N

ETWORK TOOLS

If Batch Upgrade can get a response from devices using broadcast frames, it will try to identify the device type by
using SNMP commands. If a device is recognized, the parameters listed below will be displayed on the screen. If a
known switch on the local network is not discovered by Broadcast, then use the Search option.

Search

Use Search to find a specific range of stations, stations on the local network that cannot be discovered by
Broadcast, or stations on IP nodes on other networks. Click on the Search button, specify the address range, adjust
the scan rate if required, then click OK.

Remove All

Remove all clears all data and returns the application to its original status.

TFTP Server

Opens the TFTP Server application. See “Downloading Files with the TFTP Server” on page 5-7.

Upgrade

Click on Upgrade to download the op-code to devices. Upgrade will then process switches in turn. If switches
receive firmware successfully, Upgrade will set the op-code file for start-up and then reboot the device. If a switch
fails to receive the firmware, Upgrade will display an error message and continue to process other switches.

Edit Menu Commands

Select All

Click Select All to select the devices for which you want to upgrade the firmware. You can also click Clear to clear
the devices you have selected from the screen.

5-14

Options Menu Commands

Setup

Click on Setup in the options menu to open a dialog box with the following commands:

Download Same-numbered Version

Check the Download same-numbered version check box to download firmware with the same version number as
the existing firmware in the switch. You may wish to do so if this version of the firmware has been previously
loaded into the switch and there have subsequently been problems with this firmware.

Download Older Version

Check the Download older version check box to download op-code with an older version number than the existing
firmware in the switch.

Default Polling

This is the number of times per second that Batch Upgrade will issue SNMP query messages messages see
Broadcast.

Default Retries

This is the number of times that Batch Upgrade will issue SNMP query messages messages see Broadcast.

B

ACKUP

Backup

Backup is a tool that used to backup the latest version of the configuration file on a network device. It replaces the
conventional way used to backup files by setting SNMP commands. Backup can load devices from a Map file
(Created by EliteView) or an exported file (*.dbf), discover and collect lots of networking devices located in
different places. Users can use simply Drag and Drop operations to configure backup information. After clicking
the Backup or Start Schedule speed button (or using the Utilities menu) the program will automatically process
these devices in turn.

File Menu Commands

Load From Map

Map View can load device from a Network map file.

Refresh File List

Refresh File List refreshes the files in the File View tab.

5-15

N

ETWORK TOOLS

Utilities Menu Commands

Broadcast

Click Broadcast from the Utilities menu to transmit a query message and wait for responses from the local network. Broadcast

is also useful for gathering global responses form Ethernet nodes located on different networks. When you click Broadcast the Backup application does the following:

1. Sends an SNMP packet (IP address is 255.255.255.255) to find network devices.

2. Sends an SNMP packet to specified switches and gets the device information.

3. Adds devices on the network to the Discover view tab.

The user can then select a device, then drag and drop them to the Backup List.

Search

If you are only interested in a specific range of stations or need to search for stations that are difficult to reach or
to find IP nodes on other networks, use the Search command. Click Search from the Utilities menu to open the
Search Range screen. Then, specify the IP address range, adjust the scan rate if required and click OK. When you
click OK the Backup application does the following:

1. Sends an SNMP packet to find network devices within the specified range and gets the device information.

2. Adds devices on the network with an IP address within this range to the Discovery view tab.

The user can then select a device, then drag and drop them to the Backup List.

Backup

To backup the configuration file of the devices, click Backup from the Utilities menu (or the Backup icon) to
download the configuration file from the devices added to the Backup List. Backup will process devices in turn. If
operation is failed that you backup configuration file from a device, Backup will display the error message and
change to process other devices.

5-16

Start Schedule

Select a device from the Backup List and click Start Schedule to start the download schedule for that devices configuration file.

Stop Schedule

Click Stop Schedule to stop the download schedule for that devices configuration file.

Options Menu Commands

Community

Backup will Check and search for devices within the specified communities. To include any communities other than
“private”, add the appropriate name to the Community dialog box, you can include all the communities defined for
your network in a broadcast or search command.

To automatically discover devices in a community:

Click menu Community from the Options menu to display a list of community strings.

B

ACKUP

To add or modify a community string, click on an entry in the list and edit the entry in the Edit field. Click OK to continue or Cancel to abandon the new entry.

Click Broadcast or Search from the Utilities menu to begin searching for devices.

(Note: the Community Strings has to Input read-write privilege for Set Request)

Setup

The Setup screen allows the user to configure daily and weekly backup times as well as the default polling times,
timeout time and number of retries.

Set the start time using the hour (0-23) and minute (0-59) fields. Set the days which to backup by selecting one or
more or the day checkboxes.

Click OK to save the changes

5-17

N

ETWORK TOOLS

5-18

C

HAPTER

6

SNMP MIB M

For all of SMC’s intelligent network devices which include an SNMP-based management agent, you can use the
device management modules in EliteView to easily access and manage detailed network information. EliteView’s
map module allows you to intuitively “zoom in” on objects to see low-level details on device hardware/software
configuration and associated network interface parameters. For all SNMP-based devices (both ours and third-party
products), you can access the complete SNMP Management Information Base (MIB) using the MIB Browser
utility.

EliteView provides three basic MIB management utilities:

• MIB Compiler – Used to update or add modules to MIB database.

• MIB-2 Viewer – Displays MIB-II variables based on a functional grouping.

• MIB Browser – Provides full access to all MIB variables, such as MIB II, Bridge MIB, as well as SMC private

MIBs.

This chapter provides detailed information on managing your device database. The following sections use objects
you have added to your network map. If you do not have a network map, you may want to turn to “Creating
Network Maps” in Chapter 4. For more information about managing specific devices, refer to the appropriate
EliteView users guide.

ANAGEMENT

6-1

SNMP MIB M

ANAGEMENT

MIB Compiler

The MIB Compiler is used to maintain the MIB database used by EliteView. Definitions for standard
objects, network devices, or private third-party devices can be compiled and included in this database.
All device management applications under EliteView consult this database when accessing devices.

Under normal use, rely on the setup program for new management applications to automatically adjust
the MIB database. However, if you need to modify the database yourself, the compile operation can be carried out
interactively, or as a batch process. Specific MIB databases can also be unloaded when they are no longer in use, or
out of date.

Caution: Compiling changes the MIB. Quit EliteView before running this process to make sure no module

accesses the database while it is being compiled.

MIB Database

MIB.DBF, MIB.DBF and MIB.MDX – You can find these files in the EliteView directory. MIB text files have

the following format:

<MIB Name> BEGIN

.

.

.

END

Each MIB text file can contain several MIB modules, which we may call <MIB name>. EliteView accesses
external MIB variables via this name.

6-2

Starting the MIB Compiler

Running the MIB Compiler

Select MIB Compiler from the EliteView program group.

It will automatically load the current MIB database as shown below.

MIB C

OMPILER

The following table describes each function.

Table 6-1 MIB Compiler Dialog Box

Item Description Sample Display

MIB Module List Shows all the modules used by EliteView.

Compile Status

Filename The filename for a module to add or update. smc8608.mib

Module The name of a module as recognized by the MIB database. SMC8608-MIB

Status Shows the current compile status. Merge

Line The current line being compiled. 145

Label The macro currently being processed.

6-3

SNMP MIB M

Item Description Sample Display

Functions

Load Loads a MIB text file into the database. Filename:

ANAGEMENT

Table 6-1 MIB Compiler Dialog Box

C:\EV60\MIB\SMC.MIB

Unload Unloads a MIB module from the database. If the specified module

has any dependencies; i.e., has other modules attached to it, the
compiler will ask whether or not you want to unload the specified
module and all of its dependencies. This is analogous to deleting a
subdirectory – You cannot delete a subdirectory without first deleting
the files it contains.

Current MIB:
RFC1213-MIB

Loading a new MIB

1. Select Load from the MIB Compiler.

2. Type the full name of the MIB file in the Filename field.

Each MIB file defines a MIB module. The MIB name is indicated at the beginning of the file as in the example
below, where the name of the module is given as RFC1213-MIB.

RFC1213-MIB DEFINITIONS::=BEGIN...

All MIBs are defined under the same tree, making MIB definitions related to one another.

The EliteView MIB database identifies MIB objects with names and modules. Each object has a distinct name
within a module, and each module may be loaded or unloaded at any time.

The MIB Compiler reads the specified MIB file and displays the names of the MIB objects as the file is scanned. If
any error occurs during this process, it will stop scanning and display the object label and the line number near
where the error occurred as in the example below:

6-4

MIB-2 V

If an object identifier is not defined, the following message may appear on the screen:

If an unknown object identifier is found in the definition for OBJECT-TYPE, it will be reported after all MIB
objects are checked as in the following error message. In the example given below, you should check the last line of
the OBJECT-TYPE macro section.

Error: Lost connection for node sysObjectID

IEWER

Unloading MIB modules

You can unload a MIB module when it is no longer needed, or when you wish to update or replace it. Highlight the
MIB you want to unload, list currently loaded modules, and then select Unload. If other MIB modules link to the
module you wish to unload, EliteView will ask you to unload these modules first before you can successfully
unload the required module.

Viewing the MIB Module List

Use the scroll bar next to the MIB Module List on the MIB Compiler. This list shows the modules currently loaded
in the MIB compiler.

Things to remember when using the MIB Compiler

• The system always loads the current MIB database.

• To replace a MIB with its new version, first unload the older version and then load the new version.

• If an error occurs during the loading or unloading process, the MIB Compiler automatically skips the erroneous

command and moves on to the next one.

MIB-2 Viewer

The MIB-2 Viewer is a generic SNMP monitoring tool used to browse MIB II (i.e., the Management

Information Base defined by RFC 1213). By browsing through this MIB, you can access information
recorded in MIB II for any SNMP-compliant device attached to your network. However, to set MIB
variables, remember to use the MIB Browser.

Note that although all SNMP devices support MIB II, most groups are optional and may not be implemented.
Only System, Interface and SNMP groups are likely to be found on all systems.

6-5

SNMP MIB M

ANAGEMENT

You can invoke the MIB-2 Viewer from the Tools menu in the main EliteView program (preferably after selecting
a device from the EliteView map), or by clicking on the appropriate icon in the EliteView program group. If you
are not opening the MIB-2 Viewer directly from the EliteView map, then you must also fill in the device interface
parameters in the MIB2VIEW initialization dialog box, including protocol type, target address, SNMP community,
and polling specifications.

Once loaded, the MIB-2 Viewer begins searching for definitions for the
specified object in EliteView’s MIB database. After the target data has been
retrieved, open the directory branches along the path leading to the required
variable by double-clicking on each intervening node. (Note that the icons for
collapsible nodes are highlighted at the top.)

After opening the required window, you can readily view all the key variables
associated with the selected topic. To copy MIB data into the Output
window, just press the Output button. You can edit and save the information

New Open Save Save As

copied to the Output window using the buttons provided in toolbar.

Undo Cut Copy Paste

The toolbar for the MIB Viewer contains two basic button groups for file
management and output editing. After creating a status report via cut &
paste and manual annotation, be sure to save your file before exiting
EliteView. Note that a brief description of every toolbar button is provided
in the Status bar at the bottom of the screen.
( For a more detailed description refer to “Status Bar” in Chapter 3.)

A description of the menus and a few of the display screens used by the
MIB-2 Viewer is provided below. For more detailed information of specific variables, refer to the MIB Browser or
the appropriate RFC.

6-6

MIB-2 V

Menu Bar

The menu bar for the MIB-2 Viewer provides five key menus, namely, File, Edit, Search, Window and Help.
Clicking on any of these items will open a pull-down menu from which you can invoke corresponding commands.

Table 6-2 MIB-2 Viewer Menu Bar

Menu Description

File Contains commands to open and save report files (New Output, Open File, Save Output, Save Output As),

and to exit the host management program (Exit).

Edit* Contains standard editing commands used in conjunction with the Output Window.

Search* Contains editing commands used to find or replace specified text in the Output Window.

Window Contains standard commands for arranging your windows (Cascade, Tile) and icons (Arrange Icons), or

switching to another window.

Help Used to invoke available on-line help functions, or to display the revision number for your current version of

EliteView.

* Only displayed in conjunction with the Output Window.

MIB-2 Directory

The information displayed in the MIB-2 directory is presented in easily understood graphic windows. A few of
these windows are fully described below. For further details on the other directory entries, please refer to textual
descriptions provided by the MIB Browser.

IEWER

System Information

System information is extracted from the System Group in MIB II
(RFC 1213). It provides data on the SNMP agent installed on the device
being monitored.

System Information Window

System Information provides data on the SNMP agent.

Field Descriptions for System Information Window

Table 6-3 Field Descriptions for System Information Window

Field Description

Description Name of the management agent, version number and release date.

Object ID Unique identifier for device model.

6-7

SNMP MIB M

Field Description

System Up for Time since the SNMP agent was last re-initialized.

Contact Name of contact person for this monitored node; and how to make contact.

Name Administrative designation for this node.

Location Physical location of this node.

Service Layers Internet protocol services offered by this node. The OSI model includes: (1) Physical, (2) Data Link,

ANAGEMENT

Table 6-3 Field Descriptions for System Information Window

(3) Network, (4) Transport, (5) Session, (6) Presentation, and (7) Application layers.

Interface Administration

Data for this window is extracted from the Interface Group
in MIB II (RFC 1213). Each MAC frame type supported by a
physical network interface is listed as a unique logical
network interface in the display window. (Refer to ifType in
RFC 1156.) For example, even though there may only by one
physical network interface on a monitored device, it may
concurrently support both ethernet-csmacd and
iso88023-csmacd. Also note that the same type may be
reported more than once where a logical interface includes
several valid subtypes. For example, ethernet-802.2 and
ethernet-II both fall under ethernet-csmacd.

Field Description for Interface Admin Window

Table 6-4 Field Description for Interface Admin Window

Field Description

Interface (Index) A unique index for each subnetwork connection.

Description A textual description of the interface, which may include items such as the product name,

manufacturer, or version number for the hardware interface.

Type The interface type based on the physical/link protocols running immediately below the network

layer, e.g. ethernet-csmacd (where csmacd indicates Carrier Sense Multiple Access/Collision
Detection).

Physical Address The interface address used at the protocol layer immediately below the network layer. This value

will be zero for interface types that do not support such an address.

This window provides a description and status information
on each subnetwork connected to this system.

6-8

Table 6-4 Field Description for Interface Admin Window

Field Description

Interface State The requested state of the interface including the following items. Note that when the interface is

in testing mode, no operational packets can be passed.

up:ready to pass packets

down:not allowed to pass packets

testing:operating in a test mode

Operational State The current operational status of the interface, including the same states as defined above for

Interface State, except where “down” indicates that the device is not capable of passing packets.

Specific Reference to an MIB with definitions for the media type (e.g., Ethernet) used by the interface. If no

information is available, this value will be zero.

Interface Statistics

Data for this window is extracted from the Interface Group
in MIB II (RFC 1213). An entry is included for each
subnetwork interface. This window provides information on
the amount of traffic passing through this interface and the
associated errors. This information can also be displayed as a
graph by clicking STAT, or passed to the EliteView Log
Manager by clicking LOG and defining the required event
criteria. Refer to the sections on Viewing Statistics or Adding
a Log Process if these functions are required.

MIB-2 V

This window provides statistical information on the
traffic and associated errors for the selected interface.

IEWER

Field Description for Interface Statistics Window

Table 6-5 Field Description for Interface Statistics Window

Field Description

Interface (Index) A unique index for each subnetwork connection.

InOctets Total number of bytes received on the interface, including framing characters.

InUcastPkts Number of subnetwork unicast packets delivered to a higher-layer protocol.

InNUcastPkts Number of non-unicast packets (i.e., broadcast or multicast) delivered to a higher-layer protocol.

6-9

SNMP MIB M

Field Description

InDiscards Number of inbound packets that were discarded even though no errors were detected. One

InError The number of inbound packets containing errors that prevented them from being delivered to

OutOctets Total number of bytes transmitted from the interface, including framing characters.

OutUcastPkts Total number of packets requested by higher-level protocols for retransmission to a unicast

OutNUcastPkts Total number of packets requested by higher-level protocols for retransmission to a broadcast

OutDiscards The number of outbound packets containing errors that prevented them from being delivered

OutError Number of outbound packets that could not be transmitted due to errors.

ANAGEMENT

Table 6-5 Field Description for Interface Statistics Window

reason for discarding such packets is lack of buffer space.

a higher-layer protocol.

address, including those either discarded or not sent.

or multicast address, including those either discarded or not sent.

to a higher-layer protocol. One reason for discarding such packets is to free up buffer space.

Viewing Statistics

The STAT button is used to display a real-time graph of the
corresponding counter read during each polling interval.

Click Stat to display the corresponding graph.

Click on Config under the Option menu to change parameters for the
graph. The Config Statistics dialog box appears. You can change the
graph’s scale, ruler, style [i.e., filled curve, curve (fill)], and color, or reset
the graph. Click OK to return to the graph, or Cancel to abort any
changes.

Click on Exit under the Option menu to return to the invoking window.

6-10

Adding a Log Process

The Log button is used to define a new log process for the Log Manager.

The Log Manager performs the following basic functions:

• Periodically records values for device variables.

• Sets thresholds to trigger events when conditions are met.
Click on Log to display the Log Information dialog box.

Complete the entries for Log Name, Filter, Threshold, Event Name, Notes, and
Polling Interval to provide precise control over Logging operations. Refer to Chapter 7, “Collecting Data with the
Log Manager,” for a detailed explanation of the Log Information dialog box.

MIB Browser

The MIB Browser is a generic SNMP management tool used to browse MIBs. By browsing through the

MIB, you can send commands to get or set information defined in the MIB.

You can invoke the MIB Browser by selecting MIB Browser from the Tools menu in the main EliteView
program, or by clicking on the MIB Browser icon in the EliteView program group. Once loaded it begins searching
for definitions for the specified object in EliteView’s MIB database. After selecting a desired variable, you may
issue SNMP commands to get or set various device parameters

MIB B

ROWSER

Basic Functions of MIB Browser

1. The MIB Browser window provides access to the EliteView MIB database. The definitions for all known MIB

variables can be consulted here. This window also provides access to variables stored in managed devices via
the SNMP Get, Get Next, Get Bulk, and Set commands. You can view any of these variables in either ASCII or
binary format, set values for variables that provide write access, or specify a log process.

2. The log utility allows you to define new processes for the Log Manager, and quickly paste selected variables

into the filter and threshold fields.

6-11

SNMP MIB M

ANAGEMENT

Menu Description

The menus provided for the MIB Browser are briefly introduced below.

Menu Definitions

Table 6-6 MIB Browser Menu Definitions

Menu Label Description

File Create Tree – Provides options to open a new tree

(where the default sets the root at the currently
selected node). Exit closes the MIB Browser.

Search Search Functions – Provides search related

functions.

SNMP Access MIB Variables – Provides standard access

commands for MIB variables, along with utilities to
add a new log process, display a graph for a selected
variable, use SNMP Walk to get the value of all the
child nodes of a selected node or show and edit data
in a table using the MIBTable Browser.

6-12

Options Polling – Adjust timing for data requests, including

polling interval, timeout, and retries. Set polling to
comply with the retries defined in the Polling Time
dialog box, or opt to continue polling until the
queried device responds.
Output – Set output to display values in ASCII or
binary, and select value fields to pass to the output
window

View Viewing Facility – View or hide the toolbar and

status bar by clicking on the respective option.
Erase Output – Erase all text from the output
window by clicking on the Clear All option

Table 6-6 MIB Browser Menu Definitions

Menu Label Description

Window Manage Windows – Arrange windows or icons,

or activate an existing window.

Help Help Facility – Access detailed help information

about the MIB Browser.

Accessing Device Values

Fetching Device Values Using The MIB Browser

1. Start EliteView

2. Open your network map. (Refer to Chapter 4 if you have not yet created your network map.)

3. Select the required device by clicking on it with the mouse.

4. Select MIB Browser from the Tools menu. This will bring up the MIB Browser window.

5. Open a new MIB tree by selecting File, New MIB Tree, this will open the New Subtree dialog box. Then open a

new MIB tree by specifying the root variable:

a) Indicate whether the object type is a Label or numeric Object Identifier (e.g. the object identifier for internet

is 1.3.6.1).
b) Select the MIB containing the root from the scroll list.
c) Specify the tree root (or the name of the required object) in the Object edit box.
d) To use the first entry matching the specified prefix, clear the Find exactly check box. To set the tree root at the

exact variable as specified, mark the Find exactly check box. Click OK to continue or Cancel to start the browser
without a tree window.

6. If the MIB Browser is opened from within the EliteView Platform program, the protocol and address of the
selected device will be used. However, if the MIB Browser is activated directly from the EliteView program
group, the last used tree will be opened.

MIB B

ROWSER

6-13

SNMP MIB M

Select MIB Browser from the Tools menu of the
main EliteView program, specify the root for a
new tree in the New MIB Tree dialog box, and
indicate the network protocol used for the
selected device.
If this is not the first time you have used the
SNMP MIB Browser, EliteView will
automatically open the window(s) last used.

SNMP window showing MIB description as it
appears in the MIB database and value for the
highlighted item. Each subwindow may be resized by
dragging on the inner frame with your mouse.

ANAGEMENT

- press for new subtree

- collapsible node

- expandable node

- leaf node

7. Locate the MIB variable you want to browse. Use the scroll bar to move the tree display up or

down, and double-click on any intermediate nodes in the path to the required variable to open the
map for a lower-level hierarchy. After you have found the variable, press the Get Request button to
fetch the required information. The data display options are binary or ASCII. To change the output
mode, use the Output selection under the Options menu.

Note: Object names may be duplicated in different MIB modules. For accurate results, you must select the

correct node.

8. When you select any MIB variable, the textual description (as listed in the database) is automatically displayed

to the right of the tree. Standard entries in the list box include the MIB Name, Object ID, Type, Access, Status,
Range, Size, Description and more depending on the variable selected. The following table describes each
entry.

Table 6-7 MIB Variable Textual Definitions

Item Description

Label Standard name for MIB variable (as appearing in the MIB tree).

MIB Name Name of the MIB module to which the variable belongs.

6-14

MIB B

ROWSER

Table 6-7 MIB Variable Textual Definitions

Item Description

Object ID Dotted-decimal identifier for current variable, indicating its exact location in the database

structure.

Type Refers to the way the data can be accessed. This item is only meaningful for real variables.

Acceptable values include “Read Only,” “Read/Write,” or “No Access.” Note that a Read-Only
object does not support the “set” operation.

Status Can be MANDATORY, OPTIONAL or DEPRECATED. In general, a mandatory object must

be implemented, an optional object may be omitted, and a depreciated object may be taken out of
a definition. However, according to grouping conventions as defined in the standards, objects may
be grouped such that all of them are implemented, or omitted altogether. In such case these
objects may have the status of MANDATORY but not be implemented without violating the
rules.

Index Index to current table entry. The IP address of the target device is commonly used as an index.

Value The value of the current variable. Value type depends on the specific variable.

Range Range of the variable in (x, y) format.

Size Size of the string data in number of bytes.

Description Text that briefly describes the use of the corresponding variable.

9. When you execute a Get Request (or double-click on an item
in the MIB tree) or Get Bulk Request, the value of the
selected variable(s) is retrieved from the managed device and
displayed beneath the textual description. However, note
that when the Get Next request is executed, the next variable
actually retrieved may be several nodes away, so the
ObjectID and Index entries are also displayed.

Get Bulk

Request

Get Request

Get Next

Request

6-15

SNMP MIB M

10. The MIB database contains both simple variables and tables.

ANAGEMENT

For example, the ifEntry uses a single integer to identify each
port (i.e., interface) on a network device. When you expand a
table by double-clicking on the associated node, the Input
Index dialog box will open to query for the required table
index. You can change the table index for the current
variable (provided it is a table) using the Index button.

Much of the object data stored
in the MIBs is organized in
multi-level tables that are
accessed via segmented index
pointers. The Input Index
dialog box allows you to
display the complete index
string either as raw data, or to
display individual index
segments one at a time. Raw
data is generally displayed as a
string of integers or ASCII
text, and is not easy to
interpret for table indexes.
Segmented index entries are
displayed according to the exact data type used for each individual segment, and is generally easier to work
with. The example here shows the segmented index values for a database entry that is accessed with a two-level
pointer.

6-16

11. You can modify the value of variables for which you have write access
(as indicated in MIB definition’s Access field). Once you have located the
required variable, click the Set Request button to open the Input Value
dialog box. The object and object type, as defined in the MIB, are listed in
this box. Input the new value, ensuring that you use the correct type (as
indicated in MIB definition’s Type field). Then click OK to write this value
into the managed device, or Cancel to abort the change.

12. If you need to pause/resume or discontinue a data request, click on the
appropriate buttons in the toolbar.

13. To open the Log Manager select Log from the SNMP menu from the
menu bar. Then have the Log Manager periodically record values for
device variables or set thresholds to trigger events when conditions are
met. To pass a request to the Log Manager, select the MIB variable from
the SNMP tree you want to log by highlighting it with your mouse. Then
select Log from the SNMP menu to open the Log Information dialog box.
Input the required information to provide precise control over logging
operations. Then Click the Ok button and the Log Manager dialog box
will appear.

MIB B

ROWSER

P a u s e R e s u m e A b o r t

6-17

SNMP MIB M

ANAGEMENT

Using the Output Options

The output options dialog box is designed for outputting selected system data
based on information you fetch from the MIB database. You can insert a wide
range of object information into the output window using the data request
functions provided in the MIB Tree. Click on the check boxes to choose the
data that will be output to the output window.

Viewing Output Data

1. Select Output from the Options menu to

open the Output Options dialog box.
Select the output mode as ASCII or
binary, and select the object information
to display. Then press OK to continue or
Cancel to abort the selected output
options.

2. Select the required variables from the

MIB Tree, and then use Get, GetNext, or
Set requests to insert information into
the output window. The outputted data
appears in the bottom right window of
the main MIBBrowser program.

6-18

C

HAPTER

C

OLLECTING

The Log Manager is a powerful tool for the network manager. By collecting relevant network statistics periodically
from all SNMP-compliant network devices, the Log Manager can:

• Record network characteristics (e.g., utilization, error rate)

• Set thresholds to generate events when values are out of range

• Provide the basis upon which you can predict future network load based on current usage and plan for future

requirements

The Log Manager is designed with a filtering mechanism that logs only the data you indicate. The Log Manager
works with other EliteView applications such as the Event Manager, Log Database Manager, and the MIB
Browser. Thresholds can be set to generate specific events to warn the network manager of certain unique
conditions. All information can be logged in a database and easily retrieved in numeric or graphic form. You can
pause logging at any time for a selected process or for the entire system, if necessary.

Events specified in the Log Manager are passed to the Event Manager. In response to an event, an audible alarm,
on-screen message, or a user-defined application can be executed.

D

ATA WITH

L

OG

M

ANAGER

7

Overview

To view the Log Manager window, select Log Manager from the Utilities menu of the main EliteView

program, or from the EliteView program group. If needed, the Log Manager can be started
automatically along with the EliteView main program. (See “Customizing EliteView,” Appendix B.)
The Log Manager can also be invoked from other management modules, like the MIB Browser.

7-1

C

OLLECTING DATA WITH LOG MANAGER

The Log Manager dialog box consists of a menu bar, a toolbar, a list of all
user-defined log processes, and a summary of log parameters for the
currently selected process. Note that the same functions are provided in
both the menu bar and toolbar.

The first step in using the Log Manager is to decide which MIB variables
you should log to solve a specific problem or just to maintain a record of
system performance. If you are not sure about the MIB variables, refer to
their description in the MIB Browser or in the relevant RFC documents.

To display the current log parameters for any process, click on the required
process with your mouse. (The þ and || markers to left of each process
entry indicate whether this process is currently active or paused.)

The toolbar provides access to all functions in the Log Manager. The three
key function groups include data display, process editing, and process
management. To delete, edit, activate, or pause a process, first identify the
concerned process by clicking on it with your mouse, and then select the
appropriate function.

For a description of log parameters listed in the main window, refer to
“Field Description for Log Manager/Information Dialog Boxes” in the
following section.

Add/Delete/Edit
Process

Numeric Data
Display

7-2

Activate/

Pause System

Activate/Pause
Process

Editing a Log Process

EliteView’s powerful Log Manager gathers a wide variety of network statistics based
upon rules (i.e., log processes) you define. Using the Log Manager, you can monitor any
MIB variable for a target SNMP device. Each log process defines the parameters under
which data related to the specified MIB variable is collected and placed in the central
database. The Log Manager controls the data collection activity, as well as allowing you to
display and manipulate the data gathered as described in the section on “Viewing Log
Data”

Adding a New Log Process

1. Click the Add a new record toolbar button.

2. Fill in the parameters in the Log Information dialog box. Process
parameters are defined in the table on the next page.

Not all parameters are required. Only Protocol, Target Address

and Variable are mandatory.

Protocol – Click the down arrow to choose from UDP (default),

IPX or Ethernet.

Target Address – Use appropriate notation for selected

protocol.

Community – Community strings control access rights to
network resources. Define your own community string to prevent
unauthorized access to critical resources. However, if you do not
have any special security concerns, then retain the default
community string of public. Refer to the description for object
editing in Chapter 4 “Defining the Network Configuration.”

MIB Module – Includes standard MIBs based on the RFCs,
device-specific MIBs, and private MIBs. For variable names not
duplicated in other MIB modules, the default of Any is sufficient.

3. Choose OK to add the new log process or Cancel to abort your
selections.

E

DITING A LOG PROCESS

Add/Delete/Edit a

Log Process

7-3

C

OLLECTING DATA WITH LOG MANAGER

Field Description for Log Manager/Information Dialog Boxes

Table 7-1 Field Description for Log Manager/Information Dialog Boxes

Parameter Description Example

Log Name

2

Process identifier displayed in process list.

Protocol Network transport protocol used to request data, i.e., UDP/IP, IPX or

UDP

Ethernet.

Target Address Network address of the target device. 192.168.1.50

Community

2

Community string used to access the target device. public

Version SNMP version in use by Log Manager (SNMPv1 or SNMPv2c) SNMPV2c

Target Name

MIB Module

1

2

A user-defined name for this device stored in the Name Database. MIS Server

Module to search for variable. Select a specific module or Any module. RFC1213-MIB

MIB Variable Name of the variable being polled, (as defined in the MIB database). hubTotalBytes

Index

3

Index to entry in a table variable. 1

Filter Formula used to filter information. VALUE > 100)

AND(TIME < 120000)

Threshold When true, this formula will generate an event and pass it to the Event

R>100

Manager.

Event Name Name of event enabled by Event Manager when threshold condition

CRITICAL

is met.

Polling Interval Elapsed time between data requests (sec). 30

Start Time Time to start log process. (YYYYMMDD) 20040520

Stop Time Time to stop log process. (YYYYMMDD) 20040521

1 - These variables only appear in the Log Manager dialog box.
2 - These variables only appear in the Log Information dialog box.
3 - If you are unsure if an index is required for a variable, first examine the specification for that variable under the MIB Browser.

Modifying a Log Process

To “fine tune” the parameters for any log process, carry out the steps listed below.

1. Highlight the relevant process in the Log Manager screen.

7-4

2. Open the Log Information dialog box by pressing the Edit button.

3. Enter a new value for any parameter.

Deleting a Log Process

1. Highlight the relevant log process in the Log Manager.

2. Click the Delete record toolbar button.

Log Controls

LOG C

ONTROLS

• System Activate/Pause toggles all logging activities on/off.

• Log Activate/Pause toggles logging for a selected process.

Viewing Log Data

Log data is saved in dBASE-compatible files. EliteView offers several ways to view logged data.

To v i ew a log fil e :

• Open Log Manager and double-click on the required process.

• Highlight a process with your mouse, and then press the numeric or graphic

data display icon. (Note that the numeric data display icon is just another entry
point for the Log Database Manager.)

• Open the Log Database Manager from the Program Manager.

Using the Log Database Manager

The Log Database Manager displays data from the different log processes
listed in the Log Manager window. Information in the log database may be
readily copied and shared with other applications. Open the Log Database
Manager as described above. The numeric display posts information for
data matching the filter criteria up to the current polling interval, including
the date, time and specific data for the selected variable. New Arrival shows
the count for filtered data that have not yet been included in the display.
Refer to “Data Logging and Event Management” on page 3-6 for an
illustration of how the Log Manager works.

Activate/Pause
System

Log
Manager

Log
Database
Manager

Activate/
Pause Process

Numeric Data
Display

The Log Database
Manager opens a
numeric display
for the selected

7-5

C

OLLECTING DATA WITH LOG MANAGER

File Menu

The file menu provides functions for retrieving log files, copying selected data to a specified file, or moving
specified data to another file.

To copy selected data to another file, use the Copy To. command. This data is saved in standard dBASE format
(with a dbf extension) and may be accessed using a database program for further processing.

To move selected data to another file, using the Move To. command. Moved data disappears from the database
window. This data is saved in standard dBASE format (*.dbf) and may be accessed using a database program for
further processing.

To load a data file, select Load from the File menu, select the required
process from the Load list and press OK.

Note: The Load option is only enabled when the Log Database Manager

is opened from outside the Log Manager (i.e., from the main
EliteView program or from the EliteView group window). When
using the Log Manager, the Log Database Manager will only load
the process selected from the Log Manager dialog box.

Edit Menu

The edit menu provides functions for deleting selected entries, copying data
to the clipboard, and refreshing the display.

To delete entries from the database, select the required items with your mouse, and then choose Delete from the
Edit menu. Note that deleting all entries will not remove the log file.

To copy entries from the log database to the clipboard, select the required items with your mouse, choose Copy or
Delete from the Edit menu, and then choose Paste from the target application.

Data is logged directly into a log file associated with each process. The Log Database Manager only displays the
data stored in this file. The New Arrival line at the bottom of the dialog box indicates the number of events
recorded into the log file since the last time data was retrieved by the Log Database Manager. To update the display,
use the Refresh command.

7-6

D

EFINING FILTER FORMULAS

Defining Filter Formulas

Filters may be defined for any log process. A filter sets the conditions that determine if data received by the Log
Manager will be saved into the log database. A filter is defined in the Filter field of the Log Information dialog box
(i.e., the dialog box opened when you create or edit a log process). If no filter is defined, then all the data received
is automatically logged.

Filter Formula

The filter formula uses Backus-Naur Form (BNF) as follows:

Filter::= SimpleExpression|

ComplexExpression|

<NULL> -- Nothing

SimpleExpression::=Variable rel_op Value

Variable::= "VALUE"|

"DATE"| --Date the data arrives

"TIME"| --Time the data arrives

rel_op::= ">"| --Greater than

"<"| --Less than

">="| --Greater than or Equal to

"<="| --Less than or Equal to

"=="| --Equal

"!="| --Unequal

Value::=<INTEGER VALUE>| --Number represented in decimal digits, within the range

--Value of the data

of a 4-byte unsigned integer.

<yymmdd>| --Eight digits representing a date.

<hhmmss> --Eight digits representing a time, in 24 hour format

ComplexExpression::=

"(" SimpleExpression ")" |

"(" ComplexExpression ")"|

ComplexExpression logic_op ComplexExpression

logic_op::="AND"|"OR"

7-7

C

OLLECTING DATA WITH LOG MANAGER

Filter Formula syntax

The filter formula can be a simple or complex expression.

Syntax for Simple Expressions

A simple expression conforms to the following syntax:

Variable Relation Value

Variable - Legal variables include:

VALUE -- Value of the data

DATE -- Date the data arrives

TIME -- Time the data arrives

Relation - Legal relations include:

> -- Greater than

< -- Less than

>= -- Greater than or Equal to

<= -- Less than or Equal to

== -- Equal

!= -- Unequal

Value - Legal values include:

<INTEGER VALUE> -- An unsigned integer, 0 ~ 4 bytes long.

<yyyymmdd> -- Eight digits representing a date, where yyyy stands for the year, mm the month

and dd the day

<hhmmss> -- Six digits representing time in 24-hour format, where hh stands for hour, mm

minutes and ss seconds

Syntax for Complex Expressions

A complex expression combines several simple expressions using logical operators. Each expression must be
enclosed in parentheses. The syntax for a complex expression follows:

(Simple Expression) Logical_Operator (Simple Expression)

As described in the previous section a simple expressions should have three basic elements, namely, a Variable,
Relation, and Value. Legal values for each element are described under the syntax for simple expressions.

7-8

Logical_Operator – Legal values include:

AND – Both expressions must be true to meet a given condition

OR – One true expression is enough to meet a given condition

Elements of Filter Formulas

Table 7-2 Elements of Filter Formulas

Parameter Example Description

Variable VALUE Value of the data

Date when the value is reached

Time when the value is reached

Relation >

<

>=

==

!=

Value 256

200040520

132201

Greater than

Less than

Greater than or equal to

Less than or equal to

Not equal

Positive number (4 byte unsigned integer)

Date format (YYYYMMDD) for 20 March 2004

Time format (HHMMSS) for 01:55:01pm

D

EFINING FILTER FORMULAS

Logical_Operator AND

OR

Both statements must be true

Either statement may be true

Notes: 1. The equal to (==) and unequal (!=) expressions follow C language syntax.

2. If more than one expression is used to define a filter, first enclose each expression in parentheses and

then combine them with AND or OR. Parentheses are used to maintain the order of evaluation.
Otherwise conditions are evaluated from left to right.

3. If you want to test a log process without saving data into the database, set the filter formula to an
impossible condition; for example, (TIME<000000).

7-9

C

OLLECTING DATA WITH LOG MANAGER

Example: Filter Formulas

Some possible filter formulas include:

• VALUE > 10000

• (VALUE > 100) AND (VALUE < 10000)

• (DATE < 19990701) AND (TIME>120000)) OR

• ((DATE >=20050701) AND (TIME<120000))

In the last formula, data is filtered on (before 1 May 2004 after 12 noon) or (after 1 May 2004 before 12 noon).

A formula follows this basic syntax:

(Variable Relation Value Logical_Operator)

(Variable Relation Value)

Defining Threshold Formulas

Thresholds are used to trigger events (which are defined in the Event Manager). EliteView’s powerful Event
Manager allows you to define an unlimited number of events corresponding to specific actions. See Chapter 8,
“Managing Events” for more information on defining event response procedures.

EliteView’s Log Manager uses thresholds to trigger an event. For example, a critical event can be handled
whenever CRC errors exceed 5 per minute.

To set thresholds triggering certain events:

1. Define an event using the Event Manager, specifying an Event Name and Event Action.

2. Define threshold limits using the Log Manager. Fill in the Threshold field with the appropriate formula. Also
fill in other necessary fields in the Log Information dialog box.

Threshold vs. Filter Formula

A threshold formula is very similar to the filter formula. In a threshold formula, the value of the data or the data
rate can be used. For example, a threshold formula can monitor value fluctuations based on rates per second, per
minute, or per hour.

Accuracy

Data rates greater than one per second are accurate. In computing data rates per second, the Log Manager
calculates an average between each two consecutive data units.

7-10

Threshold Formula

The threshold formula uses Backus-Naur Form (BNF) as follows:

Threshold::= SimpleExpression|

ComplexExpression|

D

EFINING THRESHOLD FORMULAS

<NULL> -- Nothin

SimpleExpression::=Variable rel_op Value

Variable::= "R"|

"H"| -- Changes in data per hour

"M"| -- Changes in data per minute

"S" -- Changes in data per second

rel_op::= ">"| -- Greater than

"<"| -- Less than

">="| -- Greater than or Equal to

"<="| -- Less than or Equal to

"=="| -- Equal

"!="| -- Unequal

Value::=<INTEGER VALUE>| -- Number represented in decimal digits, within the range of a 4-byte unsigned

-- Value of data

g

integer.

ComplexExpression::=

"(" SimpleExpression ")"|

"(" ComplexExpression ")"|

ComplexExpression logic_op ComplexExpression

logic_op::="AND"|"OR"

Threshold Formula Syntax

The threshold formula can be a simple or complex expression.

7-11

C

OLLECTING DATA WITH LOG MANAGER

Syntax for Simple Expressions

Variable Relation Value

Variable – Legal variables include:

R -- Value of data

H -- Changes in data per hour

M -- Changes in data per minute

S -- Changes in data per second

Relation – Legal relations include:

> -- Greater than

< -- Less than

>= -- Greater than or Equal to

<= -- Less than or Equal to

== -- Equal

!= -- Unequal

Value – Legal values include:

<INTEGER VALUE> – An unsigned integer, 0 ~ 4 bytes long.

Syntax for Complex Expressions

Refer to the same section under Filter Formulas Syntax.

7-12

Elements of Threshold Formulas

Table 7-3 Elements of Threshold Formulas

Parameter Example Description

D

EFINING THRESHOLD FORMULAS

Variable R

H

M

S

Relation >

<

>=

<=

==

!=

Value 256

20040529

135501

Logical_Operator AND

OR

Actual value of the data

Data rate per hour

Data rate per minute

Data rate per second

Greater than

Less than

Greater than or equal to

Less than or equal to

Equal

Not equal

Positive number (4 byte unsigned integer)

Date format (YYYYMMDD) for 29 May 2004

Time format (HHMMSS) for 1:55:01pm

Both statements must be true

Either statement may be true

Example: Threshold Formulas

Some possible threshold formulas include:

• R > 1000

• (M > 5) OR (H > 500)

• (S > 100) AND (R < 10000)

In the last formula, an event is triggered if (the data is changing at the rate greater than 100 per second) or (the
value is less than 10,000).

A formula follows this basic syntax:

(Variable Relation Value) Logical_Operator (Variable Relation Value)

7-13

C

OLLECTING DATA WITH LOG MANAGER

Chart Manager Utility

Raw data can only provide a rough idea of current system status. More detailed analysis is required to

obtain an accurate picture of your network's overall health. The Chart Manager utility allows you to
readily extract information from the database and generate a wide range of charts that provide a clear
picture of network performance.

Basic Functions of Chart Manager

1. The Chart Manager window displays network statistics from a database of log information.

2. The Chart Manager can find information such as the maximum data flow of the network.

3. This information can be used for network management, resource allocation and to improve network efficiency.

Menu Description

The menus provided for the Chart Manager are briefly introduced below.

Menu Definitions

Table 7-4 Chart Manager Menu Definitions

Menu Label Description

7-14

File File Access – Provides options to open a new log

file. Exit closes the Chart Manager.

Summary Summary – Summarizes raw data based on a

selected starting date, ending date, and fixed
interval

Graph Display Function –Displays log data based on

various 2-dimensional and 3- dimensional display
options, and color selections.

Window Manage Displays –Switches the display between

raw data and summary data.

C

HART MANAGER UTILITY

Table 7-4 Chart Manager Menu Definitions

Menu Label Description

Help Help Facility – Access detailed help information

about the Chart Manager.

* Window - indicates the windows for which this menu is active.

Creating Log Charts

Open the Chart Manager utility either from the Utility menu in the main EliteView program or from the Program
Manager. Click on Open under the File menu and select a dBase file (*.dbf) that was generated by the Log Manager.
Names for log files are based on the time the log file was generated, using a format of hhmmss (hh:hour,
mm:minutes, ss:seconds). Information displayed in the log chart includes the following items:

Table 7-5 Log Chart Information

Parameter Example Description

Date 20050322 Date this event was recorded. Format for date is

yyyymmdd (yyyy:year, mm:month,dd:day).

Time 165506 Time this event was recorded. Format for time is

hhmmss (hh:hour, mm:minute, ss:second).

Difference 1086 Difference in value for consecutive events.

Interval 5 Time between consecutive events.

Rate 217 Rate of change in recorded value per second

Editing Data

The significant parameter displayed under the data summary chart and graphic display is the rate of change for the
recorded value. If there are inconsistencies or extreme values for the rate that adversely affect your data summary
or log charts, you can easily adjust these values. Using the edit cursor, double-click on any cell under the Rate
column and change the recorded value. Remember that you can only change values for rate.

7-15

C

OLLECTING DATA WITH LOG MANAGER

Summarizing Data

The amount of data recorded for a process can quickly get out of hand.
However you can easily convert large data files into more manageable form
using the Summary function. Open the Range Selection dialog box by
clicking on Summary in the menu bar. Specify the required range using the
arrow buttons, and then set the data display interval in the edit box to any
integer value. The log charts shown below illustrate the difference between
a chart for raw data and one for summarized data.

7-16