MANAGEMENT GUIDE EliteViewTM 6.
EliteView™ User Guide SNMP-Based Network Management Software for Windows™ 20 Mason Irvine, CA 92618 Phone: (949) 679-8000 May 2008 Pub. # 149100039100A E052008-DG-R6.
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.
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.
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.
ABOUT 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 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.
iv
CONTENTS 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Management Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Application Interface . . .
CONTENTS Quick Guide to Map Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Using Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CONTENTS 6 SNMP MIB Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1 MIB Compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Starting the MIB Compiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 MIB-2 Viewer . . . . . . . . . . . . . . . . . . . . .
CONTENTS 8 Managing Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-1 Understanding the Event Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1 Starting the Event Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1 Defining Events . . . . . . . . . . . . . . . . . . . . .
CONTENTS The [system] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3 The [device] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3 The [tools] Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CONTENTS H Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H-1 I Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-1 EliteView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-1 BOOTP Server . . . . . . . . . . . . . . . . . . . . . . .
TABLES Table 3-1 Table 3-2 Table 4-1 Table 4-2 Table 4-3 Table 4-4 Table 4-5 Table 4-6 Table 4-7 Table 4-8 Table 5-1 Table 5-2 Table 5-3 Table 5-4 Table 5-5 Table 5-6 Table 6-1 Table 6-2 Table 6-3 Table 6-4 Table 6-5 Table 6-6 Table 6-7 Table 7-1 Table 7-2 Table 7-3 Table 7-4 Table 7-5 Table 7-6 Table 8-1 Table 8-2 Table 8-3 Table 9-1 Table 9-2 Table 9-3 Table 9-4 Table 9-5 Table 9-6 Table 9-7 Table 9-8 EliteView Program Menu Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TABLES Table 9-9 Table 9-10 Table 9-11 Table 9-12 Table 9-13 Table 9-14 Table 9-15 Table 9-16 Table 9-17 Table 9-18 Table 9-19 Table 9-20 Table 9-21 Table 9-22 Table 9-23 Table 9-24 Table A-1 Table A-2 Table A-3 Table B-1 Table B-2 Table B-3 Table B-4 Table B-5 Table B-6 Table B-7 Table B-8 Table B-9 Table B-10 Table B-11 Table B-12 Table B-13 Table B-14 Table B-15 Table C-1 Table D-1 Table E-1 Table F-1 Table J-1 xiv Statistics Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CHAPTER 1 INTRODUCTION 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.
INTRODUCTION 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.
FEATURES OF ELITEVIEW 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.
INTRODUCTION 1-4
CHAPTER 2 INSTALLATION 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 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.
CHAPTER 3 GETTING STARTED 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.
GETTING 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.
ELITEVIEW MODULES 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.
GETTING 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.
ELITEVIEW MODULES TFTP Server 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 Trap Manager has no tangible user interface. It is only used to pass events to the Event Manager.
GETTING 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.
DATA LOGGING AND EVENT MANAGEMENT How the Event Manager Works EliteView Application trigger event Event Manager database management Run Program Beep Action Message Box Display Message in Report Window 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.
GETTING 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.
STARTING ELITEVIEW 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.
GETTING 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 Tools Description • 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.
STARTING 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.
GETTING 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.
CHAPTER 4 DEFINING THE NETWORK CONFIGURATION 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.
DEFINING 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.
DISCOVERY 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.
DEFINING 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.
DISCOVERY 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.
DEFINING 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.
NAME DATABASE MANAGER 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. Delete Record Deletes an entry from the name database. Update Record Updates a current entry in the name database. Search Records Searches for specified record(s) in the name database. Adding a New Entry Click on the Add Record button to open this dialog box.
DEFINING THE NETWORK CONFIGURATION Searching for Device Entries You can easily display all device entries that meet your specified search criteria.
CREATING 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 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.
DEFINING THE NETWORK CONFIGURATION Table 4-5 Menu Description for Map Functions Menu Label Description 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.
CREATING 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.
DEFINING THE NETWORK CONFIGURATION Table 4-8 Map Add New Object Dialog Box Attribute Description Example Protocol The network protocol of UDP/IP or IPX. UDP 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.
CREATING 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.
DEFINING 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.
CHAPTER 5 NETWORK TOOLS 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.
NETWORK 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.
SETTING ADDRESSES WITH THE BOOTP SERVER 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.
NETWORK TOOLS To modify a node: 1. 2. 3. 4. Click on the required node in the node address list. Click the Edit Node button. Make any changes to the current information. 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.
DEFAULT 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.
NETWORK 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.
DOWNLOADING FILES WITH THE TFTP SERVER 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.
NETWORK 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.
TELNETING TO OTHER COMPUTERS ON THE NETWORK 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.
NETWORK 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.
WHERE YOU ARE (WUR) 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.
NETWORK 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.
BATCH UPGRADE • 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.
NETWORK 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.
BACKUP 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.
NETWORK 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.
BACKUP 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.
NETWORK TOOLS 5-18
CHAPTER 6 SNMP MIB MANAGEMENT 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.
SNMP MIB MANAGEMENT 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.
MIB COMPILER 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. The following table describes each function. Table 6-1 MIB Compiler Dialog Box Item Description MIB Module List Shows all the modules used by EliteView. Sample Display 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.
SNMP MIB MANAGEMENT Table 6-1 MIB Compiler Dialog Box Item Description Sample Display Load Loads a MIB text file into the database. Filename: 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.
MIB-2 VIEWER 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.
SNMP MIB MANAGEMENT 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.
MIB-2 VIEWER 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).
SNMP MIB MANAGEMENT Table 6-3 Field Descriptions for System Information Window 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.
MIB-2 VIEWER 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.
SNMP MIB MANAGEMENT Table 6-5 Field Description for Interface Statistics Window Field Description InDiscards Number of inbound packets that were discarded even though no errors were detected. One reason for discarding such packets is lack of buffer space. InError The number of inbound packets containing errors that prevented them from being delivered to a higher-layer protocol. OutOctets Total number of bytes transmitted from the interface, including framing characters.
MIB BROWSER 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.
SNMP MIB MANAGEMENT Menu Description The menus provided for the MIB Browser are briefly introduced below. Menu Definitions Table 6-6 MIB Browser Menu Definitions Menu 6-12 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.
MIB BROWSER 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. 2. 3. 4. 5. Start EliteView Open your network map. (Refer to Chapter 4 if you have not yet created your network map.) Select the required device by clicking on it with the mouse.
SNMP MIB MANAGEMENT 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.
MIB BROWSER 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.
SNMP MIB MANAGEMENT 10. The MIB database contains both simple variables and tables. 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.
MIB BROWSER 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).
SNMP MIB MANAGEMENT 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.
CHAPTER 7 COLLECTING DATA WITH LOG MANAGER 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.
COLLECTING 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.
EDITING A LOG 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.
COLLECTING 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 Name2 Process identifier displayed in process list. Protocol Network transport protocol used to request data, i.e., UDP/IP, IPX or Ethernet. UDP Target Address Network address of the target device. 192.168.1.50 Community2 Community string used to access the target device.
LOG CONTROLS 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 • • System Activate/Pause toggles all logging activities on/off. Log Activate/Pause toggles logging for a selected process. Activate/Pause System Activate/ Pause Process Viewing Log Data Log data is saved in dBASE-compatible files.
COLLECTING 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.
DEFINING 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.
COLLECTING DATA WITH LOG MANAGER Filter Formula syntax The filter formula can be a simple or complex expression.
DEFINING FILTER FORMULAS 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 Logical_Operator > Greater than < Less than >= Greater than or equal to == Less than or equal to
COLLECTING 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).
DEFINING THRESHOLD FORMULAS Threshold Formula The threshold formula uses Backus-Naur Form (BNF) as follows: Threshold::= SimpleExpression| ComplexExpression| -- Nothing SimpleExpression::=Variable rel_op Value Variable::= rel_op::= "R"| -- Value of data "H"| -- Changes in data per hour "M"| -- Changes in data per minute "S" -- Changes in data per second ">"| -- Greater than "<"| -- Less than ">="| -- Greater than or Equal to "<="| -- Less than or Equal to "=="| -- Equal "!="|
COLLECTING 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: – An unsigned integer, 0 ~ 4 bytes long.
DEFINING THRESHOLD FORMULAS Elements of Threshold Formulas Table 7-3 Elements of Threshold Formulas Parameter Variable Relation Value Logical_Operator Example Description R Actual value of the data H Data rate per hour M Data rate per minute S Data rate per second > Greater than < Less than >= Greater than or equal to <= Less than or equal to == Equal != Not equal 256 Positive number (4 byte unsigned integer) 20040529 Date format (YYYYMMDD) for 29 May 2004 135501 Time format (
COLLECTING 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.
CHART 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.
COLLECTING 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.
CHART MANAGER UTILITY Displaying Graphic Charts Graphic displays are generally more informative than a simple numeric listing. The Chart utility makes it easy for the user to display either raw or summarized data in various graphic formats. To draw a graph of a specific range, select the data to be displayed by positioning the cursor over the first entry you want to display, then holding down the left mouse button, drag the cursor to the last process in the required range.
COLLECTING DATA WITH LOG MANAGER Graph Controls The Graph Control window gives the user options to change the way data is displayed in the graph. The user has control over all aspects of the graphs. Graphs can be displayed in 2D or 3D. The user can change and add color, style, labels and many more features to the graph. A full list of these features is detailed in Table 7-6 below. To open the Graph Control window: 1. Open a graphic chart display.
CHART MANAGER UTILITY Table 7-6 Chart Manager - Graph Control Tab Title Description Titles Edit the names and layout of the titles that are used in the graph By typing the name into the text field available for each title. Each graph may have a graph title, bottom title, left title and right title. The left and right titles can be set to be read horizontally or vertically up or vertically down by clicking the respective radio button.
COLLECTING DATA WITH LOG MANAGER Table 7-6 Chart Manager - Graph Control 7-20 Tab Title Description Overlay Draw an overlay onto the graph by selecting the axis on which to draw the overlay. Selecting ‘Shared Axis’ means that the values in the ‘Overlay Data’ table will be plotted according to the values on the left vertical axis (y-axis).
CHART MANAGER UTILITY Table 7-6 Chart Manager - Graph Control Tab Title Description System To print the displayed graph select the ‘Mono’ or ‘Color’ radio button and select the layout by selecting ‘Border’, ‘Landscape’ and or ‘Full page’ check boxes. Click the ‘Apply Now’ button and then the ‘Print’ button.
COLLECTING DATA WITH LOG MANAGER 7-22
CHAPTER 8 MANAGING EVENTS 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.
MANAGING EVENTS 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. • Device Up – a device which has previously been “down” is now responding. • TFTP – a device is currently performing file transfer or download.
DEFINING EVENT ACTIONS 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) Table 8-1 Event Actions Action Description Beep Sound an audible signal on the network management station (i.e., your local PC). Show message box Display a user-defined message in a text box on the NMS’s screen. The message box appears on top of all the other windows.
MANAGING EVENTS 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. If no trap messages are available, then $$ will be null. • ## is substituted with the network address of the device.
DEFINING EVENT ACTIONS Table 8-2 Event Data Parameters Description Example Date Date when the event occurred 05/16/2004 Time Time when the event occurred 13:33:48 (1:33 pm) Device IP network address of the device 192.9.211.52 . Description Text from “Write into database” Dropped server connection 3. Click the Close button to close the Event Data window. To erase some or all event information: 1. From the Event Data window, select the target event line.
MANAGING EVENTS Receiving SNMP Traps with the Trap Manager Trap is a protocol mechanism defined in SNMP by which managed devices report unique events to the network management station. Devices can be set up to report specified conditions to EliteView using Trap messages. Limitations of Trap Messages Trap messages are designed to report information that requires immediate attention. However, the value of Traps is limited in SNMP because there is no guarantee these messages will be delivered.
POSTING MESSAGES TO THE REPORT W INDOW Posting Messages to the Report Window Both predefined and user-defined system activity may be specified in the Event Manager to be posted to EliteView’s Report window. If any event criteria have been met, then this window will display a chronological list of pertinent messages stamped by time and date. To view the Report window, select Report from the Utilities menu of the main EliteView program, or click on the Report icon in the EliteView program group.
MANAGING EVENTS 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.
CHAPTER 9 USING RMON Introduction This chapter describes how to use Remote Monitoring (RMON) to more effectively monitor your network. RMON provides a cost-effective way to monitor large networks by placing embedded 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.
USING RMON RMON is designed to limit the amount of traffic required by management applications. It consists of an independent agent that resides on the managed device, and is charged with monitoring and collecting information about network traffic or the status of the host device. The agent gradually builds up information about the attached segment or VLAN, storing this information in the relevant RMON database group.
INTRODUCTION Table 9-2 RMON Manger Main Screen Field Description Probe IP Address The IP Address of the RMON Probe. Description Description of the device including manufacturer and model name. Object Identifier The object identifier used to identify this device in the MIB tree. On Since The time at which the device was turned on. Contact The person responsible for managing this device. Name Name used for this device; such as a hierarchical network name.
USING RMON 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.
RMON UTILITIES Statistics Group The Statistics Group includes all the tools you need to monitor your network for common errors and overall traffic rates. When you open the Statistics Group the Control Table screen is displayed as shown below. This table allows you to add, edit and delete items to be monitored, or to select a specific index entry and then view the statistical data in numeric or graphic form.
USING RMON 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. The system automatically generates an index number, but you can enter any number from 1 to 65,535 that is not currently in use. Each interface number equates to a physical media on the device being monitored.
RMON UTILITIES 9-7
USING RMON Statistics are provided for the following areas. Table 9-6 Statistics 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.
RMON UTILITIES Table 9-7 Statistics Parameter Descriptions Parameters Description Utilization Util% (Now,Max, Min) This table displays the current bandwidth utilization, plus the maximum and minimum utilization since the statistics window was opened. Packets/Bytes This table displays packets and bytes. Packets Packets Packets (including bad, broadcast and multicast packets). Broadcasts Broadcast packets. Multicasts Multicast packets.
USING RMON Table 9-8 Statistics Menu and Tool Bar Field Description File Exit Polling Polling Time (5 - 3600 seconds), Pause, Resume. View All, Utilization, Packets, Errors and Collisions, or Packet Size Distribution Control! Control Table Help On-line help They also include a status bar at the bottom of the window that includes the following items: Table 9-9 Statistics Status Bar Field Description Control Index The index for the entry defined in the Statistics Control Table.
RMON UTILITIES Table 9-10 History Control Table Field Description Total The number of index entries contained in the Control Table. Read Status The read status of information in the Statistics Control Table. Index The index for the table row (automatically assigned). Owner The name of the person who created this entry in the Control Table. Interface The selected interface on this device (as defined in MIB2). (Buckets) Requested The number of samples to record.
USING RMON 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 6-5). The number of buckets indicates the number of samples to record. You should always be able to record the default of 50 buckets without overflowing the agent’s memory.
RMON UTILITIES 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.
USING RMON Table 9-11 Alarm Control Table Field Description Variable The object identifier of the MIB variable to be sampled. Only variables that resolve to an integer value may be sampled. Sample Type The method of sampling data, either Absolute or Delta. For an absolute sample the variable will be compared directly to the thresholds. For a delta sample the last sample is subtracted from the current value and the difference is then compared to the thresholds.
RMON UTILITIES Table 9-12 Event Control Table Index Entries 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. Displaying Events in the RMON Manager – The Event determines the action to take when an alarm is triggered.
USING RMON When you open the Host Group the Control Table is displayed as shown below. Use this table to select an interface on the monitored device, such as a hub’s repeater bus, or a port on a switch used for device management. Click on the Add (Edit) button to add (edit) an index entry. The dialog box that opens is described in the following table. Table 9-13 Host Control Table Field Description Index A number that identifies the row in the table. Owner The person who created this entry.
RMON UTILITIES 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 listed below.
USING RMON Table 9-14 Host Control Table Menu and Tool Bar Descriptions Field Description Tool Find – Locates a specific MAC address in the host table. Sort – Sorts the table based on any of the displayed columns, in ascending or descending order. (You can also sort the table by clicking on any column header.
RMON UTILITIES 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. The configuration and display options are listed below. Table 9-15 Host Top N Menu and Tool Bar Descriptions Field Description File Exit Polling Automatically resets polling time after each period is completed.
USING RMON Matrix Group The Matrix group can maintain statistics on conversations that occur between each pair of hosts on the network. This group can display statistics for traffic transmitted from any source address, traffic received by any destination address, or traffic passing between any host pair.
RMON UTILITIES Table 9-16 Matrix Control Table Field Description Last Delete Time The last time data was deleted from this table due to lack of space. Status Possible states include “under creation,” “valid,” and “invalid.” Refresh Time for Control Table The refresh interval for this control table. Range: 5-600 seconds To view the matrix data collected for a specific interface, highlight it in the control table and press the View button.
USING RMON Table 9-17 Matrix Menu and Tool Bar Descriptions Field Description File Exit Polling Polling Time (5 - 3600 seconds), Pause, Resume View Table – Cumulative, Delta, Specific Source/Destination Graph – Packets, Bytes, Errors Tool Find – Locates a specific MAC address in the matrix table. Sort – Sorts the table based on any of the displayed columns, in ascending or descending order. (You can also sort the table by clicking on any column header.
RMON UTILITIES Table 9-18 Channel and Buffer Control Table 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. Once enabled, the channel will start capturing packets that pass the filter.
USING RMON Table 9-18 Channel and Buffer Control Table Field Description Buffer control Index A number that identifies this buffer in the buffer control table. Description A comment provided by the user describing this channel. Buffer Displays the buffer for the selected control entry. Filter Displays the filter control table. On/Off This button is used to manually enable or disable the capture channel. Refresh Time for Control Table The refresh interval for this control table.
RMON UTILITIES 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; or IPX: All, RIP, SAP, Unknown). Also regardless of the frame type, you can choose to filter all packets or just certain error packets (such as fragments or jabber).
USING RMON Table 9-19 Filter Configuration Options Field Description Packet Status The status of packets to filter: Any Packets, No Errors, Any Errors, CRC/Alignment, Packets < 64 Bytes, Undersize (packets < 64 bytes, with no CRC/alignment errors), Packets > 1518 Bytes, Oversize (packets >1518 bytes, with no CRC/alignment errors), Fragments, Jabber, Other Name A name for this filter expression, consisting of the selected: Frame Type / Protocol / Upper-Layer Protocol.
RMON UTILITIES Configuring Channels – The data and event stream formed by the packets that match the filter (or a group of combined filters) is referred to as a “channel.” A channel can be based on a single filter or on multiple filter expressions which are OR’ed together. The channel can be configured to pass packets through if they match or fail to match the stated expression(s). Events can then be defined to turn the channel on or off, or can also be triggered when the packets are accepted.
USING RMON Table 9-20 Channel and Buffer Add/Edit Dialog Box Field Accept Event Status Description Controls the flow of events. Ready – A single event will be generated, after which the status will be set by the RMON probe to “Fired.” While in the Fired state, no events will be generated until the status is reset to Ready or Always Ready. Always Ready – Disables flow control and allows events to generated at will.
RMON UTILITIES Table 9-21 Separate Control Tables: Channels Field Description Channels Controls the flow of data and events through the channel. Index A number that identifies this channel in the channel table. Owner The person who created this channel entry. Interface Index 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.
USING RMON Table 9-21 Separate Control Tables: Channels Field Event Status Description Controls the flow of events. Ready – A single event will be generated, after which the status will be set by the RMON probe to “Fired.” While in the Fired state, no events will be generated until the status is reset to Ready or Always Ready. Always Ready – Disables flow control and allows events to generated at will.
RMON UTILITIES Table 9-22 Separate Control Tables: Filters Field Description Packet Data Not Mask The inversion mask that is applied to the match process. Packet Status The status that is to be matched with the input packet. Packet Status Mask The mask that is applied to the status match process. Packet Status Not Mask The inversion mask that is applied to the status match process. Status The current status of the index entry in the Control Table: Valid, Under Creation or Invalid.
USING RMON Table 9-23 Separate Control Tables: Buffers Field Full Action Description Controls the action of the buffer when it reaches full status. Lock – The buffer will be locked as soon as it fills. Wrap – Old data will be overwritten when the buffer fills. 9-32 Capture Slice Size The maximum number of bytes for each packet that will be saved in this capture buffer.
RMON UTILITIES 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. Table 9-24 Buffer Menu and Toolbar Descriptions Field Description File Load, Save As, Exit Note that you must pause polling before you can load or save a buffer file. Polling Polling Time (5 - 3600 seconds), Pause, Resume Also includes options to download Next 2000 Packets or Previous 2000 Packets.
USING RMON Table 9-24 Buffer Menu and Toolbar Descriptions Field Description Options Time Format includes: Absolute – Date and local time. Relative – Time relative to when the first packet was added to the buffer. Difference – Time difference between capturing last packet and current packet.
APPENDIX A TYPICAL ELITEVIEW APPLICATIONS EliteView is a versatile network management software package that supports an open platform architecture. 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.
TYPICAL ELITEVIEW APPLICATIONS 5. Use Log and Event Manager to monitor the SNMP device. 6. Customize EliteView to receive third-party traps. 7. Import Logged data into other software for further processing. Managing a Third-Party Device Using the MIB Browser Before you can manage any third-party device, you should have a clear understanding of definitions for the variables in this MIB. Please consult your vendor for details.
USING THE LOG AND EVENT MANAGERS TO MONITOR THE NETWORK Let’s say that you want to set a variable called hubNMS in a third-party device. To set a variable in a third party device: 1. Compile the third-party MIB into the EliteView MIB database. Refer to the section on “Adding a New MIB Using the MIB Compiler” for more information. If you have completed this operation, then skip to the next step. 2. Create a map that includes the third-party SNMP device (i.e.
TYPICAL ELITEVIEW APPLICATIONS Table A-1 Log and Event Manager Parameters Parameter Description Example 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. 1 Filter Formula used to filter information.
USING THE LOG AND EVENT MANAGERS TO MONITOR THE NETWORK By checking the target SNMP device’s MIB, you find that the variable ezRptrTotalFrames contains the value that you need. Further, this variable belongs to the “EZ Stack 10” module. (The term MIB module is synonymous to the term “MIB Name” in the MIB variable information window of the MIB Browser.) Additional information you already know includes – index is equal to the IP address of the target SNMP device and the community is equal to public.
TYPICAL ELITEVIEW APPLICATIONS By checking the target SNMP device’s MIB, you find that the variable hubTxCollisions contains the value that you need. Further, this variable belongs to the “EZ Stack 10” module. Additional information you already know includes – index is equal to the IP address of the target SNMP device and the community is equal to abc. To monitor the total packets received by the target device: 1. Fill in the following table with all available information.
EXPORTING LOGGED DATA TO OTHER SOFTWARE Appendix B, “Customizing EliteView” describes the format of the TRAP.INI file. For an advanced user, this format is not difficult to understand. One important thing that you have to remember is the arrangement of the events and messages for each trap. You should use the Event Manager to add all the events and responses you want. Additionally, the trap message specified in the TRAP.INI file is the “value” of the event that will be substituted for the $$ symbol.
TYPICAL ELITEVIEW APPLICATIONS A-8
APPENDIX B CUSTOMIZING ELITEVIEW 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, NT, 2000, XP and Vista environments. You can easily customize EliteView by editing the NETMGR.INI, TRAP.INI and the configuration files found in the EliteView directory (C:\EV60).
CUSTOMIZING ELITEVIEW Table B-1 Description of Sections in NETMGR.INI Section Description bitmaps Contains the bitmap graphics used to display managed devices on the network map. MIB Directory where device MIBs are stored. LOG Directory for storing log files; also includes a flag which enables/disables logging upon startup tftp Path for boot files; also includes setting for device connection. startup Indicates programs to run when EliteView is invoked.
INSIDE THE NETMGR.INI FILE • • • • The Windows-based applications are written according to a set of rules required by EliteView They accept a list of parameters provided by the EliteView main program. They are able to communicate with each other through the EliteView message center. All EliteView applications started from the main EliteView program are automatically terminated when the main EliteView program is terminated.
CUSTOMIZING ELITEVIEW Add a line describing the device, using the following format: Seq=Device_Name,Protocol,Device_Description,Device_Type,Object_ID,Device_Manager Parameter Definitions for the [device] Section Table B-3 Parameter Definitions for the [device] Section Parameter Description Seq= The sequence number of the device runs from 1 to n, where n is the total number of devices you can add to a map or monitor. Device_Name The device name, which is used by EliteView to identify the device.
INSIDE THE NETMGR.INI FILE The [tools] Section The [tools] NETMGR.INI section describes the menu items that appear in the Tools Menu of the main EliteView program. You can add, delete, or change items in the Tools Menu simply by editing this section in the NETMGR.INI file. To edit the [tools] section: 1. Edit the total=n line to specify the number of items listed in the Tools Menu. The variable n specifies the number of items listed under this menu. 2.
CUSTOMIZING ELITEVIEW The table below describes each item: Table B-5 Identifying Particular Tools for a Device Parameter Description Device_ID The device identifier defined in the [device] section. Seq= The menu item sequence number the device will override. Executeable Filename of the EliteView application that is invoked when the device type and menu items are selected.
INSIDE THE NETMGR.INI FILE Tip: If you are going to design your own graphic bitmap for a device, remember to design three kinds of graphic images • the device at normal operating condition • the device when it is “down” or not operating • the device in the “not monitored” mode 1. Identify the directory where your graphic bitmap file(s) are located by editing the first line in the [bitmap] section. This parameter identifies the directory where the bitmaps are found.
CUSTOMIZING ELITEVIEW • The same explanation follows for the other Device_IDs mentioned, e.g., GenNode, Bridge1, CompRemote and PC. The [util] Section The [util] section controls the menu items that appear in the Utility Menu of the EliteView platform program. You can add, delete or change items in the Utilities Menu by editing this section in the NETMGR.INI file. To edit the [util] section: 1. Edit the total=n line to specify the number of items listed in the Utilities Menu.
INSIDE THE NETMGR.INI FILE 5=1,&Report,REPORT.EXE,Report window,report 6=1,Tra&p Manager,TRAPMAN.EXE,Trap manager,trap 7=1,&Event Manager,EVENT.EXE,Event manager,event 8=1,&Name Database Manager,NBMGR.EXE,Name database manager,nbmgr 9=1,D&iscovery,DISCOVER.EXE,Discovery,discover 10=1,&MIB Compiler,MIBCOMP.EXE,MIB compiler,mibcomp From the [util] section, you can see the following information: • • • • There are 10 items or options in the Utilities Menu (total=10).
CUSTOMIZING ELITEVIEW Parameter Definitions for the [startup] Section Table B-8 Parameter Definitions for the [startup] Section Parameter Given Information Seq= The sequence number from 1 to n, where n is a positive number equal to the total number of startup processes you wish to invoke before running the EliteView platform program. EV_Flag Distinguishes between EliteView and non-EliteView applications. Acceptable values include: 0 Designates the entry as a “Non-EliteView Windows application.
INSIDE THE TRAP.INI FILE Parameter Definitions for the [discover] Section Table B-9 Parameter Definitions for the [discover] Section Parameter Given Information protocol Determines the initial protocol selected when the Discovery module is opened.Values: UDP, IPX, Ethernet autosave1 Saves options including currently selected protocol type and other entries under the Discovery Setup menu. Refer to the last item in the Discovery Setup menu.
CUSTOMIZING ELITEVIEW Elements of a Trap Message Table B-11 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. If IP protocol is used, the agent-addr is the IP address of the device.
INSIDE THE TRAP.INI FILE 4=1,Trap, Authentication Failure 5=1,Trap,egpNeighborLoss From the [generic] section, you can view the following data: • • • • Trap number 0 It is active (1) It triggers the “Trap” event When invoked the message “Cold Start” will be displayed in the event message box 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.
CUSTOMIZING ELITEVIEW Specific Trap Sections Each specific trap is defined in a section of its own. The section name takes the following format: [Ent(n).(m)] where: (n) is the sequence number of the enterprise (m) is the specific trap number 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.
INSIDE THE TRAP.INI FILE Table B-15 Trigger Event Parameters Parameter Description event= The event to trigger. Active_Flag Select either 1 or 0; 1=Active, 0=Disabled. Event_Name Name of the event or trap to trigger. Example: Sample of specific trap entry [Ent1.1] message=Temperature over 65 degrees event=1,Trap [Ent1.2] message=Port auto-partitioned event=1,Trap [Ent1.3] message=Port bad link event=1,Trap [Ent1.
CUSTOMIZING ELITEVIEW [Ent1.8] message=Port (%b, %c) CRC error count over %a event=1, Trap a=portCRCErrors, v b=portCRCErrors,i5 c=portCRCErrors,i6 From the preceding example, you can view the following data: • • • • • B-16 There are 8 specific traps available for enterprise number 1. All traps are active (event=1). When a trap is activated, it will trigger a specified event called “Trap” and display the corresponding message onscreen. Supposed trap number 4 is triggered [Ent1.4].
APPENDIX C SNMP ENVIRONMENT 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. EliteView currently supports transport protocols including IP and IPX. SNMP Roles There are two defined roles in SNMP: manager and managed.
SNMP ENVIRONMENT Here is a portion of the EZ Stack 10 MIB: EZ Stack-10 DEFINITIONS ::= BEGIN IMPORTS OBJECT-TYPE, Counter, TimeTicks ,IpAddress FROM RFC1155-SMI; IMPORTS DisplayString FROM RFC1213-MIB-II; enterprises 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 OBJ
OBJECTS By definition, all single MIB variables have the index 0. Only numbers are used as indices; if other data types are used as indices, then they are represented by a list of numbers separated by dots (also referred to as dotted-decimal notation). iso origin All objects in the SNMP world begin with the object ISO, which has a unique identifier of 1. In other network implementations, objects may begin with CCITT (2) or joint-ISO CCITT (3).
SNMP ENVIRONMENT Branches Some common branches to the iso origin include: Table C-1 Branches to the iso Origin 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.
APPENDIX D TECHNICAL REFERENCES 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.
TECHNICAL REFERENCES RFC Reports Table D-1 RFC Reports: Networking Information RFC Number D-2 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 SRI International, 1980 RFC-1060 Assigned Numbe
INDUSTRY-RELATED DOCUMENTATION Industry-Related Documentation Also refer to these industry-related documents: • • The Ethernet: a Local Area Network, Data Link Layer and Physical Layer Specification Standard (Digital-Intel-Xerox; also known as the Blue Book) IEEE Std 802.2 - 1985 (ISO/DIS 8802.2) IEEE Std 802.3 - 1985 (ISO/DIS 8802.3) Internetworking with TCP/IP: Principles, Protocols, and Architecture, Vol.
TECHNICAL REFERENCES D-4
APPENDIX E PERFORMANCE TIPS 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 (< 8 ms access time). √ High-resolution color display (minimum 1024x768). √ Adequate memory (256 MB of memory if EliteView is used with other applications). Windows works best with lots of memory.
PERFORMANCE TIPS Other Tips √ If you frequently use a certain map, set it as the default EliteView map. √ Click on your right mouse button to show a context-sensitive menu of applicable commands. On larger screens, this means you will not need to jump back-and-forth to the menu bar to access related commands. √ Set passwords for your network maps. This guards against unauthorized access (turning ports on/off, clearing counters, etc.).
MANAGING DATA Table E-1 RFC Reports: Managing Data RFC Number Title Publisher/Year RFC-1042 A Standard for Transmission of IP Datagrams over IEEE 802 Networks SRI International, 1988 RFC-1155 Structure and Identification of Management Information for TCP/ IP-based Internets SRI International, 1990 RFC-1156 Management Information Base for Network Management of TCP/ IP-based Internets SRI International, 1990 RFC-1157 SNMP SRI International, 1990 RFC-1166 Internet Numbers SRI International, 19
PERFORMANCE TIPS Industry-Related Documentation Also refer to these industry-related documents: • • E-4 The Ethernet: a Local Area Network, Data Link Layer and Physical Layer Specification Standard (Digital-Intel-Xerox; also known as the Blue Book) IEEE Std 802.2 - 1985 (ISO/DIS 8802.2) IEEE Std 802.3 - 1985 (ISO/DIS 8802.3) Internetworking with TCP/IP: Principles, Protocols, and Architecture, Vol.
APPENDIX F SPECIFICATIONS EliteView is designed to manage any workgroup using the SNMP network management protocol.
SPECIFICATIONS Table F-1 Product Overview EliteView Performance Management Tune network for optimum performance Selectable statistical polling intervals Traffic filters Data value, date, time with comparison operators (<, >, <=, >=, ==, !=) and logic operators (AND, OR) Quantify and graph network throughput Quantify any MIB value (SNMP or private).
PRODUCT OVERVIEW Table F-1 Product Overview EliteView Data Transfer Integrated, relational database Number of records limited only by disk space* File format compatibility dBASE IV Maximum number of nodes Limited only to disk space* Transfer with Windows Clipboard Print or transfer to any word processor or spreadsheet System Requirements Software Microsoft Windows 95, 98, 2000, XP, NT4.0 Hardware (minimum) PC with Pentium-133 CPU or equivalent and 32 MB memory, 3.
SPECIFICATIONS F-4
APPENDIX G CODEBASE 6.0 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). This legal document is an agreement between you, the CodeBase 6.
CODEBASE 6.0 DLL SUB-LICENSE AGREEMENT 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. Transfer Restrictions The DLL Software is sub-licensed to you, and may not be transferred to anyone without the prior consent of the CodeBase 6.0 DLL LICENSEE.
APPENDIX H TROUBLESHOOTING 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. When a device does not respond within the Retries limit, the device is assumed to be off-line and the “Connection Lost” event is announced. The icon turns red; and EliteView continues polling for a response.
TROUBLESHOOTING Distributable Software Symptom Discovery does not find any devices. Possible Causes 1. EliteView network management station (NMS) may be using an IP address that is used by another device. 2. There may be a cabling problem. 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.
APPENDIX I ERROR MESSAGES 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. EliteView A device should have three bitmap files in [bitmap] section of NETMGR.INI.
ERROR MESSAGES Cannot open submap window. Cause: File may be corrupt. Action: Recreate a new map file. Cannot read bitmap file. Cause: The bitmap file defined in the [bitmap] section of NETMGR.INI may be corrupt. Action: Recreate the bitmap file. 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.
ELITEVIEW Invalid password. Cause: Incorrect password. Action: Type correct password. Invalid polling interval. Cause: The specified value is out of range. Action: The value for the polling interval must be greater than 1 and less than 86400. Invalid retries value. Cause: The specified value is out of range. Action: The value for retries must be greater than 1 and less than 1000. Invalid target address. Cause: The address format is incorrect for the current protocol.
ERROR MESSAGES The (total) for [tools] or [util] in NETMGR.INI cannot be 0. Cause: The total value in the [tools] or [util] section is 0 Action: Include at least one item in the [tools] or [util] section. Write file error (xxx) Cause: Write file xxx failed. Action: Check disk space. BOOTP Server Create Dialog windows not successful. Cause: May be out of memory. Action: Close some applications and try again. database NULL!! Cause: The record or variable cannot be found in the database.
BOOTP.DLL Out of memory!! Cause: Out of memory. Action: Close some applications and try again. Out of Memory for allocation. Cause: Out of memory. Action: Close some applications and try again. Record not Found!! Cause: The input parameter cannot be found in the database. Action: Check database files. Write file error!! Cause: Write to hard drive error. Action: Delete some files for more space. BOOTP.DLL Bind to UDP socket failed with error code = %d! Cause: Bind Socket fail.
ERROR MESSAGES Cleanup WinSocket failed with error code %d when exiting BTPIFM.EXE! Cause:The Unregister operation from winsock.dll failed. The error code should refer to the WSACleanup( ) function in the WinSocket specification. Action: Check the network subsystem by error code. Close socket failed with error code %d when exiting BTPIFM.EXE! Cause: Attempt to close the socket BOOTP failed. This error code comes from the function closesocket( ) in the WinSocket specification.
BOOTP.DLL Send packet failed with error code %d. Cause: The network subsystem is unable to send a packet. The error code comes from the function sendto( ) in the WinSocket specification. Action: Check the network subsystem by error code 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.
ERROR MESSAGES Discovery Cannot find %%%%%%% or this bitmap file has problem! Cause: The bitmap file %%%%%%% is missing or the format is not correct. Action: Get the correct file of %%%%%%%. Cannot find IP general node in [device] section of NETMGR.INI. Cause: No IP general node information in NETMGR.INI. Action: Use a text editor to add it. Cannot find IPX general node in [device] section of NETMGR.INI. Cause: No IPX general node information in NETMGR.INI. Action: Use a text editor to add it.
DISCOVERY Dump all UDP objects to namebase failed. Cause: Write to hard drive fail. Action: The hard drive space may not be enough. Dump function cannot work when searching for objects. Cause: Dump function can only work when Discover is busy. Action: Wait until the search job is complete. Initial namebase failure. Cause: Name database files have a problem. Action: Use name database manager to verify. Invoke alive test program failed with error reason code = %d.
ERROR MESSAGES None of the SNMP/UDP or SNMP/IPX protocols work! Cause: All protocols supported by discover.exe are not working. Action: Check to see if your network subsystem is OK. Not enough memory to allocate channel parameter structure. Cause: Out of memory. Action: Close some applications and try again. Not enough memory to allocate for IPX packet data. Cause: The memory is not enough. Action: Close some applications and retry. Open ICMP channel failure. Cause: The ICMP network sublayer has failed.
DISCOVERY The ipnode= entity of [discover] in NETMGR.INI is not correct! Cause: The content of ipnode= entity is not correct; it should be ON or OFF. Action: Use a text editor to edit NETMGR.INI. The ipxnode= entity of [discover] in NETMGR.INI is not correct! Cause: The content of ipxnode= entity is not correct; it should be ON or OFF. Action: Use a text editor to edit NETMGR.INI. The nwserver= entity of [discover] in NETMGR.
ERROR MESSAGES 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. Error code comes from the function bind( ) of the WinSocket specification.
ICMP.DLL Cleanup WinSocket failed with error code %d when exiting ICMPIFM.EXE! Cause: The Unregister operation from winsock.dll failed. The error code refers to the WSACleanup( ) function in the WinSocket specification. Action: Check the network subsystem by error code. Close icmp socket failed with error code = %d when exiting ICMPIFM.EXE! Cause: The Close socket operation failed. This error code comes from function closesocket( ) in the WinSocket specification.
ERROR MESSAGES Open RAW Socket failed with error code = %d!; Cause: The Open Socket operation failed. The error code comes from the function socket( ) of the WinSocket API. Action: Check the network subsystem by error code. Make sure your platform supports the optional RAW Socket. Receive frame for socket %d. Not for ICMP socket %d. Cause: A Receive process error in winsock.dll. Action: Check the network subsystem. Send request failed with error code = %d. Cause: The network subsystem has failed.
IPX.DLL The slot is saturated. Cause: Too many client applications of ICMP.DLL are running. Action: Close some client applications of ICMP.DLL and retry. The windows socket’s version specified by application is not supported by this winsock.dll! Cause: The version of winsock.dll did not match the requirements of ICMP.DLL. Action: Change the TCP/IP stacks and winsock.dll. The winsock.dll should at lease support version 1.1 Cause: The version of winsock.dll is too old.
ERROR MESSAGES Invalid start time. Cause: The specified time is incorrect. Action: The format for time is (MMDDYYHHMM) where MM is month, DD is day, YY is year, HH is hour, and MM is minute. Invalid stop time. Cause: The specified time is incorrect. Action: The format for time is (MMDDYYHHMM) where MM is month, DD is day, YY is year, HH is hour, and MM is minute. LOG database is corrupt. Cause: The database file is corrupt. Action: Recreate the database file. MESSAGE.
MIB BROWSER MIB Browser Cannot create MIB tree window. Cause: May be out of memory. Action: Close other windows and create the MIB tree window again Cannot create new output file. Cause: The file already exists or the disk is full. Action: Specify another filename or skip this action. Cannot create statistics window. Cause: Cannot create a statistics window. Action: Close other statistics windows Cannot create Toolbar. Cause: Out of memory.
ERROR MESSAGES Cause: The index variable(s) listed in the entry variable cannot be found in the MIB database. Action: Load MIB file which contains the index variable(s) into the MIB database Invalid object type. It must be COUNTER, INTEGER, GAUGE or TIMETICKS. Cause: Invalid object type. Action: Object type must be COUNTER, INTEGER, GAUGE or TIMETICKS. Line xxx: Bad Record. Cause: A bad record found in line xxx. Action: None. (The record will not display in the list box.
MIB COMPILER 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. Action: Please contact SMC Technical Support for help. SNMP SetRequest Error. Cause: Lower layer (SNMPAPI.DLL) cannot build the SNMP SetRequest. Action: Please contact SMC Technical Support for help. The object has no index.
ERROR MESSAGES Cause: Trap defined in MIB file is invalid. Action: Fix trap definition and recompile. Object list is not a tree. Cause: You did not define or import some needed nodes. Action: Check all undefined node or syntax listed in the import list, fix any errors, and recompile. The parser had an error. Line: %d Message: %s Cause: MIB macro clause has some errors. You may have forgotten to define some mandatory groups. Action: Check the MIB definition, fix any errors, and recompile.
MIB COMPILER 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. Action: Correct it and compile the MIB file again. MIB Compiler cannot decide object identifier of “%s” near line %d. Cause: Cannot find the parent of a node (variable). Action: Correct the node definition and compile again. Merge Tree Error.
ERROR MESSAGES Cause: In an MIB file, an import node is composed by name-module pair. If this warning has happened, it means the exact (name, import module name) can not be found in the MIB database, but another node with the same name but a different module name (name, different module name) exists in database. Action: If you continue to process this MIB file without importing the correct one, errors may occur. You should import the correct MIB list in the import list first.
MIB-2 VIEWER Cause:The MIB database is corrupt. Action: Rebuild the MIB database. Invalid search mode. Cause: (Internal error.) An application used the wrong search mode. Action: Please contact Accton Technical Support for help. MIB database error. Cause: (General error.) Action: Please contact Accton Technical Support for help. Out of memory. Cause: Out of memory. Action: Close other programs and retry.
ERROR MESSAGES Cause: Have received no SNMP response frame. Action: Make sure the target address is correct, the network subsystem OK, and the target node supports this variable group. Mib2 viewer got no snmp response for variable. Cause: The objects may be not implemented. Action: None. Out of Memory. Cause: Out of memory. Action: Close some applications and retry. Output Window out of space. Cause: Output window is full. Action: Save contents, and then clear the window with a New Output command.
TFTP SERVER Cause: Possible reasons may be: a. General error. b. Not enough disk space available for spooling, and no more space will become available. c. Not enough memory is available for spooling. d. User terminated the job through the printer manager. Action: Check printer or disk space. If memory not enough, print directly, not through the printer manager. Reports contents have changed. Save it? Cause: The contents of report the window have been changed. Action: Save it if important.
ERROR MESSAGES 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. Action: The Namebase.dbf file may be corrupted, use the namebase manager to check it. Invalid Retry value. Cause: The retry value should be between 0 and 2000. Action: Change it. Invalid target address. Cause: The target IP address or name is not correct.
TFTP.DLL 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. Cause: Out of memory. Action: Close some applications and retry, or restart Windows. Cannot open IFM window. Cause: An error occurred initializing TFTP.DLL. May be out of memory. Action: If memory is not enough, close some applications and retry, or restart Windows.
ERROR MESSAGES Cause: Out of memory. Action: Close some applications and retry, or restart Windows. 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. Action: Check the network subsystem by error code. Receive frame from wrong socket %d.
TRAP MANAGER Cause: The version of winsock.dll did not match the requirement for TFTP.DLL. Action: Change the TCP/IP stacks and winsock.dll. The winsock.dll should at least support version 1.1 Cause: The version of winsock.dll is too old. Action: Upgrade the TCP/IP stacks platform. Action: Check the network subsystem by error code. Windows socket version %d.%d required, but not supported by winsock.dll. Cause: The version of winsock.dll did not match the requirement for TFTP.DLL.
ERROR MESSAGES I-30
APPENDIX J PRODUCT SUPPORT SERVICES SMC is an international corporation that offers worldwide technical support. Many of these services are available 24 hours a day.
PRODUCT SUPPORT SERVICES Internet: E-mail addresses:techsupport@smc.com Driver updates: http://www.smc.com/index.cfm?action=tech_support_drivers_downloads World Wide Web:http://www.smc.
GLOSSARY Address Identification of entities in a communication protocol. BOOTP (Boot Protocol) BOOTP is a popular protocol that runs on top of the UDP/IP stack. BOOTP is used by devices to discover their own IP address. In EliteView, the BOOTP server provides the services of IP addresses and filenames. Broadcast Packet A packet transmitted to all nodes attached to the network. Community A character string embedded in SNMP messages that is used to authenticate the access rights of the service requester.
GLOSSARY IP Address A 32-bit quantity representing a point of attachment to the Internet. It is usually represented by four 8-bit integers separated by dots. Each decimal integer represents a byte in an IP address. The IP address is divided into a network part and a host part. For example, 192.9.211.151. See Appendix E for more information on Internet and IP addresses. IPX Internetwork Packet Exchange is a NetWare protocol providing datagram message delivery.
GLOSSARY Out-of-Band A way of communicating with a network device from outside the standard network channels. Packet The unit of data transfer over a local area network. For Ethernet, it includes the number of preamble bits, the start of frame delimiter, the destination and source addresses, the data to be transferred, and the frame check sequence (CRC) bytes.
GLOSSARY Unicast Packet A packet transmitted to a specific node on the network. WINSOCKET Provides a common network programming interface for Microsoft Windows that allows applications using TCP/ IP software from different barriers, and allows users to share information and resources as though located on the same LAN.
INDEX A F Alarm Group 9-13 Alive Test 3-2 probing devices 5-5 solving problems 5-7 Filter and Capture Group 9-22 filter formula 7-7 B Host Top N Group 9-18 BOOTP Server 3-2, 5-2 default information 5-5 setting addresses 5-1 I C CodeBase 6.
INDEX N S Name Database Manager 3-4, 4-6 network configuration 4-1 network map 4-8 building 4-1 editing map objects 4-11 editing toolbar 4-10 functions 4-9 sample configuration 4-12 SNMP C-1 trap 8-6 Statistics Group 9-5 sub-licence agreement G-1 system event 8-2 requirements 2-1 P performance tips E-1 product support J-1 R Report module 3-4 window 8-7 RFC reports D-1 RMON 9-1 Alarm and Event Groups 9-13 alarm control table 9-13 channel and buffer control tables 9-23 displaying events 9-15 event contr
TECHNICAL SUPPORT From U.S.A. and Canada (24 hours a day, 7 days a week) Phn: 800-SMC-4-YOU / 949-679-8000 Fax: 949-502-3400 ENGLISH Technical Support information available at www.smc.com FRENCH Informations Support Technique sur www.smc.com DEUTSCH Technischer Support und weitere Information unter www.smc.com SPANISH En www.smc.com Ud. podrá encontrar la información relativa a servicios de soporte técnico DUTCH Technische ondersteuningsinformatie beschikbaar op www.smc.
