Adaptec CI/O. User s Guide. Management Software

Transcription

1 User s Guide Adaptec CI/O Management Software Stock Number: , Rev. A Page: Front Cover

2 Adaptec, Inc. 691 South Milpitas Boulevard Milpitas, CA Copyright 1994, Adaptec, Inc. All rights reserved. Adaptec and the Adaptec logo are trademarks of Adaptec, Inc. which may be registered in some jurisdictions. Printed in Singapore STOCK NO.: , Rev. A RQ 12/94 Stock Number: , Rev. A Page: Back Cover

3 Adaptec CI/O Management Software User s Guide R Stock Number: , Rev. A Page: i

4 Copyright Copyright 1994 Adaptec, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written consent of Adaptec, Inc., 691 South Milpitas Blvd., Milpitas, CA Trademarks Adaptec, the Adaptec logo, CI/O are trademarks of Adaptec, Inc. which may be registered in some jurisdictions. HP OpenView is a trademark of Hewlett-Packard Company. NetWare is a registered trademark of Novell, Inc. All other trademarks are owned by their respective owners. Changes The material in this document is for information only and is subject to change without notice. While reasonable efforts have been made in the preparation of this document to assure its accuracy, Adaptec, Inc. assumes no liability resulting from errors or omissions in this document, or from the use of the information contained herein. Adaptec reserves the right to make changes in the product design without reservation and without notification to its users. Adaptec Technical Support and Services If you have questions about installing or using your Adaptec product, check this user s guide first you will find answers to most of your questions here. If you need further assistance, please contact us. We offer the following support and information services: For technical support (answers to technical questions, information about the Adaptec BBS, and access to the Interactive Fax system), call SCSI (7274) or , 24 hours a day, 7 days a week. To speak with a product support representative, call SCSI (7274), M F: 6:00 a.m. to 5:00 p.m., Pacific Time. For sales information, call SCSI (7274) or , M F: 6:00 a.m. to 5:00 p.m., Pacific Time. The Adaptec Electronic Bulletin Board Service (BBS) provides information on software upgrades, new releases, answers to common questions, and other topics. The BBS is available 24 hours a day, 7 days a week, at ; 1200/2400/9600/14,400/28,800 baud, 8 data bits, 1 stop bit, no parity. The Adaptec Interactive Fax system provides answers to common questions and current information about Adaptec products and services. The Adaptec Interactive Fax system is available 23 hours a day, 7 days a week. The Fax system is out of service 1 hour each day. You can call this service directly at To order Adaptec software and SCSI cables, call SCSI (7274) or SCSI (7274), M F: 6:00 a.m. to 5:00 p.m., Pacific Time. To request additional documentation for Adaptec products, call or , M F: 6:00 a.m. to 5:00 p.m., Pacific Time. ii Stock Number: , Rev. A Page: ii

5 Table of Contents Section I Preface Inside This Document ix Conventions x Advisories xi Adaptec CI/O Reference 1 Overview About This Chapter 1-1 Using this Document 1-3 What is Adaptec CI/O 1-4 Adaptec CI/O Single Server 1-4 HP OpenView (100 Node Version) 1-5 Adaptec CI/O and HP OpenView Basics Getting Started About This Chapter 2-1 System Requirements 2-3 Installation 2-3 Installing HP OpenView (100 Node Version) 2-4 Installing the Backup Program 2-4 Installing Adaptec CI/O to a Client 2-5 Running Adaptec CI/O 2-5 Setting Up Passwords 2-6 Adaptec CI/O Toolbar 2-7 Overview Creating a Submap and Monitoring the Network 2-9 iii Stock Number: , Rev. A Page: iii

6 Section II 3 Using Adaptec CI/O About This Chapter 3-1 Install CI/O NLM 3-3 Installing the Adaptec CI/O NLM to a Server 3-3 Loading the Adaptec CI/O NLM 3-5 Update SCSI Drivers 3-6 Updating SCSI Drivers 3-7 Display NetWare Servers 3-12 Completing an IPX Extended Discovery 3-12 Displaying all Available NetWare Servers 3-13 Add SCSI Devices 3-14 SNMP Traps and Alarms 3-17 Monitoring Traps at Multiple Clients 3-18 SCSI I/O Monitor 3-20 Monitoring a Device on the Server 3-21 Backup Program 3-24 Launching Other Backup Programs 3-24 Configuration and About 3-26 HP OpenView Reference 4 Creating Network Maps Automatically About This Chapter 4-1 Overview 4-3 IP and IPX Discoveries 4-4 Preparing for a Discovery 4-4 Configuring Autodiscovery 4-6 Managing Autodiscovery 4-8 Maintaining the Autodiscovery Database 4-14 Creating Submaps of Discovered Devices 4-15 Configuring Preferred Names 4-15 Setting Layout Options 4-16 Executing the Layout 4-17 iv Stock Number: , Rev. A Page: iv

7 Table of Contents 5 Creating Network Maps Manually About This Chapter 5-1 Overview 5-3 Drawing a Simple Map 5-4 Drawing a Network Map 5-5 Map Example 5-6 Creating a Map File and Home Submap 5-7 Adding a Background 5-8 Adding Submap Symbols 5-9 Adding Lines 5-11 Adding Text 5-12 Add Remaining Submaps 5-12 Saving a Map 5-12 Printing a Map 5-13 Disabling the Map Editing Feature 5-13 Map Toolbar and Commands 5-14 Status Bar 5-15 Toolbar 5-15 Add Window 5-16 Select Object 5-17 Text 5-17 Lines and Connections 5-17 Symbol 5-17 Selection Lists Monitoring Devices on the Network About This Chapter 6-1 Overview 6-3 Customizing Device Access 6-4 Polling Network Devices 6-6 Creating a List of Devices to Poll 6-7 Removing Devices to Poll 6-8 Selection Lists 6-8 Configuring System Polling Parameters 6-10 Configuring Parameters for Selected Devices 6-11 Turning Polling On and Off 6-11 v Stock Number: , Rev. A Page: v

8 Monitoring Traps from Network Devices 6-12 Customizing Traps 6-12 Selecting a Device Class 6-13 Ignoring Traps 6-14 Specifying Traps for a Device Class 6-15 Choosing Trap Alarm Actions 6-16 Description Field Variable Substitution Syntax 6-17 Loading Traps 6-18 Automatically Acknowledging Alarms Generated by Traps 6-18 Managing Alarms 6-18 Selecting Map Status Options 6-18 Status Propagation 6-20 Configuring Alarms 6-23 Viewing Alarms 6-24 Selecting Alarms for Display 6-25 Acknowledging and Deleting Alarms 6-26 Configuring Alarm Processing 6-27 General Alarm Settings 6-28 Alarm Sound Settings 6-28 Alarm Sound Configuration 6-29 Alarm Status Propagation 6-29 Alarm Forwarding 6-30 Running Programs 6-32 DDE Commands 6-33 Alarm Database Managing SNMP Network Devices About This Chapter 7-1 Overview 7-3 Defining a Query 7-4 Selecting Variables to Query 7-6 Moving Around the Variable Tree 7-7 Selecting a Variable to Use in the Query 7-8 Removing a Variable From the Query List 7-8 Variable Descriptions 7-8 vi Stock Number: , Rev. A Page: vi

9 Table of Contents A Saving a Query 7-9 Selecting a Query 7-11 Removing a Query from the Menu 7-12 Displaying SNMP Query Results 7-13 Displaying a Query as a Table 7-13 Displaying a Query as a Graph 7-18 Changing a Variable's Value 7-22 Managing the SNMP Manager Database 7-23 Status Line 7-24 Adding Files 7-24 Message Field 7-24 MIB Structure 7-25 MIBs Dependent Upon MIB Vendor-Specific Private MIBs 7-26 Selecting MIB Files to Add to the Database 7-27 OpenView Command and Tool Reference About This Appendix A-1 Menu Commands A-3 File Menu Commands A-3 Edit Menu Command A-4 View Menu Commands A-4 Monitor Menu Commands A-5 Control Menu Commands A-5 Autodiscovery Menu Commands A-6 Options Menu Commands A-7 Window Menu Commands A-7 Help Menu Commands A-7 Toolbar A-8 Toolbar Functions A-8 vii Stock Number: , Rev. A Page: vii

10 Stock Number: , Rev. A Page: viii

11 Preface Inside This Document This document has the information you need to install and use Adaptec CI/O. In addition, this document provides information on using the features of HP OpenView. Section I: Adaptec CI/O Reference Chapter 1 Chapter 2 Chapter 3 Overview describes Adaptec CI/O features and how it manages networks. Getting Started lists system requirement and provides installation instructions for Adaptec CI/O. Using Adaptec CI/O describes how to use Adaptec CI/O. Section II: HP OpenView Reference Chapter 4 Chapter 5 Chapter 6 Creating Network Maps Automatically describes how to create a map using Autodiscovery. Creating Network Maps Manually describes how to create and edit network maps using the map toolbar and commands. Monitoring Devices on the Network describes polling, trapping, and configuring alarms. ix Stock Number: , Rev. A Page: ix

12 Chapter 7 Appendix A Managing SNMP Network Devices describes how to use the SNMP Manager to query SNMP devices and display query results. OpenView Command and Tool Reference lists all of the HP OpenView commands and tools and their functions. Conventions The following typographic conventions are used in this document: bold Used for keystrokes ( press the Enter key ), and screen selection fields ( select Advanced Configuration Options ). Helvetica Used for operator entry that must be typed exactly as shown ( device=c:\scsi\aspi2dos.sys ) and for messages on the screen ( Enter Password ). Helvetica Italics Used as a place holder for text you must determine and type in ( enter nn for number ). Also used for program and file names that appear in body text ( the autoexec.bat file ). Italics Used for emphasis ( is only supported ) and for document reference ( refer to Chapter 1, Overview ). Hexadecimal Numbers Are followed by an h, e.g., 330h. End Mark The symbol marks the end of the text for each chapter or section. x Stock Number: , Rev. A Page: x

13 Preface Advisories Advisories are quick notes that stress an important point or warn of a potential hazard to your system or your data. This document uses these kinds of advisories: Note: Text set off in this way presents reminders, tips, or suggestions that may make it easier for you to install, configure, and use Adaptec CI/O. Caution: Failure to observe this kind of advisory could result in loss of data or damage to your system and installed devices. Use caution when handling any electrical equipment. Advisories in this document can only cover the procedures contained here, and not all situations may have been addressed. Adaptec does not claim to have included every condition or situation that might require a Caution. You must refer to the documentation for your computer peripheral equipment when you are installing equipment or changing its configuration. xi Stock Number: , Rev. A Page: xi

14 Stock Number: , Rev. A Page: xii

15 Adaptec CI/O Reference Section I Stock Number: , Rev. A Page: xiii

16 Stock Number: , Rev. A Page: xiv

17 1 Overview About This Chapter Read this chapter to find out How to use this document What is Adaptec CI/O An overview of the capabilities of Adaptec CI/O 1-1 Stock Number: , Rev. A Page: 1-1

18 Stock Number: , Rev. A Page: 1-2

19 Overview 1 Using this Document This document is divided into two sections: Section I, Adaptec CI/O Reference and Section II, HP OpenView Reference. Section I (Chapters 1 through 3) provides all the information needed to install and use Adaptec CI/O. Section II (Chapters 4 through 7, and Appendix A) provides information on OpenView features. To use this document, first scan the remainder of this chapter to gain an overview of the capabilities of Adaptec CI/O. Next, follow the instructions in Chapter 2 to install HP OpenView, the Backup Program, and Adaptec CI/O. This chapter also describes how to run Adaptec CI/O, and provides descriptions of the Adaptec CI/O toolbar. When Adaptec CI/O is installed and running, Chapter 3 describes how to use Adaptec CI/O to manage SCSI devices on your network. If you need more information on using the features available in OpenView, refer to Chapters 4-7, and Appendix A. Note: References to both the TCP/IP (IP) and IPX network protocols are included in Chapters 4-7; however, the version of OpenView (100 Node Version) shipped with Adaptec CI/O does not support the IP protocol. References to the IP protocol are only applicable if you are running the full-featured version of OpenView. 1-3 Stock Number: , Rev. A Page: 1-3

20 What is Adaptec CI/O Adaptec CI/O is a client/server management tool for SCSI subsystems installed on NetWare servers. From any 386-based or higher client PC, Adaptec CI/O allows you to observe, manage, and receive alarms from SCSI subsystems located on multiple NetWare servers. Adaptec CI/O is available in two versions: Adaptec CI/O Professional (referred to as Adaptec CI/O) and Adaptec CI/O Single Server. Adaptec CI/O is intended for use by network administrators. Some, though not all, of the features require supervisor privileges. Adaptec CI/O operates along with HP OpenView (100 Node Version included), providing an enterprise-wide view of the network topology and resources. Adaptec CI/O features include Concise graphical and text listings of all NetWare-based servers Graphical view of SCSI devices installed on each NetWare server Installation/update of Adaptec CI/O NLM and SCSI drivers from client Remote failure notification of storage devices Performance monitor for storage subsystems Server Backup Program Coexistence with other HP OpenView applications Adaptec CI/O Single Server The Adaptec CI/O Single Server version of Adaptec CI/O is included with some Adaptec SCSI Host Adapter kits. The single server version is identical to the full featured version of Adaptec CI/O, with one exception: This version allows you to load the Adaptec CI/O NLM on only a single server on the network. You can observe, manage, and receive alarms from installed SCSI devices on that server. To upgrade to the full-featured version so that Adaptec CI/O can be installed on multiple servers, you can contact Adaptec directly by calling the number for ordering Adaptec software shown on page ii. 1-4 Stock Number: , Rev. A Page: 1-4

21 Overview HP OpenView (100 Node Version) The 100 Node Version of OpenView provided with Adaptec CI/O is the same as the full-featured HP application, with the following exceptions: A maximum of 100 network nodes can be mapped. The defaults have been set to limit autodiscovery to exclude common IPX and TCP/IP workstations, so this should not be a significant restriction for most installations. TCP/IP Client Services are not provided. Adaptec CI/O and HP OpenView Basics Adaptec CI/O is a client/server SCSI subsystem management utility. HP OpenView is a network management application shell that runs on top of Windows. This distinction is important in understanding how Adaptec CI/O and HP OpenView work together: Adaptec CI/O brings specific SCSI features that are not available in OpenView; OpenView provides a platform that Adaptec CI/O uses in cooperation with other OpenView-based applications. The Adaptec CI/O interface focuses on individual servers and their SCSI components. For instance, if you are most interested in finding and servicing a defective drive, the Adaptec CI/O interface gets you there quickly. The same holds true if you want to install new host adapter drivers to a server or profile the performance of your disk drives. The HP OpenView interface brings powerful network management capabilities. It provides a standard graphical interface allowing multiple network applications to share a common display and alarm system. In addition, HP OpenView provides basic network management functions to interface with devices on the network. The features of HP OpenView that Adaptec CI/O uses extensively include Maps and Submaps Autodiscovery Alarms Traps For more information about the features and functions of HP OpenView, refer to Section II, HP OpenView Reference. 1-5 Stock Number: , Rev. A Page: 1-5

22 Maps and Submaps Devices in the network are displayed on maps. Devices and subnetworks can be organized into submaps to suit your needs. You can create separate submaps of devices grouped by device functions, network organization, or corporate organization. You can use the maps to manage your network from a single display even when the network includes devices from different manufacturers. Changes in network status are displayed on network maps with icons representing devices. Color is used to indicate device status. Submaps allow you to create several views of your network to simplify management. You can add meaningful graphics such as geographic maps and floor plans as backgrounds for your map to provide real world visual references for your network. Autodiscovery Autodiscovery is an OpenView function that helps you find the servers in your network. It uses information such as the range of network addresses, community names, and device type to locate those servers. OpenView can then draw a network map based on the discovered network segments and servers. Adaptec CI/O uses both the Autodiscovery database plus its own automatic discovery process. User Autodiscovery List of Discovered Devices Layout Maps 1-6 Stock Number: , Rev. A Page: 1-6

23 Overview Alarms Changes in device status are provided through alarms. Alarms are displayed on maps and are listed in the alarm log. The alarms are also recorded in a database. The alarm database allows you to generate reports. In addition to visual cues, alarms can trigger sounds or programs and can even activate a remote paging device through the use of other OpenView-compatible accessories. OpenView allows you to configure how alarms are processed or displayed on maps, clear alarm conditions, and create reports from the alarm log. Traps Alarms Applications 1-7 Stock Number: , Rev. A Page: 1-7

24 Traps Certain subsystems and devices can send messages when certain conditions occur. The conditions may be startup, shutdown, data error, or a preset level of activity. The message resulting from a device condition is called a trap. Device Traps User OpenView Trap Manager Alarms Log Map Note: In order for a device to send a trap, you must specify the client to receive the trap. Refer to SNMP Traps and Alarms on page Once devices are configured to send traps to OpenView, the traps are recorded in the alarm log by default. You can customize how OpenView responds to traps using the Customize Traps dialog. You can select which traps to respond to. The traps can be of particular types or from particular device classes. Trap types can be selected from a list of standard traps or you can define custom traps for specific device classes. When OpenView receives a trap message, OpenView converts it into an alarm and processes it through the alarm system. Adaptec CI/O provides trap support for devices attached to certain SCSI host adapters on NetWare servers. 1-8 Stock Number: , Rev. A Page: 1-8

25 2 Getting Started About This Chapter Read this chapter to find out How to install HP OpenView, the Backup Program, and Adaptec CI/O to a client How to run Adaptec CI/O A description of the buttons available on the Adaptec CI/O toolbar 2-1 Stock Number: , Rev. A Page: 2-1

26 Stock Number: , Rev. A Page: 2-2

27 Getting Started 2 System Requirements The following are the minimum and recommended hardware and software system requirements needed to run Adaptec CI/O and HP OpenView: Minimum System Requirements Recommended System Requirements 386 series IBM PC-compatible computer with a minimum of 8 MBytes of RAM 486 series IBM PC-compatible computer with a minimum of 8 MBytes of RAM VGA color monitor SVGA color monitor 520 KBytes of free conventional memory 520 KBytes of free conventional memory 10.5 MBytes of free disk space: 2.5 MBytes for Adaptec CI/O 6 MBytes for HP OpenView 2 MBytes for Backup Program MS-DOS, 5.0 or higher Microsoft Windows, 3.1 or higher NetWare 3.12 or higher with IPX network protocol loaded and attached to a NetWare server 1 1 Attachment to a server is not required during installation of the client MBytes of free disk space: 2.5 MBytes for Adaptec CI/O 6 MBytes for HP OpenView 2 MBytes for Backup Program MS-DOS, 5.0 or higher Microsoft Windows, 3.1 or higher NetWare 3.12 or higher with IPX network protocol loaded and attached to a NetWare server 1 Installation This section provides the information needed to install Adaptec CI/O on your system. An overview of the installation steps is listed below. The steps should be performed in the order they appear. 1 Install HP OpenView (100 Node Version) 2 Install the Backup Program 3 Install Adaptec CI/O to a client 2-3 Stock Number: , Rev. A Page: 2-3

28 Installing HP OpenView (100 Node Version) You will need approximately 6 MBytes of available hard disk space to install HP OpenView. To install HP OpenView to a client, follow these steps: 1 Start Windows. 2 Insert the OpenView diskette #1 in your diskette drive. 3 From the Windows File menu choose Run. 4 In the Run dialog box, enter a:\setup if you are using the A drive or b:\setup if you are using the B drive. 5 Specify the destination path. 6 In the next dialog box, select SNMP over IPX Communication. Note: TCP/IP Client Services are not supported with this version of OpenView. Do not select SNMP over TCP/IP Communications. Follow the instructions that appear on screen. You are alerted when the installation is complete. At the end of the installation process, an HP OpenView program group is created. Installing the Backup Program A backup program is included with Adaptec CI/O. This program has its own manual. Please refer to this manual for installation instructions and information on using the program. Note: If you would like to use a backup program other than the one provided with Adaptec CI/O, refer to Backup Program on page 3-24 for instructions. 2-4 Stock Number: , Rev. A Page: 2-4

29 Getting Started Installing Adaptec CI/O to a Client To install Adaptec CI/O to a client, follow these steps: 1 Insert the Adaptec CI/O diskette in your diskette drive. 2 From the Windows File menu, choose Run. 3 In the Run dialog box, enter a:\setup if you are using the A drive or b:\setup if you are using the B drive. Follow the instructions that appear on screen. At the end of the installation process, an Adaptec CI/O program group is created. Note: If you upgrade from HP OpenView (100 Node Version) to the full-featured version of OpenView, you must reinstall Adaptec CI/O to the client. Running Adaptec CI/O Adaptec CI/O is launched by OpenView and cannot be launched independently of the OpenView environment. Run OpenView using any of the standard Windows techniques, including From the Adaptec CI/O program group, double-click the Adaptec CI/O icon. From the HP OpenView program group, double-click the HP OpenView icon. From the File Manager program, go to the OpenView directory and double-click the ovwin.exe file. Note: HP OpenView for Windows makes substantial use of memory located below 640 KByte (DOS memory). We recommend that your client have at least 520 KBytes of memory available before running Windows. To free up more DOS memory, refer to your Microsoft Windows or DOS documentation. After a few seconds the Adaptec CI/O toolbar appears along with the HP OpenView main menu. 2-5 Stock Number: , Rev. A Page: 2-5

30 Setting Up Passwords The Set Password command allows you to selectively grant access to parts of OpenView. The three levels of access are Supervisors have access to all of the OpenView features, including editing maps and setting passwords. Operators have access to all OpenView features except setting passwords, configuration, map editing, and most control functions. Observers are only allowed to view information. To set a password for each access level, follow these steps: 1 Choose Set Password from the Options menu. The Set Password dialog box appears. 2 Select a security level option (Supervisor, Operator, or Observer). 3 Type in a password and then retype the password to confirm it. 4 Click OK. The Log In dialog box appears after you start up OpenView, prompting you to select a security level and enter a password if one was assigned for that level. You can select the Log In menu item at any time to log in at a different security level. To disable all menu items in OpenView and lock the map, choose Log Out in the Options menu. The only menu items that are functional (not grayed) are Log In in the Options menu and the Help menu. 2-6 Stock Number: , Rev. A Page: 2-6

31 Adaptec CI/O Toolbar Getting Started Most of the functionality of Adaptec CI/O is accessible from the buttons on the Adaptec CI/O toolbar. This toolbar may be opened as a window or may be iconized. It is always present and is available until you exit your OpenView session. Note: By default, the Adaptec CI/O toolbar first appears in a vertical orientation (the horizontal orientation is shown below). To configure how the toolbar is displayed on your screen, refer to Configuration and About on page Install CI/O NLM Run CI/O Remote Console Shell Add SCSI Devices Run Backup Program CI/O Help Update SCSI Drivers Display NetWare Servers SCSI I/O Monitor Configuration and About Install CI/O NLM installs the Adaptec CI/O NLM to a NetWare server on the network. Each server you wish to manage through Adaptec CI/O must have the Adaptec CI/O NLM installed and loaded. Update SCSI Drivers updates the server s Adaptec host adapter with the latest Adaptec drivers. The latest drivers must be installed and loaded in order to take advantage of some of the advanced features of Adaptec CI/O. Note: These drivers are only compatible with Adaptec host adapter products. 2-7 Stock Number: , Rev. A Page: 2-7

32 Run CI/O Remote Console Shell provides remote access to a server s NetWare console. From Adaptec CI/O, you can use Remote Console (RConsole) to remotely load and unload files, such as the Adaptec CI/O NLM and host adapter drivers. To exit RConsole, press Alt-F2, then Esc. Note: To use the RConsole feature on a server, make sure the rspx.nlm is loaded on the server. The rspx.nlm loads the remote.nlm automatically. Caution: The PIF file used to run the RConsole from Adaptec CI/O is set so Allow Close When Active is disabled. Leave this option disabled; otherwise, unpredictable results may occur when trying to exit RConsole. Display NetWare Servers creates a layout of NetWare servers available for network management. From this layout, you can quickly locate the server you wish to manage through Adaptec CI/O. Add SCSI Devices locates and identifies SCSI devices on NetWare servers that have the Adaptec CI/O NLM installed and loaded. SCSI devices include host adapters and target devices (disks, CD drives, tape drives, etc.). Once Adaptec CI/O locates all SCSI devices, you can easily monitor the performance of the devices and any alarms that are generated. SCSI I/O Monitor graphically displays I/O activity for SCSI devices attached to an Adaptec host adapter. Various statistics can be measured including the number of bytes read or written, and the number of SCSI commands that have been processed. Run Backup Program backs up selected server files and directories to your tape medium. The backup program provided with Adaptec CI/O has its own windows, help screens, and manual. Please refer to these materials for more details about the backup program. 2-8 Stock Number: , Rev. A Page: 2-8

33 Getting Started Configuration and About configures the settings for Discovery Management, Toolbar Management, and Program Launch (Backup Program and Remote Console). Information about the version of Adaptec CI/O currently installed can also be obtained. CI/O Help offers a quick way to find information on specific CI/O topics. Click the CI/O Help button to view help relative to the part of the program last accessed. For example, if you click the Update SCSI Drivers button (bringing up the utility) and then click the CI/O Help button, information describing the basic functionality of the utility is provided. Overview Creating a Submap and Monitoring the Network Creating a submap of SCSI devices allows you to remotely view those devices installed within the servers on your network. Further, you can detect failure of those devices when SNMP traps and alarms are generated. From the submap, you can also access the SCSI I/O Monitor to graphically display I/O activity for SCSI devices. Refer to SNMP Traps and Alarms on page 3-17 and SCSI I/O Monitor on page 3-20 for additional information. An overview of the procedures needed to create a submap of SCSI devices is listed below. The procedures should be performed in the order they appear. Install Adaptec CI/O to a server See Install CI/O NLM on page 3-3. Update server drivers See Update SCSI Drivers on page 3-6. Display NetWare servers See Display NetWare Servers on page Add SCSI devices See Add SCSI Devices on page Stock Number: , Rev. A Page: 2-9

34 Stock Number: , Rev. A Page: 2-10

35 3 Using Adaptec CI/O About This Chapter Read this chapter to find out How to use Adaptec CI/O to manage the SCSI devices on your network 3-1 Stock Number: , Rev. A Page: 3-1

36 Stock Number: , Rev. A Page: 3-2

37 Using Adaptec CI/O 3 Install CI/O NLM Install CI/O NLM remotely installs the Adaptec CI/O NLM to a selected NetWare server on the network. The Adaptec CI/O NetWare Loadable Module (NLM) must be installed on NetWare servers you wish to monitor through Adaptec CI/O. Using both a client PC that has Adaptec CI/O installed, and a server that has the Adaptec CI/O NLM installed, you can monitor the operation and status of SCSI devices installed on that server. When installed, the Adaptec CI/O NLM maintains a database of SCSI devices attached to the server and provides access to instrumented and noninstrumented SCSI NetWare drivers. The Adaptec CI/O NLM polls the drivers at regular intervals to monitor SCSI devices installed on the system. When the Adaptec CI/O NLM detects certain conditions that affect a SCSI device, it generates an SNMP trap. For example, if a drive loses power or goes offline, the Adaptec CI/O NLM generates an SNMP trap and notifies an Adaptec CI/O client PC(s) of the change (this trap shows up as an alarm under OpenView). In order to receive notification of SNMP traps, the client PC(s) must be specified in the traptarg.cfg file located on the server. If the client PC is the same PC from where you installed the Adaptec CI/O NLM to the server, then this PC is automatically specified in the traptarg.cfg file. Installing the Adaptec CI/O NLM makes this change for you. See Monitoring Traps at Multiple Clients on page Installing the Adaptec CI/O NLM to a Server To Install the Adaptec CI/O NLM, follow these steps: 1 From the Adaptec CI/O toolbar, click the Install CI/O NLM button. A list of all NetWare servers that Adaptec CI/O has detected appears. 3-3 Stock Number: , Rev. A Page: 3-3

38 Note: This list may not correspond to the servers displayed when using either Do Basic Layout from OpenView, or Display NetWare Servers from the Adaptec CI/O toolbar. This discrepancy occurs because different methods of identifying network devices are used when invoking these features. When installing the Adaptec CI/O NLM, however, you must select from the list of servers that Adaptec CI/O has detected. This selection includes the most complete list of servers compatible with Adaptec CI/O. 2 Select the server to which you are installing. 3 Complete the User Login Information dialog box, then click the Select button. The user name and password you enter must have supervisor privileges to the server. Note: If you are already logged in to the server as a user, logging in to the server from this dialog box as a new user with supervisor privileges will log out the original user. At the conclusion of NLM installation, the newer user is also logged-out. If necessary, the original user must log in to the server again. The Adaptec CI/O NLM (cio.nlm) is copied to the server s \system subdirectory of the sys: volume. Note: If you are running Adaptec CI/O Single Server, the cioss.nlm is copied to the server s \system subdirectory of the sys: volume. 4 Once the Status field indicates that the Adaptec CI/O NLM has successfully installed, click the Exit button to exit the dialog box. 5 To install the Adaptec CI/O NLM to another server, repeat steps 2 through 4; otherwise, click the Cancel button to exit. 3-4 Stock Number: , Rev. A Page: 3-4

39 Using Adaptec CI/O Loading the Adaptec CI/O NLM Once the Adaptec CI/O NLM is installed on a server, you must then load the NLM. To Load the Adaptec CI/O NLM, follow these steps: 1 From the Adaptec CI/O toolbar, click the RConsole button. A list of all NetWare servers that RConsole has detected appears. 2 Select the server that has the Adaptec CI/O NLM installed. 3 Enter a password that has RConsole privileges to the server. 4 Once you are logged in to the console of the server, type load cio parameters If you are running Adaptec CI/O Single Server, type load cioss parameters Parameters are optional and must be separated by at least one blank space. If a parameter is not included as part of the load command, then the default is assumed. The available parameters are: Parameter Description cd Clears the device database. The default is to not clear the database. cl Clears the SNMP trap log. The default is to not clear the trap log. pn Sets polling frequency to n seconds. The default is 180 seconds. sn Scans for new devices every n polling cycles. The default is 3 cycles. If n is 0, then polling is disabled. r Resets all driver counters. The default is to not reset the counters. x Disables collection of statistics in the drivers. The default is to collect statistics. l Checks only logical unit zero for each device. The default is to check all logical units. cu Clears the driver update log. The default is to not clear the update log. un Scans for new drivers every n seconds.the default is 5 seconds. If n is 0, then scanning for new drivers is disabled. 5 To exit the console of the server, press Alt-F2, then select Yes. 6 Press Esc, then select Yes to exit the RConsole. Note: To automatically load the Adaptec CI/O NLM every time the server comes up, add the load cio (or load cioss) command to your autoexec.nc files. Refer to your NetWare documentation. 3-5 Stock Number: , Rev. A Page: 3-5

40 Update SCSI Drivers For NetWare servers that already have the Adaptec CI/O NLM installed and loaded, Update SCSI Drivers allows you to update an existing Adaptec driver with the latest Adaptec instrumented driver. Adaptec instrumented drivers provide useful information about the operation of devices, such as the number of Read commands or the number of bytes written to the device. These drivers must be installed in order to take advantage of certain advanced features of Adaptec CI/O such as trap generation or performance profiling. Currently, Update SCSI Drivers allows you to selectively update drivers for several families of Adaptec host adapters. The drivers for NetWare 4.x and NetWare 3.x include the following: NetWare 4.x NetWare 3.x aha1540.dsk, aha1540.dsk aha1540.ddi aic7770.dsk, aic7770.dsk aic7770.ddi aic7870.dsk, aic7870.dsk aic7870.ddi aspitran.dsk, aspitran.dsk aspitran.ddi aspicd.dsk, aspicd.dsk aspicd.ddi Note: When updating a driver for the first time, the \adaptec\cio.3x or \adaptec\cio.4x directory are created on the server s startup directory of the DOS partition. The driver for either version of NetWare is then copied to the appropriate directory: NetWare 3.x drivers include only a.dsk file, NetWare 4.x drivers include both a.dsk and.ddi file. The.dsk files copied to the \adaptec\cio.3x subdirectory can only be used with servers running NetWare 3.x, and the.dsk and.ddi files copied to \adaptec\cio.4x on servers running NetWare 4.x. 3-6 Stock Number: , Rev. A Page: 3-6

41 Using Adaptec CI/O Updating SCSI Drivers To update drivers, follow these steps: 1 From the Adaptec CI/O toolbar, click the Update SCSI Drivers button. A list of all NetWare servers that have the Adaptec CI/O NLM installed and loaded appears. 2 Select a server and click the Select button. The User Login Information dialog box appears. 3 Complete the User Login Information dialog box, then click the Login button. The user name and password you enter must have supervisor privileges to the server. Note: If you are already logged in to the server as a user, logging in to the server from this dialog box as a new user with supervisor privileges will log out the original user. At the conclusion of Updating SCSI Drivers, the newer user is also logged-out. If necessary, the original user must log in to the server again. A dialog box appears displaying the login status to the selected server. 4 Click the Continue button. A dialog box appears that displays a list of Adaptec host adapters installed on the server. If no Adaptec host adapters are installed, you must install one before continuing. 3-7 Stock Number: , Rev. A Page: 3-7

42 5 Select the host adapter(s) you wish to update and click the Update button. The drivers are copied to either the \system\adaptec\cio.3x or \system\adaptec\cio.4x directory (created if necessary) on the server s sys: volume. This directory serves as a temporary storage location until the Adaptec CI/O NLM is able to transfer the drivers to the server s DOS partition. This transfer occurs when the Adaptec CI/O NLM detects the presence of the drivers in either directory. Since the Adaptec CI/O NLM is already loaded at this point, and because the NLM is constantly checking for the presence of the drivers, the drivers can be detected in a matter of seconds; the drivers are then transferred to the corresponding \adaptec\cio.3x or \adaptec\cio.4x directory (created if necessary) on the server s startup directory of the DOS partition. Note: The frequency of how often the Adaptec CI/O NLM checks for the presence of the drivers can be configured by loading the NLM with the u parameter followed by the number of seconds. For example, entering load cio u10 causes the NLM to check every 10 seconds. Selecting a value of 0 seconds causes the NLM to never check for the driver. The default is 5 seconds. See Loading the Adaptec CI/O NLM on page Stock Number: , Rev. A Page: 3-8

43 Using Adaptec CI/O After the drivers have successfully been transferred, an entry is created in the update log (i.e., sys:\system\adaptec\update.log) that identifies the name of the drivers, and the time and date they were transferred. The drivers located in the sys:\system\adaptec\cio.3x or sys:\system\adaptec\cio.4x directory are then removed. 6 Once the Status field indicates that the driver update is completed, click the Exit button to return to the previous dialog box. 7 Click the Cancel button to return to the list of servers. Once the drivers are available on the DOS partition, you must then load the drivers in order to utilize them. Loading Drivers from the Server s DOS Partition If the driver you are loading controls a disk that mounts the sys: volume, then complete Steps 1 through 8, and follow the instructions at the end of Step 8. You will need to have physical access to the server you are updating in order to bring the server down and back up. If the driver you are loading controls a disk that does not mount the sys: volume, then complete Steps 1 through 13. In this case, there is no need to down the server. All steps to load the driver may be done from the client through the RConsole feature of Adaptec CI/O. Some storage devices, however, will be temporarily brought offline. To load the drivers, follow these steps: 1 From the Adaptec CI/O toolbar, click the RConsole button. A list of all NetWare servers that RConsole has detected appears. 2 Select the server you wish to update. 3 Enter a password that has RConsole privileges to the server. Note: Steps 4 through 8 below explain how to modify your autoexec.ncf and startup.nc files so that the drivers are loaded at bootup. 4 Edit your autoexec.ncf and startup.ncf files, by typing load install 3-9 Stock Number: , Rev. A Page: 3-9

44 Note: Before making changes to your startup.nc files, be sure to note any load command line parameters for your drivers so that they can be entered again when needed (Steps 6 and 10). 5 Edit your autoexec.nc file and delete any references to existing host adapter drivers you wish to update. 6 Edit your startup.nc file and add load commands specifying the updated drivers located in either the \adaptec\cio.3x or \adaptec\cio.4x directory on the server s startup directory of the DOS partition. Make sure to include any load command line parameters noted above (e.g., load.\adaptec\cio.4x\aic7770.dsk slot=1). 7 Add the following line after the last load parameter. mount all 8 Exit install and return to the colon (:) prompt. If none of the drivers you are loading controls a disk that does not mount the sys: volume: Continue with Step 9. If the driver you are loading controls a disk that mounts the sys: volume: Follow these steps: a Exit the console of the server by pressing Alt-F2, then select Yes. b Press Esc, then select Yes to exit the RConsole. c Walk over to the server you are updating and then down the server and exit to DOS. d Run server.exe to bring up the server and start the load process. The changes made to the startup.ncf and autoexec.ncf will now take effect. This completes loading the new drivers; do not continue with Steps Unload the existing driver by typing unload drivername (e.g., unload aic7770.dsk) 3-10 Stock Number: , Rev. A Page: 3-10

45 Using Adaptec CI/O 10 Load the appropriate driver from either the \adaptec\cio.3x or \adaptec\cio.4x directory on the DOS partition. Make sure to include any load command line parameters noted above (e.g., load.\adaptec\cio.3x\aic7770.dsk slot=1). 11 Type the following line. mount all 12 To exit the console of the server, press Alt-F2, then select Yes. 13 Press Esc, then select Yes to exit the RConsole. Note: An alternative method to load the drivers is to copy them from the \adaptec\cio.4x or \adaptec\cio.3x directory on the server s DOS partition to the server s startup directory on the DOS partition (overwriting any existing drivers with the same name). Then run server.exe to bring up the server and start the load process. We recommend, however, loading the drivers by modifying load commands in your startup.ncf file, as explained in the above steps Stock Number: , Rev. A Page: 3-11

46 Display NetWare Servers Display NetWare Servers creates a custom layout of all NetWare servers available on the network. From this layout you can quickly locate the server you want to manage through Adaptec CI/O. Before you can do Display NetWare Servers, however, you must first complete an IPX Extended Discovery from OpenView. An IPX Extended Discovery locates all IPX devices, identifies devices, and assigns the appropriate map symbol to each device. For more information, see IP and IPX Discoveries on page 4-4. Completing an IPX Extended Discovery To complete an IPX Extended Discovery, follow these steps: 1 From the OpenView Autodiscovery\Discover submenu, choose Discovery Manager. The Discovery Manager dialog box appears. 2 In the Display section of the dialog box, click on Database Contents and Extended Discovery. 3 Click the Start Extended Discovery button. The Start Extended Discovery button grays out and the Extended Discovery begins. 4 Wait for the Extended Discovery to complete (when completed, the Start Extended Discovery button becomes selectable and is no longer grayed out, and Extended Discovery in the Status box displays Idle). Depending on your network, the Extended Discovery may take several minutes. Note: HP OpenView (100 Node Version) discovers all server nodes of the network; however, any maps that are created with the Do Basic Layout option are truncated after the first 100 server nodes are shown. 5 When the Extended Discovery is completed, close the Discovery Manager dialog box. Note: A server that is not up and running when you begin the IPX Extended Discovery is not included as part of the discovery Stock Number: , Rev. A Page: 3-12

47 Using Adaptec CI/O Displaying all Available NetWare Servers To display NetWare servers, follow these steps: 1 Make sure an IPX Extended Discovery has been completed. 2 Click the Display NetWare Servers button from the Adaptec CI/O toolbar. An alphabetized custom layout of the network servers found through the IPX Extended Discovery appears. Each icon displayed represents a server on the network. To create a submap of SCSI devices connected to these servers, refer to Add SCSI Devices on page Note: A comprehensive layout of the network can be created by opening the OpenView Autodiscovery/ Layout submenu, and choosing Do Basic Layout. This layout includes all the devices in the Autodiscovery database. If you are using OpenView (100 Node Version), Adaptec CI/O by default masks out the IPX and TCP/IP workstations (including PCs). For Adaptec CI/O purposes, only the NetWare servers are of interest. 3 Save this layout to a file by opening the OpenView File menu and choosing Save As Stock Number: , Rev. A Page: 3-13

48 Note: When the Adaptec CI/O NLM is installed in additional servers or when the SCSI configuration of a server is changed, a Display NetWare Servers map should be created and saved again. The file is saved with an.ovm extension and can be opened at a later time without having to run another OpenView IPX Extended Discovery. Add SCSI Devices Add SCSI Devices quickly locates and identifies SCSI devices connected to NetWare servers that have the Adaptec CI/O NLM installed and loaded. Add SCSI Devices polls the servers on the network and creates submaps of all SCSI devices it discovers. From the submap, you can easily monitor alarms and graph the performance of your SCSI devices. Refer to SNMP Traps and Alarms on page 3-17 and SCSI I/O Monitor on page Note: When the Adaptec CI/O NLM is installed in additional servers; or when the configuration of a server is changed, the CI/O submap should be created and saved again. In order to add SCSI devices, a Display NetWare Servers map (or a Do Basic Layout map from OpenView) must be created. Refer to Display NetWare Servers on page To add SCSI devices, follow these steps: 1 Make sure a Display NetWare Servers map has been created, and the server you wish to manage is displayed as an icon. 2 From the Adaptec CI/O toolbar, click the Add SCSI Devices button. A dialog box appears that displays a count of the total number of servers and the number of servers to which SNMP requests have been sent. After all requests have been sent, the message changes to display the number of servers from which replies have been received. Allow this routine to complete; it may take several seconds (or longer, if some servers are down). You may 3-14 Stock Number: , Rev. A Page: 3-14

49 Using Adaptec CI/O stop the process at any time by clicking the Stop button. All outstanding requests are canceled. Note: We recommend that you not switch to other windows or programs until this routine is completed. 3 From the Display NetWare Servers map, double-click the icon of the server you wish to display SCSI devices for. A submap similar to the following is displayed. Note: All server submaps are created with a single execution of the Add SCSI Devices button. If the Adaptec CI/O NLM has been installed and a SCSI subsystem exists on the server, a submap with icons representing the SCSI devices appears, similar to that shown in the above figure. Note: If a comprehensive layout of the network was created with Do Basic Layout from OpenView, the GoTo and Network Interface Card icons shown in the above figure are included as part of the submap Stock Number: , Rev. A Page: 3-15

50 If the Adaptec CI/O NLM has not been installed, or if no SCSI subsystem appears, an empty submap or a submap with only the GoTo and Network Interface Card icon appears. Note: To view a description of, or to view the alarm log generated for each icon on the submap, select an icon and click the right mouse button to access a selection menu. The GoTo icon represents a link to another associated map. To follow the link, double-click the icon. The Network Interface Card (NIC) icon represents the network card for the server. The name of the server is displayed with the icon. The Host Adapter icon represents an Adaptec host adapter connected to the server. The Adaptec family name of the adapter is displayed with the icon. The SCSI Device icon represents a SCSI device connected to the Adaptec host adapter. The type of device, along with the model name of the device are displayed with the icon. To begin monitoring the I/O activity for the device, double-click the icon. See SCSI I/O Monitor on page Note: If a layout is created with the Do Basic Layout command from OpenView, the SCSI icons are deleted from all submaps; you must run Add SCSI Devices again to display the icons Stock Number: , Rev. A Page: 3-16

51 SNMP Traps and Alarms Using Adaptec CI/O SNMP traps are messages that are generated to indicate a change in the status of a device on the server. Alarms are the main mechanism on the client used to communicate a change in device status. When the Adaptec CI/O NLM detects certain changes in the SCSI devices on the server, it generates an SNMP trap. This trap is then sent to specific client PCs that have Adaptec CI/O installed and are specified in the traptarg.cfg file located in the sys:\etc directory on the server (see Monitoring Traps at Multiple Clients on page 3-18). When an SNMP trap is received, the client PC converts the trap into an OpenView alarm. When an alarm is displayed on a submap of SCSI devices (see Add SCSI Devices on page 3-14), the device s icon, along with both the server icon and the network icon associated with the device, changes color to visually signify that an alarm has been generated. For example, if a hard disk loses power or goes offline, the device s icon changes from blue to red, indicating that an alarm has been generated. Once the hard disk goes back online, the icon changes from red to green, indicating that the device is again functioning. When the alarm condition is cleared by the user, the icon reverts to blue. Three types of SNMP traps are generated by the Adaptec CI/O NLM and subsequently converted into the following OpenView alarms: Administrative Alarms generated when the Adaptec CI/O NLM detects changes which may render it unable to detect failures in the SCSI subsystem. This may occur when the device database is corrupted or when the NLM is unloaded. Host Adapter Alarms generated when the status of any SCSI host adapter changes. This change can occur when an adapter comes online or goes offline. The nature of the change is displayed in the alarm. Logical Unit Alarms generated when the status of any device attached to a host adapter changes. Change may be due to failure of the device, a new device becoming available, or a previously failed device returning to operation. Some devices such as jukebox CD-ROM players may have multiple logical units. For a jukebox CD-ROM player, these logical units correspond to each of the slots available for a CD Stock Number: , Rev. A Page: 3-17

52 Opening the OpenView Alarm Log window allows details of alarms to be examined and alarms to be cleared or acknowledged. Refer to Chapter 6, Monitoring Devices on the Network for information on monitoring, managing, and configuring alarms. Monitoring Traps at Multiple Clients In order for a client PC to receive SNMP traps and to view OpenView alarms, the PC s IPX network number and MAC address must be included as an entry in the servers s traptarg.cfg file (located in the sys:\etc directory of the server where you installed the Adaptec CI/O NLM). If the client PC is the same PC from where you installed the Adaptec CI/O NLM to the server, then this PC s IPX network number and MAC address is already included as an entry in the traptarg.cfg file. Installing the Adaptec CI/O NLM automatically makes this change for you (see Installing the Adaptec CI/O NLM to a Server on page 3-3). Note: If your server does not have the traptarg.cfg file located in the sys:\etc subdirectory, it may indicate that SNMP is not installed on the server. SNMP must be installed on all servers that run Adaptec CI/O. NetWare 3.11: This version of NetWare is shipped without SNMP; it is available at no charge from Novell. Contact your NetWare supplier or Novell to obtain SNMP. NetWare 3.12 or NetWare 4.xx: These versions of NetWare install SNMP automatically when you install the server. If you would like to specify different or additional client PCs to receive SNMP traps from the server, you must manually edit the traptarg.cfg file to include the IPX network number and MAC address of each PC. To edit the traptarg.cfg file from a client PC, follow these steps: 1 Open a DOS session in Windows Stock Number: , Rev. A Page: 3-18

53 Using Adaptec CI/O 2 Log on to the server by entering the following (you must have supervisor privileges): attach servername\loginname 3 Enter the password. 4 Map to the sys: volume of the server by entering the following: map next servername\sys: 5 Change to the mapped drive and open the traptarg.cfg file (i.e., sys:\etc\traptarg.cfg) with a DOS text editor. 6 Scroll down to the Protocol IPX section of the file. 7 For each client PC to which you want to send traps, add a line to the file that includes the IPX network number (8 digits) and the MAC address (12 digits) of each client PC; include a Tab before the IPX Network Number. For example (Tab) :008DAD088E24 When all of the appropriate entries are added, the Protocol IPX section should look something like the following Protocol IPX :008DAD088E :0080AD0761EC 8 Save the file and exit. Obtaining IPX Network Numbers and MAC Addresses You can get the IPX network number and MAC address for your CI/O client by switching to another DOS session and typing userlist /a loginname (NetWare 3.x) or nlist user=loginname /a (NetWare 4.x) where loginname refers to the client login of your PC. If there are multiple logins, use the information marked with an asterisk (*). When the user information is displayed for the server, the Network number identifies the IPX network number and the Node Address identifies the MAC address. When adding these numbers to the Protocol IPX section, be sure to include enough leading 0s so that the IPX network number is made up of 8 digits and the MAC address of 12 digits Stock Number: , Rev. A Page: 3-19

54 SCSI I/O Monitor The SCSI I/O Monitor allows you to monitor the performance of SCSI devices attached to Adaptec host adapters installed in a server. The monitor graphs the Input/Output (I/O) activity taking place on a SCSI device. A variety of graphs can be created, and different levels of I/O activity can be measured, including the number KBytes read and/or written, and the number of SCSI commands processed. Note: The I/O Monitor works only with the latest set of Adaptec instrumented device drivers. See Update SCSI Drivers on page 3-6 for instructions on installing and loading these drivers. Depending on your client PC s system resources (memory and processing power), several devices may be monitored simultaneously; or you may open multiple I/O Monitors for the same device Stock Number: , Rev. A Page: 3-20

55 Using Adaptec CI/O Monitoring a Device on the Server In order to monitor a device on the server, a SCSI device submap of the server must be displayed on your screen. This submap must consist of at least an Adaptec SCSI host adapter, and at least one SCSI device. Refer to Add SCSI Devices on page 3-14 to create the submap. To monitor a SCSI device, follow these steps: 1 Make sure a submap of the server is displayed on your screen, and the SCSI device you wish to monitor appears as an icon. 2 From the submap, double-click the icon of the SCSI device you wish to monitor. (An alternative method is to highlight (click) the icon, then either click the SCSI I/O Monitor button from the Adaptec CI/O toolbar; or choose I/O Monitor from the OpenView Diagnostics menu.) The I/O Monitor opens and immediately begins monitoring. If there is any activity on the device, the I/O Monitor starts graphing Stock Number: , Rev. A Page: 3-21

56 The Performance Graph The I/O Monitor graphs data points only when there is I/O activity on the selected device. When there is no I/O activity to graph, the animated bitmap (located above the Resume button) serves as an indicator that data sampling is still active. Device This field displays the type of device being monitored; the channel number or the array number; the SCSI ID number; and the Logical Unit Number (LUN), respectively. Current This field displays the current level of I/O activity. If there is no I/O activity to report, this field displays a 0. Avg This field displays the average level of I/O activity for the number of data samples that have been obtained. Peak This field displays the highest level of I/O activity obtained by a data sample. Animated Bitmap If the bitmap is not active, it indicates that no data sampling is taking place. When the performance graph is not displaying any I/O activity, this bitmap continues to show activity. Resume This button resumes the data sampling after a pause. Pause This button pauses the data sampling. Exit This button terminates data sampling and exits the I/O Monitor Stock Number: , Rev. A Page: 3-22

57 Using Adaptec CI/O Configuring the I/O Monitor The I/O Monitor default settings are set to graph the number of KBytes read per second in an area graph with 25 data points. To graph a different I/O activity or to change the type of graph displayed, change the configuration parameters in the lower half of the I/O Monitor. I/O Monitor Radio Buttons Select combinations of these buttons to graph the desired I/O activity. The combinations are as follows: Reads and KBytes: Graph the number of KBytes read from the disk. Writes and KBytes: Graph the number of KBytes written to the disk. Both and KBytes: Graph the number of KBytes read, written, and their total on a single graph. Reads and Scatter/Gather: Graph the number of driver Scatter/Gather SCSI Read commands processed. The software driver consolidates SCSI Read commands for increased speed and efficiency into what are called Scatter/Gather lists. This is the count of these lists. Compare this value to that for Requests to see how Scatter/Gather improves the I/O throughput of your NetWare server. Writes and Scatter/Gather: Graph the number of driver Scatter/Gather SCSI Write commands processed. Both and Scatter/Gather: Graph the number of all Scatter/ Gather Read, Write, and total commands processed by the driver. Reads, Writes, or Both and Requests Received: Similar to Scatter/Gather, but displays total I/O requests processed Stock Number: , Rev. A Page: 3-23

58 Sampling Interval Enter a value, in seconds, from 1 to 60. You may also use the vertical scroll bar to increase or decrease the interval value. By default, the I/O Monitor obtains a data sampling from the server about once a second. To reduce the sampling rate to only as often as once a minute, change the Sampling Interval to 60. Graph Points Enter a value from 10 to 50 data points. You may also use the vertical scroll bar to increase or decrease the number of data points. Graph Type Use the drop down list box to select a Line, Bar, Area, or 3D Area graph. Defaults Click the Defaults button to reset the configuration parameters back to their default values. Backup Program The Backup Program allows you to back up selected server files and directories to your tape medium. To launch the Backup Program, click the Run Backup Program button on the Adaptec CI/O toolbar. This program has its own windows, help screens, and manual. Please refer to these materials included with Adaptec CI/O for more information on using the Backup Program. Launching Other Backup Programs The Run Backup Program button on the Adaptec CI/O toolbar can be configured to launch other Windows backup programs instead of the one provided with Adaptec CI/O. To configure the Run Backup Program button, switch to any DOS or Windows text editor and complete the following: 1 Open the cio.ini (or cioss.ini for Adaptec CI/O Single Server) file, located in the directory on your client PC where Adaptec CI/O is installed. 2 Scroll down to the [CIO_Defaults] section of the file and locate the following lines: BackUpInstalled=yes BackUpDir=c:\procx BackUpApp=cladmin.exe 3-24 Stock Number: , Rev. A Page: 3-24

59 Using Adaptec CI/O 3 Modify the lines so that the following is specified: BackUpInstalled= is set to Yes (if set to anything but yes, then the next two lines are ignored and an error box appears when trying to launch the program from the toolbar). BackUpDir= includes the path to the directory of your backup program. BackUpApp= includes the executable file used to start the program. Note: The BackUpInstalled= and BackUpDir= lines can also be modified through the Configuration and About dialog box, as explained in Configuration and About on page The BackUpApp= line, however, must be modified by manually editing the cio.ini file. 4 Save the file Stock Number: , Rev. A Page: 3-25

60 Configuration and About The Configuration and About dialog allows you to configure how CI/O manages the discovery of network devices and the appearance of the Adaptec CI/O toolbar on your screen. You can also configure how the Backup Program and CI/O Remote Console Shell are launched from the Adaptec CI/O toolbar. Information about the version of Adaptec CI/O currently installed can also be obtained from this dialog. To access the dialog, click the Configuration and About button from the Adaptec CI/O toolbar. The following shows the settings of the dialog when it is opened for the first time. Discovery Management: This section of the dialog configures how Adaptec CI/O handles Extended Discovery, as explained in Completing an IPX Extended Discovery on page Ignore Generic IPX Click this check box to exclude client PCs and workstations operating under the IPX network protocol from being discovered Stock Number: , Rev. A Page: 3-26

61 Using Adaptec CI/O Ignore Generic TCP/IP Click this check box to exclude client PCs and workstations operating under the TCP/IP (IP) network protocol from being discovered. SNMP Retries Enter the number of times (1-60) SNMP attempts to communicate with a server for information about the devices installed. SNMP Timeout Enter the number of seconds (1-60) between SNMP Retries. Toolbar Management: This section of the dialog configures how the Adaptec CI/O toolbar is displayed on your screen. Orientation Click Vertical to display the toolbar vertically. Click Horizontal to display the toolbar horizontally. Always on Top? Click Yes to display the toolbar always on top. Click No to allow other windows to cover the toolbar. Startup Mode Click Show to display the toolbar (in either its vertical or horizontal orientation) when Adaptec CI/O is launched. Click Iconize to display the toolbar as an icon when Adaptec CI/O is launched. Screen Position Click Remember at Program Close to display the toolbar in the same location it is in when OpenView is shutdown. Click Remember Current Position to display the toolbar in the same location it is in when you click the OK button on this dialog. Click Don t Set Position to ignore this item. Program Launch: This section of the dialog configures how the Backup Program and Remote Console are launched from the Adaptec CI/O toolbar. Backup Installed Click this check box to enable launching the Backup Program from the toolbar. Backup Directory Enter the full path of where the Backup Program files are located on your client PC Stock Number: , Rev. A Page: 3-27

62 Note: To specify the executable file used to launch the Backup Program, you must manually edit the cio.ini (or cioss.ini) file, as explained in Launching Other Backup Programs on page Remote Console Installed Click this check box to enable launching the CI/O Remote Console Shell from the toolbar. Remote Console Directory Enter the full path of where the Remote Console files are located on your client PC. (Adaptec CI/O installation automatically creates an rconsole subdirectory under the directory where Adaptec CI/O is installed and installs the Remote Console files to that directory.) Remote Console Executable Enter the name of the file used to launch the Remote Console. The rconsole.pi file usually launches the Remote Console. OK: Click this button to accept the current configuration of the dialog. Cancel: Click this button to exit the dialog without recording any changes. Defaults: Click this button to restore the values displayed when this dialog is opened. About: Click this button to view information about the version of Adaptec CI/O currently installed on the client PC Stock Number: , Rev. A Page: 3-28

63 HP OpenView Reference Section II Stock Number: , Rev. A Page: xxix

64 Stock Number: , Rev. A Page: xxx

65 4 Creating Network Maps Automatically About This Chapter Read this chapter to find out How to create maps using Autodiscovery 4-1 Stock Number: , Rev. A Page: 4-1

66 Stock Number: , Rev. A Page: 4-2

67 Creating Network Maps Automatically 4 Overview You can create network maps automatically using Autodiscovery to locate and identify devices on your network. You can also manually create network maps using the map tools. In most instances, creating maps with Autodiscovery is the fastest and easiest method. You can change a map created with Autodiscovery at any time using the map tools. Note: References to both the TCP/IP (IP) and IPX network protocols are included in this chapter; however, the Open- View (100 Node Version) shipped with Adaptec CI/O does not support the IP protocol. References to the IP protocol are only applicable if you are running the full-featured version of OpenView. This chapter provides information about how to create maps using Autodiscovery. It includes information about IP and IPX Discoveries Entering information required to perform a discovery Starting the process for a Basic IP Discovery and an Extended Discovery Creating submaps of discovered devices For information about manually creating new maps or editing existing maps, see Chapter 5, Creating Network Maps Manually. Configure Discover Layout Configure Discovery Networks Discovery Enter network and device specifications Configure and start Autodiscovery Build database of discovered devices Select layout options and draw map 4-3 Stock Number: , Rev. A Page: 4-3

68 IP and IPX Discoveries Autodiscovery searches both IP and IPX networks, identifies devices on the network, and assigns the appropriate OpenView map symbol to each device. You can then use Autodiscovery s layout function to create an OpenView map of the devices. Basic Discovery uses routers to discover and identify all IP devices on your network. Autodiscovery reads each router's next hop and ARP tables, then discovers and identifies all the devices listed in the tables. Autodiscovery continues the Basic IP Discovery until it has searched all segments of the network. Extended Discovery uses NetWare diagnostic services to locate all IPX devices, then uses SNMP to identify the devices. It can also run program modules created by equipment suppliers that provide additional discovery information. These supplemental modules may or may not be present depending on your OpenView system s configuration. Once you start either a Basic IP or an Extended Discovery, they run in the background and perform periodic discoveries to update a database of device information. You can configure Autodiscovery to schedule discoveries, limit the devices included in a search, and customize the layout of an OpenView map. Preparing for a Discovery In order to start a discovery, you need to know some information about your own network and the networks you want Autodiscovery to search. To run a basic discovery, you must provide the following information: Your IP subnet mask The IP networks you want to discover The IP address and community name for your default gateway or router You can run an Extended Discovery of IPX devices without providing information about your network. However, if you want to limit the discovery to specific IPX networks, you need to provide the 4-4 Stock Number: , Rev. A Page: 4-4

69 Creating Network Maps Automatically names of those networks. You can use Novell s COMCHECK utility to see which IPX networks are currently in use. You can use the form provided here to record the information. IP Subnet Mask IP Network Addresses Default Gateway IP Address Default Gateway Community Name IPX Network Names Before running Autodiscovery, add the community name for your default gateway or router. Choose Customize Device Access from the Options menu. Choose Add, this displays the Add Device Access Information dialog box. Type the addresses of the network routers and their respective community names in the Address and Community Name text boxes. Click OK. For more information about how to use the Customize Device Access dialog box, see Chapter 6, Monitoring Devices on the Network. 4-5 Stock Number: , Rev. A Page: 4-5

70 Configuring Autodiscovery Before you can run a discovery, you need to enter information about your network and the networks you want to search. You enter this information in the Configure Discovery Networks dialog box. To open the dialog box, choose Configure from the Autodiscovery menu and then choose Discovery Networks. Networks Enter the address of a network you want to search in the Networks text field, then click the Add button. Autodiscovery adds the network to the list of networks to be searched. To delete a network from the list, select the network address in the list, then click the Delete button. If you do not know the address of a network, you can enter the address of one device on the network and click the Add button. Autodiscovery calculates the network s address range using the IP subnet mask and adds it to the list. The complete range of networks calculated is not displayed. 4-6 Stock Number: , Rev. A Page: 4-6

71 Creating Network Maps Automatically Note: You do not need to have both IP and IPX devices on your network for Autodiscovery to run. If you have only one type of device, just enter the IP or IPX information in the appropriate fields. IP Subnet Mask Enter your subnet mask. This should be the same as the mask you specified when you installed your TCP/ IP protocol stack. The subnet mask is used to calculate the node address range for your network. IP Default Gateway Enter the address for your IP default gateway or router. Autodiscovery needs this address to begin a discovery. IPX Maximum Hops If you want to limit the range of an Extended IPX discovery, enter the number of servers you want Autodiscovery to search. Each hop represents one server beyond the first NetWare server on the network. Discover All IPX Networks Select this option if you do not want to limit the IPX discovery to only those IPX networks listed in the Networks list box, but want Autodiscovery to locate and identify all IPX Networks within the number of hops specified in IPX Maximum Hops. Note: If you are using a router with a different community name than other devices, you can specify its community name in the line SNMPAltRouterCommunity= in the [OpenViewSNMP] section of the ovwin.ini file. When you have entered all the information, click OK to save the information and start the Basic IP Discovery. All of the information that you enter in the Configure Discovery Networks dialog is saved with the map. When you load a different map, you load the values saved with the newly loaded map. 4-7 Stock Number: , Rev. A Page: 4-7

72 Managing Autodiscovery Both IP and Extended Discoveries can be scheduled to run automatically. (You can start Extended Discovery on demand using the Discovery Manager dialog box.) You can specify devices to be added to or deleted from Autodiscovery. You can also monitor the progress of both the Basic IP and Extended Discoveries in the Discovery Manager dialog box. Note that the Discovery Manager dialog box is iconized and the Discovery Manager command disabled while an Extended Discovery is running. Scheduling Discovery You can set a schedule for Autodiscovery to run both the Basic IP and Extended Discoveries. You set these schedules in the Configure Discovery Schedule dialog box. To open the dialog box, go to the Autodiscovery menu and choose Configure, then choose Discovery Schedule. Basic IP Discovery Enter the number of minutes you want as the interval between discovery processes. Choose the Enable ARP Cache Reader option if you want Autodiscovery to search all ARP caches each time Basic IP Discovery is run. 4-8 Stock Number: , Rev. A Page: 4-8

73 Creating Network Maps Automatically Choose the Enable IP Router Discovery option if you want Autodiscovery to search routers each time Basic IP Discovery is run. If you want to completely disable Basic IP Discovery, deselect both the Enable ARP Cache Reader option and the Enable IP Router Discovery option. Extended Discovery If you want Autodiscovery to start the Extended Discovery at regular intervals, choose the Timed Intervals option button and enter the number of minutes you want for the interval. If you want Autodiscovery to start the Extended Discovery at specific times, choose the Specific Times option button and place a marker at each hour you want to run a discovery. To place a marker, choose the Move option button, then click the New Marker button and drag the marker to the time you want. As you drag the marker, the corresponding time appears over the bar. If you want to delete a marker, choose the Delete option button, then click the marker you want to delete. Configuring Device Classes If you want to narrow the search for a discovery or limit the devices drawn by layout, you can configure Autodiscovery to ignore certain device types in its search. For example, if your network has a large number of personal computers, you may want to reduce the discovery process time by excluding the computers from the discovery or you may want to layout a map that contains only certain types of devices. You specify the device types you want Autodiscovery to ignore in the Configure Device Classes dialog box. To open the dialog box, choose Configure from the Autodiscovery menu, then choose Device Classes. 4-9 Stock Number: , Rev. A Page: 4-9

74 The Configure Device Classes dialog box lists all registered device classes. Any device that does not respond to an SNMP identification request (such as most personal computers) is listed as a Generic IP or Generic IPX Device. Ignore Choose the device type that you want Autodiscovery to ignore and then click the Ignore button or double-click on the entry to toggle the ignore flag. If you want to include the device type in the search or layout again, choose the device type in the list, then click the Include button. Configuring Ignored Devices If you want to prevent devices from being added to the Autodiscovery database, you can configure Autodiscovery to ignore those devices. You specify these devices in the Configure Ignored Devices dialog box. To open the dialog box, choose Configure from the Autodiscovery menu, then choose Configure Ignored Devices. Ignored Devices Enter the network address of the device you want to ignore, then click the Add button to add the device to the list of ignored devices. The device is not removed from the Autodiscovery database but it is not included in any maps you create from the database. If you want an ignored device to be included during layout, remove it from the list of ignored devices. Click the device s address in the list box, then click the Delete button to remove it from the list. If the device is contained in the database, Autodiscovery includes it in any maps you create from the database. Press OK to save the changes to the database. The list of ignored devices is stored with the current map Stock Number: , Rev. A Page: 4-10

75 Creating Network Maps Automatically User-Specified Devices You can maintain a separate list of devices to be added, without running an entire discovery. When you add a device manually, Autodiscovery includes it in the database and in any maps you create from the database. You add these devices using the Configure User-Specified Devices dialog box. To open the dialog box, choose Configure from the Autodiscovery menu, then choose User-Specified Devices. User-Specified Devices Enter the network address of the device you want to add to the supplemental list, then click the Add button to add the address to the list box. If you want to delete a device from the list, select the device s address in the list box and click the Delete button. Press OK to save the changes to the database. If a device you entered is in a network that you did not specify as a discovery network, a message box asks if you want the network added to the list of discovery networks. If you answer Yes, all devices in the added network are discovered and added to your database. If you say No, the device that you specified is added as a user-specified device. The list of userspecified devices is stored with the current map Stock Number: , Rev. A Page: 4-11

76 Viewing Autodiscovery Results To view the Autodiscovery Manager process, choose Discover from the Autodiscovery menu, then choose Discovery Manager. If the Discovery Manager command is grayed, the Discovery Manager is already displayed, though it may be hidden behind another window or possibly be iconized. The list box in the Discovery Manager displays the address, device name, and system description MIB variable of each discovered SNMP device. If Autodiscovery cannot identify a device, the list displays the device name as a Generic IP or Generic IPX Device. Networks This field lists the address of each network that contains a listed discovered device. Display You can control the contents of the device list by choosing one or more of the display options. Choose Database Contents to show all discovered devices. Choose Basic IP Discovery to show all devices discovered by Basic IP Discovery since the last time you reset the display Stock Number: , Rev. A Page: 4-12

77 Creating Network Maps Automatically Choose Extended Discovery to show all devices discovered by Extended Discovery since the last time you reset the display. Choose New Since Last Layout to show all devices added to the database since the last layout. (This choice deselects the other options.) Database Contents This option overrides the other three options. For example, if you choose Database Contents, but do not choose Extended Discovery, Autodiscovery still displays all discovered devices, including those located by an Extended Discovery. However, newly discovered devices do not appear. This list is not updated with new data. Totals This box displays current totals of devices and networks for the display list and for the Autodiscovery database. Start Extended Discovery Click this button to start an Extended Discovery. Stop Extended Discovery Click this button to stop an Extended Discovery. Reset Display Click this button to clear the list box. When you click Reset Display, Autodiscovery clears only the display list, not the Autodiscovery database. The date and time when you last reset the display is shown at the top of the Discovery Manager. Status This box shows the current status of the Basic IP and Extended Discoveries. Basic IP Discovery This field shows the amount of time until the next discovery. When Autodiscovery is running this field also displays next hop routers and SNMP requests to specific IP addresses. Extended Discovery This field tells you whether Autodiscovery is currently running an Extended Discovery Stock Number: , Rev. A Page: 4-13

78 Maintaining the Autodiscovery Database You can print the contents of the Autodiscovery database. If the database has more information than you want, you can clear it. The database is a part of the map. Saving the map also saves the autodiscovery database for the map. Saving the Database To see a readable description of the database, choose Discover from the Autodiscovery menu, then choose Dump Discovery Database. Autodiscovery lists the database contents in the ovdumpit file. This file is stored in the OpenView for Windows directory. Each dump appends to the end of the ovdumpit file, so you may want to delete the current file before dumping the database to it. Clearing the Database To clear a database, choose Discover from the Autodiscovery menu, then choose Clear Discovery Database. Autodiscovery displays a message asking if you want to reset all the discovery information. To clear the database, click on Yes. If you do not want to clear the database, click on No. Note that this does not clear the user-specified configuration information such as discovery networks, user-specified devices, ignored devices, or scheduling information. It only affects the discovery database for the currently loaded map. Running a Router Discovery After completing an initial discovery, Autodiscovery runs periodic discoveries, updating its database with new information from routers and ARP caches. But you may want to start a router discovery without waiting for a scheduled discovery process. This may occur if for example, you have installed a new router, or added a new network to discover Stock Number: , Rev. A Page: 4-14

79 Creating Network Maps Automatically To run a router discovery, choose Discover from the Autodiscovery menu, then choose Discover Routers. Autodiscovery displays a message to confirm that a router discovery should be performed. Click OK to clear the message from the screen. Creating Submaps of Discovered Devices Once you have used Autodiscovery to identify network devices, you can create submaps containing the discovered devices. To create submaps using information obtained from Autodiscovery you Configure preferred names (optional) Set layout options Perform the layout Configuring Preferred Names You can associate a more meaningful name (for example, Denver Office#2) with the device address. This preferred name is saved into the central database and is used for all maps drawn by layout on this OpenView console. To associate a name with a device address, choose Configure Preferred Name from Layout in the Autodiscovery menu. Type the address in the Network Address text box and then type the name you want to associate with the device in the Preferred Name text box. Click on the Save button Stock Number: , Rev. A Page: 4-15

80 Setting Layout Options You can change the general appearance of your layout map by setting layout options in the Basic Layout Options dialog box. To open the Basic Layout Options dialog box, choose Layout from the Autodiscovery menu, then choose Basic Layout Options. Internetwork View Symbol Spacing Drag the scroll box to decrease or increase the distance between symbols on the Internetwork submap (called All Nets) of the current map. The spacing number decreases or increases according to the position of the scroll box on the scroll bar. Network View Symbol Spacing Drag the scroll box to decrease or increase the distance between symbols on each of the Network View submaps created by layout. The spacing number decreases or increases according to the position of the scroll box on the scroll bar. Network View Submap Width Drag the scroll box to decrease or increase the width of all submaps in your layout. The width number decreases or increases according to the position of the scroll box on the scroll bar. A greater width allows more symbols to fit on a submap. Label Devices with MAC Addresses A MAC (Media Access Control) address is the hard-coded address of the device s network interface. These addresses are assigned by hardware manufacturers and should be present on the network device or 4-16 Stock Number: , Rev. A Page: 4-16

81 Creating Network Maps Automatically with the documentation shipped with the device. Choose this option if you want to display the MAC address for each device in the device labels of your layout map. When you have made all the changes you want to the layout options, click OK to save the changes. Autodiscovery implements the changes in the next map you create with the Do Basic Layout command. Executing the Layout The Do Basic Layout command creates a new submap named All Nets with the notation Internetwork View and a set of Network View submaps consisting of one submap for each network containing discovered devices. Each time you perform a layout in a given map file, any previous internetwork and network submaps are cleared before the new submaps are drawn. Home Submap All NETS Submap Internetwork View Network B Network A Network C Submap A Network View Submap B Network View Submap C Network View If you choose to manually annotate submaps, you should keep them under different submap names. Add notation, bitmaps, and other drawing enhancements to the working submaps, not the ones created by the layout process. When the layout process completes a 4-17 Stock Number: , Rev. A Page: 4-17

82 new layout, transfer devices from the discovery submaps to your working submaps using Cut and Paste commands, or rename the submaps to preserve them. To determine whether to perform another layout, click the New Since Last Layout check box in the Discovery Manager dialog box. It displays nodes not drawn on your map that have been discovered since the last time you ran layout Stock Number: , Rev. A Page: 4-18

83 5 Creating Network Maps Manually About This Chapter Read this chapter to find out How to create, edit, save, and print maps using the map toolbar and Map commands. 5-1 Stock Number: , Rev. A Page: 5-1

84 Stock Number: , Rev. A Page: 5-2

85 Creating Network Maps Manually 5 Overview This chapter describes how to create, edit, save, and print maps using the map toolbar and Map commands. The first part provides instructions on how to create a map. The last part of the chapter provides a summary of the map tools and commands. For information about how to create maps using the Autodiscovery feature, see Chapter 4, Creating Network Maps Automatically. OpenView maps use symbols or icons to represent network devices and references to submaps. Lines show communication links between devices. Connections within your submaps attach device symbols to each other so that the devices remain connected when moved on the map. You can assign a background image for a map that shows the physical location of the network devices. 5-3 Stock Number: , Rev. A Page: 5-3

86 Drawing a Simple Map Before you create a network map, you need to know the physical layout of your network. It may be a single LAN, several LANs, or a very complex enterprise-wide network. Whenever possible you should break your map into submaps that help you visualize the network organization. You can create submaps for a workgroup, building site, device type, or any other convenient grouping. The same device can be placed on several submaps to provide alternate views of the network. The home submap should contain a symbol for each submap on the next lower level in your map. Some home submaps include a submap symbol for every submap in the entire map. From the home submap you can walk through your entire network by clicking on submap symbols to display the associated submap. If your home submap does not contain a symbol for every submap, it should contain a path to every device in the network via the submap symbol. The submap symbol displays the most severe status color for all of the nodes or devices within it. This allows the most severe status information for any device in the network to be propagated up to the home submap. The home submap can then give you an overview of status for the entire network. Home Home Submap A Submap A Submap B Submap B Home submap with a submap symbol for each submap Home submap with a path to all submap 5-4 Stock Number: , Rev. A Page: 5-4

87 Drawing a Network Map Creating Network Maps Manually A typical procedure for drawing a network map is as follows: 1 List all of the devices that you want represented in your map. Note the network address of each device (if available) and its relation to the other devices. 2 Organize the devices hierarchically into levels based on their network position, device type, or function. 3 Create a home submap. If possible, add an appropriate background bitmap. Add a submap symbol on the home submap for each submap in the next level of your network hierarchy. If you have selected the Create Submaps Automatically option in the Customize OpenView dialog, a submap is created automatically for each submap symbol that you add to the map. 4 Create a submap for each of the second level submaps shown on the home submap. If possible, add an appropriate bitmap to aid in symbol placement. Add device symbols to each submap along with lines, connections, and annotations. 5 Repeat the process for each level of the hierarchy until all devices are represented. 6 Add additional submaps as desired for alternate views of your network. For example, it might be useful to have a submap that shows all of the hubs or routers in a network. 5-5 Stock Number: , Rev. A Page: 5-5

88 Map Example The following example uses OpenView to create a simple network map. The map file containing the submaps is northnet.ovm. Northnet consists of a home map, three regional submaps, and three local submaps for each regional submap. Home Submap World Regional Submaps Local Submaps Devices Europe Edinburgh Support PC #11, 12, 13 Frankfurt Support PC# 31, 32, 33 Lyon Support PC # 21, 22, 23 Japan Nagoya Lab PC# 31, 32, 33 Osaka Support PC# 41, 42, 43 Tokyo PC, Hedeki, John, Yoshi Hub #3 USA Dallas Lab PC# 11, 12, 13 New York Marketing PC# 11, 12, Sales Manager PC San Jose Lab PC# 21, 22, 23 Background bitmaps are used to make submap layouts more meaningful. The bitmaps used in NorthNet are worldmap.bmp, usa.bmp, europe2.bmp, fareast2.bmp, and office.bmp. 5-6 Stock Number: , Rev. A Page: 5-6

89 Creating Network Maps Manually Creating a Map File and Home Submap To create a map file and home submap, follow these steps: 1 Choose New from the File menu to create a new map. OpenView displays an empty submap with a name of the form <map>:<submap> where <map> and <submap> are initially Untitled 2 Choose Save As from the File menu to name the map file Practice. 3 Choose Rename Submap from the Edit menu to name the current submap WORLD 4 Choose Set Home Submap from the Edit menu and select WORLD as the home submap. Adding a Background It is not necessary to use a background for a submap. They are independent of your network map data and can be added at any time. 5-7 Stock Number: , Rev. A Page: 5-7

90 However, if you have access to suitable.bmp or.tif images, they can actually make it easier to position icons. The bitmaps for NorthNet are provided in the ov\bkground directory. If you do not use a background image, the grid commands in the View menu can be used to aid in positioning icons. To add a background, follow these steps: 1 Choose Set Background Image from the Edit menu. 2 Find and select worldmap.bmp as the background for the WORLD submap. 3 Click OK. 5-8 Stock Number: , Rev. A Page: 5-8

91 Creating Network Maps Manually Adding Submap Symbols To add submap symbols to your map, follow these steps: 1 Choose Add from the Edit menu to display the Add Toolbox. 2 Select Compound Object symbols from the Submap Class list (the symbol class button should be down). 3 Select the Submap symbol from the icon list. 5-9 Stock Number: , Rev. A Page: 5-9

92 4 Position the cursor in the center of North America on the WORLD submap and click to drop the icon. 5 Enter the name for the submap symbol icon. If desired you can enter Net or MAC addresses. Click OK. 6 Repeat steps 4 through 6 for Europe and again for Japan. 7 If necessary, you can click on an icon and drag it to adjust its position on the submap. You can determine whether or not to enter a description at the time you add an icon. Choose Customize HP OpenView from the Options menu. This displays the Customize HP OpenView dialog box. If you check the Describe objects as added check box, the Describe box appears each time you add an object. If you do not check the Describe objects as added check box, the object is added without a name or label. You can add descriptions later on by selecting a map icon and using the Describe command in either the Edit or Monitor menus. If the Describe function has not been deferred, you can press OK in the Describe dialog box and continue adding objects without reselecting from the Add box Stock Number: , Rev. A Page: 5-10

93 Creating Network Maps Manually If the Describe function has been deferred, you can use Ctrl - click to select the Symbol Class button to place multiple icons of the same type on the submap without returning to the Add toolbox. Adding Lines Lines are used to show relationships between network elements and to depict the physical wiring of a network. Use the Line button in the Add toolbox to select line drawing mode. Open the Line Type list box and select a line pattern or weight. Lines are drawn by clicking to set a start point and then dragging and releasing to set the end point. To create a connection between two symbols, you can use the connection button to select connect mode. Connections differ from lines in that map objects can be moved and their connections stretches or contracts to maintain the connection. Connections are drawn from the center of one symbol to the center of another. Connections are displayed behind the symbols that they connect. To connect the three submap symbols on the WORLD submap, follow these steps: 1 Select Connections using the Connection button in the Add toolbox. 2 Select the second thinnest solid line type in the Line Type list box. 3 Click on the USA icon and then drag the connection to the EUROPE icon and release. Repeat this so that all three regional submaps are connected. 4 To label a line, select the line and then choose Describe from the Edit or Monitor menus. Once a description has been entered for a line or connection, it can be given status the same as other device icons Stock Number: , Rev. A Page: 5-11

94 Adding Text You can add text to a submap at any time using the Text button in the Add toolbox. Text is available in different sizes, bold, and underline. The font used is the Windows system default. To add text to a submap, follow these steps: 1 Click the Text button. 2 Select the size and style you want. 3 Click on the submap where text should start. 4 Type in the text. 5 Click again with the mouse or press the Enter key to end text entry. 6 After a text block has been entered, its position can be changed by selecting and dragging it with the mouse. If you need to change the text, delete and reenter the text block. Add Remaining Submaps If you have the Create Submaps Automatically option turned on in the Customize HP OpenView dialog box, a submap has been created for each submap symbol placed on your home submap. You can double-click on the submap symbols one at a time and add symbols as required to each of the submaps. If your map contains several levels of submaps, repeat the process for each level. Saving a Map To save a map file with all of its submaps and symbol descriptions, choose Save from the File menu. This saves the map under its current name. To save the map to another name, choose Save As from the File menu Stock Number: , Rev. A Page: 5-12

95 Printing a Map Creating Network Maps Manually You can print individual submaps. To print the displayed portion of the submap with all of its symbols, lines, connections, text notations, and background bitmaps, choose Print Submap from the File menu. You can also print out a text list of all of the submaps in a map as well as the names and types of devices in the submaps. This list is useful to check your map. Choose Print Object List from the File menu. Disabling the Map Editing Feature You can disable OpenView's map editing to prevent accidental changes to maps. Note: Layout can still modify the map. The layout feature sets the map to Protected mode while it is generating a new map. When the map is completed, it changes to Unprotected mode. The map locking feature allows you to prevent accidental changes to maps. It does not provide data security. To disable manual editing of a map, follow these steps: 1 Choose Protect Map from the Options menu. A dialog box is displayed prompting you to enter a password. The password is case sensitive Stock Number: , Rev. A Page: 5-13

96 2 Enter a password. 3 Click OK. The map editing feature is disabled and the editing status is displayed at the end of the Status Bar. The locking feature is only meant to prevent accidental map changes by the supervisor. The operator and observer can never edit the map regardless of the Map Protect settings. It does not provide data security. If you forget the password, open the ovwin.ini file and delete the Key= entry under [Open- View]. To unlock a map, follow these steps: 1 Choose Unprotect Map from the Options menu. 2 Enter the password and click OK. The editing status is displayed at the end of the Status Bar. Map Toolbar and Commands OpenView provides a toolbar and menu items for creating and modifying network maps. Each of these tools and commands are described below. Note: Applications can add new menus and commands to existing menus. Refer to your application documentation for specific functions Stock Number: , Rev. A Page: 5-14

97 Creating Network Maps Manually Status Bar The Status Bar indicates the current selection and displays descriptive text for toolbar and menu selections. If you are not selecting a tool or menu command the field displays the last selected object's name and type. It also shows the security level of the current user and whether the map is in Protected (i.e., read-only) mode. See Disabling the Map Editing Feature on page Toolbar OpenView displays a toolbar at the top of the main window. The toolbar provides quick access to frequently used functions that allow you to create network maps. The toolbar buttons are described in the following table. Toolbar Functions Tool Description Scissors Cut (same as in the Edit menu). Camera Copy (same as in the Edit menu). Paste Paste (same as in the Edit menu). Eraser Delete (same as in the Edit menu). Pencil Describe (same as in the Edit menu). 1:1 Zoom 1 (same as in the View menu). 1:2 Zoom 1/2 (same as in the View menu). 1:4 Zoom 1/4 (same as in the View menu). 1:8 Zoom 1/8 (same as in the View menu). Home Submap Display the home submap (same as in the Window menu). Previous Submap Display the previous submap (same as in the Window menu). Alarm Bell Display the alarm log. Icon color reflects the highest unacknowledged alarm Stock Number: , Rev. A Page: 5-15

98 Add Window Choose Add from the Edit menu to display the toolbox with drawing functions. The Add window contains the following: Selection Pointer Text Lines Connections Symbols (compound objects, computers, and components) Select Objects Add Text Add Lines Add Connections Add Symbols Display Symbols Choose Text Style Choose Line Style Choose Symbol Set Choose Symbol Click on the appropriate button to select the Text, Lines, Connections, or Symbols buttons. Selecting these buttons while holding the Ctrl key allows you to make multiple adds of a given symbol without returning to the Add window. Click on the Select Object pointer in the Add window to get out of the Multiple Add mode. When you draw a map you can display and choose from various styles of text, lines, and symbols. Applications that run under OpenView can add their own symbols. Refer to your application documentation for additional information. If symbols in the Display symbols list appear as question marks, they are probably symbols added by an application and have not been properly installed. Check for proper installation of applications that use these symbols Stock Number: , Rev. A Page: 5-16

99 Creating Network Maps Manually Select Object The Select Object pointer button is used to restore the cursor to Selection mode when in multiadd mode. Text You can select from different combinations of size and style of text. Text is available in 8, 9, 10, 12, and 14 points. You can specify each size using regular, bold, or underline styles. Lines and Connections You can select lines in 8 thicknesses. Thin lines are available in five patterns, including solid. If you want the line to be attached (connected to a symbol) use the Connection button. You can use different line types to represent different connections in your network. For example, use a thick line to represent a LAN and a thin line for connections from computers to the LAN. Symbol The Symbol button allows you to add selected symbols to a submap. First select a symbol set, Compound Object, Computer, or Component. Then display a list of the available symbols for the set using the list button at the right of the field Stock Number: , Rev. A Page: 5-17

100 The Display Symbols button can be used to display the icons for a symbol set. When adding a symbol to a submap you can select the symbol from either the text list or the graphic list. OpenView provides five Compound Object symbols: Submap, GoTo, Personal Computer, Medium Computer, and File Server. OpenView applications may add additional compound icons. A Compound Object icon can be opened with a double click. In general, symbols for Compound Objects are displayed with a + at the end of their names to help differentiate them from Computer and Component symbols. Note: OpenView stores names entered for Compound Objects using uppercase characters. OpenView also truncates these names to 15 characters. The Submap symbol (shown as a small network) indicates another submap. The background of the Submap symbol displays the status color of the referenced submap. In a hierarchically structured map, the Submap symbol can be used to point to a lower level submap. Double clicking on the Submap symbol causes the referenced submap to display. The GoTo symbol does not display status and can be used to reference any submap. Use the GoTo symbol to link any submaps where you do not want status information to pass between the submaps. Double clicking on the GoTo symbol causes the referenced submap to display Stock Number: , Rev. A Page: 5-18

101 Creating Network Maps Manually Other symbols in the Compound Object category are used for devices that provide internal configuration information to OpenView. If a supporting application is installed, opening one of these could display hardware configuration and status, memory usage, disc space, or installed software. There are several Computer symbols depicting large and medium computers, PCs, and various computer components. OpenView applications can add symbols to or delete symbols from the standard set. The Component symbol set contains various network components such as hubs, routers, and multiplexers. OpenView applications can add symbols to or delete symbols from the standard set. Selection Lists If you frequently make changes to a group of map objects, you can make a list of the objects to use as a group selection function. You can use this list to automatically select the objects to perform operations on them as a group. The effect is the same as if you had selected the objects manually. Two list commands are available in the File menu: Load Selection List and Save Selection List As. For information about using the Selection List commands, refer to Chapter 6, Monitoring Devices on the Network Stock Number: , Rev. A Page: 5-19

102 Stock Number: , Rev. A Page: 5-20

103 6 Monitoring Devices on the Network About This Chapter Read this chapter to find out How to monitor the devices in your network 6-1 Stock Number: , Rev. A Page: 6-1

104 Stock Number: , Rev. A Page: 6-2

105 Monitoring Devices on the Network 6 Overview OpenView provides several different ways that you can monitor the devices in your network. You can Customize the access parameters for devices on your network Poll network devices at set intervals to determine the functioning status of each device Monitor Trap messages sent by network devices alerting you to changes in device status Configure how alarms are processed, displayed, recorded, and forwarded This chapter explains how to configure and use each of these monitoring features. Device Polling Traps Log OpenView Map Alarms Applications Audible alarms, forwarded alarms, triggering of programs 6-3 Stock Number: , Rev. A Page: 6-3

106 Customizing Device Access You can associate with network address control information that is specific to that address. This information is stored in a database that is independent of which map is loaded. For example, you can enter the community name, set community name, and time-out values for devices. These values are used in polling, Autodiscovery, SNMP queries, and third party applications. Devices that you have not customized (devices not in the list) use the system default values. Only customize the access for devices that require values different from the system default values. To customize device access, choose Customize Device Access from the Options menu. The following dialog box appears: The Customize Device Access dialog box lists the default settings for the selected device s community names, retries and time-out values, and whether it is a proxy agent. A proxy agent is a device that acts on behalf of a device that does not have SNMP capabilities. The trap manager uses the Proxy Agent field. 6-4 Stock Number: , Rev. A Page: 6-4

107 Monitoring Devices on the Network To change values for any one of the devices listed, select a device and then click on Modify. The following dialog box appears: Type in the new values that you want to change and click OK. The values that you entered become the new values for the selected device. Note that the Community and Set Community passwords are case sensitive. If you select Use Defaults and click OK, the entry for this device is removed from the database because it is no longer an exception and now uses the default system settings. To change the default values for devices that are not listed in the network addresses list (i.e., the device currently is using system default values), click on Add. The Add Device dialog box appears. Type in the network address and then change the values you want. Click OK. The address of the device appears in the network addresses list. Note that if you do not change any values, the network address does not appear in the list. 6-5 Stock Number: , Rev. A Page: 6-5

108 Polling Network Devices To poll network devices, you perform the following tasks: Create a list of the devices that you want to poll Set the polling parameters (optional) Turn on polling At any time, you can change the list of devices you want to poll. You can also change the current polling parameters for a specific device using the Configure Device Parameters dialog box. If you do not change the device polling parameters it uses the system defaults. To view the current polling list, choose View Polling List from Polling in the Monitor menu. 6-6 Stock Number: , Rev. A Page: 6-6

109 Monitoring Devices on the Network Creating a List of Devices to Poll You can poll any device in the map that has an IP or IPX address. To add a device to poll, follow these steps: 1 Select the device(s) on the map that you want to poll. (Use Shift-Click or Ctrl-Click to select more than one device.) If you want to poll all of the devices in a submap, select the submap icon. 2 Choose Add Device(s) from Polling in the Monitor menu. The following dialog box appears. The network addresses for the devices that you selected appear in the dialog box. Note: If a device that you selected to poll has more than one address, a dialog box asks you to select the address(es) that you want to poll. 3 Click OK. The list of devices to poll is kept separately with each map. One map with device A may choose to poll the device, another map also showing device A may not poll the device. 6-7 Stock Number: , Rev. A Page: 6-7

110 Removing Devices to Poll To remove devices from the polling list, follow these steps: 1 Select the devices on the map that you want removed from the polling list. You can select a single device, multiple devices, or a submap. 2 Choose Remove Device(s) from Polling in the Monitor menu. A message appears telling you how many devices were removed from the polling list. Note: You can also remove devices from the polling list using the Remove button in the View Polling List dialog box. A shortcut for adding and deleting devices in the polling list is to save the selected devices as a Selection List. The list can then be retrieved using Load Selection List. See the discussion on Selection Lists that follows. Selection Lists Some applications support operation on a group of objects. If you frequently make changes to a group of map objects, you can make a list of objects to use as a group selection function. You can use this list to automatically select the objects to perform operations on them as a group. The effect is the same as if you had selected the objects manually. Two list commands are available on the File menu: Load Selection List and Save Selection List. Loading a Selection List Use the Load Selection List command to get a previously saved list. A dialog box asks for the name of the list file to use. When you enter a file name, the objects listed in the file are automatically selected on your map. 6-8 Stock Number: , Rev. A Page: 6-8

111 Monitoring Devices on the Network Saving a Selection List To create a selection list, follow these steps: 1 Select a set of symbols and lines with a Shift-click on each map object that you want in the list. Each object that you select must have been described using the Describe command. 2 Use the Save Selection List As command to save the list to a file. The default list file name is the current map name with the extension.ovl and is stored in the current map directory. In the future, when you wish to select this set of objects, use the Load Selection List command and specify the list file name. Editing a Selection List To add or delete objects from an existing selection list, follow these steps: 1 Use the Load Selection List command and select the file containing the list that you want to edit. The objects in the list are selected on the map. 2 To add objects to the list, Shift-click the new objects. To delete objects, Shift-click on the objects that are already selected. This deselects the objects and deletes them from the list. 3 Use the Save Selection List As command to save the list to a file. All map objects that are selected (highlighted), are saved in the list. 6-9 Stock Number: , Rev. A Page: 6-9

112 Configuring System Polling Parameters OpenView has preset default values that control the polling interval and determine what action to take when a device starts or stops functioning. Use system defaults to poll the most devices with the longest interval such as PC s and printers. For large networks you might have to set longer intervals to keep from overloading the system. To change the system default values, follow these steps: 1 Choose Configure System Defaults from Polling in the Monitor menu. The following dialog box appears. 2 To set the polling interval, enter the appropriate number of hours, minutes, or seconds in the Interval text boxes. 3 Select a severity level for the Device Down and Device Up conditions. 4 Select what types of action to take for the Device Down and Device Up conditions. For more information about alarms, see Configuring Alarm Processing on page Click OK Stock Number: , Rev. A Page: 6-10

113 Monitoring Devices on the Network Configuring Parameters for Selected Devices You can override the system polling parameters for individual addresses. Use this for setting poll rates for those devices requiring shorter intervals such as routers, bridges, and hubs. Use longer intervals for remote devices. To do this, follow these steps: 1 Select the desired device on the map and choose Configure Device Parameters from Polling in the Monitor menu. The following dialog box appears. 2 If you did not select a device on the map, enter the device address that you want to exempt from the system polling values. Note that you do not have to enter the name. 3 Change the values that you want for the polling interval timing, severity, or alarm action. 4 Click Save to save the new values. Click Use Defaults to restore the system default values. Turning Polling On and Off To start the polling process, choose Start Polling from Polling in the Monitor menu. To stop the polling process, choose Stop Polling from Polling in the Monitor menu Stock Number: , Rev. A Page: 6-11

114 Monitoring Traps from Network Devices Traps are specific types of messages that are generated by some devices to indicate a change in their status. When a device is installed on the network, part of its installation procedure is to enter the address of a management console where these traps are to be sent. Refer to the device installation and configuration documentation and set the trap address to the network address of the OpenView console. OpenView automatically logs an information alarm for each trap it receives. You can change OpenView's default response to traps to sound an alarm, change color of the map symbol for the device sending the trap, or enter the trap in the alarm log. You can also change the default response to ignore traps from some or all devices, or configure one trap to auto-acknowledge another one when it is received. Each device class (hub type 1, hub type 2, router, server, etc.) can be assigned a different set of default and customized trap responses. Initially the default trap response for each device class is set to the OpenView system default response. You can change the default response for each device class. In addition, for each device class you can create a customized response for any trap that might be received from a device in that class. Customizing Traps Customizing traps consists of Selecting the device classes for which you want to customize trap alarm actions Selecting or entering the trap IDs for the traps you want to configure Choosing what alarm actions to take when OpenView receives the trap Some device vendors supply trap definition files (.tdf) that can be used to automate trap configuration. If trap definition files have been installed, you can load the predefined traps using the Load Traps button. When a device class has been selected, any predefined traps for this device class is displayed in the Customized Traps list Stock Number: , Rev. A Page: 6-12

115 Monitoring Devices on the Network To customize trap alarms, you use the Customize Traps dialog box. Choose Customize Traps in the Monitor menu. The following dialog box appears. Selecting a Device Class To select a device class for which you want to change the default trap response, follow these steps: 1 Click Add Device Class. The following dialog box appears: 2 Select the device class and click OK. The class name and ID appears in the Device Class Name list. Note: To remove a device class from the list, select the device class and click Remove Device Class Stock Number: , Rev. A Page: 6-13

116 Ignoring Traps By default, all traps are logged according to the actions configured for the system. If you have another application managing traps for a particular class of device, you may want OpenView to ignore traps it receives and let the application maintain the device status. To ignore incoming traps, select the device class whose traps are to be ignored and click Ignore Device Class. Ignore appears in the Flag column next to the device class name. To turn off Ignore, click Include Device Class Stock Number: , Rev. A Page: 6-14

117 Monitoring Devices on the Network Specifying Traps for a Device Class You can create a list of the traps that OpenView responds to for a specific device class. The list of traps is displayed in the Customized Traps list box of the Customize Traps dialog box. For a list of traps for a particular device see the manufacturer s documentation. To add a trap for a device class, follow these steps: 1 Click Add Trap. The following dialog box appears: 2 Select a trap from the Generic list, or choose Specific in the Generic box and enter a trap number into the Specific text box. 3 Click OK. The type of trap you selected or entered appears in the Customized Traps list in the Customize Trap Alarms dialog box Stock Number: , Rev. A Page: 6-15

118 Choosing Trap Alarm Actions You can choose to update the map status (change color of map symbols), sound a bell, or log an alarm entry when a trap is received. To select any of these options, click on the appropriate Alarm Actions check box(es). To set the severity level you want for the alarm, select the option you want from the Severity list. For the Description and Extended Description fields, you can specify information from the trap packet to be displayed in the alarm log. To select the OpenView response to a trap, follow these steps: 1 Select the Device Class. A list of traps available for that device class are displayed in the Customized Traps list box. 2 Select the desired trap from the list of Customized Traps. 3 Choose the desired actions (Update Map, Sound Bell, Log, etc.). 4 Choose OK to save and close, or choose another trap to configure. If you choose another trap, you are prompted to save or cancel your selections for the previous trap Stock Number: , Rev. A Page: 6-16

119 Monitoring Devices on the Network Description Field Variable Substitution Syntax You can specify how information from the trap packet is displayed in the Description and Extended Description fields using field variables. The Extended Description allows you to add additional information to the alarm message. The following table lists the field variables and descriptions. Variables Descriptions \n newline \t tab $C trap community string $E enterprise, represented as a text string if possible $e enterprise, represented as an object ID string of numbers $A name of device that sent the trap. If this device is not represent by a symbol in the map, this field defaults to addressed: concatenated with the device address. $G generic trap id number $S specific trap id number $T timestamp (time since device was last restarted) $* print all variables in the trap $# number of variables in the trap $$ print the $ character $n print the value of the nth variable in the trap, where n is the variable sequence number starting at 1 used to reference subobjects in a device. $-n print the nth variable as a name-type:value string, where n is the variable sequence number starting at 1 used to reference subobjects in a device. $+n print the nth variable as a name:value string, where n is the variable sequence number starting at 1 used to reference subobjects in a device Stock Number: , Rev. A Page: 6-17

120 Loading Traps You can select a trap definition file from which you can select a device class. Click on the Load Traps button. Select a device class and click OK. The traps and their alarm actions for the selected devices class are copied to the trap database (trapmgr.ini). Automatically Acknowledging Alarms Generated by Traps The Acknowledge Alarm text box allows you to specify another trap to automatically acknowledge the currently selected trap. The original trap is moved from the current alarm log to the history alarm log. If the device uses a variable in the trap message to more exactly specify which device subcomponent is sending the trap, you can require the value of this variable to match in the original and acknowledging traps. The variable is used to match the value in the subobject field of the trap message. For example if the trap is from a hub with 16 ports, the trap may contain a value in the subobject field to specify which port caused the trap. Using the variable in the acknowledging trap specification ensures that if port 7 creates a trap by going down, it is only cleared by a trap from port 7 going up. This setting is displayed in the subobject field in the alarm log. If the subobject field is not used, set it to NONE. Otherwise, set it to the ordinal value of the field (i.e. 1 for the first variable in the trap packet, 2 for the second, etc.). Managing Alarms Alarms generated by applications, traps, or polling are managed through the map, alarm log, and alarm forwarding functions. Selecting Map Status Options The map symbol of a device is displayed in the color that represents the device status Stock Number: , Rev. A Page: 6-18

121 Monitoring Devices on the Network To display the available status colors, choose Status Legend from the Monitor menu. The table below lists the status levels and their colors. State Map Alarm Log 1 Description Critical Red Red The device is unavailable. It may be down or in a critical state. Major Dark Red Red There is a problem with the device. Some degradation of function exists. Minor Orange Yellow A noncritical condition has been reported, or the device is in a degraded state. Warning Yellow Yellow There is a problem with the device. No degradation of function exists. Marginal Mustard Yellow The device is approaching shutdown or malfunction. Informational Green Green The device is up and working properly. Disabled Blue Cyan OpenView has no information on the device's state. Unmanaged Cyan Cyan The device is down. Normal Magenta Magenta An informational message about this device has been sent by an application. Unknown Wheat White The device is not managed by an OpenView application. 1 Note that the colors displayed in the alarm log are slightly different than those used on maps Stock Number: , Rev. A Page: 6-19

122 Status Propagation You can select the way device status is propagated to higher submap levels using Customize Alarms in the Options menu. Status propagation can be set to Do not pass status up Pass status up one level Pass status up all levels World - "Home Submap" = Normal = Warning = Criotical U.S.A. Europe Japan U.S.A. Europe Japan San Jose Dallas New York Normally, you would select to propagate up all levels. Then, if your home submap contains a submap symbol for each submap in the next lower level in the map, you can check your network's overall status from the home submap. If a submap represents several devices, its submap symbol on the home submap displays the most severe device status for the lower submap. (Note that the GoTo submap symbol does not propagate status.) 6-20 Stock Number: , Rev. A Page: 6-20

123 Monitoring Devices on the Network You can examine alarms using two methods: Using the map, click on the submap symbol showing an alarm status and walk down the submap levels until you display the submap containing the device that generated the alarm Click Alarm in the toolbar or choose Alarm Log from the Monitor menu to display the alarm log. Select the alarm that you want to check and then click GoTo to display the submap containing the device that generated the alarm Stock Number: , Rev. A Page: 6-21

124 Click on the map object using the right mouse button to display the submap containing the device that generated the alarm Stock Number: , Rev. A Page: 6-22

125 Monitoring Devices on the Network Configuring Alarms Applications monitor the state of network devices and processes and can trigger alarms. The alarms alert network managers of changes in the status of a device or group of devices. When an application detects a change in a device status, it can request OpenView to do one or more of the following: Change the device symbol to the new status color Make an entry in the alarm log Forward an alarm to another management console Sound an alarm Run a program Regardless of whether OpenView is an active window or not, if a device symbol changes color to red, yellow, or magenta, the Alarm icon in the toolbar changes color and displays the most severe unacknowledged alarm in the log. Alarms of all levels are recorded in the alarm log. Note: Not all applications monitor device status. Check your device and application documentation to find if a particular network device indicates its status Stock Number: , Rev. A Page: 6-23

126 Viewing Alarms To display the alarm log, click on the Alarm button in the toolbar or choose Alarm Log from the Monitor menu. The alarm log lists all alarms that have occurred since the last time OpenView was restarted. You can display either Current (unacknowledged) alarms or History (acknowledged) alarms. You can list the alarms either by the order received or severity using the Sort by controls in Customize Alarms in the Options menu. Select Time as the sort criteria if you want the alarms to be listed in chronological order with the most recent alarm at the top of the list. Select Status as the sort criteria if you want the alarms to be listed by the severity of the alarms. Critical alarms are grouped before warning alarms, and alarms within status groups are displayed in chronological order. The alarm log can display up to 900 alarms. Refer to the next section Selecting Alarms for Display for instructions on how to select the alarms displayed Stock Number: , Rev. A Page: 6-24

127 Monitoring Devices on the Network Selecting Alarms for Display You can display selected groups of alarms from the alarm log. Alarm displays can be limited to a type of device, specific device, or class of alarm severity. To configure an alarm display, click on Filters in the Alarm Log window. This displays the Alarm Log Filters dialog box. The Alarm Log Filters dialog box contains the following entries: Alarm type (specific alarm name) This field allows you to select the alarm message type to be displayed. If you have several OpenView applications, each has its own set of alarms and associated messages. Refer to your application documentation for additional information. To select an alarm type, display the alarm type list and select one or all alarm types from the list. The default is All Alarms. Object Type (e.g. Personal Computer) This field allows you to select the types of devices (e.g., hubs, PCs, etc.), whose alarms you want to display. To select an object type, display the list of object types and select one or all object types. The default is All Object Types. Object Name (e.g. PC #21) This field allows you to select individual devices (e.g., hub #1, PC # 3, etc.) whose alarms you want to display. To select object names, display the list of object names and select one or all names. The default is All Objects. In addition to specifying map objects by their names, you can also report on specific subcomponents in a device. To do this 6-25 Stock Number: , Rev. A Page: 6-25

128 enter the desired Subcomponent or Node numbers for the subcomponent devices. Object Status (e.g. Critical) This field allows you to select the types of alarms you want to display. To select status type, display the list of status types and select one or all status types. The default is Any Status. Acknowledging and Deleting Alarms To acknowledge or clear an alarm, select the alarm in the current list, and click Acknowledge. (Note that this does not delete the alarm entry. It moves the entry from the current to the history portion of the alarm log.) The color of the Alarm button on the toolbar is updated to the status of the most severe alarm remaining. The Acknowledge button is disabled unless an alarm is selected. When the last alarm in the list is acknowledged, the Alarm button is grayed to indicate that there are no more unacknowledged alarms. You can select multiple alarms to be cleared using Ctrl-click. To acknowledge all alarms in the list, click Acknowledge All. To delete all of the alarms from the history log, click on Delete All. To delete selected alarms from the history log, click on Delete. To display a submap showing the device that generated an alarm, select the alarm in the list, then click GoTo. If possible, the device is shown in the middle of the Map window. If there are multiple instances of the device in the map, a dialog box is displayed to allow you to select the desired submap. If the multiple instances are on different submaps a dialog box is displayed asking you which submap you wish to use to view the device. If the device does not exist in the map, an error message is displayed. The GoTo button is disabled unless an alarm is selected. If there is additional information about a selected alarm the More Info button is enabled. To display the additional information, click on it to view the additional information in a separate dialog box. To close the Alarm Log window, click Close. The alarm log can hold a large number of alarms and is limited primarily by the amount of disk space available. The number of entries in the log that can be displayed is limited by the amount of RAM memory available. You can configure OpenView to delete acknowledged alarms after a set number of days using Customize Alarms in 6-26 Stock Number: , Rev. A Page: 6-26

129 Monitoring Devices on the Network the Options menu. Normally this is sufficient to maintain a manageable log. If it is necessary to save the alarm data beyond the configured date, you can copy the contents of the alarm database files to archive files. Configuring Alarm Processing You can control the way OpenView processes alarm information. The major configuration groups for alarms are Alarms (general) Alarm Sound Status Propagation Alarm Forwarding To set the alarm options, choose Customize Alarms from the Options menu to display the following dialog box: 6-27 Stock Number: , Rev. A Page: 6-27

130 General Alarm Settings The general alarm settings include Frequency This setting is used to prevent multiple alarms of the same state from the same device. Duplicate alarms are ignored if they occur within the specified time period. The default time is 60 seconds. A duplicate alarm occurring after this time generates a new entry in the alarm log. Delete After This field is used to delete acknowledged alarms from the alarm database after the specified number of days. When OpenView is started and at midnight (if OpenView is running) any acknowledged alarms exceeding this time is deleted from the database. Sort By This field selects whether the alarm log displays alarms in order received (most recent first) or by order of severity, i.e. most critical alarms first. Alarms of the same severity are ordered by time. The color of the Alarm button in the toolbar and the color of an iconized alarm log or submap show the status of the most severe unacknowledged alarm regardless of the Sort By setting. Alarm Sound Settings Alarm Sound The settings control the sounds generated by an alarm. No sound is generated regardless of the setting unless the application managing a particular device requests an audible alarm. The alarm sound settings allow you to control Whether sounds are enabled Whether a sound alarm is generated only once If an alarm is to be repeated, the repeat rate for each status of alarm Note: You must also have an appropriate Sound Driver program installed. Disable Sounds This turns off sound for all alarms, Sound Once plays the appropriate alarm sound when the alarm is generated. The Repeat setting plays reminder sound every x 6-28 Stock Number: , Rev. A Page: 6-28

131 Monitoring Devices on the Network minutes until the alarm is acknowledged. The sound used for the Repeat setting is that for the most severe uncleared alarm at or above the selected status level. For the example shown, a sound is generated whenever an alarm is generated and a sound is generated every minute if there are any unacknowledged Major or Critical alarms. Alarm Sound Configuration OpenView can generate a sound when a device changes status, and a different sound can be generated for each status level. If you have a sound card and drivers installed, you can use the Sound dialog in the Windows Control Panel to associate OpenView alarms with any Windows wave (.wav) file. Otherwise, the system beep is used for all alarm sounds. Alarm Status Propagation The Status Propagation field controls how alarms are passed between submap levels. The Status Propagation setting allows you to select from one of following three status propagation methods: Do not propagate status Propagate status to the next higher submap only Propagate status to all higher submaps If status is not passed up, submap symbols at higher levels remain unchanged when devices under them change status. If status passes up one level, the submap symbols are displayed with the color of the most severe status of all devices on the level below them. If status passes up all levels, submap symbols are displayed with the color of the most severe status of all devices contained on any level below 6-29 Stock Number: , Rev. A Page: 6-29

132 them. When a submap is minimized, its icon is the color of the most severe status contained in the submap and propagates status based on the Status Propagation configuration. Alarm Forwarding Alarms can be forwarded to another console. This is useful in complex networks where there is a hierarchical network management scheme using multiple consoles. A console monitoring a local network can pass status information on devices in its network to a master console. Selected alarms at the local console can be converted to traps and sent to another console. Traps Master Console Alarms Log Map Local Console #1 Local Console #2 Local Console #3 Alarms Alarms Alarms Local Network #1 Local Network #2 Local Network #3 To forward alarms you must configure the following: The address of the console to receive the trap The map objects whose alarms are to be forwarded The types of alarms to be forwarded 6-30 Stock Number: , Rev. A Page: 6-30

133 Monitoring Devices on the Network The alarm forwarding is configured using the Alarm Forwarding box of the Customize Alarms dialog box. 1 Enter the address of the console where the forwarded alarms are to be sent. 2 Select the map objects whose status is to be forwarded. If you do not want alarms for all objects on your map to be forwarded, click on the Select button. This causes a list of map objects to appear. You can then select the desired objects. 3 Select the status levels that are to be forwarded. 4 Click on OK in the main Customize Alarms dialog box. This saves your alarm forwarding information in the ovwin.ini file. In the example shown above, two devices, Lab #21 and Lab #22 forward alarms of Major or Critical status to an OpenView console at address Stock Number: , Rev. A Page: 6-31

134 Running Programs OpenView can run an MS-DOS or Windows program when an alarm is generated. You can select what program is run based on the status of the alarm. Information about the alarm can be passed as command line arguments to the program. You control the program trigger function by making entries in the ovwin.ini file before running OpenView. (Note that if the alarm is generated by an application program, the application program must have enabled programs to be run in response to the alarm. Refer to documentation for the application program responsible for generating the alarm. Program execution is enabled for alarms generated by the polling and trap management features of OpenView.) To run a program for a particular level of alarm, add an entry to the [OVAlarm] section of ovwin.ini as follows: RunCritical=<command line> RunMajor=<command line> RunMinor=<command line> RunWarning=<command line> RunMarginal=<command line> RunNormal=<command line> RunDisabled=<command line> RunUnknown=<command line> RunInformational=<command line> RunUnmanaged=<command line> where <command line> is the program name and parameters. For example: RunCritical=write.exe readme.wri runs MS Write and display the file readme.wri. OpenView provides alarm information in the following command line variables: %a Alarm text %o Object name %i Alarm type ID %p Alarm application ID %m More info field %s Subobject number %n Node number %t Time of alarm %y Object type 6-32 Stock Number: , Rev. A Page: 6-32

135 Monitoring Devices on the Network The command line can include these variables to provide more information about the alarm. For example, if the entry in the ovwin.ini file for RunCritical was RunCritical=prog.exe %t - %o - %a then a critical alarm on Brian's PC at 2:30 on Feb 16 would execute the following: prog.exe Tue Feb 16 14:30: Brian's PC - Power Supply Overheating DDE Commands In addition to running a program with a command line string, the alarm system can also pass information to another Windows application using DDE. Refer to Microsoft Windows documentation for more information on DDE operation. DDE exchanges are indicated using the > character after the = sign in the Run entry in the ovwin.ini file. DDE Run commands use the following format: RunCritical => <program>,<service>,<topic>;<command> When an alarm occurs, OpenView attempts to establish a DDE conversation with the specified service and topic. If the connection to the service cannot be established, the indicated program is run and another attempt made to establish the conversation. Once established, OpenView sends a DDE Execute message of command, and then terminates the conversation. Alarm Database Every alarm is recorded in an alarm database. Each entry contains the date, time, status, device name, and device type of the alarm. The alarm log is saved in Borland Paradox database format. The files are named ovalins.* and are stored in the OpenView directory (\ov). You can copy these files for archival purposes and save alarm history information beyond the deletion date. You can also use a Paradox database application to access the database and create reports or manipulate the archived files Stock Number: , Rev. A Page: 6-33

136 Caution: Do not make changes directly to the ovalins.* files as this can cause improper operation of OpenView. The database uses one record for each alarm with a primary key on time and a secondary key on status. The record structure is as follows: Field Format Description key number Paradox database key, combination of time and object ID. date date Date at which the alarm occurred. hours time Hour at which the alarm occurred. minutes time Minute at which the alarm occurred. seconds time Second at which the alarm occurred. severity number Severity of alarm, Critical=10,..., Unmanaged=1. application ID number Application that generated the alarm. device class number Device class. not used - - open/cleared number Alarm state, Open=0, Cleared=1. device type number Device symbol number. device name 64 characters Name of the map object that generated the alarm. subcomponent number Subcomponent number or -1 if not used. node number Part number of subcomponent or -1 if not used. status number Current status. message 64 characters Alarm text displayed for this alarm. extended description blob text Extended description of a field, activated by the More Info button Stock Number: , Rev. A Page: 6-34

137 7 Managing SNMP Network Devices About This Chapter Read this chapter to find out How to define, select, and display the query results as a table or graph How to manage the SNMP database 7-1 Stock Number: , Rev. A Page: 7-1

138 Stock Number: , Rev. A Page: 7-2

139 Managing SNMP Network Devices 7 Overview SNMP Version 1 network devices store information about themselves in a Management Information Base (MIB). A MIB contains variables that describe the characteristics and current state of a network device. The SNMP Manager can access this information and control network devices that support SNMP. You can manage an SNMP device by querying or setting its MIB variables. The SNMP Manager supports all Internet MIB-II variables and can be extended to support other MIBs. Operations on MIB-II variables, such as egp and transmission, does not return values from devices supporting only MIB-I. Note: In order to manage or query an SNMP device, you must log in as a supervisor or operator. The OpenView SNMP Manager uses information from MIB files provided by network device manufacturers to build its own database. This database tells the SNMP Manager what device variables are available to query. If you are not familiar with MIBs you should read Managing the SNMP Manager Database on page Note: The MIB file for Adaptec CI/O is available on the client in the NLM subdirectory where CI/O is installed. 7-3 Stock Number: , Rev. A Page: 7-3

140 Defining a Query OpenView allows you to generate tables or graphs about information available in a device's MIB database. To define a query, you select a device and then select the variables that you want to query. To define a query, choose Define Query from SNMP Manager in the Control menu. The following dialog box appears: To select a device to query you must supply the network address. If an object is selected on the map, its device name and network address appears in the Device fields. To select a device to query, use one of the following procedures: Select a device from your map before you open the SNMP Manager. 7-4 Stock Number: , Rev. A Page: 7-4

141 Managing SNMP Network Devices Click the Name field or use the list button to view the list of all devices configured in your current map. You can then scroll through the list to select the desired device. (If the list of devices is long, some may not be displayed. You then need to select the device from the map or type in the network address.) Type the first letter of the device name in the name field. The device list from the current map automatically appears and jumps to the first entry starting with that letter. Pressing that letter repeatedly scrolls through the list of all devices starting with that letter. Once the device name is selected, the network address, as configured for the device in your map, appears in the Network Address field. If no address was configured in the map, type the network address into the field. The SNMP Manager uses the network address, not the device name, to perform the actual query. You can also select a device when you only have the network address. You can use this method to access a device that is not part of your current map: Type in the network address in the Network Address field. The network address does not have to be associated with the current map. The device name is blank. Addresses must be in IP format ( ) or IPX format ( ). 7-5 Stock Number: , Rev. A Page: 7-5

142 Selecting Variables to Query The accessible SNMP variables are listed in the Variables box and may come from various MIBs. An extensive set comes with OpenView. Applications installed into OpenView may have added their own MIBs to the list. You may also use the MIB compiler to add MIBs. The variables are displayed in a tree fashion with the MIB-II level displayed as a default. The following map helps you navigate through the tree. Additional information about the map and compiling MIBs can be found in the MIB Maps section of this chapter. iso org dod internet directory mgmt experimental private mib-2 enterprises system interfaces... Default level displayed 7-6 Stock Number: , Rev. A Page: 7-6

143 Managing SNMP Network Devices Moving Around the Variable Tree To move around the variable tree, follow these steps: 1 Select the group variable you want to query. For example, select [system]. 2 To move up the tree, click Up (this would move you to mib-2). 3 To move down the tree, click Down (or double-click the variable name). Entries in the variables list are displayed using the following format: Format [square brackets] {curly braces} double quotes Description denote a group that contains additional variables denote SNMP tables denote textual values If you select a group variable to query, all variables in that group are part of that query. Queries can be for a single table variable (for example, {attable}) several values from a given table, or one or more nontable variables (ipinreceives). If an SNMP table variable is selected, no other variable may be selected. Individual values (columns) may be selected for an SNMP table by clicking on the Down button to move down the tree below the table and entry definitions to the individual column variables. You may select multiple column table variables and then click Add to add these to the query. In this case, any previously selected variables are removed from the selection list, as only columns within a single table may be queried. 7-7 Stock Number: , Rev. A Page: 7-7

144 Selecting a Variable to Use in the Query To select a variable to use in the query, follow these steps: 1 In the Available Variables box, click on a single variable you want, or Ctrl-click to highlight more than one variable. 2 Click Add. The variable name moves into the Selected Variables box. Removing a Variable From the Query List To remove a variable from the query list, follow these steps: 1 In the Selected Variables box, highlight the variable you want to remove. 2 Click Remove. It disappears from the Selected Variables box. Variable Descriptions When you highlight a variable, the corresponding description is displayed in the Description box. For example, the description for ifspeed ([interfaces,], {if Table},[ifEntry]) would be as shown. The Description box displays information about the variable highlighted in the Available or Selected Variables boxes. This information uses the standard format for SNMP object identifiers (OID 1.2.3) and an associated description. 7-8 Stock Number: , Rev. A Page: 7-8

145 Saving a Query Managing SNMP Network Devices You can save a query so that you can query a selected device in the future or use it as a template for creating other queries. To save a query, follow these steps: 1 Make sure all of the information you want to save has been entered into the Define Query window. You should perform the query to make sure it generates the expected report. 2 Click Save. The following window is displayed. 3 In the Name field, type in a filename of up to 8 characters. Do not enter a file extension OpenView appends the.ovq file extension when the file is saved. 4 If you want, you may use the Description field to describe the saved query. This is especially helpful where the query has a specific use in your environment or where the query is to be used by others. 7-9 Stock Number: , Rev. A Page: 7-9

146 5 Make your choice in the check box. If this box is checked, the next time you start OpenView, the query is listed in the menu under the SNMP Manager command. Up to nine queries are displayed in this menu. There is no limit to the number of queries that can be saved only how many can be displayed in the menu. If you save ten or more queries, the list only displays the last nine. 6 Click OK. To perform, edit, or delete saved queries, choose Select Query from SNMP Manager in the Control menu. The queries are stored as separate files with the.ovq extension in the OpenView directory Stock Number: , Rev. A Page: 7-10

147 Selecting a Query Managing SNMP Network Devices Selecting a query allows you to perform, edit, or delete the query. To select a query, follow these steps: 1 Choose Select Query from SNMP Manager in the Control menu. The following dialog box appears. 2 Highlight a saved query from the list in the Query box. A description of the query appears in the Description box. 3 If you want, change the device name and address in the Device box. 4 Click the appropriate button listed below for the action you want: Button Perform Edit Delete New Description Executes the Query. Opens the Define Query window and inserts the query selected in Select Query. Modifications can be made and saved under the same or a new name. Deletes the query file and all references to the query. Opens a blank Define Query window Stock Number: , Rev. A Page: 7-11

148 Removing a Query from the Menu Since there is a limit of nine queries that are listed in the menu, you may want to remove a query from the menu commands. Note: Removing the query from the menu does not delete the query. To delete the query, select the query, click Delete in the Select Query dialog box. See Selecting a Query on page 7-11 for information. To remove a query from the menu, follow these steps: 1 In the Select Query dialog box, select a query in the Query box. 2 Click Edit. The Define Query window is displayed. 3 Click Save. The Save Query window is displayed. 4 Deselect Display in menu next session to remove the x by clicking on the check box Stock Number: , Rev. A Page: 7-12

149 Managing SNMP Network Devices 5 Click OK. 6 Close the Define Query window. The menu change takes effect when you restart OpenView. (Exit OpenView and restart.) Displaying SNMP Query Results After you select the devices and variables you want to query, you can display the query results as a table or a graph. This section describes how to display query results as a table or graph. To choose the Table or Graph Display option, select Define Query from SNMP Manager in the Control menu. Displaying a Query as a Table Table queries can be for a single table variable (a table variable is displayed in {curly braces} in the variable list), for one or more nontable variables. The format of the table generated varies, as follows: If the query contains an SNMP table, the variable names are displayed across the top of the table. There are numbered rows below the heading. You can scroll through the rows, but cannot add or delete rows. If the query does not contain an SNMP table, the values are listed in scalar format. Any group that you request in the query is expanded to list individual variables. Values within a table may appear as strings, integers, network addresses, or object names displayed in notation. Other data, such as a MAC address, appears in hexadecimal format (for example: 01 F3 07) Stock Number: , Rev. A Page: 7-13

150 Note: OpenView supports a maximum of 999 rows in each table. If your computer does not have enough memory, the table may not be able to reach this limit. To minimize network traffic and memory requirements, select only the columns that you want to display. For information about how to select specific columns, see the example under Performing a Query. After selecting to display your query results as a table, click Options in the Display section of the Define Query dialog or Table dialog box. Then set the polling interval and enter the Community and Set Community names. Command Polling Description Polling sets the number of seconds between updates when a query is performed. For example, if polling is set to 5, once the query is performed, the data is updated every 5 seconds. Polling can be set from 0 to 6000 seconds. Community Set Community A zero (0) means polling takes place only once when the Perform or Start button is pressed. Community is the name used by an SNMP device to restrict access to MIB variables. Entering a valid community name gives you read-only access to MIB variables. Set Community is the name used by an SNMP device to restrict access to device MIB variables. Entering a valid Set Community name gives you read and write access to device MIB variables Stock Number: , Rev. A Page: 7-14

151 Managing SNMP Network Devices Note: To permanently set community values, choose Customize Device Access from the Options menu. Performing a Query After you enter the appropriate information for the device, variable, and options, click Perform to execute the query. If a polling value other than zero was set, the table or graph is updated periodically. Example 1: Displaying an SNMP Table Variable The following screen shows a sample query with results to be displayed as a table. The {iftable} variable is selected. Since the selected variable is an SNMP table, it is the only variable selected. When you select the {iftable} variable, you have two options: You can display the {iftable} variable with a column for every variable in the table. You can display a subset of the {iftable} variables. To do this, click {iftable} in the Available box and then click the Down button. [ifentry] appears, click the Down button again. A list of column names appears. To get a description, click a column name. To add one or more column names to the Selected box, click one column name or Ctrl-click to select multiple column names, and then click Add. When you perform a query, only the selected columns appear in the table. For this example, polling was set to zero so that the polling only occurs once. If polling were set to 10 seconds, the values in the table 7-15 Stock Number: , Rev. A Page: 7-15

152 would be updated from the device every 10 seconds while this window is displayed on the screen. Performing this query results in the following table: 7-16 Stock Number: , Rev. A Page: 7-16

153 Managing SNMP Network Devices Button Start Set Copy Log Options Description Polls the device. The button changes to STOP until the poll is completed or until pressed again (which cancels the polling). If the polling time is set to anything other than zero, the polling continues until the STOP button is pressed. Allows a variable's value to be changed if the device permits the value to be changed. Copies selected cells from the table to the clipboard in tab delimited format. You can paste this information into other applications, such as word processors, spreadsheets, and databases. The variable names corresponding to the selected cells are also included on the clipboard. Allows the current data to be saved to a named file in comma delimited format, replacing the contents of an existing file. Each time you log new data obtained by polling, the log file is appended. The log file includes the name and address of the logged device followed by a blank line, the names of the variables logged, and a time stamp. Allows you to set the polling rate and community. Example 2: Displaying Non SNMP Table Variables The following screen also shows a sample query with results to be displayed as a table. The variables selected do not include an SNMP table, so multiple variables can be selected Stock Number: , Rev. A Page: 7-17

154 Multivariable results displayed in table form: Displaying a Query as a Graph If single value variables are selected, you can view your query results as a graph. After selecting to display your query results as a graph, you can select several options with the Options button in the Display box Stock Number: , Rev. A Page: 7-18

155 Managing SNMP Network Devices Command Polling Samples Community Graph Type Graph Style Grid Legend Print Color Description Polling sets the number of seconds between updates when a query is performed. For example, if polling is set to 5, once the query is performed, the data is updated every 5 seconds. Polling can be set from 0 to 6000 seconds. A zero (0) means polling takes place only once when the Perform or Start button is pressed. A nonzero value plots the variables against time. You may set a sample size when displaying the query as a graph and polling is set to one or greater. For example, if the sample size is set to 10 (the default), the graph displays the last ten sample points one sample point for each poll. Community is the name used by an SNMP device to restrict access to MIB variables. It is often used as a password and is obtained from your network manager. Select from several different graph types. Select from a variety of presentation styles based on the Graph Type selected. You can add a grid to the graph. No grid is the default. You can add a legend to the graph. Having a legend is the default. If you have a color printer, you can print the graph in color. No color is the default (output is shades of gray). NOTE: The Print option is available after the Perform button is pressed Stock Number: , Rev. A Page: 7-19

156 Performing the Query As with a table, enter the information into the Define Query window, then click Perform to execute the query. In this case, a graph is displayed on the screen. If you set a polling value other than zero, the graph is updated periodically. Function Start Print Copy Log Description Polls the device. The button changes to STOP until the poll is completed or until pressed again (which cancels the polling). If the polling time is set to anything other than zero, the polling continues at its designated interval until the STOP button is pressed. Prints the graph. If you have a color printer, select Print Color from the Options button. Copies the entire graph as a bitmap to the clipboard. You can paste it into drawing programs or word processors. Allows the current data saved to a named file in comma delimited format, replacing the contents of an existing file. Each time you log new data obtained by polling, the log file is appended. The log file includes the name and address of the logged device followed by a blank line, the names of the variables logged, and a time stamp. Example 3: Displaying a Query as a Graph Display variable (ipindelivers). By selecting the Options button in the Display box, a polling rate and a sample size can be set. In this example, we set polling to 10 seconds and the sample size to Stock Number: , Rev. A Page: 7-20

157 Managing SNMP Network Devices The type of graph is set to 3D Bar Chart Click Perform to generate the graph. The x axis is time, since the polling is set to 10 (1 or greater). If you set the polling to zero, the x axis would list the variables selected in the Define Query window. The y axis gives the values of the variables. If you wait a minute before you STOP the polling, you can see how polling and sample size work. Because polling was set to 10 seconds, every ten seconds after the Perform button was pressed, the device was polled. The sample size was set to 5, so the last five samples are displayed Stock Number: , Rev. A Page: 7-21

158 Changing a Variable's Value You can change Read/Write variables when they are displayed as a table. To change a variable s value, follow these steps: 1 Select the value you want to modify from the Variable column. The value appears in the Edit field above the table. If the value cannot be set, the status line displays the message: Read-only variable. 2 Make the change you want to the value in the Edit field. To cancel the changes, press the Cancel button. 3 Press the Update button. The changed value is displayed in the table. The value changed is displayed in red. The change has not yet been made to the device. 4 Repeat steps 1 through 3 for each value you wish to modify. 5 To update the device with the changes, press the Set button. If you click the Start button before the Set button, all changes to the table values are canceled without changing the device's values. Any table values that were modified are updated from the device (by polling) Stock Number: , Rev. A Page: 7-22

159 Managing SNMP Network Devices Managing the SNMP Manager Database The Manage Database command is accessed from the SNMP Manager in the OpenView Control menu. Manage Database accesses a compiler that adds MIBs to the Manager s database. MIBs can contain additional information which change the list of variables displayed in the Define Query window. To use the compiler to modify the existing OpenView MIB database, an asn.1 definition file is required. The definition files normally have the file extension.mib. After the definition file has been compiled into the OpenView database, the new variables appears in the variable list in the Define Query window. The Manage Database window consists of several parts: The Status line The Add Files buttons and list The Messages field Status Add Files Messages 7-23 Stock Number: , Rev. A Page: 7-23