OWLView for HP OpenView for UNIX USER’S...

OWLView for HP OpenView for UNIX

USER’S GUIDE" " " " " " " " " " " " " " " " " " " " " " " " " " " "

P/N: 961-051-011Revision A

January 1998

" NOTICE The information contained herein is proprietary and is provided solely for thepurpose of allowing customers to operate and service Intermec manufacturedequipment and is not to be released, reproduced, or used for any other purposewithout written permission of Intermec.

Disclaimer of Warranties. The sample source code included in this document ispresented for reference only. The code does not necessarily represent complete,tested programs. The code is provided “AS IS WITH ALL FAULTS.” ALLWARRANTIES ARE EXPRESSLY DISCLAIMED, INCLUDING THEIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE.

We welcome your comments concerning this publication. Although every effort hasbeen made to keep it free of errors, some may occur. When reporting a specificproblem, please describe it briefly and include the book title and part number, aswell as the paragraph or figure number and the page number.

Send your comments to:Intermec Technologies CorporationPublications Department550 Second Street SECedar Rapids, IA 52401

ANTARES, INTERMEC, NORAND, NOR*WARE, PEN*KEY, ROUTEPOWER,TRAKKER, and TRAKKER ANTARES are registered trademarks andENTERPRISE WIRELESS LAN, INCA, Mobile Framework, MobileLAN, TE 2000,UAP, and UNIVERSAL ACCESS POINT are trademarks of Intermec TechnologiesCorporation.

1998 Intermec Technologies Corporation. All rights reserved.

Acknowledgments

Portions of this product contain software which is licensed from and is copyright byEpilogue Technology Corporation, 1988–1995, all rights reserved.

ActiveX, Microsoft, MS, and MS-DOS, Windows, and Windows NT are registeredtrademarks and MSDN, Visual Basic, Visual C++, and Windows for Pen aretrademarks of Microsoft Corporation.

AS/400, IBM, IBM PC, Micro Channel, PS/2, and OS/2 are registered trademarksand AIX and Presentation Manager are trademarks of International BusinessMachines Corporation.

DEC, Digital, VAX, VMS, VT, VT131, VT220, VT330, VT340, and VT52 areregistered trademarks of Digital Equipment Corporation.

Hewlett-Packard, HP, and DeskJet are registered trademarks and HP OpenViewand HP UX are trademarks of Hewlett-Packard Company

Intel is a registered trademark of Intel Corporation.

Novell and UNIX are registered trademarks of Novell Inc.

XEROX is a registered trademark of Xerox Corporation.

This software and documentation are based in part on HP OpenView under licensefrom the Hewlett-Packard Company.

OWLView for HP OpenView for UNIX User’s Guide i

CONTENTS

" " " " " " " " " " " " " " " " " " " " " " " " " " " "

OWLView Quick Start

Installation and Set Up 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Running OpenView with OWLView 1. . . . . . . . . . . . . . . . . . .Quick Tips 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HP OpenView Maps 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .NORAND OWLView Maps 2. . . . . . . . . . . . . . . . . . . . . . . .

Loading/Unloading NORAND MIB into HP OpenView 2. .

SECTION 1

Introduction and Setup

Overview 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .System Requirements 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Hardware 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Software 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Product Contents 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .About this Product 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Installation and Set Up 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Running HP OpenView with OWLView 1-5. . . . . . . . . . . . . . . .Loading and Unloading NORAND MIB

into HP OpenView 1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Uninstalling OWLView 1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CONTENTS

ii OWLView for HP OpenView for UNIX User’s Guide

SECTION 2

Product Overview

Discovery, Autodiscovery, andOpen Wireless LAN Map Creation 2-1. . . . . . . . . . . . . . . . .

Terminal Map 2-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Device Information 2-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Register and DeRegister for Traps 2-12. . . . . . . . . . . . . . . . . . . . .Multiple Device Set 2-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .OWLMIBs 2-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 3

Using OWLView

Configure OWL Discovery 3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . .Configure Map Layout 3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Set Community Name 3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Discover OWL Network 3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating an HP OpenView Network Map 3-6. . . . . . . . . . .Creating an OWLView Map 3-7. . . . . . . . . . . . . . . . . . . . . . .Refresh OWL Map 3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Redraw OWL Map 3-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Root Map 3-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .NORAND OWL Map 3-10. . . . . . . . . . . . . . . . . . . . . . . . . .OWL LAN Map 3-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Device Status 3-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating Terminal Maps 3-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . .Device Information 3-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Closeup 3-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .For an Access Point 3-16. . . . . . . . . . . . . . . . . . . . . . . . . . .For a Gateway 3-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration 3-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Software 3-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Bridge 3-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Physical Port 3-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CONTENTS

OWLView for HP OpenView for UNIX User’s Guide iii

Traps 3-27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Register 3-27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Selection Criteria 3-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . .Active Node 3-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Error Alarms 3-29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Deregister 3-29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Selection Criteria 3-30. . . . . . . . . . . . . . . . . . . . . . . . . . . . .Active Node 3-30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Error Alarms 3-30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Filtering Level 3-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Multiple Device Set 3-32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Selection Criteria 3-33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Query Selection 3-33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Active Node 3-34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Error Alarms 3-34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Defining Multiple Device Set Queries 3-34. . . . . . . . . . . . . .

OWLMIBs 3-36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Function OIDs 3-37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6710 Access Point 3-39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6910 Integrated Gateway/Access Point 3-40. . . . . . . . . . . . .4030 Gateway 3-41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6950 Terminal Server 3-42. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CONTENTS

iv OWLView for HP OpenView for UNIX User’s Guide

OVER

OWLView Quick Start

Installation and Set UpBefore Installing OWLView: OWLView runs under HP OpenView Network Node Manager (NNM). Priorto installing OWLView, HP OpenView NNM must be installed and started with the NNM command ovstart.See the HP OpenView Network Node Manager Products Installation Guide for HP OpenView NNMinstallation instructions and see the HP OpenView Using Network Node Manager for HP OpenView NNMstartup and product usage instructions.

1. Extract OWLView file from CD:

a. Create a directory on the HP UX system for OWLView:" Format: mkdir <owlview path>

" Example: mkdir /usr/owlview

b. Copy the owlviewu.tar file from the CD into the owlview directory." Format: cp owlviewu.tar /usr/owlview

" Examples: cp owlviewu.tar /usr/owlviewcp owlviewu.tar\;1 /usr/owlview

2. Install OWLView: Run <owlview path>/util_HPUX_10/install

" Format: <owlview path>/util_HPUX_10/install <owlview path>

" Example: /usr/owlview/util_HPUX_10/install /usr/owlview

3. Optional: Install OWL symbols into HP OpenView: To see NORAND devices on the HP OpenView’s IP Map,cut and paste the lines in <owlview path>/config/oid_to_sym.owl into HP OpenView’s oid_to_symfile, which is in /etc/opt/OV/share/conf/C.

Once you have copied the oid_to_sym.owl entries into NNM’s oid_to_sym file, run ovtopofix -u.This merges the new symbols into existing maps.

Running OpenView with OWLViewOnce OWLView is installed, it starts along with HP OpenView NNM when NNM is started by the ovw com-mand. For information about starting NNM, see the HP OpenView Using Network Node Manager guide.

Quick Tips

HP OpenView MapsHP OpenView NNM automatically discovers the network and paints and synchronizes an IP map upon start-up. For information about creating maps using NNM, see the HP OpenView Using Network Node Managerguide. Wait for this operation to complete before generating OWLView maps.

HP OpenView might not find all of the NORAND devices during its discovery process. HP OpenView uses thecontents of the routers’ ARP caches to find devices. To ensure that HP OpenView finds all of the NORANDdevices, run the “ping-lan” utility in the OWLView bin directory.

" Format: <owlview-path>/bin/ping-lan subnet-prefix

" Example: /usr/owlview/bin/ping-lan 172.10.7

The above command sends out PINGs to devices 172.10.7.1 -- 172.10.7.255.

NORAND OWLView MapsNORAND OWLView draws an OWL map based on information gathered through HP OpenView discovery andthe information gathered through OWLView Refresh, Redraw, or OWLView autodiscovery. Once HP Open-View has completed its map synchronization, the OWLView map can be drawn.

" To draw the OWLView LAN map, access the HP OpenView menu and select:OWLView → Discovery OWLNetwork → Refresh OWLMap

" To draw a Terminal map, double-click an Access Point or Gateway node on an OWLView LAN map.

" To get device information, click an Access Point or Gateway node, then access the HP OpenView menuand select:OWLView → Device Information

Loading/Unloading NORAND MIB into HP OpenViewThe OWLView installation procedure automatically loads the NORAND OWL MIB (norowl.mib). Thefollowing explains how to load and unload NORAND MIBs, should the need arise:

1. Access the HP OpenView menu and select: Options → Load/Unload MIBs: SNMP

2. Select Load... to load a MIB; or select Unload... to unload a MIB.

3. Enter the path and MIB file name:

" OWL Access Point and Gateway MIB: <owlview path>/mibs/norowl.mib

" OWL Access Point only MIB: <owlview path>/mibs/owlap.mib

" OWL Gateway only MIB: <owlview path>/mibs/owlgw.mib

" Standard Ethernet MIB: <owlview path>/mibs/rfc1398.mib

OWLView for HP OpenView for UNIX User’s Guide 1-1

Section 1

Introduction and Setup

" " " " " " " " " " " " " " " " " " " " " " " " " " " "

OverviewThe NORANDR OWLView is a powerful management ap-plication for the HP OpenView, in managing the NORANDOpen Wireless LANs.

OWLView provides a view of the NORAND Open WirelessLANs showing the wired and wireless components andconnections of the NORAND LAN devices. OWLView alsoprovides a view of the mobile wireless hand-held computersand client devices communicating through the NORANDOpen Wireless LAN. OWLView displays and periodicallyupdates the maps with the status of NORAND devices andconnections. OWLView provides customized trap handlingfor all traps originating from NORAND devices.

OWLView provides a Graphical User Interface (GUI) config-uration display with point-and-click access to device andport level configuration. In addition, this application pro-vides a tool to configure multiple devices simultaneously,thus simplifying and shortening device configuration.

OWLView is available for Network Node Manager (NNM)for UNIX and HP OpenView for Windows.

Plugging in the Chips SECTION 1

1-2 OWLView for HP OpenView for UNIX User’s Guide

The OWLView application features the following:

" Custom maps of Open Wireless LANs showing wiredand wireless communication links.

" Displays of terminal nodes connected to NORANDOpen Wireless LAN devices.

" GUI device configuration display." Customized trap handling for NORAND devices.

" Multiple device set capability, which allows users toperform sets on multiple devices with one click.

SECTION 1 Introduction and Setup


System RequirementsHardware and software requirements are as follows:

Hardware" HP9000 Series 700 or 800" 10 Mbytes free disk space

Software" HP UX Version 10.2" HP OpenView Network Node Manager Version 4.11 or

5.01

Product ContentsWhen purchasing the OWLView for HP OpenView for UNIXfrom Intermec Technologies Corporation, the followingitems should be included:

" OWLView application and NORAND Open WirelessLAN MIBs (1 4mm DAT tape)

" OWLView for HP OpenView for UNIX User ’s Guide(P/N: 961-051-011)

"NOTE: HP OpenView for UNIX (Network Node Manager) is purchased fromHewlett-Packard. Contact your HP sales representative for productsales information.

About this ProductNORAND OWLView loads into the HP OpenView applica-tion at installation. HP OpenView must be installed beforeinstalling OWLView.

Introduction and Setup SECTION 1


Installation and Set UpBefore Installing OWLView: OWLView runs under HPOpenView Network Node Manager (NNM). Prior to instal-ling OWLView, HP OpenView NNM must be installed andstarted with the NNM command ovstart. See the HPOpenView Network Node Manager Products InstallationGuide for HP OpenView NNM installation instructions andsee HP OpenView Using Network Node Manager for HPOpenView NNM startup and product usage instructions.

1. Extract OWLView file from CD:a. Create a directory on the HP UX system for

OWLView:" Format: mkdir <owlview path>

" Example: mkdir /usr/owlview

b. Copy the owlviewu.tar file from the CD into theowlview directory.

" Format: cp owlviewu.tar <owlview path>

" Examples: cp owlviewu.tar /usr/owlview

cp owlviewu.tar\;1 /usr/owlview

2. Install OWLView:Run <owlview path>/util_HPUX_10/install

" Format:<owlview path>/util_HPUX_10/install <owlview path>

" Example:/usr/owlview/util_HPUX_10/install /usr/owlview

3. (Optional) Install OWL symbols into HP OpenView:To see NORAND devices on HP OpenView’s IP Map,cut and paste the lines in <owlview

path>/config/oid_to_sym.owl into HP OpenView’soid_to_sym file, which is in /etc/opt/OV/share/conf/C.

Once you have copied the oid_to_sym.owl entries into NNM’soid_to_sym file, run ovtopofix -u. This merges the newsymbols into existing maps.

SECTION 1 Introduction and Setup


Running HP OpenView with OWLViewOnce OWLView is installed, it starts along withHP OpenView NNM when NNM is started by the ovw com-mand. See the HP OpenView Using Network Node Managerguide for information on starting NNM.

HP OpenView might not find all of the NORAND devicesduring its discovery process. HP OpenView uses the con-tents of the routers’ ARP caches to find devices. To ensurethat HP OpenView finds all of the NORAND devices, runthe “ping-lan” utility in the OWLView bin directory.



The above command sends out PINGs to devices 172.10.7.1-- 172.10.7.255.

Loading and Unloading NORAND MIBinto HP OpenView

The OWLView installation procedure automatically loadsthe NORAND OWL MIB (norowl.mib). The followingexplains how to load and unload NORAND MIBs, shouldthe need arise:

1. Access the HP OpenView menu and select:Options → Load/Unload MIBs: SNMP

2. Select Load... to load a MIB; or select Unload... tounload a MIB.

Introduction and Setup SECTION 1


3. Enter the path and MIB file name:" OWL Access Point and Gateway MIB:

<owlview path>/mibs/norowl.mib

" OWL Access Point only MIB:<owlview path>/mibs/owlap.mib

" OWL Gateway only MIB:<owlview path>/mibs/owlgw.mib

" Standard Ethernet MIB:<owlview path>/mibs/rfc1398.mib

Uninstalling OWLView1. Remove the NORAND OWL Submap from the HP

OpenView Map.a. Access the HP OpenView menu and select:

Map → Submap → Open/List...b. Select Norand OWL from the list of submaps.c. Click Delete.

2. Run <owlview path>/util_HPUX_10/uninstall ." Format:

<owlview path>/util_HPUX_10/uninstall <owlview path>

" Example:/usr/owlview/util_HPUX_10/uninstall /usr/owlview

3. Remove OWL symbols from OpenView oid_to_symfile. If you did installation step #3, remove thefollowing OWL oid_to_sym.owl entries from HPOpenView’s oid_to_sym file, which is in/etc/opt/OV/share/conf/C.


Section 2

Product Overview

" " " " " " " " " " " " " " " " " " " " " " " " " " " "

OWLView provides five major functions:

" Discovery and Autodiscovery and Open Wireless LANMap Creation

" Terminal Map" Device Information" Trap Handling" Multiple Device Set

Discovery, Autodiscovery, and OpenWireless LAN Map Creation

OWLView discovery presents a view of the NORANDR

Wireless Local Area Network (LAN) components separatefrom other network devices. OWLView uses the discoverydatabase of HP OpenView and the information that HPOpenView gathers from NORAND devices on the networkto display a logical topology display of the Open WirelessLAN. OWLView discovery creates an OWL LAN icon onthe HP OpenView top level Root map. Double-click theOpen Wireless LAN icon to reveal the Open Wireless LANs(identified by OWL LAN ID) on the network.Double-clicking an OWL LAN icon reveals the OpenWireless LAN Access Point topology map which displays the

Product Overview SECTION 2


wired and wireless links between the Access Points on theNORAND Open Wireless LAN.

OWLView Discovery provides three basic functions:

" Autodiscovery: Automatically gathers OWL LANdevice information on regular intervals. Draws OWLLAN maps if they do not exist. Updates existing OWLLAN map topologies.

" Refresh Map: Gathers OWL LAN device informa-tion. Draws the OWL LAN maps if they do not exist.Updates existing OWL LAN topologies.

" Redraw Map: Gathers OWL LAN device informa-tion. Deletes and redraws existing OWL LAN maps.

"NOTE: Wait for HP OpenView to complete its discovery and map synchro-nization before performing an OWL Refresh or Redraw to ensurethat all NORAND devices are found by HP OpenView.

SECTION 2 Product Overview


Following are several sample map diagrams:

" Root: Has OWL icon for the NORAND Open WirelessLAN.



" NORAND OWL: Includes the OWL LAN icons.



" OWL LAN ID: Shows a LAN with both wired andwireless hops.



Terminal MapThe OWLView Terminal Map provides a display of the ter-minal devices connected to a NORAND LAN device. A ter-minal device is a hand-held computer (or terminal), PC, orworkstation communicating through the NORAND OpenWireless LAN. Terminals are represented by a terminalicon. PCs and workstations are represented by a desktopcomputer icon.

Double-click a NORAND Access Point icon to generate anOWLView terminal map that displays terminal devicesdirectly connected to that Access Point. Double-click aNORAND Gateway icon to generate an OWLView terminalmap that displays the NORAND terminal emulationcomputers having host sessions through that Gateway.



Device InformationOWLView provides point-and-click device configuration in-formation. Device configuration is available by selecting aNORAND Access Point or Gateway on the HP OpenView orOWLView map. The following configuration information isavailable:

" CloseUp: A Graphical User Interface (GUI) displayof the device back panel and LED display. Double-clicking hot spots reveal communication port configu-ration information.



" Configuration: Displays device identification in-formation and system up-time.



" Software: Displays the software files resident on thedevice.



" Bridge (Access Point): Displays device bridge confi-guration.



" Physical Port (Access Point): Displays Ethernet andradio port configurations.



Register and DeRegister for TrapsOWLView provides customized trap handling for NORANDdevices. NORAND Access Points and Gateways have a res-ident Simple Network Management Protocol (SNMP) agent.These devices can be configured to send standard SNMPtraps and specific NORAND traps to SNMP managementstations (such as HP OpenView). OWLView provides func-tions that simplify NORAND trap configuration and pro-vides enhanced filtering for specific traps from Norand.OWLView provides the following trap functions:

" Register: Register with the selected NORAND de-vices to receive traps. This configures the NORANDdevices to send traps to this management station.

" Deregister: Deregister to receive traps from theselected NORAND devices. This configures theNORAND devices not to send traps to thismanagement station.



" Filtering Level: Sets a filtering level for traps re-ceived from NORAND devices. This provides a meth-od to control the severity level of traps viewed throughfiltering specified trap severity levels.



Multiple Device SetOWLView Multiple Device Set simplifies deviceconfiguration by performing SNMP SET operations onmultiple devices with one command. SET operations arepredefined into Queries stored in an owlquery.ini file.These queries are accessed through the OWLView MultipleDevice Set window and executed on selected NORANDdevices.



OWLMIBsOWLView OWLMIBs is a customized MIB browser thatprovides quick access to Open Wireless LAN MIB informa-tion and organizes these MIBs by device type. When thedevice type is selected through OWLMIBs, the Open Wire-less LAN MIB items supported by that device are displayed,those not supported are not displayed.

Open Wireless LAN MIB items are categorized by manage-ment information areas such as system, bridge, or port.This allows for browsing MIB information by functionalcategory.


Section 3

Using OWLView

" " " " " " " " " " " " " " " " " " " " " " " " " " " "

The NORANDR OWLView Management Application isintegrated into the HP OpenView platform. Click theOWLView option from the HP OpenView title bar. Adrop-down menu appears:

OWLView has eight menu options:

" Configure OWL Discovery " Device Information" Configure Map Layout " Traps

" Set Community Name " Multiple Device Set" Discover OWL Network " OWLMIBs

Using OWLView SECTION 3


Configure OWL DiscoveryClick the Configure OWL Discovery option to set theOWLView autodiscovery schedule. The Configure OWLDiscovery window appears:

Enter the time interval in minutes. OWLView performs anOpen Wireless Local Area Network (LAN) discovery andmap refresh every n minutes after the last Open WirelessLAN discovery, Refresh Open Wireless LAN Map, orRedraw Open Wireless LAN Map. Open Wireless LANdiscovery is in addition to the HP OpenView discovery.OWLView discovery uses data gathered by the HPOpenView discovery, thus, you must wait for HP OpenViewto complete its discovery and map synchronization beforedoing the OWLView discovery (Autodiscovery, Refresh,Redraw).

Enter zero to disable the OWLView autodiscovery. Enterfrom 1 through to 999 minutes, for how frequently anOWLView autodiscovery is to be done. The default is 30minutes.

Click the OK button to save, or click the Cancel button toexit this window without changes.

SECTION 3 Using OWLView


Configure Map LayoutClick the Configure Map Layout option to define the la-bels that appear under icons in the Open Wireless LAN andterminal maps. The Configure Map Layout window ap-pears:

" Fixed End Map: Select a label option for the fixedend map. A label of the selected type appears undereach NORAND device icon in the fixed end map. Thedefault label for the fixed end map is the IP Address.If the selected label information is not available,OWLView displays the default label IP Address un-der the NORAND device icon.



" Terminal Map: Select a label option for the Terminalmap. A label of the selected type appears under eachterminal device icon in the Terminal map. The defaultlabel for the Terminal map is the MAC Address. If theselected label information is not available, OWLViewdisplays the default label MAC Address under theTerminal device icon.




Set Community NameClick the Set Community Name option for the Set Com-munity Name window:

Set Community Name allows for read and write access tothe NORAND Access Point and Gateway deviceManagement Information Base (MIB) objects.

CR52401 is the default, which allows OWLView SET opera-tions to be successful for current NORAND Access Pointsand Gateways.

A Set Community Name of public allows read-only accessto NORAND device MIB objects. If used, SET operationsresult in an Authentication Failure error.




Discover OWL NetworkA goal of network management is to track the status of thenetwork and to identify problems. To effectively track thestatus of a network, a network must first be drawn with allknown network devices. Once the complete “baseline” mapis drawn, periodic checks can determine if devices are up,down, or new to the network. The best practice is to createa baseline map of what the network is to look like when ev-ery node is up, save the map, and then use this map in theday-to-day tracking of network status.

HP OpenView and OWLView provide tools to create andsave network maps and to discover and track the status ofyour network. HP OpenView provides the tools to createnetwork maps. OWLView provides tools to create aseparate Open Wireless LAN map, showing all devicescommunicating through the Open Wireless LAN. An HPOpenView network map must be created and synchronizedbefore the OWLView map is created.

Creating an HP OpenView NetworkMapHP OpenView Network Node Manager automatically dis-covers the network at start up. When HP OpenView isstarted, the default map is automatically synchronized anddrawn. See the HP OpenView Using Network Node Manag-er section for more information on the HP OpenView discov-ery and maps.



HP OpenView might not find all of the NORAND devicesduring its discovery process. HP OpenView uses the con-tents of the routers’ ARP caches to find devices. To ensurethat HP OpenView finds all of the NORAND devices, runthe “ping-lan” utility in the OWLView bin directory.



The above command sends out PINGs to devices 172.10.7.1-- 172.10.7.255.

Creating an OWLView MapOnce the HP OpenView network map is created, theOWLView map can be created using the Discover OWLNetwork functions from the OWLView menu option.

"NOTE: Wait for HP OpenView discovery to complete and synchronizebefore executing the Discover OWL Network functions.

Click the Discover OWL Network option to create theOWL LAN map, update an existing OWL LAN map, or re-draw the OWL LAN map.

Refresh OWL MapClick the Refresh OWL Map option to discover the OpenWireless LAN now. This updates an existing Open WirelessLAN map or draws a new Open Wireless LAN map if themap does not exist.



Redraw OWL MapClick the Redraw OWL Map option to delete any existingOpen Wireless LAN maps and do an Open Wireless LANdiscovery to generate new maps.

The Discovery Status window appears for both Refresh andRedraw functions:

The Discover OWL Network functions create objects onthese levels of maps:

" Root" NORAND OWL" OWL LAN ID



Root MapThe Root map is the top-most map created by HPOpenView. OWLView puts a NORAND OWL icon on thismap. Double-clicking the NORAND OWL icon displays theNORAND OWL map. Following is a sample Root map:



NORAND OWL MapThe NORAND OWL map shows each OWLView-discoveredOWL LAN and NORAND terminal emulation gateway de-vices. An OWL LAN icon with an OWL LAN ID markseach OWL LAN. Double-clicking an OWL LAN displays anOWL LAN ID map. Following is a sample NORAND OWLmap:



OWL LAN MapThe OWL LAN map shows the logical topology of the AccessPoints making up this OWL LAN, denoted by LAN IDs,with the wired and wireless links connecting the AccessPoints to the LAN. An icon with an “R” inscribed denotesthe OWL LAN’s root node. Following is a sample NORANDOWL LAN map:



Device StatusThe Discover OWL Network option also paints the statusof each device in the map. Each NORAND device appearsin a color indicating its status. Status is transmitted up toparent maps for the parent icon to exhibit the highestseverity device status color. The following colors indicatedevice status:

" Green: Up" Bright Red: Down



Creating Terminal MapsThere are two types of terminal maps to be created:

" Access Point Terminal Connections:Double-click on an Access Point icon:

to create a terminal map that displays the terminalsconnected to that selected Access Point:



" Gateway Terminal Sessions:Double-click on a Gateway icon:

to create a terminal map that displays the terminalsessions associated with the selected host Gateway:



The terminal map displays two types of devices:

" Wireless: Any device that is radio-enabled (wireless)appears as a terminal:

" Wired: Any device that is attached to the Ethernet(wired) appears as a PC:

Terminal devices appear in color, indicating status. If sta-tus is not normal (color status is not green), an alarm ap-pears in the alarm log with status and information. Thefollowing are the terminal status colors:

" Green Normal Terminal is connected andactive

" Light Blue Inactive Terminal has been inactive" Light Blue Connection Terminal lost connection;

Loss reconnected at least once



Device InformationDevice information provides point-and-click device configu-ration information. Click an Access Point or Gateway iconto access its device information.

CloseupCloseup provides a GUI display of the device back paneland LED display of any NORAND Access Point or Gateway.Any port in green is a hot spot and can be clicked for a portconfiguration display. Gateway information appears onpage 3-20, after the following Access Point information.

For an Access PointThe following Back Panel and LED Display window dis-plays radio ports and LEDs for an Access Point device:



Each Access Point port appears in one of three status col-ors:

" Up (information available): Green" Down: Red" No Information Available: No color

Selected devices appear with LEDs. If the device is notreached, as when a query returns with no response, LEDsappear with no color (all OFF). Each LED in use for thedevice appears in color.

The LED display matches the LED display on the physicaldevice, except for blinking LEDs on the Access Point. If thedevice is operational and the MODE LED is blinking, this isnot apparent on the OWLView display. Likewise, if theradio port is sending or receiving data, the NICx LEDblinks (also not shown on the OWLView display).

The 6710 Access Point has the following LEDs:

" LINK: Orange Hardware controlled" POLARITY: Green Hardware controlled" STATUS: Orange OFF: No error

ON: Error" MODE: Green OFF: Command

ON: Network" R-LINK: Orange Radio attachment" W-LINK: Green Ethernet attachment

Blink Bridge to secondary LAN" NIC1: Orange OFF: Disabled

ON: Enabled" NIC2: Green OFF: Disabled

ON: Enabled

"NOTE: If R-LINK is on and W-LINK is on (green), the Access Point is a RootNode.



Double-click on any of the green port hot spots to see thePhysical Port information window for that port:

The parameters in the Physical Port window are defined asfollows:

" Port Number: Assigned number for this port (1--4)." Port Type: Ethernet, Proxim24, Falcon, or UHF." Radio Port: True if a radio port; or False if Ethernet." Mac Address: Mac Address of this port." Port State: Active: transmit or receive (port is up);

Disabled: idle (port is down)." Port Hello Period: Time in .01 seconds for network

internet hello time.



" Port is Primary Bridge Port: True or false field,stating if port bridges to primary LAN.

" Port is Secondary Bridge Port: True or false field,stating if port bridges to a secondary LAN.

" Port is Secondary Candidate: True or false field,stating if port has a bridge priority set greater thanzero.

" Port Requires Unicast Flooding: True for second-ary bridge ports that require unicast flooding.

" Port Supports Pending Messages: True if portsupports pending messages.

Click Close to exit the Access Point and Physical Port win-dows.

"NOTE: See the 6710 Access Point User’s Guide (NPN: 961-047-081) fora more detailed explanation of the above details and concepts.



For a GatewayThe following Back Panel and LED Display window dis-plays radio ports and LEDs for a Gateway device:

Selected devices appear with LEDs. If the device is notreached, such as a query comes back with no response,LEDs appear with no color (all OFF). Each LED in use forthe device appears in a color and blink state.

The 4030 Gateway has the following LEDs:

" PWR: Green Power ON" STAT: Not used" NET: Not used" RF: Not used" ETHERNET: Green Ethernet enabled

Click the Close button to exit the Physical Port window.

"NOTE: Currently, no port configuration information is available for the gate-way.



ConfigurationClick the Configuration option to view the device configu-ration for the selected Access Point or Gateway:

The parameters in the System Configuration window aredefined as follows:

" Device Type: Describes this device." Device IP Address: IP Address of this device." Device Name: Name of this device." Device Location: Where this device is located." Device Uptime: How long device is with this Open

Wireless LAN." Hardware Part Number: Part number assigned to

this device." Hardware Description: Describes this device." Hardware Revision: Revision level of the hardware.



" Hardware Serial Number: Serial number assignedto device.

Click the Close button to exit this window.

SoftwareClick the Software option for a directory listing of the soft-ware and software version number loaded on the selecteddevice. The Software Configuration window appears:

The parameters in the Software Configuration window areas follows:

" File Name: Name of this file." File Type: Executable or Data." File Size: File size in bytes." File Date: Day this file was created." File Time: Time this file was created." File Version: Current version of this file.

" File Segment: The ID of the segment containing thisfile.




Bridge"NOTE: Bridge information is available only for Access Points.

Click the Bridge option for bridging and networking config-uration parameters of the 6710 Access Point device:

The parameters in the Bridge/Network Information windoware defined as follows:

" Mac Address: Mac Address of this device." OWL LanID: OWL LAN ID (0--254)." Device is Root: True if the device is a root node." Device attached to OWL LAN: True if the device is

attached to an OWL LAN." Device Root Priority: Root priority assigned to this

device. If zero, this device cannot become the rootnode.

" Unicast Flooding Level: Level of flooding for uni-cast frame.



" Multicast Flooding Level: Level of flooding formulticast frames.

" Bridges to Primary Lan: True if the device bridgesto a primary LAN.

" Bridges to Secondary Lan: True if the devicebridges to a secondary LAN.


Physical Port"NOTE: Physical Port information is available only for Access Points.

Click the Physical Port option to select the configurationparameter for the physical ports of the Access Point device.The Port Selections window appears:



The Port Selections window shows the active ports for theselected device. Select one of the ports and click the OKbutton to view the port configuration information, as shownin this example:

" If Ether is selected, the Physical Port window appearswith a “1” in the Port Number field and “Ether” inthe Port Type field.

" If Falcon is selected, the Physical Port windowappears with a “2” in the Port Number field and“Falcon” in the Port Type field.

The parameters in the Physical Port window are defined asfollows:

" Port Number: Assigned number for this port (1--4)." Port Type: Ethernet, Proxim24, Falcon, or UHF." Radio Port: True if a radio port; or False if Ethernet." Mac Address: Mac Address of this port.



" Port State: Open, transmit or receive (port is up);Disabled, idle (port is down).

" Port Hello Period: Time in .01 seconds for networkinternet hello time.

" Port is Primary Bridge Port: True or false field,stating if port bridges to primary LAN.

" Port is Secondary Bridge Port: True or false field,stating if port bridges to a secondary LAN.

" Port is Secondary Candidate: True or false field,stating if port has a bridge priority set greater thanzero.

" Port Requires Unicast Flooding: True for second-ary bridge ports that require unicast flooding.

" Port Supports Pending Messages: True if portsupports pending messages.

Click the Close button to exit the Physical Port window.Click the Ok button to save, or click the Cancel button toexit the Port Selections window without changes.



TrapsClick the Traps option for Register for traps, Deregisterfor traps, or to set trap Filtering Levels.

The OWLView trap options provide customized traphandling for NORAND devices. NORAND Access Pointsand Gateways have a resident SNMP agent. These devicescan be configured to send standard SNMP traps andspecific NORAND traps to SNMP management stations.The OWLView trap options simplify this configurationprocess through the Register, Deregister, and FilteringLevel options.

RegisterClick the Register option to register this management sta-tion to receive traps from the selected NORAND devices:



Selection CriteriaThere are three options to select nodes for registration:

" Selected Nodes: Click this radio button to registerwith all nodes that are selected on the map. To selectnodes on the map, press and hold the <CTRL> keyand click the left mouse button on all of the devices tobe registered.

" Selection File: Click this radio button to activatethe Selection File. Traps will be registered with alldevices in the selection file. To create a selection file,edit the file:

<owlview path>/config/selection.list

The format of the file is:Line1: IP address of deviceLine2: Symbol Class:Symbol SubClass

Modify the example selection.list file to includethe IP addresses and corresponding SymbolClass:Symbol SubClass for each device on whichperiodic Trap Registration, Trap DeRegistration, orMultiple Device Set operation is to be performed.

" All Nodes: Click this radio button to register with allNORAND Access Points and Gateways in the map.

Click the Execute button to register to receive traps fromselected devices.

Active NodeThis box shows the current device that the Register opera-tion is executing. The percentage box on the right displaysthe amount of registration completed. When all selecteddevices are registered, “Finished” appears in the ActiveNode field.



Error AlarmsIf a node fails to be registered, the system generates analarm and logs the alarm into the HP OpenView event log.The alarm names the device that did not register.

DeregisterThis option deregisters this management station fromreceiving traps from the selected NORAND devices. Clickthe Deregister option to access the De-Register for Trapswindow:



Selection CriteriaThere are three options to select nodes for registration:

" Selected Nodes: Click this radio button to deregisterall nodes that are selected on the map. To select nodeson the map, press and hold the <CTRL> key and clickthe left mouse button on all of the devices to be dere-gistered.

" Selection File: Click this radio button to activatethe Selection Lists. Traps will be registered with alldevices in the selection file. To create a selection file,edit the file:


The format of the file is:Line 1: IP address of deviceLine 2: Symbol:Class:Symbol SubClass


" All Nodes: Click this radio button to deregister allNORAND Access Points and Gateways in the map.

Click the Execute button to deregister selected devices.

Active NodeThis box shows the current device that the Deregister op-eration is executing. The percentage box on the right dis-plays the amount of deregistration completed. When allselected devices are deregistered, “Finished” appears in theActive Node field.

Error AlarmsIf a node fails to be deregistered, the system generates analarm and logs the alarm into the HP OpenView event log.The alarm names the device that failed deregistration.



Filtering LevelClick Filtering Level for the Filter Level window:

Scroll to select a filter level for unacknowledged trap severi-ty. Traps with the selected level of severity level and higherappear in the alarm log -- all other traps get filtered out.

" Critical: Bright red" Major: Orange" Minor: Yellow" Informational (warning): No color" None: Does not receive NORAND

specific traps“Critical” is the most severe trap level and “Informational”is the least severe trap level. “Informational” is the defaulttrap level and allows for receiving all traps. “None” doesnot allow for receiving any NORAND specific traps.

A filter specifies the lowest trap severity that OWLView re-ceives. For example, “Informational” allows for receivingall traps: “warning,” “minor,” “major,” or “critical,” whereas“Major” allows for receiving only “major” and “critical”traps.Click the OK button to save, or click the Cancel button toexit this window without changes.



Multiple Device SetOWLView Multiple Device Set simplifies deviceconfiguration by performing SNMP SET operations onmultiple devices with one command. SET operations arepredefined into queries stored in an owlquery.ini file.These queries are accessed through the Multiple Device Setwindow and executed on selected NORAND devices.

Click theMultiple Device Set option to set objects for asingle device or multiple devices. The Multiple Device Setwindow appears:



Selection CriteriaThere are two options to select nodes for registration:

" Selected Nodes: Click this radio button to performthe multiple device set operation on all nodes selectedon the map. To select nodes on the map, press andhold the <CTRL> key and click the left mouse buttonon all of the devices that the multiple device set is toperform on.

" Selection File: Click this radio button to activate theSelection File. Multiple device set operations areperformed for all devices in the selection file. Tocreate a selection file, edit the file:


The format of the file is:Line 1: IP address of deviceLine 2: Symbol:Class:Symbol SubClass


Query SelectionThis box selects the query to be performed. All queries arepredefined in the owlquery.ini file found in the<owlview path>/config directory. See next page todefine Multiple Device Set queries.

Each query is displayed in the Query Selection field. Usethe scroll box to view all available queries and select thequery to be performed on selected devices.

Click the Execute button to perform theMultiple DeviceSet command on selected devices.



Active NodeThis box shows the current device that theMultipleDevice Set operation is executing. The percentage box onthe right shows the amount of operation completed. Whencomplete for all selected devices, “Finished” appears in theActive Node field.

Error AlarmsIf theMultiple Device Set operation fails for a node, thesystem generates an alarm and logs the alarm into the HPOpenView event log. The alarm names theMultipleDevice Set operation-failed device.

Defining Multiple Device SetQueriesMultiple Device Set queries are predefined in theowlquery.ini file found in the <owlviewpath>/config installation directory.

EXAMPLE: owlquery.ini file[sys Group]sysLocation=“Warehouse1”sysContact=“Service”

[reset_gw]gsReset=1rcbsTableReset=1hdTableReset=1tdTableReset=1gsTermDelayTraceOn=1tdTrxnTime=3 1tdTrxnTime=7 2tdTrxnTime=15 3tdTrxnTime=30 4tdTrxnTime=50 5tdTrxnTime=100 6tdTrxnTime=200 7tdTrxnTime=600 8tdTrxnTime=1500 9



[Soft_download]sdStartTime=nsdServerIpAddress=n.n.n.nsdScriptFilename=“filename”sdCheckPoint=0sdSetActivePointers=1sdTerminate=2

[reboot_device]pwrNextPowerUpTime=500

Each query name appears in brackets ([ . . . ]). The pre-vious example shows four queries:

" sys Group Sets MIB II system objects." reset_gw Resets Gateway performance table

values. Good to use when startingnew tests.

" Soft_download Readies Access Points for SoftwareDownload. Must modifyStartTime, IPAddress, andFilename.

" reboot_device Reboots device in five seconds (timein .01 seconds).

Each query contains a list of MIB objects and values in ei-ther format:

" MIB ObjectName=Value(for scalar data objects)

or

" MIB ObjectName=Value RowNumber(for tabular data objects)

Each object is SET to a value specified when theMultipleDevice Set operation executes.



OWLMIBsOWLView OWLMIBs is a customized MIB browser thatdisplays Open Wireless LAN MIB items supported by a giv-en device type. Those not supported are not displayed.These MIB items are categorized by management informa-tion areas (system, bridge, port, etc.), thus MIB informationcan be browsed by function.

To use the OWLMIBs function, select the devices to query,then choose the OWLMIBs menu and MIB information. Ifmore than one device is selected, multiple OWLMIBs win-dows appear. Below is a sample OWLMIBs window:

" File: Select this menu option to save or print the de-vice MIB information.



" View: Select this menu option to expand or reducethe MIB information.

" Name or IP Address: Shows the name or the IP ad-dress of the device displayed.

" Messages: Lists any errors or messages regardingthis particular device.

" Close: Click this button to exit this OWLMIBs win-dow.

" Stop: Click this button to stop the display of MIB in-formation.

" Restart: Click this button to rebuild the display ofMIB information.

Function OIDsThe OWLMIBs functions listed below and on the next pageinclude a brief description followed by the MIB Object IDen-tifier (OID), in italics. To obtain detailed information aboutthe MIB objects displayed for each function listed below, usethe MIB OID to reference the object definitions in the OpenWireless LAN MIB.

Uptime Device up timemib-2.system.sysUpTime

TrapHosts Trap receiver registrynorand.manage.norandNet.nSNMP.v1Config.trapTargetTable

SystemConfigHardware Device hardware configuration

norand.manage.norandNet.nSystem.hwSoftware Device software configuration

norand.manage.norandNet.nSystem.file.dir.dirTable



PortInfoMIBIIifTable MIB II if Table, Device port information

mib-2.interfaces.ifTablePortState Device Open Wireless LAN port information

norand.manage.norandNet.nInterfaces.portState.psT ablePortStatistics Device Open Wireless LAN port statistics

norand.manage.norandNet.nInterfaces.portStats.pstcT ableEthernetPort

EthStats Ethernet interface statisticsmib-2.transmission.dot3.dot3StatsTable

EthCollisions Ethernet collisionsmib-2.transmission.dot3.dot3CollTable

NetworkInfoOwlLanConfig Open Wireless LAN configuration information

norand.manage.norandNet.nBridge.brgStateOwlLanStats Open Wireless LAN statistics

norand.manage.norandNet.nBridge.brgStatsOwlAddrTable(root) Open Wireless LAN root address table

norand.manage.norandNet.nBridge.addr.addrTableConnections

RoutedNodes Open Wireless LAN routed connectionsnorand.manage.norandNet.nBridge.rt.rtTable

BridgedNodes Open Wireless LAN bridged connectionsnorand.manage.norandNet.nBridges.brg.brgTable

GatewayGWStatistics Gateway statistics

norand.manage.norandNet.nApplication.gwSession.gsSessions Terminal sessions associated with the gateway

norand.manage.norandNet.nApplication.gwSession.rcbs.rcbsT ableHostDelay Host delay statistics

norand.manage.norandNet.nApplication.gwSession.hd.hdT ableTermDelay Terminal delay statistics

norand.manage.norandNet.nApplication.gwSession.td.tdT able



6710 Access PointDo the following to display MIB functions supported by the6710 Access Point (AP):

1. Select the Access Points to be queried.2. Select OWLView → OWLMIBs → 6710 AP to open

the OWLMIBs windows.The following functions are supported under Access Points:

Uptime

TrapHosts

SystemConfigHardwareSoftware

PortInfoMIBIIifTablePortStatePortStatisticsEthernetPort

EthStatsEthCollisions

NetworkInfoOwlLanConfigOwlLanStatsOwlAddrTable(root)Connections

RoutedNodesBridgedNodes



6910 Integrated Gateway/AccessPointDo the following to display MIB functions supported by the6910 Integrated Gateway/Access Point (IGAP):

1. Select the IGAPs to be queried.

2. Select OWLView → OWLMIBs → 6910 IGAP toopen the OWLMIBs windows.

The following functions are supported under IGAPs:

Uptime

TrapHosts


PortInfoMIBIIifTablePortStatePortStatisticsEthernetPort

EthStatsEthCollisions

NetworkInfoOwlLanConfigOwlLanStatsOwlAddrTable(root)Connections

RoutedNodesBridgedNodes

GatewayGWStatisticsSessionsHostDelayTermDelay



4030 GatewayDo the following to display MIB functions supported by the4030 Gateway:

1. Select the Gateways to be queried.2. Select OWLView → OWLMIBs → 4030 GW to open

the OWLMIBs windows.The following functions are supported under Gateways:

Uptime

TrapHosts





6950 Terminal ServerDo the following to display MIB functions supported by the6950 Terminal Server:

1. Select the Terminal Servers to be queried.2. Select OWLView → OWLMIBs → 6950 TS to open

the OWLMIBs windows.The following are supported under Terminal Servers:

Uptime



Glossary

" " " " " " " " " " " " " " " " " " " " " " " " " " " "

Access Point (AP)

Operates as a wireless bridge. Connects to or coexists withexisting wired LANs that conform to ASNI/IEEE 802.3 andDIX Ethernet specifications.

Address Mask

A bit mask that identifies which address bits, such as an IPaddress, are network, subnet, and host significant portionsof the complete address. Also known as the subnet maskbecause the address subnetwork portion is determined bycomparing the mask binary version to an IP address in thatsubnet. The mask holds the same number of bits as theprotocol address it references.

Address Resolution Protocol (ARP)

A protocol that dynamically discovers the low level physicalnetwork hardware address that corresponds to the higherlevel protocol address for a given host. ARP is limited tophysical network systems that support broadcast packetsthat can be heard by all hosts on the network.

GLOSSARY


Agent

The entity portion that responds to management requestsand preprogrammed traps. Part of the system that pre-pares information and exchanges it for client or server ap-plication.

ASN.1

Abstract Syntax Notation One. A machine independentdata definition language used by ISO protocols. Most nota-ble use is for SNMP and the MIBs. ASN.1 is defined in ISOdocuments 8824.2 and 8825.2.

Assigned Numbers

The codes (numbers in hexadecimal, decimal, or binary for-mat) officially recognized and assigned as part of the Inter-net standards.

Backbone

The main connectivity device of a distributed system. Allsystems that have connectivity to the backbone will connectto each other. This does not stop systems from setting upprivate arrangements with each other to bypass the back-bone for cost, performance, or security.

Bridge

A device that expands a LAN by forwarding frames be-tween data link layers associated with two separate cables,usually carrying a common protocol. Bridges can usually bemade to filter packets (to forward only certain traffic). InOSI terminology, a bridge is a Data Link Layer intermedi-ate system. See also: router.

GLOSSARY


Collision

When more than one LAN station attempt communicationson the same transmission medium simultaneously.

Community

Defines a level of authentication and access control at theSNMP agent. The SNMP agent established one communityfor each desired combination of authentication and accesscontrol characteristics.

Gateway (GW)

In current usage, “gateway” and “application gateway” re-fer to translating systems that convert data traveling fromone environment to another.

Get

A basic SNMP PDU operation that lets a management sta-tion tell an agent to retrieve a value that agent stores. Away to retrieve management information.

Hop

Used in vector distance routing. Equal to one data link. Apath to the final destination on a net is a series of hopsaway from the origin.

GLOSSARY


ICMP (Internet Control Message Protocol)

The protocol that handles errors and control messages atthe IP layer. ICMP is actually a part of the IP protocol lay-er. It can generate error messages, test packets, and in-formational messages related to IP.

Integrated Gateway/Access Point (IGAP)

Operates as a wired bridge or a wireless access point. Con-nects to or coexists with existing wired LANs that conformto ASNI/IEEE 802.3 and DIX Ethernet specifications. Incurrent usage, “gateway” and “application gateway” refer totranslating systems that convert data traveling from oneenvironment to another.

IP (Internet Protocol)

The network layer for the TCP/IP Protocol Suite. It is aconnectionless, best-effort packet switching protocol thatoffers a common layer over dissimilar networks.

IP address

An IP defined 32-bit address usually in dotted decimalnotation. See also: IP, network address, subnet address.

LAN (Local Area Network)

A data network intended to serve an area of only a fewsquare kilometers or less. Because only a small area is cov-ered, optimization can be made in the network signal proto-cols that permit higher data rates. See also: WAN.

GLOSSARY


Layer

A modular portion of a stacked protocol that consists of oneor more semi-independent protocols. Each layer builds onthe layer beneath it and feeds information to the protocolsin the layers above it. TCP/IP has five layers of protocols,and OSI has seven.

MAC (Media Access Control)

The lower portion of the datalink layer. The MAC differsfor various physical media. See also: MAC Address.

MAC Address

The “built-in” hardware address of a device connected to ashared media. See also: MAC.

Management Agent

Resides on the managed device and responds to informationrequests from the management station (GETs or SETs).May provide unsolicited information about extraordinaryevents (TRAPs) to the station.

Management Station

Provides an interface or is responsible for monitoring andcontrolling the network or a portion of the network. Themanagement station talks to network management agents,which resides in the managed nodes.

GLOSSARY


MIB (Management Information Base)

A database which contains information about managementobjects used as access points at the management agent forthe management station. The information identifies themanagement element and specifies its type and accessmode (Read-Only, Read-Write). See also: SNMP.

Network

A computer network is a data communications systemwhich interconnects computer systems at various differentsites. A network may include any combination of LANs,MANs, or WANs. See also: LAN, WAN.

Network Address

In TCP/IP, the network portion of an IP address. For aclass A network, the network address is the first byte of theIP address. For a class B network, the network address isthe first two bytes of the IP address. For a class C network,the network address is the first three bytes of the IP ad-dress. In each case, the remainder is the host address. Inthe Internet, assigned network addresses are globallyunique. See also: IP address, subnet address.

In NetWare, the unique number assigned to each logicalnode of the network.

Network Management Protocol

Allows management stations and management agents toexchange information.

Node

An addressable device attached to a computer network. Seealso: router.

GLOSSARY


OID (Object IDentifier)

A unique SNMP identifier assigned to each object. OIDsconsist of a sequence of integer values represented in dotnotation or address.

Packet

The unit of data sent across a packet switching network. InTCP/IP, it has come to refer to the data package sent acrossa physical network as in Ethernet packet.

PDU (Protocol Data Unit)

An OSI term for “packet.” A PDU is a data object ex-changed by protocol machines (entities) within a given lay-er. In TCP/IP, it defines the type of SNMP message beingsent.

Port

Physically, an access point to a computer, multiplexer de-vice, or network. Logically, a pointer to a TCP/IP applica-tion.

Protocol

A formal description of message formats and the rules com-puters must follow to exchange those messages.

Protocol Stack

A modular set of functions, one at each layer of the stack,that form a network service. Each layer of the stack usesthe services of the module beneath it.

GLOSSARY


RFC (Request For Comments)

The document series, begun in 1969, which describes theInternet suite of protocols, related experiments, and otherInternet-related information and ideas.

Router

A device that forwards traffic between networks or subnet-works. It operates at the OSI Network Layer (layer 3) orthe IP layer in TCP/IP. See also: bridge, gateway.

Set

A basic SNMP PDU operation that lets a management sta-tion tell an agent to change a value that agent stores. Away to manipulate management information.

SNMP (Simple Network Management Protocol)

The Internet standard protocol for managing nodes on anIP network. See also: MIB.

Subnet Address

The network-significant part of the locally administeredpart of a network IP address. Identified using a subnet (oraddress) mask. See also: address mask, IP address, net-work address.

TCP (Transmission Control Protocol)

An Internet standard transport protocol in the Internet pro-tocols suite for reliable, connection-oriented, full-duplexstreams. Contrasts with UDP.

GLOSSARY


TCP/IP Protocol Suite (TransmissionControl Protocol over Internet Protocol)

This is a common shorthand which refers to the suite oftransport and application protocols which run over IP. Seealso: IP, ICMP, TCP, UDP, Telnet, SNMP.

Telnet

The virtual terminal protocol in the Internet suite of proto-cols. Users on one host can access another host and workas users of that host.

Trap

A basic SNMP operation that sets unsolicited SNMP agentmessages, about extraordinary events that occurred, for theSNMP management station.

UDP (User Datagram Protocol)

An Internet standard transport protocol that exchanges da-tagrams without acknowledgements or guaranteed delivery.

WAN (Wide Area Network)

A network that covers a large geographic area.

Wired Bridge

A device that connects to the Ethernet medium through atransceiver, such as a 10BASE2 T-connector. It expands aLAN by forwarding frames between data link layers associ-ated with two separate cables, usually carrying a commonprotocol.

GLOSSARY


Wireless Bridge

A device that does not use a transceiver and does not direct-ly connect to the Ethernet medium. It expands a LAN byforwarding frames between data link layers associated withtwo separate cables, usually carrying a common protocol.

OWLView for HP OpenView for UNIX User’s Guide Index-1

General Index

" " " " " " " " " " " " " " " " " " " " " " " " " " " "

NOTE:This index covers all topics.Those in italics are figures,those in bold are tables.

AAccess Pointbridge, 3-23closeup, 3-16configuration, 3-21LEDs, 3-17OWLMIBs, 3-39physical port, 3-18, 3-24software, 3-22

AP. See Access Point

BBridge (AP only), 3-23

CCloseupAccess Point, 3-16Gateway, 3-20

Configuration (AP and GW),3-21

Creating device status, 3-12Creating mapsHP OpenView network, 3-6NORAND OWL, 3-10OWL LAN, 3-11OWLView, 3-7root, 3-9

terminal, 3-13

D

Device information, 3-16bridge, 3-23closeup, 3-16configuration, 3-21physical port, 3-18port selections, 3-24software, 3-22

Discover network, 3-6creating device status, 3-12creating mapsHP OpenView network, 3-6NORAND OWL, 3-10OWL LAN, 3-11OWLView, 3-7root, 3-9terminal, 3-13

F

Fixed end map, map layout, 3-3

G

Gatewaycloseup, 3-20configuration, 3-21LEDs, 3-20OWLMIBs, 3-41physical port, 3-20software, 3-22

GW. See Gateway

HHardware requirements, 1-3

IIGAP. See Integrated Gateway/

Access PointInstallation, uninstalling OWL-

View, 1-6Installation and set up, 1-4Integrated Gateway/Access

Point, OWLMIBs, 3-40

LLoading and unloading, MIB

with HP OpenView, 1-5

MMIBs, loading and unloading

with HP OpenView, 1-5Multiple device set, 2-14, 3-32

OOverview, 1-1OWLMIBs, 3-36access point, 3-39functions, 3-37gateway, 3-41integrated gateway/access

point, 3-40overview, 2-15terminal server, 3-42

GENERAL INDEX

Index-2 OWLView for HP OpenView for UNIX User’s Guide

OWLView, 1-1device information, 2-7, 3-16discover network, 3-6discovery, 3-2fixed end map, 3-3map layout, 3-3menu, 3-1multiple device set, 2-14, 3-32redraw OWL map, 3-8refresh OWL map, 3-7set community name, 3-5terminal map, 2-6, 3-4trap handling, 2-12deregister for traps, 3-29filter level, 3-31menu, 3-27register for traps, 3-27

PPhysical Port (AP only), 3-24

Product contents, 1-3

R

Redraw OWL map, 3-8

Refresh OWL map, 3-7

Running HP OpenView withOWLView, 1-5

S

Set community name, 3-5

Software (AP and GW), 3-22

Software requirements, 1-3

System requirementshardware, 1-3

software, 1-3

T

Terminal map, map layout, 3-4

Terminal Server, OWLMIBs,3-42

Trap handling, 2-12deregister for traps, 3-29filter level, 3-31menu, 3-27register for traps, 3-27

TS. See Terminal Server

U

Uninstalling OWLView, 1-6

OWLView for HP OpenView for UNIX USER’S...

Documents

Transcript of OWLView for HP OpenView for UNIX USER’S...