SMC Networks 8606SX - annexe 2 User Manual

Snmp-based network management software for windows
Table of Contents

Advertisement

Quick Links

EliteView
SNMP-Based
Network Management Software
for Windows
User Guide
EliteView 6.10

Advertisement

Table of Contents
loading

Summary of Contents for SMC Networks 8606SX - annexe 2

  • Page 1 EliteView ™ SNMP-Based Network Management Software for Windows ™ User Guide EliteView 6.10...
  • Page 3: User Guide

    EliteView™ User Guide SNMP-Based Network Management Software for Windows ™ 6 Hughes Irvine, CA 92618 Phone: (949) 679-8000 June 2003 R02...
  • Page 4 6 Hughes Irvine, CA 92618 All rights reserved. Trademarks: SMC is a registered trademark; EliteView, EZ Stack, TigerSwitch and TigerStack are trademarks of SMC Networks, Inc. Other product and company names are trademarks or registered trademarks of their respective holders.
  • Page 5: Limited Warranty

    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.
  • Page 6 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.
  • Page 7: About This Guide

    BOUT UIDE About This Guide Welcome to EliteView network management software (version 6.10). 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 optimize the performance and efficiency of your network. General Manual Coverage This manual is your guide to using EliteView to manage all your network resources.
  • Page 8 BOUT UIDE...
  • Page 9: Table Of Contents

    ABLE OF ONTENTS .................... 1-1 HAPTER NTRODUCTION General Description .......................1-1 Management Functions ......................1-2 Application Interface ......................1-2 Features of EliteView ......................1-3 ....................2-1 HAPTER NSTALLATION Installation for EliteView .......................2-1 System Requirements ......................2-1 Using SETUP to Install EliteView ...................2-2 Software Installation ......................2-2 ..................
  • Page 10 ABLE OF ONTENTS Menu Description ......................6-10 Accessing Device Values ..................... 6-11 ............7-1 HAPTER OLLECTING ATA WITH ANAGER Overview ..........................7-1 Editing a Log Process ......................7-2 Modifying a Log Process ....................7-3 Log Controls ..........................7-4 Viewing Log Data ........................7-4 Using the Log Database Manager ..................7-4 Using the Graphic Display Dialog Box .................7-5 Defining Filter Formulas......................7-6 Filter Formula ........................7-6...
  • Page 11 ABLE OF ONTENTS Host Group ........................9-12 Host Top N Group ......................9-14 Matrix Group ......................... 9-16 Filter and Capture Groups ................... 9-19 ..............A-1 PPENDIX YPICAL LITE PPLICATIONS 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 ...........
  • Page 12 ABLE OF ONTENTS Product Overview ........................F-1 Features and Specifications ....................F-1 6.0 DLL S ..........G-1 PPENDIX ICENSE GREEMENT ..................H-1 PPENDIX ROUBLESHOOTING EliteView Map: Icon Stays Red ................... H-1 Discovery: No Nodes Found ....................H-2 Trap Manager: MIB Variable Not Found ................H-2 ..................
  • Page 13: Chapter 1 Introduction

    HAPTER NTRODUCTION EliteView provides a user-friendly interface for managing SMC brand 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.
  • Page 14: Management Functions

    • 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.
  • Page 15: Features Of Eliteview

    NTRODUCTION 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.
  • Page 16 NTRODUCTION...
  • Page 17: Chapter 2 Installation

    This chapter describes setup procedures for EliteView network management software (version 6.10). 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.
  • Page 18: Using Setup To Install Eliteview

    NSTALLATION If you frequently use multiple Windows-based applications, you may need a more powerful environment to run EliteView along with other applications. Otherwise, you may not be able to take advantage of EliteView’s full range of management capabilities. Advanced system requirements include: •...
  • Page 19: Hapter 3 Getting Started

    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.
  • Page 20: Eliteview Modules

    TARTED 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.
  • Page 21 ETTING TARTED 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. You can also set up profiles which are used to fetch or set selected MIB variables as a group.
  • Page 22: Data Logging And Event Management

    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.
  • Page 23 ETTING TARTED The Log Manager periodically sends requests to target devices according to a fixed polling interval. The target device receives the requests and send replies to the Log Manager. The Log Manager then processes data in two different ways: •...
  • Page 24: Starting Eliteview

    ETTING TARTED 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.
  • Page 25 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.
  • Page 26 ETTING TARTED 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.
  • Page 27: Hapter

    HAPTER EFINING THE ETWORK ONFIGURATION Before running any EliteView device management tools, first define the device interconnection hierarchy, network addresses, and mnemonic names for each network node. If you don’t already have this information mapped out, then use Discovery to help identify each device in your network.
  • Page 28: Discovery

    EFINING THE ETWORK ONFIGURATION 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.
  • Page 29: Menu Description

    EFINING THE ETWORK ONFIGURATION Menu Description The menus provided for Discovery are briefly introduced below. Toolbar buttons are also described in this section. Menu Definitions Menu Label Description File Closes the Discovery window and exits to the Exit current module - calling program (i.e., EliteView platform or Windows Program Manager).
  • Page 30 EFINING THE ETWORK ONFIGURATION 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.
  • Page 31: Name Database Manager

    (i.e. UDP/IP or IPX), the physical device address, the network protocol (i.e. IP or IPX), the functional device type, and any informal notes. Rememeber 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...
  • Page 32: Creating Network Maps

    EFINING THE ETWORK ONFIGURATION Updating Device Entries Button Label Description Use your mouse to highlight Adds a new entry into the name database. Record the entry you want to Delete Deletes an entry from the name database. update. Then change any of Record fields in the dialog box as Update...
  • Page 33 EFINING THE ETWORK ONFIGURATION You can organize network maps using any number of hierarchial 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.
  • Page 34 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.
  • Page 35 EFINING THE ETWORK ONFIGURATION 3. Fill in the dialog box with the object attributes described below. Field Definitions for the Add Object Dialog Box Attribute Description Example Label Enter up to 16 characters. This label appears below the device icon. Mktg001, Bldg1020, Hub42.32 Address...
  • Page 36 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 nework devices, the corresponding device management module will be activated when you double-click on the device icon.
  • Page 37 EFINING THE ETWORK ONFIGURATION 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.
  • Page 38 EFINING THE ETWORK ONFIGURATION 4-12...
  • Page 39: Chapter 5 Network Tools

    HAPTER ETWORK OOLS 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.
  • Page 40 ETWORK OOLS Here is 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.
  • Page 41 ETWORK OOLS 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.
  • Page 42 ETWORK OOLS 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.
  • Page 43: Probing Devices With The Alive Test

    ETWORK OOLS 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.
  • Page 44 ETWORK OOLS 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.
  • Page 45: Downloading Files With The Tftp Server

    Downloading Files with the TFTP Server 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.
  • Page 46: Telneting To Other Computers On The Network

    ETWORK OOLS 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: Parameters Description Example Target Node The IP address of the device that initiates the TFTP file transfer session. 192.74.255.74 Action Indicates file download or simple transfer.
  • Page 47: C 6 Snmp Mib M

    SNMP MIB M ANAGEMENT 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.
  • Page 48: Starting The Mib Compiler

    SNMP MIB M ANAGEMENT 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 Each MIB text file can contain several MIB modules, which we may call <MIB name>. EliteView accesses external MIB variables via this name.
  • Page 49 The macro currently being processed. Functions Load Loads an MIB text file into the database. Filename: C:\EV60\MIB\SMC.MIB Unload Unloads an MIB module from the database. If the specified module Current MIB: RFC1213-MIB 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.
  • Page 50 SNMP MIB M ANAGEMENT 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.
  • Page 51: Mib-2 Viewer

    SNMP MIB M ANAGEMENT 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.
  • Page 52: Mib-2 Directory

    SNMP MIB M ANAGEMENT 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.
  • Page 53: Interface Administration

    SNMP MIB M ANAGEMENT Interface Administration Data for this window is extracted from the Interface This window provides a description and status Group in MIB II (RFC 1213). Each MAC frame type information on each subnetwork connected to supported by a physical network interface is listed as this system a unique logical network interface in the display window.
  • Page 54: Interface Statistics

    SNMP MIB M ANAGEMENT Interface Statistics This window provides statistical information on the traffic and associated errors for the selected interface. Data for this window is extracted from the Interface Group in MIB II (RFC 1213). An entry is included for each subnetwork interface.
  • Page 55: Mib Browser

    SNMP MIB M ANAGEMENT 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. •...
  • Page 56: Menu Description

    SNMP MIB M ANAGEMENT Menu Description The menus provided for the MIB Browser are briefly introduced below. Menus are only enabled for applicable windows as indicated in the Window field. Menu Definitions Menu Label Window* Description File Tree File and Printer Access - Provides standard file access and Profile printer functions for the Output Editor window, open and save Output...
  • Page 57: Accessing Device Values

    SNMP MIB M ANAGEMENT Menu Label Window* Description Options Tree Polling - Adjust timing for data requests, including polling Profile interval, timeout, and retries. Set polling to comply with the Output retries defined in the Polling Time dialog box, or opt to continue polling until the queried device responds.
  • Page 58 SNMP MIB M ANAGEMENT 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)
  • Page 59 Index = 0 10. The MIB database contains both simple variables and tables. For example, Value = SMC TigerSwitch 8 V01.01 the atEntry uses the IP address as a pointer to specific network devices. 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.
  • Page 60 SNMP MIB M ANAGEMENT 12. If you need to pause/resume or discontinue a data request, click on the appropriate buttons in the toolbar. To exit the MIB Browser, click on the exit button. 13. You may display the real-time value for suitable variables (i.e., types including counter, integer, gauge or time ticks) by clicking on the Graphical Statistics button.
  • Page 61 SNMP MIB M ANAGEMENT Note: To open an existing profile, select Open Profile from the File menu. To open the profile window, select New Profile from the File menu and enter the target parameters in the dialog box. Select the required variables from the MIB Tree window and press the Add to Profile button.
  • Page 62 SNMP MIB M ANAGEMENT Using the Output Editor The output editor is designed for creating system status reports based on information you fetch from the MIB database. You can insert a wide range of object information into the output editor using the data request functions provided in the MIB Tree and Profile windows.
  • Page 63: Chapter 7 Collecting Data With Log Manager

    HAPTER OLLECTING ATA WITH ANAGER 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 •...
  • Page 64: Editing A Log Process

    OLLECTING ATA WITH ANAGER 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.
  • Page 65: Modifying A Log Process

    OLLECTING ATA WITH ANAGER 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.
  • Page 66: Log Controls

    OLLECTING ATA WITH ANAGER To delete a log process: 1. Highlight the relevant log process in the Log Manager. 2. Click the “Delete record” toolbar button. Note that deleting a process also deletes all log files associated with that process. Log Controls The Log Manager has two basic toggle switches for logging: •...
  • Page 67: Using The Graphic Display Dialog Box

    OLLECTING ATA WITH ANAGER 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.
  • Page 68: Defining Filter Formulas

    OLLECTING ATA WITH ANAGER Click Config to change the display parameters. The Config Statistics dialog box appears. You can change the scale, style (i.e., filled curve, curve, line) and color, or reset the graph. To change the scale, you can adjust the display interval by sliding the red slider up or down on the ruler, by defining a specific interval in the edit box (located in the lower left corner of the dialog box), or by editing the value for each tick mark in the edit...
  • Page 69: Filter Formula Syntax

    OLLECTING ATA WITH ANAGER --Number represented in decimal digits, within the range of a 4-byte unsigned integer. --Eight digits representing a date. --Eight digits representing a time, in 24 hour format 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: - Legal variables include:...
  • Page 70 OLLECTING ATA WITH ANAGER 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.
  • Page 71: Defining Threshold Formulas

    OLLECTING ATA WITH ANAGER In the last formula, data is filtered on (before 1 July 1994 after 12 noon) or (after 1 July 1994 before 12 noon). A formula follows this basic syntax: 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.
  • Page 72: Threshold Formula Syntax

    OLLECTING ATA WITH ANAGER -- Value of data -- Changes in data per hour -- Changes in data per minute -- Changes in data per second -- Greater than -- Less than -- Greater than or Equal to -- Less than or Equal to -- Equal -- Unequal -- Number represented in decimal digits, within the range of a 4-byte...
  • Page 73 OLLECTING ATA WITH ANAGER -- Greater than or Equal to -- Less than or Equal to -- Equal -- Unequal - Legal values include: -- An unsigned integer, 0 ~ 4 bytes long. Syntax for Complex Expressions Refer to the same section under Filter Formulas Syntax. Elements of Threshold Formulas Parameters Example...
  • Page 74 OLLECTING ATA WITH ANAGER 7-12...
  • Page 75: Chapter 8 Managing Events

    HAPTER ANAGING VENTS Understanding the Event Manager Events are special conditions which occur during normal operation of network devices, and normally require the network manager’s attention. Events are generated by the main EliteView program, the Log Manager, and the Trap Manager. In response to messages from the main EliteView program, the Trap Manager or Log Manager, the Event Manager can dispatch actions in any of five different ways.
  • Page 76: Defining Events

    ANAGING VENTS Defining Events The Event Manager supports system and user events, as indicated in the Type field for the selected event. Pre-Defined “System” Events Pre-defined system events include the following: • Connection Lost - a device fails to respond after the specified number of retires. •...
  • Page 77 ANAGING VENTS To define an action: 1. Click on the event name 2. Enter annotation in the Note field (optional) 3. Click on one or more Actions (Beep, Show, Run, Send, Write) Actions Description Example Beep Sound an audible signal on the network management station (i.e., your local PC).
  • Page 78: Using Special Text

    ANAGING VENTS Using Special Text The Event Manager supports special text messages using the $$ and ## symbols in the text boxes. • $$ is substituted with text provided by the source of the event. For example, Trap Manager will pass a text string translated from the trap message provided by the device.
  • Page 79: Receiving Snmp Traps With The Trap Manager

    ANAGING VENTS To erase some or all event information: 1. From the Event Data window, select the target event line. To delete all event information, click the Select All button. The selected entries are highlighted. 2. Click on the Delete button to delete highlighted events. To print information from the event database: 1.
  • Page 80: Trap Manager

    ANAGING VENTS Trap Manager EliteView’s Trap Manager collects trap messages and converts them into events. The Trap Manager generates a “trap” event and outputs a text message according to the pattern specified in TRAP.INI. These events are then handled by the Event Manager. If the TRAP.INI file is changed, re-boot the Trap Manager by closing it and then starting it again.
  • Page 81: Chapter 9 Using Rmon

    RMON provides a cost-effective way to monitor large networks by placing embeded or external probes on distributed network equipment (i.e., hubs, switches or routers). EliteView can access the probes embedded in recent SMC network products to perform traffic analysis, troubleshoot network problems, evaluate historical trends, or implement proactive management policies.
  • Page 82: Starting The Rmon Manager

    RMON SING Starting the RMON Manager To use the RMON Manager, open any network map and select the RMON program from the menu bar . You can also run the RMON Manager directly from the Start Menu by selecting the RMON Manager icon directly from the EliteView program group.
  • Page 83: Rmon Utilities

    The RMON Manager currently provides access to all nine RMON groups, as shown in the following table. Most of SMC’s intelligent products provide support for mini-RMON (which include Statistics, History, Alarms and Events). This selection covers key information required to manage your network on a regular basis, and also switches, and especially on all backbone switches.
  • Page 84 RMON SING Adding or Editing an Entry in the Control Table Click on the Add (Edit) button in the Statistics Control Table to add (edit) an index entry. The dialog box that opens includes three fields (1) entry index number, (2) system interface number, and (3) owner of this entry.
  • Page 85 RMON SING Viewing Statistics The RMON Manager collects statistics that allow you to quickly determine how the network is performing. Information is provided on bandwidth utilization, packet types, errors and collisions, as well as the distribution of packet sizes. Information is also included on peak utilization. Statistics are displayed in both a numeric and graphic format that can be easily interpreted.
  • Page 86 RMON SING...
  • Page 87 RMON SING Statistics are provided for the following areas Field Description Utilization Displays the percentage of bandwidth utilized over the sample period. It also shows the total count, the rate, and the rate of change (delta) for packets and bytes seen on the interface. Packets Displays the total count, the rate, and the rate of change (delta) for all packets, broadcasts, multicasts, and dropped packets.
  • Page 88: History Group

    RMON SING Each of these windows includes a Menu bar and Tool bar with the following items: Field Description File Exit Polling Time (5 - 3600 seconds), Pause, Resume Polling View All, Utilization, Packets, Errors and Collisions, or Packet Size Distribution Control! Control Table Help...
  • Page 89 RMON SING Adding or Editing an Entry in the Control Table Click on the Add (Edit) button in the History Control Table to add (edit) an index entry as shown on the preceding page. Each interface equates to a physical media on the device being monitored. This information can be found under MIB2 (see page 6-5).
  • Page 90: Alarm And Event Groups

    RMON SING Alarm and Event Groups The Alarm and Event Groups allow you to record important events or immediately respond to critical network problems. The Alarm and Event Control Tables (shown below) are used together to define specific criteria that will generate response events. (Note that you must use the scroll bar to display all the columns in the tables.) These tables allow you to add, edit and delete items, or to select a specific index entry and then view the corresponding response event (from the Alarm Table) or triggered events (from the Event...
  • Page 91 RMON SING Field Description Index The system automatically generates an index number. Owner The name of the person who configured the entry in the Control Table. Interval The time interval in seconds over which data is sampled and compared with the rising or falling threshold.
  • Page 92: Host Group

    RMON SING Field Description Index A number that identifies the row in the table. Description A text comment that describes the entry in the Control Table. Type The type of action that is taken for the alarm. This can be None, Log, Trap, or Log and Trap. Community The SNMP community name that a trap manager must use to receive trap messages.
  • Page 93 RMON SING Field Description Index A number that identifies the row in the table. Owner The person who created this entry. Interface A media interface on the monitored device. (MIB-2: 1.3.6.1.2.1.2.2.1.2) Table Size The number of host entries added to this table by the RMON probe. Last Delete Time The last time data was deleted from this table due to lack of space.
  • Page 94: Host Top N Group

    RMON SING By default, the entries are sorted according to address, cumulative values are listed in the numeric table at the top of the screen, and packets/second are displayed in the graph at the bottom of the screen. The configuration and display options are lised below. Field Description File...
  • Page 95 RMON SING Field Description Index A number that identifies the row in the table. Owner The person who created this entry. Host Index, Interface A media interface on the monitored device. (MIB-2: 1.3.6.1.2.1.2.2.1.2) Rate Base The statistic to monitor (In Packets, Out Packets, In Bytes, Out Bytes, Errors, Broadcasts, or Multicasts).
  • Page 96: Matrix Group

    RMON SING The entries are sorted according to the most active hosts, with the change in value (delta) and rate of change shown by the table at the top of the screen, and the rate shown by the graph at the bottom of the screen.
  • Page 97 RMON SING Use the control table shown below to configure entries for the Matrix group, including the device interface and owner. Click on the Add (Edit) button to add (edit) an index entry. The dialog box that opens is described in the following table. Field Description Index...
  • Page 98 RMON SING By default, the entries are sorted according to the source address, cumulative values are listed in the numeric table at the top of the screen, and packets/second are displayed in the graph at the bottom of the screen. Since the graph displays rate, nothing will be displayed for the highlighted entry if no activity was seen during the last polling interval.
  • Page 99: Filter And Capture Groups

    RMON SING Note: When specifying the view for a specific source- destination pair, you can specify both the source and destination, just the source or destination (using Any Address as shown in this example), or all the transmitted and received traffic for a specific address pair (using Reverse direction).
  • Page 100 RMON SING Field Description Owner The person who created this entry. Interface A media interface on the monitored device. (MIB-2: 1.3.6.1.2.1.2.2.1.2) Data Control Indicates if the capture channel is enabled or not. The capture channel may be manually enabled or disabled using the On/Off button. Or a Turn-On Event defined for this channel can be used to enable it.
  • Page 101 RMON SING You can filter raw data for any frame type. Or you can filter detailed information from the header fields if you indicate frame type. When filtering Ethernet II, Ethernet 802.2 or Ethernet SNAP, you can specify the network protocol (IP, IPX, Unknown), as well as the transport protocol (IP: All, TCP, UDP, Unknown;...
  • Page 102 RMON SING The following example shows a filter expression designed to capture any errors occurring in AppleTalk packets. While the other example shows filtering for decoded details that is designed to capture any Ethernet II packets directed to the IP address 10.1.0.23 that have the Don’t Fragment flag set.
  • Page 103 RMON SING Field Description Channel Controls the flow of data through the channel. Index A number that identifies this channel in the channel table. Interface A media interface on the monitored device. (MIB-2: 1.3.6.1.2.1.2.2.1.2) Accept Type Controls how the filters associated with this channel are implemented. Matched - Packets will be accepted if they match both packet data and packet status entries defined in the filter.
  • Page 104 RMON SING - You can quickly display the configuration for channels, filters and Viewing Separate Tables buffers using the tabbed window shown below. The information provided is described in the following tables. Field Description Channels Controls the flow of data and events through the channel. Index A number that identifies this channel in the channel table.
  • Page 105 RMON SING Displaying Buffer Contents - The capture buffer displays information on packets in three different windows. The upper window shows summary information on each packet, including source, destination, timestamp, and protocol type. The middle window decodes information for each layer in the protocol stack.
  • Page 106 RMON SING Notes: 1. To display decoded and raw data for a summary item, highlight it with your cursor. 2. To display raw data corresponding to a decoded entry, highlight it with your cursor. Field Description Load, Save As, Exit File Note that you must pause polling before you can load or save a buffer file.
  • Page 107: Appendixa Typical Elite View Applications

    Users with enough technical knowhow can customize it according to their needs in order to monitor and control SMC or other third-party SNMP devices. This chapter describes a few useful applications you can adopt to your own network environment.
  • Page 108: Managing A Third-Party Device Using The Mib Browser

    Assumption: With the absence of a sample third-party MIB and device, and for purposes of this example, let us assume that SMC’s EZ Stack-10 system is a third-party SNMP device. Let’s say that you want to monitor the total number of packets the third-party SNMP device receives.
  • Page 109: Using The Log And Event Managers To Monitor The Network

    Using the Log and Event Managers to Monitor the Network The Log Manager and the Event Manager are two powerful network monitoring modules. Regardless of whether you are managing SMC or other third-party manageable systems, these two modules work in conjuction with each other to allow flexible network management.
  • Page 110 Target Address IP address of target SNMP device you wish to monitor. 192.72.24.05 MIB Module A collection of managed objects. SMC-MIB Variable Name of variable as defined in the MIB. sysDescr Index Value of index as defined in MIB which is used to access a table.
  • Page 111 YPICAL LITE PPLICATIONS To monitor the total packets received by the target device: 1. Fill in the following table with all available information. Parameter Given Info Target Address 192.72.24.1 Community public MIB Module SMC3116-MIB Variable ifInOctets Index 192.72.24.1 Polling Interval Filter (TIME>080000) AND (TIME<170000) Threshold...
  • Page 112: Customizing Eliteview To Receive Third-Party Traps

    YPICAL LITE PPLICATIONS To monitor the total packets received by the target device: 1. Fill in the following table with all available information. Parameter Given Info Target Address 192.72.24.2 Community MIB Module SMC3116-MIB Variable ifInUnknownProtos Index 192.72.24.2 Polling Interval Filter TIME<0 (This is an impossible filter because you do not want to save any data.) Threshold...
  • Page 113: Exporting Logged Data To Other Software

    YPICAL LITE PPLICATIONS To configure the Trap Manager to receive traps from any third-party SNMP device, you should find answers to the following questions from the vendor of your third-party device: 1. What is the enterprise of the device? 2. How many enterprise (private) traps does the device have? 3.
  • Page 114 YPICAL LITE PPLICATIONS...
  • Page 115: Appendixb Customizing Elite View

    PPENDIX USTOMIZING LITE EliteView is a powerful network management platform that is designed to meet all your needs. To maximize system usability and functionality, EliteView takes full advantage of all user and programming interfaces available in the Microsoft Windows 95, 98, 2000 and NT environments. You can easily customize EliteView by editing the NETMGR.INI, TRAP.INI and the configuration files found in the EliteView directory (C:\EV60).
  • Page 116: Changing Parameters In Netmgr.ini

    USTOMIZING LITE Changing Parameters in NETMGR.INI You may edit any of the sections included in NETMGR.INI to meet the needs of your specific environment. However, a few of the more common changes include the following items. • You may add any Windows-based application to the tools and utilities menus. Edit the [tools] section to add or delete tools;...
  • Page 117: The [System] Section

    The default community string that appears in the Add Object dialog box. Community=public Map= Default map opened by the EliteView main map when it starts. If no Map=SMC default map is assigned, it opens with an empty map. Polling= Default polling interval, measured in seconds. This appears in the Add Polling=1 Object dialog box.
  • Page 118: The [Tools] Section

    • These items are included in the Add Object dialog box. • You can monitor these device types, namely, a Generic Node (i.e., third-party SNMP device) also called an SNMP node, and SMC’s EZ Stack 10. • Both of these devices use the UDP/IP protocol.
  • Page 119 0 Designates the entry as a "Non-EliteView Windows application"; i.e., it cannot work closely with EliteView, but may be initiated from within some EliteView commands as an independent process. 1 Designates the entry as an "EliteView Application"; i.e., it follows the set of rules specified by SMC to allow interaction with other EliteView modules.
  • Page 120: The [Bitmaps] Section

    • For the SNMP node, there is no override. This means that when Zoom and MIB Browser are selected, SNMPTREE.EXE is executed. • For SMC devices, the Zoom command invokes the corresponding EliteView management module; the Alive Test command invokes ALTEST.EXE; and the MIB Browser command invokes SNMPTREE.EXE.
  • Page 121 USTOMIZING LITE The following table describes each item: Parameter Description Device_ID The device identifier defined in the [device] section. bitmap1 The bitmap used to represent the normal status of the device. bitmap2 The bitmap used to represent "down" status of the device. bitmap3 The bitmap used to represent the "not monitored"...
  • Page 122: The [Util] Section

    EliteView, but may be initiated within some EliteView commands as an independent process. 1 Designates the entry as an “EliteView Application;” and that it follows the set of rules specified by SMC to allow interaction with other EliteView modules. Menu_Item This is the text that appears in the menu.
  • Page 123: The [Tftp] Section

    USTOMIZING LITE From the [util] section, you can see the following information: • There are 10 items or options in the Utilities Menu (total=10). • The first item in the menu is the Log Manager. You can run it by selecting it from the Utilities Menu;...
  • Page 124: The [Startup] Section

    0 Designates the entry as a “Non-EliteView Windows application.” This means it cannot work closely with EliteView, but may be initiated within some EliteView commands as an independent process. 1 Designates an “EliteView Application;” i.e., it follows the set of rules specified by SMC to allow interaction with other EliteView modules. Menu_Item This is the text that appears in the menu.
  • Page 125: The [Discover] Section

    USTOMIZING LITE The [discover] Section This section determines the settings for protocol selection and polling parameters under the Discovery module. These settings are determined by the choices you make during Configuration and within the Discovery Setup menu (page 4-3). Parameter Definitions for the [discover] Section Parameter Description protocol...
  • Page 126: The [Generic] Section

    USTOMIZING LITE Elements of a Trap Message Element Description enterprise In a generic trap, this is the object identifier of the device that generates the trap (sysObjectID). In a specific trap, this field contains an identifier used to differentiate the definition domain of the trap. agent-addr The network address of the device that issues the trap.
  • Page 127: The [Enterprise] Section

    USTOMIZING LITE The [enterprise] Section This section lists and defines all enterprises used in the program. Enterprises are object identifiers used in generic and specific traps. To edit the [enterprise] section, 1. Edit the total=n line to specify the total number of available enterprises. The variable n is a positive number that specifies the number of items listed under this menu.
  • Page 128 USTOMIZING LITE To edit specific traps: 1. Define trap message using the following format: message=string The string variable can be any character string with some components generated from the information in the variable list. You can use variables in the form of %x, where x is any letter from a to z.
  • Page 129 USTOMIZING LITE [Ent1.4] message=Hub %b collision count over %a event=1,Trap a=groupTotalCollisions,v b=groupTotalCollisions,i5 [Ent1.5] message=Hub %b alignment error count over %a event=1,Trap a=groupFAEErrors,v b=groupFAEErrors,i5 [Ent1.6] message=Hub %b CRC error count over %a event=1,Trap a=groupCRCErrors,v b=portCRCErrors,i5 [Ent1.7] message=Port(%b,%c)length < 64 bits count over %a event=1, Trap a=portPygmys,v b=portPygmys,i5...
  • Page 130 USTOMIZING LITE B-16...
  • Page 131: Appendixc Snmp E Nvironment

    PPENDIX SNMP E NVIRONMENT EliteView uses Simple Network Management Protocol (SNMP), the most popular network management protocol. SNMP was developed by the Internet Engineering Task Force (IETF) using the Internet Protocol (IP). SNMP was originally designed to run on top of the UDP/IP transport protocol.
  • Page 132: Objects

    OBJECT IDENTIFIER ::= { iso(1) org(3) dod(6) internet(1) private(4) 1} smc OBJECT IDENTIFIER ::= { enterprises 202 } hmBasicCapability OBJECT IDENTIFIER ::= { smc 1} hmSelfTestCapability OBJECT IDENTIFIER ::= { smc 2} hmPerfMonCapability OBJECT IDENTIFIER ::= { smc 3} hmAddrTrackCapability OBJECT IDENTIFIER ::= { smc 4} The MIB itself has a hierarchical structure, defining objects in a tree-like structure.
  • Page 133: Iso Origin

    By comparison, the EV60.EXE file is an executable file and EV60.HLP is a help file for the EliteView program. Branches Some common branches to the iso origin include: Object identifier Numeric identifier iso.org.dod.internet.mgmt.mib2 1.3.6.1.1.2.1 iso.org.dod.internet.mgmt.private.enterprises 1.3.6.1.4.1 iso.org.dod.internet.mgmt.private.enterprise.smc 1.3.6.1.4.1.202 For example, SMC is assigned an identifier of 202 under “enterprise.”...
  • Page 134 SNMP E NVIRONMENT...
  • Page 135: Ppendix

    PPENDIX ECHNICAL EFERENCES Information about networking and protocols is available from RFC reports and industry-related documentation. RFC Reports The most comprehensive collection of networking information is a series of reports called Request for Comments (RFC). Each RFC has a title and an RFC number, such as Internet Protocol, RFC-791. RFCs are all listed in an index, titled rfc-index.
  • Page 136: Industry-Related Documentation

    ECHNICAL EFERENCES RFC Reports RFC Number Title Publisher/Year RFC-768 User Datagram Protocol SRI International, 1980 RFC-783 Trivial File Transfer Protocol (TFTP) SRI International, 1981 RFC-791 Internet Protocol SRI International, 1982 RFC-792 Internet Control Message Protocol SRI International, 1980 RFC-793 Transmission Control Protocol SRI International, 1981 RFC-854 Telnet Protocol...
  • Page 137: Appendixe Performance Tips

    PPENDIX ERFORMANCE EliteView is a flexible network management platform that may be easily customized for your needs. Here are some suggestions that will help your get the best performance from your system. Optimize Your Computer System Fast, local hard disk (< 15 ms access time). High-resolution color display (minimum 1024x768).
  • Page 138 ERFORMANCE E - 2...
  • Page 139: Appendixf Specifications

    PPENDIX PECIFICATIONS EliteView is designed to manage any workgroup using the SNMP network management protocol. Product Overview • Event-driven, scalable, modular architecture • Heterogeneous device management with discovery • Object-oriented, Microsoft Windows 95, 98, NT or XP application with menus-on-demand, drag-and- ®...
  • Page 140 Inventory and Configuration Management Hierarchical network map Unlimited levels Manage heterogeneous devices Manages all SMC adapters. Also manages non-SMC SNMP products with SNMP MIB SNMP MIB tree browser Interactive browser with SET, GET and GET NEXT commands Database of network devices...
  • Page 141: Dll Sub -License Agreement

    This section contains a statement of agreement between Sequiter Software Inc. and the CodeBase 6.0 LICENSEE (SMC) concerning sub-licensing (specifically for software used in the file C4DLL.DLL). All the terms and conditions in this agreement are imposed upon the CodeBase 6.0 DLL SUB- LICENSEE (i.e., the party purchasing the software described in this manual).
  • Page 142 5.0 DLL S ICENSE GREEMENT 2. Sub-License You may use the DLL Software with, and only with, the Distributable Software provided by the CodeBase 6 LICENSEE. You may not use the DLL Software for any other purpose. Specifically, you agree not to use the DLL Software for the purposes of developing or creating Executable Software. 3.
  • Page 143: Appendixh Troubleshooting

    PPENDIX ROUBLESHOOTING This section summarizes the most common error messages generated by EliteView. EliteView Map: Icon Stays Red Symptoms 1. When a map is opened, the icon(s) stay red. 2. When an object is added, the icon stays red. Possible Causes EliteView cannot communicate with the device.
  • Page 144: Trap Manager: Mib Variable Not Found

    ROUBLESHOOTING Suggestions 1. Try changing the address of the EliteView NMS. 2. If EliteView is running, you should see a trap and an alarm indicating that a device has been restarted. From the Alarm Log, copy the IP address into the search criteria and attempt to discover this node.
  • Page 145: Appendixi Error Messages

    PPENDIX RROR ESSAGES The error messages related to the overall EliteView platform are described in this appendix. Error messages relating to specific network devices are listed in the corresponding EliteView manual. The following error messages are sorted by program module. First match the error message’s label with the module name in this appendix, and then look up the error message in alphabetical order.
  • Page 146 RROR ESSAGES Cannot read bitmap file for submap. Cause: The bitmap file of a submap object may be corrupt. Action: Recreate the bitmap file for the submap. Cannot run the program (xxx) Cause: File xxx may be corrupt or does not exist. Action: Reinstall the concerned file.
  • Page 147: Bootp Server

    RROR ESSAGES Invalid timeout value. Cause: The specified value is out of range. Action: The value for timeout must be greater than 1 and less than 86400. Link file is corrupt. Cause: The connection information between objects is corrupt. Action: Recreate the map file. Map file and link file mismatch.
  • Page 148: Bootp.dll

    RROR ESSAGES database Tagname error!! Cause: database error. Action: Check database files. Input parameter invalid!! Cause: Input parameters are not correct. Action: Retype the parameters. Invoke toolbar not successful. Cause: May be out of memory. Action: Close some applications and try again. Open database error!! Cause: Open database file failed.
  • Page 149 RROR ESSAGES Cannot run BTPIFM.EXE. or Cannot run BTPIFM.EXE with error code %d. Cause: Initial BOOTP.DLL error; may be out of memory. Action: Close some applications and retry, or restart windows. The error code comes from the SDK WinExec( ) API function. Cleanup WinSocket failed with error code %d when exiting BTPIFM.EXE! Cause: The Unregister operation from winsock.dll failed.
  • Page 150: Discovery

    RROR ESSAGES Setup receive message error with error code = %d. Cause: Cannot setup a Windows message for received frames. The error code comes from the WSASelect( ) function in the WinSocket specification. Action: Check the network subsystem by error code. The BOOTP application is installed.
  • Page 151 RROR ESSAGES Cannot find IPX Server device in [device] section of NETMGR.INI. Cause: No IPX Server general node information in NETMGR.INI. Action: Use a text editor to add it. Cannot find SNMP general node in [device] section of NETMGR.INI. Cause: No SNMP general node information in NETMGR.INI. Action: Use a text editor to add it.
  • Page 152 RROR ESSAGES IPX Diagnostic Service Socket open failure. Cause: The network sublayer has a problem. Action: Use the alive test program to verify. No bitmap file information in [bitmaps] of NETMGR.INI. Cause: Cannot find any bitmap file information in NETMGR.INI. Action: Use a text editor to edit NETMGR.INI.
  • Page 153 RROR ESSAGES Search for MIB object not successful. Cause: Cannot find the sysObjectID variable in the MIB database. Action: Make sure the MIB database contains MIB II information. The autosave= entity of [discover] in NETMGR.INI is not correct! Cause: The content of autosave= entity is not correct; it should be ON or OFF. Action: Use a text editor to edit NETMGR.INI.
  • Page 154: Event Manager

    RROR ESSAGES Event Manager Out of memory. Cause: Not enough memory. Action: Close some applications and retry. Write Error! Event disabled Cause: Disk full. Action: Free up some disk space and try again. ICMP.DLL The following error messages may occur when running EliteView under a WinSocket platform. Bind ICMP.DLL to ICMP socket failed with error code = %d! Cause: The Bind Socket operation failed.
  • Page 155 Action: Check the network subsystem by error code. ICMP communication channel has terminated. Cause: This is an internal error of the application program. Action: Please contact SMC Technical Support for help. Memory allocation is not successful. Cause: Out of memory.
  • Page 156 So, the program cannot close communication channel. Cause: This is an internal error of the application program. Action: Please contact SMC Technical Support for help. The network subsystem is not ready! Cause: The network subsystem may not be the correct platform.
  • Page 157: Ipx.dll

    RROR ESSAGES IPX.DLL See ICMP.DLL Log Manager Duplicate LOG event. Cause: Requested LOG event is a duplicate. Action: Provide a unique key including a MIB variable label, target node address, and index. Invalid filter. Cause: Incorrect filter format. Action: Refer to the filter formula section in Chapter 7 of this User’s Guide. Invalid threshold.
  • Page 158: Mib Browser

    RROR ESSAGES Number out of range. (1 <= N <= 1000) Cause: The number is out of range for “retry.” Action: Enter a valid number. Number out of range. (1 <= N <= 86400) Cause: The number out of range for “polling interval” or “timeout.” Action: Enter a valid number.
  • Page 159 RROR ESSAGES Cannot open SNMP session. Cause: There are too many sessions or a lower layer (SNMPAPI.DLL) crashed. Action: Close other windows based on SNMPAPI.DLL, or reset the computer and restart Windows. Cannot read file. Cause: Cannot read a text file from disk. Action: Verify that the correct file was specified, or recreate the file.
  • Page 160: Mib Compiler

    Action: Add a new MIB that contains the required object into the MIB database. SNMP GetRequest Error. Cause: Lower layer (e.g., SNMPAPI.DLL) cannot build the SNMP GetRequest. Action: Please contact SMC Technical Support for help. SNMP GetNextRequest Error. Cause: Lower layer (SNMPAPI.DLL) cannot build the SNMP GetNextRequest.
  • Page 161 RROR ESSAGES %s has already been imported. Cause: A duplicate MIB Name has been found in line xxx of the “mib_file.” Action: If they are different MIB modules, rename one of the modules, and then compile it into the database. If they are the same, reload the latest module, and compile the new MIB. Trap error.
  • Page 162 RROR ESSAGES ACCESS %s in %s near line %d is unknown. Cause: The ACCESS clause of a variable has an invalid value in line xxx. Action: Correct it and compile the MIB file again. Status “%s” in %s near line %d is unknown Cause: The STATUS clause of a variable has an invalid value in line xxx.
  • Page 163: Mib.dll

    RROR ESSAGES Index “%s” is not defined in the database or MIB file. Cause: The MIB Compiler cannot find the referenced index node in the database. Action: You should check if the index is defined in other MIBs. If yes, add the MIB in the import list.
  • Page 164: Mib-2 Viewer

    RROR ESSAGES MIB-2 Viewer Cannot find the text any more! Cause: The text you specified cannot be found at the other position. Action: None. Cannot find this text. Cause: The text you specified cannot be found. Action: Verify text. Cannot open statistics window. Cause: System may be out of resources.
  • Page 165: Report

    RROR ESSAGES Report Cannot access printer. Cause: Cannot create device context. Action: Memory may not be enough. Cannot find the text specified. Cause: Report cannot find the specified text. Action: Check the case, and be sure the text is correct. File is too large, the content of file will be truncated.
  • Page 166 Initialize mib database failed, the download function will be disabled. Cause: The MIB may not contain the SMC MIB. Action: Use the MIB compiler to add the SMC MIB. Initialize namebase failed. Cause: The name database dynamic library failed to initialize.
  • Page 167: Tftp.dll

    RROR ESSAGES TFTP.DLL Bind to UDP socket failed with error code = %d. Cause: The Bind Socket operation failed. The error code comes from the function bind( ) of the WinSocket specification. Action: Check the network subsystem by error code. Cannot allocate callback routine.
  • Page 168 RROR ESSAGES No usable WinSock.dll found. Cause: The WinSocket network subsystem failed. Verify the platform. Action: Check the network subsystem. Open UDP socket failed with error code = %d. Cause: An Open Socket operation failed. The error code comes from the function socket( ) of the WinSocket API.
  • Page 169: Trap Manager

    Action: Load the MIB(s) which contains these variable(s) into the MIB Database, and restart the Trap Manager. Out of memory. Cause: Out of memory. Action: Close other programs and retry. Trap Manager cannot register trap channel. Cause: (Internal error.) Cannot register a trap channel. Action: Contact SMC Technical Support. I-25...
  • Page 170 RROR ESSAGES I-26...
  • Page 171: Ppendix

    RODUCT UPPORT ERVICES SMC is an international corporation that offers worldwide technical support. Many of these services are available 24 hours a day. To help us serve you more effectively, please have the following information available before calling SMC: AUTOEXEC.BAT •...
  • Page 172 RODUCT UPPORT ERVICES...
  • Page 173: Glossary

    A logical binding between two or more users of a service. EliteView EliteView is a complete network management platform. EliteView is composed of a core program and groups of related modules. EliteView is a complete network management product with modules for managing SMC and third-party SNMP devices. Ethernet A 10 Mbps baseband LAN that uses a bus configuration and CSMA/CD.
  • Page 174 LOSSARY Internetwork Packet Exchange is a NetWare protocol providing datagram message delivery. Local Area Network (LAN) A group of interconnected computers and other devices. MAC Address Media Access Control address that represents a unique physical address for each port in a local area network.
  • Page 175 LOSSARY SNMP Simple Network Management Protocol (SNMP). The application protocol offering network management services in the Internet suit of protocols. Software Interrupt The software interrupt is the communication channel between the device driver (e.g., ODIPD or NWPD) and other applications (e.g., WINPD or ELITEVIEW). The recommended software interrupt is 0x60 (60 hex).
  • Page 176 LOSSARY Glossary-4...
  • Page 177: Index

    NDEX Alarm Group 9-9 History Group 9-8 Alive Test 3-2, 5-5 initialization files B-1 BOOTP Server 3-2, 5-1 NETMGR.INI B-2 broadcast 4-2 TRAP.INI B-11 buffer, displaying 9-26 installation 2-1 Capture Group 9-19 log database 7-4 channel, configuring 9-22 manager 3-2, 7-4 CodeBase 5.0 DLL G-1 Log Manager 3-2, 7-1, A-3 community string 3-8, 4-4...
  • Page 178 NDEX product support J-1 profile window 6-14 Report module 3-3 window 8-6 RFC reports D-1 RMON 9-1 Manager 3-3, 9-2 utilities 9-3 SNMP C-1 trap 8-5 sub-license agreement G-1 support services J-1 system event 8-2 requirements 2-1 TCP/IP 3-1 technical support J-1 Telnet 5-8 TFTP Server 3-4, 5-7 third-party...
  • Page 179 97 14 299 4466 Fax 97 14 299 4664 Thailand: 66 2 651 8733 Fax 66 2 651 8737 If you are looking for further contact information, please visit www.smc.com, www.smc-europe.com, or www.smc-asia.com. 6 Hughes Irvine, CA 92618 Phone: (949) 679-8000...

This manual is also suitable for:

8608sx - annexe 38606t - annexe 2Eliteview 6.10

Table of Contents