home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 16 Announce
/
16-Announce.zip
/
LNVBET.ZIP
/
LNVOBJWP.ASC
< prev
Wrap
Text File
|
1993-01-05
|
214KB
|
5,284 lines
IBM LAN NETVIEW:
AGENTS AND OBJECTS OVERVIEW
- WHITE PAPER -
January 6, 1993
Version 1.0d
International Technical Support Center
Austin
(C) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1992. ALL
RIGHTS RESERVED.
Note to U.S. Government Users -- Documentation related to restricted
rights -- Use, duplication or disclosure is subject to restrictions
set forth in GSA ADP Schedule Contract with IBM Corp.
ABSTRACT
________
This white paper discusses the IBM LAN NetView Agents and LAN NetView Agents
Extended products and the Management Information Base (MIB) they represent.
This paper is intended for IBM marketing representatives, IBM system
engineers, customers and software developers who desire a general
understanding of the systems management capabilities provided by IBM LAN
NetView. It focuses on the LAN NetView agent products and the potential
for using them when developing systems management applications.
Note that IBM LAN NetView was previously named "IBM LANfocus Management/2".
(C) Copyright IBM Corp. 1992 iii
CONTENTS
________
ABSTRACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . III
TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VI
AUTHORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VII
CHAPTER 1. INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . 1-1
CHAPTER 2. THE LAN NETVIEW FRAMEWORK . . . . . . . . . . . . 2-1
2.1 The Object-Oriented Model . . . . . . . . . . . . . . . . . . . . 2-1
2.2 Managers, Agents and Managed Object Interaction . . . . . . . . . 2-2
2.3 Standards Used by LAN NetView . . . . . . . . . . . . . . . . . . 2-4
CHAPTER 3. THE LAN NETVIEW FAMILY OF PRODUCTS . . . . . . . . 3-1
3.1 LAN NetView Manage . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2 LAN NetView View . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.3 LAN NetView Enable . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.4 LAN NetView Agents . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.5 LAN NetView Agents Extended . . . . . . . . . . . . . . . . . . . . 3-2
3.6 LAN NetView Applications . . . . . . . . . . . . . . . . . . . . . 3-3
CHAPTER 4. LAN NETVIEW AGENTS . . . . . . . . . . . . . . . . . 4-1
4.1 Resource Manager Agents . . . . . . . . . . . . . . . . . . . . . 4-1
4.1.1 Resource Manager Objects . . . . . . . . . . . . . . . . . . . 4-2
4.1.2 Management Support Objects (Monitor-Scanner) . . . . . . . . . 4-2
CHAPTER 5. SOLUTIONS BASED ON LAN NETVIEW AGENTS . . . . . . 5-1
5.1 Operations Management . . . . . . . . . . . . . . . . . . . . . . 5-2
5.1.1 Monitoring the Status of Resources . . . . . . . . . . . . . . 5-2
5.1.2 Querying/Changing Operational Characteristics of Resources . . 5-4
5.1.3 Performing Actions on Resources . . . . . . . . . . . . . . . 5-4
5.1.4 Operations Management Summary . . . . . . . . . . . . . . . . 5-5
5.2 Configuration Management . . . . . . . . . . . . . . . . . . . . . 5-6
5.2.1 Retrieving Configuration Information . . . . . . . . . . . . . 5-6
5.2.2 Changing the Configuration . . . . . . . . . . . . . . . . . . 5-7
5.2.3 Tracking Changes to Configurations . . . . . . . . . . . . . . 5-7
5.2.4 Configuration Management Summary . . . . . . . . . . . . . . . 5-7
5.3 Problem Management . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.3.1 Monitoring Resources . . . . . . . . . . . . . . . . . . . . . 5-8
5.3.2 Analyzing Received Notifications . . . . . . . . . . . . . . . 5-8
5.3.3 Corrective Actions . . . . . . . . . . . . . . . . . . . . . . 5-9
5.3.4 Problem Management Summary . . . . . . . . . . . . . . . . . . 5-9
5.4 Performance Management . . . . . . . . . . . . . . . . . . . . . 5-10
5.4.1 Monitoring Systems and Isolating Performance Problems . . . 5-10
5.4.2 Performance Management Summary . . . . . . . . . . . . . . . 5-11
5.5 Inventory Management . . . . . . . . . . . . . . . . . . . . . . 5-12
5.5.1 Discovery of New Nodes . . . . . . . . . . . . . . . . . . . 5-13
5.5.2 Inventory Management Summary . . . . . . . . . . . . . . . . 5-13
(C) Copyright IBM Corp. 1992 iv
5.6 Summary of Agent Based Solutions . . . . . . . . . . . . . . . . 5-14
APPENDIX A. LAN NETVIEW MIB SUMMARY . . . . . . . . . . . . A-1
A.1 OS/2 Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
A.2 DOS Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16
A.3 DOS/Windows Agent . . . . . . . . . . . . . . . . . . . . . . . A-24
A.4 LAN Server Agent . . . . . . . . . . . . . . . . . . . . . . . . A-28
A.5 Communications Manager Agent . . . . . . . . . . . . . . . . . . A-37
A.6 Database Manager Agent . . . . . . . . . . . . . . . . . . . . . A-46
Contents v
TRADEMARKS
__________
The following terms, which are denoted by an asterisk (*) in this
publication, are trademarks of the International Business Machines
Corporation in the United States and/or other countries:
APPN
IBM
Micro Channel
NetView
OS/2
The following terms, which are denoted by a double asterisk (**) in this
publication, are trademarks of other companies:
Microsoft is a trademark of Microsoft Corporation.
Windows is a trademark of Microsoft Corporation.
(C) Copyright IBM Corp. 1992 vi
AUTHORS
_______
The authors of this white paper were:
Bart Jacob
International Technical Support Center, Austin
Marie-Christine Laffont
IBM France
This publication is the result of a residency conducted at the International
Technical Support Center, Austin.
Thanks to Mike Sauro, Lori Moritz and the entire agent development team for
their time and knowledge contributed to the creation of this white paper.
For questions regarding this white paper, contact Bart Jacob :
IBM VNET : JACOBB @ AUSVM8
Internet : jacobb@ausvm8.vnet.ibm.com
IBMMAIL : USIB3NBP @ IBMMAIL
(C) Copyright IBM Corp. 1992 vii
CHAPTER 1. INTRODUCTION
________________________
+--- IMPORTANT DISCLAIMER!!! -----------------------------------------------+
| |
| THIS WHITE PAPER INCLUDES GENERAL INFORMATION REGARDING THE IBM LAN |
| NETVIEW FAMILY OF PRODUCTS AND SPECIFICALLY ADDRESSES THE LAN NETVIEW |
| AGENTS AND LAN NETVIEW AGENTS EXTENDED PRODUCTS. THIS INFORMATION IS |
| BASED ON EARLY DOCUMENTATION AND SPECIFICATIONS. IT IS INEVITABLE THAT |
| SOME OF THE INFORMATION PRESENTED HERE WILL CHANGE BY THE GENERAL |
| AVAILABILITY OF THESE PRODUCTS. (OR EVEN BY THE TIME YOU READ THIS!) |
| |
| THE INTENTION IS TO GIVE THE READER A GENERAL UNDERSTANDING OF THE |
| CAPABILITIES ADDRESSED BY THE LAN NETVIEW AGENT PRODUCTS. FOR SPECIFIC |
| IMPLEMENTATION DETAILS, WE REFER THE READER TO THE PRODUCT DOCUMENTATION |
| WHEN IT BECOMES AVAILABLE. |
| |
+---------------------------------------------------------------------------+
The IBM* LAN NetView* family of products provides a framework and applications
to implement OS/2*-based distributed systems management solutions. The
LAN NetView framework utilizes industry standard interfaces and protocols
that allow an OS/2 system to manage heterogeneous systems in a LAN environment.
An OS/2 system may also be managed by other systems that conform to the same
standards.
The LAN NetView family of products is based on systems management
standards such as those developed by ISO (the International Organization for
Standardization) and IEC (the International Electrotechnical Commission) as
part of their work on Open Systems Interconnection (OSI).
The primary purpose of this white paper is to provide the reader with a look
at the LAN NetView Agents and LAN NetView Agents Extended products and the
Management Information Base (MIB) they represent.
The LAN NetView agents are a key component of the LAN NetView family of
products. They provide systems management application developers with access
to a wide variety of objects associated with OS/2, its major subsystems (LAN
Server V3.0, Database Manager and Communications Manager), DOS V5.0 and DOS
V5.0 with Microsoft** Windows** V3.1. In addition these agents provide
information regarding the hardware on which they are running.
Agents are systems management applications which perform operations on
managed objects at the request of managing applications and emit
notifications on behalf of managed objects.
IBM LAN NetView systems management applications will take advantage
of these agents. However, and maybe more importantly, these agents may be
utilized by systems management applications written by other vendors or
customers. The MIB defined by these agents represents a rich set of object
(C) Copyright IBM Corp. 1992 1-1
classes which can be used by applications that span all functional areas (or
disciplines) of systems management.
This paper will briefly introduce the LAN NetView concepts and products, and
then provide a more in-depth look at the MIB defined by the LAN NetView Agents
and LAN NetView Agents Extended products and the possibilities it presents for
systems management applications.
Chapter 1. Introduction 1-2
CHAPTER 2. THE LAN NETVIEW FRAMEWORK
_______________________________________________
The LAN NetView family of products is based on a series of industry
standards as mentioned previously. This family of products provides systems
management applications and a framework. This framework provides an enabling
platform for IBM applications as well as applications written by vendors or
customers. The following sections will provide a brief overview of the
concepts behind the LAN NetView framework.
2.1 THE OBJECT-ORIENTED MODEL
______________________________
Communications protocols were developed to provide communications between
systems. But for distributed systems management, communications protocols
alone are insufficient. Distributed management programs require standard
descriptions of the resources to be managed.
Therefore OSI adopted an object-oriented model for encapsulating these
resources and standardizing the interfaces they present to the network.
In an object-oriented model, code and data are fused into a single entity
called a managed object. A managed object is composed of a set of attributes
which characterize it, actions that it can perform, and notifications that it
can emit.
In the LAN NetView environment, a managed object is an abstraction
that models some physical resource (such as a workstation) or logical
resource (such as a file system).
Those aspects of resources that are related to the management of the resource
are accessible through the managed-object abstraction.
A managed object is defined by :
o Attributes
The attributes represent information about the object.
Operations may be performed on objects or specific attributes of objects.
Examples of these operations are GET, SET for attribute values and CREATE
and DELETE for objects themselves.
o Actions
Actions represent functions that an object can perform.
o Notifications
A notification is an unsolicited message that an object sends
asynchronously to agents and managers.
(C) Copyright IBM Corp. 1992 2-1
A set of object classes and their associated attributes, actions and
notifications make up a Management Information Base (MIB). Management
applications may then be designed to utilize the MIB in performing management
functions.
2.2 MANAGERS, AGENTS AND MANAGED OBJECT INTERACTION
____________________________________________________
A distributed systems management environment is achieved through distinct
entities called managers and agents. This environment is similar to a
client-server model.
An agent is the part of a distributed management program that supervises one
or more managed objects. The agent receives requests for operations to be
performed on managed objects or requests for objects to perform certain
actions. The agent is responsible for passing these requests to a resource
manager. A resource manager provides the interfaces required to carry out
the specific request.
For example, in an OS/2 environment, the LAN Server, Communications Manager,
Database manager or even the operating system itself can be considered a
resource manager.
The agent is also responsible for emitting notifications (events/traps) when
it detects special conditions in the managed object.
A manager is the part of distributed management program that issues requests
for actions and receives notifications. A manager uses the services of one
or more agents. Managers do not manage resources directly, rather they issue
requests to objects which are represented by agents.
Figure 2-1 on page 2-3 represents the interactions between managers, agents
and managed resources.
Chapter 2. The LAN NetView Framework 2-2
+---------------------------------------------------------------------------+
MANAGER-AGENT-OBJECT INTERACTION
┌─────────────┐
│ Managed │Model-
MANAGER AGENT │ Objects │ing
│ ▓▓ │<----─┐
┌────────┐ Re- ┌──────┬─────────┬──────────┐---------│ ▓▓ │ |
│ │ quests │GET | │ │ │ ▓▓ │ |
│Manage- │───────> │SET | │ │ Mgmt. └─────────────┘ |
│ment │ │CREATE| CMIS │ │ Opera- |
│Program │<─────── │DELETE| Proces- │┌─────────┤ tion ┌──┬──────┐ ┌───────┐|
│ │ Re- │ACTION| sing ││ Access │───────> │A │Re- │ │Man- │|
│ │ sponses ├-----─┤ ││ Managed │ │ │source│ │aged │|
│ │<─────── │EVENT | ││ Resource│<─────── │P │Mana- │ │Re- ├┘
└────────┘ Notifi- └──────┴─────────┴┴─────────┘ Result │ │ger │ │sources│
cations │I │ │ │ ░ ░ │
┌────────┐ ┌───────────────────────────┐ │ │ │ │ ░ │
│Mgmt API│ │ Mgmt API │ └──┴──────┘ └───────┘
└────────┘ └───────────────────────────┘
┌────────┐ CMIP ┌───────────────────────────┐
│Mgmt │<───┐ │ Management │
│Frame- │ └───>│ Framework │
│work │ SNMP │ │
└────────┘ └───────────────────────────┘
+---------------------------------------------------------------------------+
Figure 2-1. Systems Management Interactions
Each subsystem which controls a set of resources is called a resource
manager. Examples include:
o the Operating System
o the Communications Manager
o the Database Manager
o the LAN Server
An agent will perform management operations on resources through API's
provided by the resource manager.
The interfaces used between an agent and the resources it represents are not
subject to standardization. An agent is free to use whatever interfaces are
available in the system in order to carry out operations or actions. Even
though the framework is object-oriented, the actual interaction between the
Chapter 2. The LAN NetView Framework 2-3
agent and the resource manager may use non-object oriented interfaces. This
interaction is completely hidden from the managing system.
The LAN NetView architecture currently supports two different sets
of protocols and services to be used between managing and managed systems :
o CMIP, the Common Management Information Protocol was designed for
managing OSI networks. The services defined for CMIP are known as the
Common Management Information Services, or CMIS.
o SNMP, the Simple Network Management Protocol was designed for managing
TCP/IP networks and devices.
The LAN NetView framework provides three key APIs for building
applications:
o The X/Open OSI-Abstract-Data Manipulation (XOM) API
o The X/Open Management Protocols (XMP) API
o The Graphic User Interface (GUI) API
The XOM API is used to manipulate the data structures associated with
objects.
The XMP API is used for standards-based process to process communications
between a managing system and a managed system.
The GUI API is used by applications on the managing system to provide a
consistent user interface to all management applications in a LAN NetView
environment and to enhance the capability for seamless navigation between
systems management applications for the user.
2.3 STANDARDS USED BY LAN NETVIEW
____________________________________________
The LAN NetView architecture is based on and utilizes a variety of
industry standards, including:
o 8824 (X.208): OSI - Specification of Abstract Syntax Notation One
(ASN.1)
o 8825: OSI - Specification of Basic Encoding Rules for Abstract Syntax
Notation One (ASN.1)
o ISO/IEC 9595 (X.710): Common Management Information - Service Definition
o ISO/IEC 9596-1 (X.711): Common Management Information - Protocol
Specification
o ISO/IEC 10165-1 (X.720): Structure of Management Information -
Management Information Model
o ISO/IEC 10165-2 (X.721): Structure of Management Information -
Definition of Management Information
o ISO/IEC 10165-4 (X.722): Structure of Management Information -
Guidelines for the Definition of Managed Objects
o RFC 1155: Structure and Identification of Management Information for
TCP/IP-based Internets
Chapter 2. The LAN NetView Framework 2-4
o RFC 1157: A Simple Network Management Protocol (SNMP)
o RFC 1213: Management Information Base for Network Management of
TCP/IP-based Internets: MIB-II
Chapter 2. The LAN NetView Framework 2-5
CHAPTER 3. THE LAN NETVIEW FAMILY OF PRODUCTS
________________________________________________________
The LAN NetView family of products includes support for both
managing and managed systems. The LAN NetView environment is depicted in
Figure 3-1.
+---------------------------------------------------------------------------+
LAN NetView ENVIRONMENT
┌───────────────┐ ┌───────────────┐
┌─────────────────────┐ │ │ │ Resource Mgrs │
│ VIEW │ │ AGENTS │ │ - OS/2 │
├─────────────────────┤ ┌────>│ AGENTS EXT'D │ │ - LAN Server │
│ Graphical Interface │ │ │ │ │ - DB Manager │
└─────────────────────┘ │ │ │ │ - Comm. Mgr. │
┌─────────────────────┐ │ │ │ │ │
│ System & Network │ │ └───────────────┘ └───────────────┘
│ Mgmt Apps │<─────┘
│ │ ┌──────────────────────────────────┐
│ - NETVIEW TIE │ │ XMP/XOM │
│ - MONITOR │ ├──────────────────────────────────┤
│ - FIX │ │ ENABLE │
│ - START │<──────┐ └──────────────────────────────────┘
│ - Other Apps │<────┐ │ ┌──────────────────────────────────┐
└─────────────────────┘ │ │ │ OS/2 V2.0 │
┌─────────────────────┐ │ │ └──────────────────────────────────┘
│ XMP/XOM │ │ │
├─────────────────────┤ │ │ Managed Clients/Servers
│ MANAGE │ │ │
│ │ │ └──────────────────────────────────┐
│ Topology Services │ └──────────┐ │
│ Discovery Services │ V V
│ Event Mgmt Services │ ┌─────────────┐ ┌─────────────┐
│ Metadata Services │ │ AGENTS │ │ SNMP Agent │
└─────────────────────┘ └─────────────┘ └─────────────┘
┌─────────────────────┐ ┌─────────────┐ ┌─────────────┐
│ OS/2 V2.0 │ │ DOS/DOS+WIN │ │TCP/IP Device│
└─────────────────────┘ └─────────────┘ └─────────────┘
MANAGING SYSTEM MANAGED CLIENTS
+---------------------------------------------------------------------------+
Figure 3-1. LAN NetView Environment
(C) Copyright IBM Corp. 1992 3-1
The following sections will briefly describe the products that make up the
LAN NetView environment and the roles that they take.
3.1 LAN NETVIEW MANAGE
_______________________
LAN NetView Manage provides the core functions required by a managing system.
These include event management, metadata, topology and discovery services.
LAN NetView Manage provides the industry standard X/Open Management API's
(XMP) and the X/Open OSI-Abstract-Data Manipulation API's (XOM) for the
development of management applications.
LAN NetView Manage requires OS/2 V2.0 as an operating system environment.
3.2 LAN NETVIEW VIEW
_____________________
LAN NetView View provides a graphical interface to the LAN NetView environment.
Developers may use the LAN NetView View programming interfaces to deliver
a consistent look and feel to their management applications.
LAN NetView View will automatically provide for easy navigation through
a series of LAN NetView applications. It also provides services to allow
for the displaying of management data in progressive layers of detail.
3.3 LAN NETVIEW ENABLE
______________________
LAN NetView Enable provides the managed system platform on OS/2 V2.0-based
systems. It also provides the XMP/XOM programming interfaces for the
development of management agents which will interact with applications on
The managing system.
3.4 LAN NETVIEW AGENTS
______________________
LAN NetView Agents provide the managed system agent capabilities for DOS V5.0,
DOS V5.0 with Microsoft Windows V3.1 and OS/2 V2.0 systems. It also provides
the agent support for the IBM LAN Requester.
The LAN NetView Agents software interfaces with the specific operating system
or LAN Requester to provide a bridge between the managing applications and the
objects being managed.
The objects that are defined by the LAN NetView Agents and the LAN NetView
Agents Extended (see below) products are the main topic of this white paper.
3.5 LAN NETVIEW AGENTS EXTENDED
_______________________________
The LAN NetView Agents Extended provide the agent support for the LAN Server
V3.0, Database Manager and Communications Manager subsystems.
Chapter 3. The LAN NetView Family of Products 3-2
3.6 LAN NETVIEW APPLICATIONS
_______________________________________
The following management applications have also been announced by IBM. These
applications will run on a managing system (requiring LAN NetView Manage and
LAN NetView View) and will utilize the LAN NetView Agents and LAN NetView
Agents Extended software on the managed systems.
LAN NETVIEW FIX - LAN NetView Fix is a problem management application. It
will assist in tracking problems which have been identified through
notifications emitted from the agents. Information gathered and
maintained for such problems include:
o the set of notifications related to the problem
o the set of resources affected by the problem
o diagnostic conclusions
o one or more recommended actions.
The problem information may be displayed graphically as well as
textually.
LAN NETVIEW MONITOR - LAN NetView Monitor is a performance management
application. LAN NetView Monitor allows system administrators and
capacity planners to monitor system performance (including the
setting of thresholds), analyze performance trends and to perform
tuning and load balancing.
LAN NETVIEW TIE - LAN NetView Tie provides a mechanism for the filtering
and transmission of notifications emitted on the LAN to a NetView*
host. LAN NetView Tie transforms notifications in OSI alarm format
to SNA alert format before forwarding them to a NetView host.
LAN NETVIEW START - LAN NetView Start is a configuration management applica-
tion. LAN NetView Start provides a graphical, object oriented
interface for managing and validating the configuration of OS/2
systems on the LAN. It also provides interfaces required to enable
software distribution, installation and configuration using NetView
DM/2.
Chapter 3. The LAN NetView Family of Products 3-3
CHAPTER 4. LAN NETVIEW AGENTS
___________________________
In Chapter 2, "The LAN NetView Framework" on page 2-1 we discussed the role of
agents in a distributed systems management environment and in Chapter 3, "The
LAN NetView Family of Products" on page 3-1 we described the LAN NetView Agents
and LAN NetView Agents Extended products.
This chapter will provide additional detail and introduce a few new concepts
that are key to understanding the agents and the MIB.
4.1 RESOURCE MANAGER AGENTS
____________________________
Through the LAN NetView Agents and LAN NetView Agents Extended products, IBM
will define objects for the following resource managers:
o the operating system
- OS/2
- DOS V5.0
- DOS V5.0 w/ Microsoft* Windows* V3.1
o LAN Server V3.0
o Communications Manager
o Database Manager
The agents will define objects and their associated attributes, actions and
notifications related to the resource. A summary of these agents and objects
is provided in Appendix A, "LAN NetView MIB Summary" on page A-1.
It is important to note that the different operating system agents were
designed with as much commonality as possible. This allows management
applications to be written to manage any of the operating system environments
with a minimum of operating system specific code. Many of the same object
classes are defined under the different operating system agents.
For example, there are several object classes related to hardware which are
defined by the operating system agents. Therefore, it is possible to
reference the same object class (such as Fixed Disk Drive) from a management
application that is managing both DOS and OS/2 systems.
(C) Copyright IBM Corp. 1992 4-1
4.1.1 RESOURCE MANAGER OBJECTS
The majority of the objects defined by the agents relate to specific physical
or logical resources and the attributes associated with those objects can be
mapped to specific information about those resources. The managing application
addresses these resources as objects. The agent uses whatever API's are made
available by the resource manager to access the resources and the associated
information.
Accessing the attributes is usually accomplished by a managing application
issuing a GET or SET request to the appropriate object. This returns or
modifies the specific attribute. If multiple attributes are involved, then
this would require multiple GET or SET operations.
This is fine for most management applications, but there are some cases where
a slightly different mode of operation is required. In these cases we will
define special objects called Management Support Objects, which is the
subject of the next section.
4.1.2 MANAGEMENT SUPPORT OBJECTS (MONITOR-SCANNER)
In support of the LAN NetView Monitor application or other applications
wishing to gain access to system performance data, the agents have defined
special objects which we will call management support objects. The methods
associated with these objects utilize performance instrumentation provided by
OS/2 V2.0. This instrumentation provides access to low level counters,
timers and control blocks necessary for performance management.
There are several reasons why performance data may need to be handled
differently than other attributes:
o There must be synchronization of the access to different attributes.
A series of GET functions to take a snapshot of multiple attributes would
not be adequate as each would return attribute values from a different
point in time.
o There is a requirement to monitor or scan certain counters/timers.
This provides the capability to generate a notification when certain
thresholds are reached.
o There is a requirement to log or capture certain data over time and at
specific intervals.
OS/2's performance instrumentation provides the system level functions
required to achieve each of the above objectives. However, implementing this
through the standard GET/SET interfaces to the resource manager objects would
be difficult if not impossible.
Therefore a special monitor-scanner object class is provided to provide the
necessary interfaces for a managing application. The monitor-scanner object
will interface directly with OS/2 to provide the functions required.
Chapter 4. LAN NetView Agents 4-2
The performance information can be mapped to attributes associated with
resource manager objects. In fact, the MIBs associated with the OS/2 and LAN
Server agents will define the attributes associated with the monitor-scanner
object. However, a managing application would not issue a GET or a SET to
the resource manager object agent to retrieve or modify these attributes.
Instead, the managing application will CREATE an instance of the
monitor-scanner object. In creating this instance, it will define such
parameters as the specific attributes to monitor, the granularity period (how
often it scans the information), thresholds, schedules and more.
Once the monitor-scanner object is instantiated, the performance data will be
gathered/monitored. Notifications will be generated when thresholds are
exceeded. If a managing application wishes to retrieve the monitored
information, it then issues a specific ACTION which will return the logged
data.
There are other management support objects related to the monitor-scanner and
the log files that it generates. The information related to these objects
and how to access the information they represent will be supplied in the
LAN NetView MIB documentation.
In Appendix A, "LAN NetView MIB Summary" on page A-1 we provide a
summary of the LAN NetView MIBs. We do not specifically cover the
monitor-scanner object. The information it represents is listed as
attributes of the objects defined by the OS/2 and LAN Server agents.
We handled the attributes in this way in order to more easily summarize the
available information. The actual process for accessing the individual
attributes (either through the resource manager object or the monitor scanner
object) is beyond the scope of this white paper.
Chapter 4. LAN NetView Agents 4-3
CHAPTER 5. SOLUTIONS BASED ON LAN NETVIEW AGENTS
______________________________________________
This chapter will provide the reader with a look at the MIB that has been
defined by and is supported by the LAN NetView Agents and LAN NetView Agents
Extended products.
This rich set of object classes will allow applications to be written that
take advantage of the IBM supplied agents. This will relieve application
developers of the requirement to write their own agents and will increase
consistency across applications developed independently.
This chapter should not be considered to be a comprehensive look at all of
the available attributes, actions and notifications defined by the LAN NetView
agents' MIB, but rather a sampling that represents a subset of those
provided.
We will present this information by looking at five primary systems
management functional areas:
o Operations Management
o Configuration Management
o Problem Management
o Performance Management
o Inventory Management
Though most of these areas are addressed in part by IBM LAN NetView
applications, customers may desire additional management applications which
meet their specific needs.
The primary objective of IBM's agent design team was to provide support for
the monitoring and control of the operating systems and subsystems.
The secondary objective was to monitor and control specific resources owned
by the operating systems and subsystems.
Each of these objectives were addressed in light of the five functional areas
listed above.
(C) Copyright IBM Corp. 1992 5-1
5.1 OPERATIONS MANAGEMENT
__________________________
Operations Management functions address the capability to monitor and alter
the operational state of the systems and subsystems within a network. The
primary functions include:
o Monitoring the status of resources
o Querying/changing operational characteristics of resources
o Performing actions on resources
+--- EXAMPLES OF OPERATIONS MANAGEMENT TASKS -------------------------------+
| |
| The following are examples of the types of operational management that |
| would be desired in a distributed OS/2 environment: |
| |
| o Monitoring status of critical systems (LAN Servers, Database Servers, |
| etc.) |
| |
| o Monitoring status of peripheral devices such as printers |
| |
| o Monitoring status of critical processes or threads |
| |
| o Holding or releasing print queues |
| |
| o System shutdown/restart |
| |
+---------------------------------------------------------------------------+
5.1.1 MONITORING THE STATUS OF RESOURCES
The resources within the network that require monitoring can include both
hardware and software.
When monitoring the status of resources within the network, it is desirable
to be able to receive changes in status through unsolicited notifications.
It is equally desirable to be able to explicitly query the status of a
particular resource. Both of these capabilities are supported by the
LAN NetView agents.
The ISO/IEC 10165-2 (X.721): Structure of Management Information - Definition
of Management Information specification defines the state attributes listed
below. The LAN NetView agents will use these states as applicable.
o ADMINISTRATIVE STATE
- the resource is prohibited (locked)
- permitted for existing users (shutting down)
- permitted to perform services for its users (unlocked).
o OPERATIONAL STATE
Chapter 5. Solutions Based on LAN NetView Agents 5-2
- the resource is totally inoperable (disabled),
- partially or fully operable (enabled)
o AVAILABILITY STATE
- test
- failed
- power off
- off line
- off duty
- dependency
- degraded
- not installed
- log full
One or more of the above states may be applicable to a particular
resource at any moment in time.
o USAGE STATE
- the resource is currently not in use (idle)
- in use and has enough capacity to accommodate additional users
(active)
- in use but does not have enough capacity to accommodate additional
users (busy).
In addition, IBM has defined additional states that are resource specific and
are not covered by those defined above.
The following is a list of some of the objects represented by the LAN NetView
agents that will provide status information:
o Hardware Objects
- Machine
- Display
- CPU
- Logical ports
o OS/2 Programming Objects
- Processes
- Threads
o Printing Objects
- Printers
- Queues
- Jobs
o Subsystem Objects
- LAN Server Objects
- LAN Server
- LAN Requester
- Communications Manager Objects
- Configuration File
- APPN Node
- Logical Link
- Transaction Program
- SNA Session
Chapter 5. Solutions Based on LAN NetView Agents 5-3
- Physical Port
- Database Manager Objects
- Database Manager
- Database
- Database Gateway
5.1.2 QUERYING/CHANGING OPERATIONAL CHARACTERISTICS OF RESOURCES
In addition to querying the operational status of a resource, an operations
management program can issue a GET operation to retrieve object attributes
which contain information about the operational characteristics of managed
resources.
The following list provides examples of some of the objects and attributes
that provide operational information. Many attributes can also be altered
through a SET command issued to the agent.
o Logical Volumes : Volume Size, Allocation information, Utilization.
o Monitored Files : Content (CRC value), Size, Last modification
date/time.
o Printer : Current print job, Printer status
o Print Queue : List of printers, Priority, Queue Status, Number of jobs in
the queue
o Spooled Job : Printer name, Position in Queue, Name of user
o LAN Server : Service Statistics, Current Status
o Communications Manager : Status and information for APPN Nodes, Logical
Links, SNA Sessions, Transaction Programs
o Database Manager: Database State (Consistent, Requires back-up,
Roll-forward in progress)
5.1.3 PERFORMING ACTIONS ON RESOURCES
An operational management application should also be able to initiate actions
to be performed by an agent on an object.
The following list provides examples of some of the actions that are defined
and supported by the LAN NetView agents:
o Shutdown/Restart the operating system
o Hold/Release a queue or a job in a queue
o Pause/continue printing
o Pause/continue LAN Server services
o Clear LAN Server statistics
o Activate/deactivate Communications Manager, APPN node
o Activate/deactivate adapter
o Deactivate logical link
o Deactivate LU 6.2 session
o Activate/deactivate Database Manager
o Activate/deactivate a database
o Create/Drop a database.
Chapter 5. Solutions Based on LAN NetView Agents 5-4
5.1.4 OPERATIONS MANAGEMENT SUMMARY
The LAN NetView agents:
o provide access to a wide array of status information
o allow for operational characteristics to be queried and altered
o permit operational actions to be performed on a managed system's hardware,
operating system and supported subsystems.
Chapter 5. Solutions Based on LAN NetView Agents 5-5
5.2 CONFIGURATION MANAGEMENT
_____________________________
Configuration management involves the capability to determine, alter and
track the configuration of systems within the network. These tasks can be
summarized as:
o Retrieving the configuration of selected systems
o Changing configuration parameters on selected systems
o Receiving notifications of configuration changes to selected systems
The LAN NetView agents provide access to both hardware and software
configuration information.
+--- EXAMPLES OF CONFIGURATION MANAGEMENT TASKS ----------------------------+
| |
| The following are examples of the types of configuration management tasks |
| that would be desired in a distributed environment: |
| |
| o Query physical configuration of devices in the network |
| |
| o Query/change system configuration parameters (for example, |
| CONFIG.SYS) |
| |
| o Query/change IBM LAN Server configuration parameters (IBMLAN.INI) |
| |
| o Query Communications Manager configuration files |
| |
| o Query/change Database Manager configuration parameters |
| |
| o Receive notifications of changes to configurations on monitored |
| systems |
| |
+---------------------------------------------------------------------------+
5.2.1 RETRIEVING CONFIGURATION INFORMATION
The following lists summarizes some of the configuration information which
can be retrieved from a managed system running the LAN NetView agents.
o Operating System : Version/Level
o Memory : installed memory, memory allocation (OS/2), expanded extended
memory allocation (DOS), memory configuration virtual memory (WINDOWS)
o Current system : Boot drive , Time/Date
o Code page, Country code
o System parameters (CONFIG.SYS)
o LAN Server : Version/Level, Initialization parameters (IBMLAN.INI),
Run-time parameters
o Communications Manager : Version/Level, List of Configuration Files,
Active Configuration File
o Database Manager : Version/Level, Configuration Information
Chapter 5. Solutions Based on LAN NetView Agents 5-6
5.2.2 CHANGING THE CONFIGURATION
The LAN NetView agents allow a management program to alter various
configuration parameters through a SET operation. The following list
summarizes these capabilities:
o Parameters specified in the CONFIG.SYS file.
o LAN Server : IBMLAN.INI and run-time.
All start-up (IBMLAN.INI) parameters may be set. Selected run-time
parameters may also be set/modified by a management program.
o Database Manager : Catalog/Uncatalog Databases, Create/Delete Database
directory information, Create/Delete Database Connection Services
Information, Create/Delete Node Directory information
o Actions exist for resetting database and database manager configuration
values to defaults.
5.2.3 TRACKING CHANGES TO CONFIGURATIONS
The agents will generate notifications for the creation or deletion of some
resources and will generate notifications for changes to certain attributes
such as configuration parameters.
In addition, there is a 'Monitored File' object class that will allow an
agent to monitor critical files (such as configuration files) and emit
notifications if they are changed.
5.2.4 CONFIGURATION MANAGEMENT SUMMARY
The LAN NetView MIB provides the prerequisite object class definitions to
develop a powerful configuration management application which can access most
configuration parameters within a managed system. The capability to be
alerted to changes to 'monitored files' provides a key function for
identifying changes to configuration files on key systems within the network.
Chapter 5. Solutions Based on LAN NetView Agents 5-7
5.3 PROBLEM MANAGEMENT
_______________________
Problem management involves the monitoring of resources, analyzing
notifications emitted from resources and performing actions to correct, avoid
or circumvent error conditions.
+--- EXAMPLES OF PROBLEM MANAGEMENT TASKS ----------------------------------+
| |
| The following are examples of the types of problem management tasks that |
| may be performed in a distributed environment: |
| |
| o Monitor the 'heartbeat' of critical systems/subsystems |
| |
| o Receiving 'alarms' generated by the LAN Server/ Requester |
| |
| o Receiving 'alarms' associated with the Database Manager |
| |
| o Receiving 'alarms' associated with the Communications Manager |
| |
| o Perform actions to correct, avoid or circumvent error conditions |
| |
+---------------------------------------------------------------------------+
5.3.1 MONITORING RESOURCES
Agents can send 'heartbeat' notifications on behalf of monitored resources.
This allows for recognition that an agent is or is not operable.
Agents will send notifications as objects are created or deleted. For
instance, a notification will be generated when the Communications Manager
becomes active on a node.
5.3.2 ANALYZING RECEIVED NOTIFICATIONS
It is the responsibility of the managing application to analyze the
notifications it receives from agents in order to help determine the cause of
failure.
Examples of the type of notifications that are generated by the agents on
behalf of the managed resources are listed below:
o LAN Server
- Quality of service alarms : Network I/O error threshold reached, disk
drive nearing capacity, audit log full, etc.
- Equipment alarms : Fault Tolerance system fixed a bad sector, Fault
Tolerance system detected a difference between the contents of the
primary and the secondary partitions of a mirrored fixed-disk drive,
etc.
- Environmental Alarms : LAN Server has detected multiple failed
password-entry, multiple unauthorized resource-access attempts, etc..
o LAN Requester
Chapter 5. Solutions Based on LAN NetView Agents 5-8
- Quality of service alarm : Error log has reached its maximum size,
redirecter has reached the configured threshold for a specified
resource
- Processing alarm : Internal processing error, resources not
available, etc.
Detailed information about each error condition will be transmitted in
the notification.
o Communications Manager
- APPN node : Insufficient storage for intermediary session setup (only
by APPN network node), SNA protocol error, etc.
- LAN adapter used for SNA : open failure detected by token-ring lobe ,
CSMACD bus inoperative
- SDLC adapter used for SNA : Link error due to the remote link station
address, link error due to bad line, etc.
Error conditions that normally generate SNA alerts in the Communications
Manager will cause the CM agent to generate a notification to a managing
system.
The notification carried information about the event ( probable cause,
specific problem, severity, proposed repair actions), and the problem
data (product IDs, alert type, failures cause).
o Database Manager
- Processing Error Alarm : Internal processing errors
- State Changes
- Creation/Deletion of Objects
Notifications will include the SQL return code if applicable.
5.3.3 CORRECTIVE ACTIONS
Many of the capabilities discussed under other functional areas such as
operations management and configuration management apply equally as well
within problem management. Once a problem has been detected and the cause
determined, operations or actions are typically performed to carry out the
problem resolution.
For example, a configuration change might be required with a system restart
to follow. These capabilities are addressed in the sections relating to
configuration and operations management.
5.3.4 PROBLEM MANAGEMENT SUMMARY
The LAN NetView agents provide a rich set of resource monitoring and
notification capabilities across all resources. The capabilities exist to
perform corrective actions once the proper resolution has been determined.
Chapter 5. Solutions Based on LAN NetView Agents 5-9
5.4 PERFORMANCE MANAGEMENT
___________________________
Performance management involves the monitoring of resources to identify
potential or real performance problems, isolate the causes and to correct the
situations through load balancing and reconfiguration.
+--- EXAMPLES OF PERFORMANCE MANAGEMENT TASKS ------------------------------+
| |
| The following are examples of the types of performance management tasks |
| that may be performed in a distributed environment: |
| |
| o Tracking the current resource utilization on critical systems (LAN |
| servers, DB Servers) |
| |
| - CPU |
| |
| - Memory |
| |
| - Disk |
| |
| o Monitoring CPU utilization by thread to identify 'runaway' |
| applications |
| |
| o Perform actions on subsystems to correct/alleviate conditions |
| |
| o Reconfigure systems to assist with load balancing |
| |
+---------------------------------------------------------------------------+
5.4.1 MONITORING SYSTEMS AND ISOLATING PERFORMANCE PROBLEMS
In monitoring performance as well as isolating potential problems, it is key
to be able to receive notifications as thresholds on performance related
resources are reached. It must also be possible to continually monitor or
GET values of key performance indicators such as counters and timers.
The list below shows some of the information that may be monitored through
the LAN NetView agents.
o The OS/2 CPU : Number of interrupts, CPU idle time
o The OS/2 Memory : Swapping statistics, number of page faults
o The OS/2 Disk : Cache utilization
o The OS/2 File I/O : Number of open files
o Disk I/O : Number of bytes read/written from disk.
o Logical serial port : Time spent reading/writing
o OS/2 thread : CPU used by thread, time spent waiting.
Chapter 5. Solutions Based on LAN NetView Agents 5-10
o Printer I/O : Number of write operations
o LAN Server : The activity of the server in read and write operations, use
of buffers
As key performance indicators are tracked, management programs can be alerted
as thresholds are approached.
A performance management application could then utilize operations and
configuration management functions to perform corrective actions such as
reconfiguration and/or load balancing.
5.4.2 PERFORMANCE MANAGEMENT SUMMARY
It was not feasible to list here all of the attributes that can be used in
performance management. However, the MIB provides access to a large number
of counters, timers, control blocks and other information that will allow for
powerful performance management applications to be written.
Chapter 5. Solutions Based on LAN NetView Agents 5-11
5.5 INVENTORY MANAGEMENT
_________________________
Tracking inventory in a large network can be a difficult task.
Workstations are constantly being added, removed, upgraded and reconfigured.
Software inventory can be even more dynamic as different service levels of
programs may exist and be applied independently.
+--- EXAMPLES OF INVENTORY MANAGEMENT --------------------------------------+
| |
| The following are examples of the types of inventory management tasks |
| that may be desired in a distributed environment: |
| |
| o Collecting software vital product data from known systems |
| |
| o Collecting hardware vital product data from known systems |
| |
| o Discovery of new nodes entering the network |
| |
+---------------------------------------------------------------------------+
An inventory management program can retrieve vital product data for all
subsystems supported by the LAN NetView agents.
Information can be gathered for software and hardware. The list below
provides examples of the type of information available through the LAN NetView
agents that can be used for inventory management.
o Software
- The product name, version and the CSD of the Operating System
- The product name, version and the CSD of the OS/2 LAN Server, the
computer name and the domain name.
- The product name, version and the CSD of the Database Manager and of
the Communication Manager
o Hardware
- The identifier of the machine specified by the manufacturer
- The Machine type, location, owner, contact information : this
information is specified during system installation.
- The display type
- The CPU type, the co-processor type
- The fixed disk and diskette drive size and capacity
- The keyboard identifier and type
- The MCA adapter identifier
Chapter 5. Solutions Based on LAN NetView Agents 5-12
5.5.1 DISCOVERY OF NEW NODES
The LAN NetView Manage product provides topology and discovery services.
If new nodes that enter the network contain the LAN NetView agents,
they will be identified to the managing system. Other nodes, such as those
running TCP/IP will also be discovered by LAN NetView Manage. An inventory
management application residing on the managing system could then query the
software and hardware as described above to add the information to an
inventory database.
5.5.2 INVENTORY MANAGEMENT SUMMARY
The LAN NetView agents provide access of both hardware and software vital
product data to management applications. This information is key to the
development and maintenance of an inventory management database.
Chapter 5. Solutions Based on LAN NetView Agents 5-13
5.6 SUMMARY OF AGENT BASED SOLUTIONS
_____________________________________
This chapter provided a glimpse of the capabilities of the LAN NetView MIB
represented by the LAN NetView Agents and LAN NetView Agents Extended products.
Additional information will be provided in the appendix to this document.
However, to fully appreciate all of the building blocks that have been made
available for systems management applications using the LAN NetView agents, we
refer you to the LAN NetView documentation.
Chapter 5. Solutions Based on LAN NetView Agents 5-14
APPENDIX A. LAN NETVIEW MIB SUMMARY
______________________________________________
This appendix presents six tables that summarize the LAN NetView
MIB.
THIS IS NOT A COMPLETE REFERENCE OF THE LAN NETVIEW MIB. RATHER IT IS INTENDED
TO PROVIDE THE READER WITH AN OVERVIEW OF THE ORGANIZATION OF THE MIB AND
EXAMPLES OF THE OBJECTS, ATTRIBUTES, ACTIONS AND NOTIFICATIONS IT DEFINES.
PLEASE REFER TO THE LAN NETVIEW DOCUMENTATION FOR COMPLETE DETAILS ON THE MIB.
The tables are organized as follows:
TABLE 1 OS/2 Agent
TABLE 2 DOS Agent
TABLE 3 DOS/Windows Agent
TABLE 4 LAN Server Agent
TABLE 5 Communications Manager Agent
TABLE 6 Database Manager Agent
Each table lists the defined objects for the particular agent, a summary of
the attributes, actions and notifications. Under the summary of attributes
the following information will be presented:
o The number of attributes defined for the object
o The number of attributes the object has inherited from other classes
(this is in addition to the number defined).
o Examples of attributes by group, if applicable.
+--- COMMON OBJECTS --------------------------------------------------------+
| |
| It should be observed that the OS/2, DOS and DOS/Windows agents include |
| many common object definitions. This allows management applications to |
| easily access these different platforms and present the common |
| information without requiring platform specific code. |
| |
+---------------------------------------------------------------------------+
(C) Copyright IBM Corp. 1992 A-1
A.1 OS/2 AGENT
_______________
The OS/2 Agent is part of the LAN NetView Agents product. It defines 20
object classes that represent OS/2 objects as well as related hardware.
Appendix A. LAN NetView MIB Summary A-2
+---------------------------------------------------------------------------+
| Table A-1 (Page 1 of 13). Managed Objects for OS/2 AGENT |
+------------+------------------------------+--------------+----------------+
| OBJECT | SUMMARY OF ATTRIBUTES | ACTIONS | NOTIFICATIONS |
+------------+------------------------------+--------------+----------------+
| OS/2 | Number of defined attributes | Restart | Object |
| | : 109 | system | creation |
| | | | |
| | Number of inherited | Shutdown | Object |
| | attributes : 21 | system | deletion |
| | | | |
| | o Attribute groups | | Attribute |
| | | | value change |
| | - Session parameters | | |
| | | | State change |
| | Examples: maximum # | | |
| | of VDM sessions, | | Agent |
| | maximum # of PM | | Heartbeat |
| | sessions | | |
| | | | |
| | - Memory information | | |
| | | | |
| | Example: page size, | | |
| | total available | | |
| | memory, total | | |
| | physical memory | | |
| | | | |
| | - Current system | | |
| | information | | |
| | | | |
| | Examples: boot | | |
| | drive, maximum path | | |
| | length, time date | | |
| | | | |
| | - Current country | | |
| | information | | |
| | | | |
| | Examples: code page, | | |
| | country code | | |
| | | | |
| | - Initialization | | |
| | parameters | | |
| | | | |
| | These attributes | | |
| | will return values | | |
| | of parameters in | | |
| | CONFIG.SYS such as | | |
| | Device, DOS, | | |
| | Buffers, DiskCache | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-3
+------------+------------------------------+--------------+----------------+
| OS/2 | o Other attributes | | |
| (continued)| | | |
| | - Attributes for | | |
| | performance | | |
| | monitoring of | | |
| | memory, CPU, disk, | | |
| | file I/O. | | |
| | | | |
| | Examples: number of | | |
| | page faults, number | | |
| | of interrupts | | |
| | raised, number of | | |
| | files open. | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | - Product attributes | | |
| | | | |
| | Examples: product | | |
| | name, product | | |
| | version, current CSD | | |
| | level | | |
| | | | |
| | - State/status | | |
| | | | |
| | Examples: usage | | |
| | state, operational | | |
| | state, availability | | |
| | status | | |
| | | | |
| | - Agent information | | |
| | | | |
| | Examples: agent | | |
| | version, start time, | | |
| | heartbeat rate | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-4
+------------+------------------------------+--------------+----------------+
| Machine | Number of defined attributes | | Object |
| | : 15 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 11 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | - Information entered | | |
| | by the user during | | |
| | the installation | | |
| | | | |
| | Examples: the | | |
| | contact, the | | |
| | location, the owner, | | |
| | the type, the serial | | |
| | number | | |
| | | | |
| | - Information obtained | | |
| | from the machines | | |
| | ROM : the model ID | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
| Physical | Number of defined attributes | | Object |
| Keyboard | : 2 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 11 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Keyboard type and ID | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-5
+------------+------------------------------+--------------+----------------+
| Display | Number of defined attributes | | Object |
| | : 4 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 11 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Adapter memory, adapter | | |
| | type, display ID, | | |
| | display type | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
| Micro | Number of defined | | Object |
| Channel* | attributes: 1 | | creation |
| Adapter | | | |
| | Number of inherited | | Object |
| | attributes : 12 | | deletion |
| | | | |
| | o Defined attribute | | |
| | | | |
| | Adapter ID | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
| | | | |
| | Slot ID | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-6
+------------+------------------------------+--------------+----------------+
| Floppy | Number of defined attributes | | Object |
| Drive | : 2 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 12 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Floppy capacity and | | |
| | floppy size | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
| | | | |
| | Physical storage ID | | |
+------------+------------------------------+--------------+----------------+
| Fixed Disk | Number of defined attributes | | Object |
| Drive | : 11 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 12 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Fixed disk capacity | | |
| | | | |
| | Number of sectors per | | |
| | cylinder, number of | | |
| | cylinders on a fixed | | |
| | disk | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
| | | | |
| | Physical storage ID | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-7
+------------+------------------------------+--------------+----------------+
| Processor | Number of defined attributes | | Object |
| | : 2 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 11 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Processor Id, processor | | |
| | type | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
| Co-proces- | Number of defined attributes | | Object |
| sor | : 2 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 11 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Co-processor Id, | | |
| | co-processor type | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-8
+------------+------------------------------+--------------+----------------+
| Logical | Number of defined attributes | | Object |
| Parallel | : 3 | | creation |
| Port | | | |
| | Number of inherited | | Object |
| | attributes : 13 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Infinite retry (on/off), | | |
| | port status | | |
| | (timeOUT,ioError), port | | |
| | timeOut value (seconds) | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
| | | | |
| | Logical device driver, | | |
| | logical device name | | |
+------------+------------------------------+--------------+----------------+
| Logical | Number of defined attributes | | Object |
| Serial | : 21 | | creation |
| Port | | | |
| | Number of inherited | | Object |
| | attributes : 13 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Communication status, | | |
| | modem input/output | | |
| | signal, | | |
| | | | |
| | Min/max BitRate, | | |
| | read/write TimeOut | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
| | | | |
| | Logical device driver, | | |
| | logical device name | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-9
+------------+------------------------------+--------------+----------------+
| Logical | Number of defined attributes | | Object |
| Pointing | : 1 | | creation |
| Device | | | |
| | Number of inherited | | Object |
| | attributes : 13 | | deletion |
| | | | |
| | o Defined attribute | | |
| | | | |
| | pointing device info | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
| Logical | Number of defined attributes | | Object |
| Volume | : 10 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 13 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Local or remote, volume | | |
| | available space, volume | | |
| | name, volume size, | | |
| | volume serial number | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-10
+------------+------------------------------+--------------+----------------+
| File | Number of defined attributes | | |
| | : 7 | | |
| | | | |
| | Number of inherited | | |
| | attributes : 3 | | |
| | | | |
| | Defined attributes | | |
| | | | |
| | File Name, time spent | | |
| | reading and writing to | | |
| | the file, | | |
| | | | |
| | Number of reads and | | |
| | writes to the file | | |
| | | | |
| | Number of bytes read | | |
| | from or written to the | | |
| | file | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-11
+------------+------------------------------+--------------+----------------+
| OS/2 | Number of defined attributes | | Object |
| Process | : 7 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 13 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Process Status, parent | | |
| | process Id, process | | |
| | type, number of thread | | |
| | control blocks | | |
| | | | |
| | Number of run-time | | |
| | libraries, list of | | |
| | run-time linked | | |
| | libraries | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status, | | |
| | process ID, process name | | |
+------------+------------------------------+--------------+----------------+
| Monitored | Number of defined attributes | | Object |
| File | : 7 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 11 | | deletion |
| | | | |
| | o Defined attributes | | State change |
| | | | |
| | Monitored file name, | | Attribute |
| | file size, time stamp, | | value change |
| | | | |
| | file Attributes, CRC | | Processing |
| | (the signature of the | | error alarm |
| | file) | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-12
+------------+------------------------------+--------------+----------------+
| OS/2 | Number of defined attributes | | |
| Thread | : 12 | | |
| | | | |
| | Number of inherited | | |
| | attributes : 13 | | |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Thread state, user time, | | |
| | system time, thread | | |
| | slot, sleep Id | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status, | | |
| | thread ID, thread | | |
| | priority | | |
+------------+------------------------------+--------------+----------------+
| Spooled | Number of defined attributes | Continue | Object |
| Printer | : 13 | | creation |
| | | Delete | |
| | Number of inherited | current job | Object |
| | attributes : 11 | | deletion |
| | | Pause | |
| | o Defined attributes | | |
| | | Restart job | |
| | Printer status, printer | | |
| | name, current print job | | |
| | Id, | | |
| | | | |
| | List of installed device | | |
| | drivers supported and | | |
| | list installed device | | |
| | drivers | | |
| | | | |
| | Time printing | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-13
+------------+------------------------------+--------------+----------------+
| OS/2 | Number of defined attributes | Hold queue | Object |
| Spooler | : 17 | | creation |
| Queue | | Release | |
| | Number of inherited | queue | Object |
| | attributes : 11 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Connected printers, | | |
| | device driver, queue | | |
| | priority | | |
| | | | |
| | Separator file, queue | | |
| | start time, queue until | | |
| | time | | |
| | | | |
| | List queue processors, | | |
| | queue name, queue | | |
| | comment, | | |
| | | | |
| | Queue description, queue | | |
| | priority, queue status, | | |
| | queue type | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-14
+------------+------------------------------+--------------+----------------+
| OS/2 | Number of defined attributes | Copy the job | Object |
| Spooler | : 15 | | creation |
| Job | | Release the | |
| | Number of inherited | job | Object |
| | attributes : 11 | | deletion |
| | | Hold the job | |
| | o Defined attributes | | |
| | | | |
| | Job priority | | |
| | | | |
| | Job Id, job size, | | |
| | document name, data | | |
| | type, job status | | |
| | | | |
| | Device driver data, | | |
| | device driver name | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-15
A.2 DOS AGENT
______________
The DOS Agent is part of the LAN NetView Agents product. It defines 13 object
classes that represent DOS objects and related hardware.
Appendix A. LAN NetView MIB Summary A-16
+---------------------------------------------------------------------------+
| Table A-2 (Page 1 of 7). Managed Objects for DOS AGENT |
+------------+------------------------------+--------------+----------------+
| OBJECT | SUMMARY OF ATTRIBUTES | ACTIONS | NOTIFICATIONS |
+------------+------------------------------+--------------+----------------+
| DOS | Number of defined attributes | Restart | Object |
| | : 28 | | creation |
| | | Shutdown | |
| | Number of inherited | | Object |
| | attributes : 17 | | deletion |
| | | | |
| | o Attribute groups | | State change |
| | | | |
| | Current DOS country | | Agent |
| | information | | heartbeat |
| | | | |
| | Examples: code page, | | |
| | country code | | |
| | | | |
| | o Other attributes | | |
| | | | |
| | Memory management | | |
| | | | |
| | Examples: allocation | | |
| | strategy, extended | | |
| | memory, | | |
| | expended memory, total | | |
| | physical memory, total | | |
| | available memory | | |
| | | | |
| | Boot drive, net status, | | |
| | machine name, set | | |
| | version | | |
| | | | |
| | Printer setup, current | | |
| | tasks, link flag | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | - Product attributes | | |
| | | | |
| | Examples: product | | |
| | name, product | | |
| | version, current CSD | | |
| | level | | |
| | | | |
| | - State/status | | |
| | | | |
| | Examples: usage | | |
| | state, operational | | |
| | state, availability | | |
| | status | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-17
+------------+------------------------------+--------------+----------------+
| Machine | Number of defined attributes | | Object |
| | : 11 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 11 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | - Information entered | | |
| | by the user during | | |
| | the installation | | |
| | | | |
| | Examples: the | | |
| | contact, the | | |
| | location, the owner, | | |
| | the type, the serial | | |
| | number | | |
| | | | |
| | - Information obtained | | |
| | from the machines | | |
| | ROM : the model ID | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
| Physical | Number of defined attributes | | Object |
| keyboard | : 2 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 11 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Keyboard type and ID | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-18
+------------+------------------------------+--------------+----------------+
| Display | Number of defined attributes | | Object |
| | : 4 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 11 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Adapter memory, adapter | | |
| | type, display ID, | | |
| | display type | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
| Micro | Number of defined | | Object |
| Channel | attributes: 1 | | creation |
| Adapter | | | |
| | Number of inherited | | Object |
| | attributes : 12 | | deletion |
| | | | |
| | o Defined attribute | | |
| | | | |
| | Adapter ID | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
| | | | |
| | Slot ID | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-19
+------------+------------------------------+--------------+----------------+
| Floppy | Number of defined | | Object |
| Drive | attributes: 2 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 12 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Floppy capacity and | | |
| | floppy size | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
| | | | |
| | Physical storage ID | | |
+------------+------------------------------+--------------+----------------+
| Fixed Disk | Number of defined attributes | | Object |
| Drive | : 5 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 12 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Number of bytes per | | |
| | sector | | |
| | | | |
| | Number of sector per | | |
| | cylinder, number of | | |
| | cylinders on a fixed | | |
| | disk | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
| | | | |
| | Physical storage ID | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-20
+------------+------------------------------+--------------+----------------+
| Processor | Number of defined attributes | | Object |
| | : 2 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 11 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Processor Id, processor | | |
| | type | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
| Co-proces- | Number of defined attributes | | Object |
| sor | : 2 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 11 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | co-processor Id, | | |
| | co-processor type | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
| Logical | Number of defined attributes | | Object |
| Parallel | : 3 | | creation |
| Port | | | |
| | Number of inherited | | Object |
| | attributes : 11 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Infinite retry (on/off), | | |
| | port status | | |
| | (timeOUT,ioError), port | | |
| | timeout value (seconds) | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-21
+------------+------------------------------+--------------+----------------+
| Logical | Number of defined attributes | | Object |
| Serial | : 13 | | creation |
| Port | | | |
| | Number of inherited | | Object |
| | attributes : 13 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Examples: modem | | |
| | input/output Signal, | | |
| | current BitRate, parity, | | |
| | transmitDataStatus, | | |
| | readTimeOut, | | |
| | writeTimeOut | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
| Logical | Number of defined attributes | | Object |
| Volume | : 5 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 13 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Examples: local or | | |
| | Remote, volume available | | |
| | space, volume name | | |
| | | | |
| | volume Size, file system | | |
| | Id, volume serial number | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-22
+------------+------------------------------+--------------+----------------+
| Logical | Number of defined attributes | | Object |
| Pointing | : 1 | | creation |
| Device | | | |
| | Number of inherited | | Object |
| | attributes : 13 | | deletion |
| | | | |
| | o Defined attribute | | |
| | | | |
| | pointing device Info | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-23
A.3 DOS/WINDOWS AGENT
______________________
The DOS/Windows Agent is part of the LAN NetView Agents product. It defines
14 object classes that represent DOS/Windows objects and related hardware.
Appendix A. LAN NetView MIB Summary A-24
+---------------------------------------------------------------------------+
| Table A-3 (Page 1 of 3). Managed Objects for WINDOWS AGENT |
+------------+------------------------------+--------------+----------------+
| OBJECT | SUMMARY OF ATTRIBUTES | ACTIONS | NOTIFICATIONS |
+------------+------------------------------+--------------+----------------+
| Microsoft | Number of defined attributes | Shutdown | |
| Windows | : 52 | | |
| | | | |
| | Number of inherited | | |
| | attributes : 17 | | |
| | | | |
| | o Attributes groups | | |
| | | | |
| | Startup country | | |
| | information | | |
| | | | |
| | Examples: init time | | |
| | format, init country | | |
| | code, init measurement | | |
| | system | | |
| | | | |
| | o Other parameters | | |
| | | | |
| | Total memory, initial | | |
| | virtual memory, | | |
| | | | |
| | Initial OEM font file, | | |
| | initial network driver, | | |
| | initial display driver | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | - Product attributes | | |
| | | | |
| | Examples: product | | |
| | name, product | | |
| | version, current CSD | | |
| | level | | |
| | | | |
| | - State/status | | |
| | | | |
| | Examples: usage | | |
| | state, operational | | |
| | state, availability | | |
| | status | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-25
+------------+------------------------------+--------------+----------------+
| Logical | Number of defined attributes | | Object |
| Parallel | : 3 | | creation |
| Port | | | |
| | Number of inherited | | Object |
| | attributes : 13 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Infinite retry (on/off), | | |
| | port status | | |
| | (timeOUT,ioError), port | | |
| | timeOut value (seconds) | | |
+------------+------------------------------+--------------+----------------+
| Logical | Number of defined attributes | | Object |
| Serial | : 7 | | creation |
| Port | | | |
| | Number of inherited | | Object |
| | attributes : 13 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Examples: modem | | |
| | input/output signal, | | |
| | current BitRate, parity, | | |
| | transmitDataStatus, | | |
| | readTimeOut, | | |
| | writeTimeOut | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-26
+------------+------------------------------+--------------+----------------+
| Logical | Number of defined attributes | | Object |
| Pointing | : 1 | | creation |
| Device | | | |
| | Number of inherited | | Object |
| | attributes : 13 | | deletion |
| | | | |
| | o Defined attribute | | |
| | | | |
| | pointing Device Info | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
| Windows | Number of defined attributes | | Object |
| Spooler | : 4 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 12 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Examples: active | | |
| | printer, inactive | | |
| | printer, print manager | | |
| | | | |
| | spooler name | | |
+------------+------------------------------+--------------+----------------+
| Process | Number of defined attributes | | Object |
| | : 2 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 11 | | deletion |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Process Id, process name | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | State/status | | |
| | | | |
| | Examples: usage state, | | |
| | operational state, | | |
| | availability status | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-27
A.4 LAN SERVER AGENT
_____________________
The LAN Server Agent is part of both the LAN NetView Agents and LAN NetView
Agents Extended products. The LAN Requester object classes are shipped
with the LAN NetView Agents product, however the LAN Server and LAN Server
Connection classes require the LAN NetView Agents Extended product. There
are three object classes representing the LAN Server, Requester and the
connections between them.
Appendix A. LAN NetView MIB Summary A-28
+---------------------------------------------------------------------------+
| Table A-4 (Page 1 of 8). Managed Objects for LAN SERVER AGENT |
+------------+------------------------------+--------------+----------------+
| OBJECT | SUMMARY OF ATTRIBUTES | ACTIONS | NOTIFICATIONS |
+------------+------------------------------+--------------+----------------+
| LAN Server | Number of defined attributes | Clear | Quality of |
| | : 175 | statistics | service alarm |
| | | | |
| | Number of inherited | Pause | Equipment |
| | attributes : 12 | | alarm |
| | | Continue | |
| | o Attribute groups | | Processing |
| | | Activate | error alarm |
| | - Server information | | |
| | | Deactivate | Environmental |
| | Examples: component | | alarm |
| | ID, current CSD | | |
| | level, product name, | | State change |
| | product version, | | |
| | run-time computer | | Object |
| | name, run-time | | creation |
| | domain name | | |
| | | | Object |
| | - Server initial | | deletion |
| | system configuration | | |
| | | | |
| | Examples: network | | |
| | I/O ratio, | | |
| | | | |
| | The free space of | | |
| | the disk before | | |
| | before notifying the | | |
| | administrator | | |
| | | | |
| | The number of | | |
| | invalid l/O before | | |
| | notifying the | | |
| | administrator | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-29
+------------+------------------------------+--------------+----------------+
| LAN Server | o Attribute groups | | |
| | (continued) | | |
| | | | |
| | - Server initial | | |
| | capacity | | |
| | configuration | | |
| | | | |
| | Examples: maximum | | |
| | audit file size, | | |
| | | | |
| | The number of | | |
| | connections to | | |
| | netnames allowed | | |
| | | | |
| | The maximum files | | |
| | locks active. | | |
| | | | |
| | - Server initial | | |
| | tunable config | | |
| | | | |
| | Examples: | | |
| | configuration of | | |
| | buffers, heuristics | | |
| | | | |
| | - Server run-time | | |
| | system configuration | | |
| | | | |
| | Examples: network | | |
| | I/O ratio, | | |
| | | | |
| | The free space of | | |
| | disk before | | |
| | notifying | | |
| | administrator | | |
| | | | |
| | The number of | | |
| | invalid logons | | |
| | before notifying | | |
| | administrator | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-30
+------------+------------------------------+--------------+----------------+
| LAN Server | o Attribute groups | | |
| | (continued) | | |
| | | | |
| | - Server run-time | | |
| | capacity | | |
| | configuration | | |
| | | | |
| | Examples: the | | |
| | maximum audit file | | |
| | size, the maximum | | |
| | files locks active | | |
| | | | |
| | number of | | |
| | connections to | | |
| | netnames allowed | | |
| | | | |
| | - Server run-time | | |
| | tunable config | | |
| | | | |
| | Examples: the | | |
| | configuration of | | |
| | buffers, heuristics | | |
| | | | |
| | - Server statistics | | |
| | | | |
| | Examples: the number | | |
| | of server file and | | |
| | named pipe opens, | | |
| | | | |
| | The number of server | | |
| | session starts, | | |
| | auto-disconnects, | | |
| | errored out, | | |
| | violations, access | | |
| | permission errors. | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-31
+------------+------------------------------+--------------+----------------+
| LAN Server | o Other attributes | | |
| | | | |
| | - Entry package | | |
| | attributes | | |
| | | | |
| | Examples: number of | | |
| | user sessions with | | |
| | the server, | | |
| | configuration of | | |
| | requester buffers, | | |
| | number of different | | |
| | reads / writes | | |
| | (small, multiplex, | | |
| | raws). | | |
| | | | |
| | - Advanced package | | |
| | attributes | | |
| | | | |
| | Examples: number of | | |
| | transactions | | |
| | processed by the | | |
| | server, | | |
| | configuration of | | |
| | requester buffers, | | |
| | number of different | | |
| | reads/writes (small, | | |
| | multiplex, raws). | | |
| | | | |
| | o Attributes inherited | | |
| | | | |
| | Product name, product | | |
| | version, current CSD | | |
| | level | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-32
+------------+------------------------------+--------------+----------------+
| LAN | Number of defined attributes | Clear | Quality of |
| Requester | : 144 | statistics | service alarm |
| | | | |
| | Number of inherited | Pause | Equipment |
| | attributes : 12 | | alarm |
| | | Continue | |
| | o Attribute groups | | Processing |
| | | Activate | error alarm |
| | - Requester | | |
| | information | Deactivate | State Change |
| | | | |
| | Examples: component | | Object |
| | ID, current CSD | | creation |
| | level, product name | | |
| | product version, | | Object |
| | run-time computer | | deletion |
| | name, run-time | | |
| | domain name, user | | |
| | name | | |
| | | | |
| | - Requester initial | | |
| | system configuration | | |
| | | | |
| | Examples: initial | | |
| | services to start, | | |
| | list names of | | |
| | networks on which | | |
| | the requester runs, | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-33
+------------+------------------------------+--------------+----------------+
| LAN | o Attribute groups | | |
| Requester | (continued) | | |
| | | | |
| | - Requester initial | | |
| | capacity | | |
| | configuration | | |
| | | | |
| | Examples: the list | | |
| | of services that can | | |
| | be start on the | | |
| | requester, the | | |
| | number of buffers | | |
| | allocated for | | |
| | receiving datagrams. | | |
| | | | |
| | - Server initial | | |
| | tunable | | |
| | configuration | | |
| | | | |
| | Examples: the | | |
| | configuration of | | |
| | buffers, heuristics | | |
| | | | |
| | - Requester run-time | | |
| | system configuration | | |
| | | | |
| | Examples: initial | | |
| | services to start, | | |
| | list names of | | |
| | networks on which | | |
| | the requester runs | | |
| | | | |
| | - Requester run-time | | |
| | capacity | | |
| | configuration | | |
| | | | |
| | Examples: the number | | |
| | of services that can | | |
| | be start on the | | |
| | requester, the | | |
| | number of buffers | | |
| | allocated for | | |
| | receiving datagrams. | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-34
+------------+------------------------------+--------------+----------------+
| LAN | o Attribute groups | | |
| Requester | (continued) | | |
| | | | |
| | - Server run-time | | |
| | tunable config | | |
| | | | |
| | Examples: the | | |
| | configuration of | | |
| | buffers, heuristics | | |
| | | | |
| | - Requester statistics | | |
| | | | |
| | Examples: the number | | |
| | of NCB issued | | |
| | (redirecter, server, | | |
| | application) | | |
| | | | |
| | The number of NCB | | |
| | failed (redirecter, | | |
| | server, application) | | |
| | | | |
| | - Other attributes | | |
| | | | |
| | The name of the | | |
| | primary domain | | |
| | controller for this | | |
| | machine | | |
| | | | |
| | If the redirecter is | | |
| | paused, if the | | |
| | redirecter for disks | | |
| | is paused | | |
| | | | |
| | If the redirection | | |
| | for spool device is | | |
| | paused | | |
| | | | |
| | - Attributes inherited | | |
| | | | |
| | Product name, | | |
| | product version, | | |
| | current CSD level | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-35
+------------+------------------------------+--------------+----------------+
| Server | Number of defined attributes | | |
| connection | : 8 | | |
| | | | |
| | Number of inherited | | |
| | attributes : 11 | | |
| | | | |
| | o Defined Attributes | | |
| | | | |
| | The name of the user at | | |
| | the client machine that | | |
| | made the session, | | |
| | | | |
| | The number of seconds a | | |
| | session has been active, | | |
| | idle | | |
| | | | |
| | The number of | | |
| | connections that have | | |
| | been made during the | | |
| | session | | |
| | | | |
| | o Attributes inherited | | |
| | | | |
| | Partner connection, | | |
| | connection ID | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-36
A.5 COMMUNICATIONS MANAGER AGENT
_________________________________
The Communications Manager agent is part of the LAN NetView Agents Extended
product. It defines 14 object classes for use by management applications.
Appendix A. LAN NetView MIB Summary A-37
+---------------------------------------------------------------------------+
| Table A-5 (Page 1 of 8). Managed Objects for COMMUNICATION MANAGER AGENT |
+------------+------------------------------+--------------+----------------+
| OBJECT | SUMMARY OF ATTRIBUTES | ACTIONS | NOTIFICATIONS |
+------------+------------------------------+--------------+----------------+
| Comm. | Number of defined | Activate | Object |
| manager | attributes: 1 | | creation |
| | | Deactivate | |
| | Number of inherited | | Object |
| | attributes : 20 | Deactivate | deletion |
| | | when no | |
| | o Defined attribute | users | State change |
| | | | |
| | Default configuration | Change back | Attribute |
| | file | | value change |
| | | Change over | |
| | o Inherited attributes | | |
| | | | |
| | Product version, product | | |
| | name, current CSD level, | | |
| | prior CSD level | | |
| | | | |
| | Usage state, operational | | |
| | State, availability | | |
| | status | | |
| | | | |
| | Activate, deactivate | | |
+------------+------------------------------+--------------+----------------+
| Config. | Number of defined attributes | | |
| file | : 3 | | |
| | | | |
| | Number of inherited | | |
| | attributes : 3 | | |
| | | | |
| | o Defined attribute | | |
| | | | |
| | Configuration file name, | | |
| | is active, is default | | |
| | | | |
| | o Inherited attribute | | |
| | | | |
| | Operational state | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-38
+------------+------------------------------+--------------+----------------+
| APPN* | Number of defined attributes | Activate | State change |
| Network | : 3 | | |
| Node | | Deactivate | Communications |
| | Number of inherited | | alarm |
| | attributes : 21 | Deactivate | |
| | | when no | Object |
| | o Defined attribute | users | creation |
| | | | |
| | Examples: procedural | Change back | Object |
| | status, route additional | | deletion |
| | resistance | Change over | |
| | | | Attribute |
| | o Inherited attributes | Activate | value change |
| | | with | |
| | Examples: usage state, | parameters | |
| | operational state, | | |
| | availability status | Deactivate | |
| | | with | |
| | SNA node name, dependent | parameters | |
| | LU list | | |
+------------+------------------------------+--------------+----------------+
| APPN End | Number of defined attributes | Activate | State change |
| Node | : 1 | | |
| | | Deactivate | Communications |
| | Number of inherited | | alarm |
| | attributes : 20 | Change back | |
| | | | |
| | o Defined Attributes | Change over | |
| | | | |
| | Network node server | Activate | |
| | pointer | with | |
| | | parameters | |
| | o Inherited attributes | | |
| | | Deactivate | |
| | Examples: usage state, | with | |
| | operational state, | parameters | |
| | availability status | | |
| | | Deactivate | |
| | SNA node name, dependent | when no | |
| | LU list | users | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-39
+------------+------------------------------+--------------+----------------+
| Logical | Number of defined attributes | Change back | Attribute |
| Unit 6.2 | : 3 | | value Change |
| | | Change over | |
| | Number of inherited | | Object |
| | attributes : 22 | Activate | creation |
| | | | |
| | o Defined Attributes | Deactivate | Object |
| | | | deletion |
| | Default LU, active | Deactivate | |
| | partner LU list, LU | with | State change |
| | alias | parameters | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | Usage state, operational | | |
| | State, availability | | |
| | status | | |
| | | | |
| | The destination network | | |
| | address of the LU for | | |
| | session, | | |
| | | | |
| | Name of the PU that's | | |
| | supporting this | | |
| | dependent LU. | | |
+------------+------------------------------+--------------+----------------+
| Partner LU | Number of defined attributes | | |
| | : 7 | | |
| | | | |
| | Number of inherited | | |
| | attributes : 3 | | |
| | | | |
| | o Defined Attributes | | |
| | | | |
| | Examples: Partner LU | | |
| | alias, partner LU name, | | |
| | active mode list | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | Object class , package | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-40
+------------+------------------------------+--------------+----------------+
| Active | Number of defined attributes | : | |
| mode | : 18 | | |
| | | | |
| | Number of inherited | | |
| | attributes : 3 | | |
| | | | |
| | o Defined Attributes | | |
| | | | |
| | Examples: Mode name, | | |
| | name of the class of | | |
| | service, | | |
| | | | |
| | THE MINIMUM NUMBER OF | | |
| | contention loser/winner | | |
| | session permissible | | |
| | between the local LU and | | |
| | the partner LU. | | |
| | | | |
| | maximum RU size | | |
| | upper/lower | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | Object class , package | | |
+------------+------------------------------+--------------+----------------+
| Transaction| Number of defined attributes | Change back | Attribute |
| program | : 18 | | value Change |
| | | Change over | |
| | Number of inherited | | Object |
| | attributes : 5 | Activate | creation |
| | | | |
| | o Defined Attributes | Deactivate | Object |
| | | | deletion |
| | Examples: transaction | | |
| | program ID, name | | State change |
| | | | |
| | The conversation in | | |
| | which the TP is involved | | |
| | | | |
| | Local or remote | | |
| | initiated | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | Object class , package, | | |
| | operational state, usage | | |
| | state | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-41
+------------+------------------------------+--------------+----------------+
| LU 6.2 | Number of defined attributes | Change back | Attribute |
| session | : 15 | | value Change |
| | | Change over | |
| | Number of inherited | | Object |
| | attributes : 20 | Activate | creation |
| | | | |
| | o Defined Attributes | Deactivate | Object |
| | | | deletion |
| | Examples: session ID, | Deactivate | |
| | session type | with | State change |
| | | parameters | |
| | Type of pacing, | | |
| | send/receive RU size, | | |
| | send/receive pacing size | | |
| | | | |
| | destination address | | |
| | field, origin | | |
| | destination address | | |
| | indicator | | |
| | | | |
| | origin address field | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | Object class , package, | | |
| | operational state, usage | | |
| | state | | |
| | | | |
| | Partner connection, | | |
| | connection ID | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-42
+------------+------------------------------+--------------+----------------+
| Conversa- | Number of defined attributes | Change back | Attribute |
| tion | : 7 | | value Change |
| | | Change over | |
| | Number of inherited | | Object |
| | attributes : 20 | Activate | creation |
| | | | |
| | o Defined Attributes | Deactivate | Object |
| | | | deletion |
| | Examples: conversation | Deactivate | |
| | state, conversation | with | State change |
| | type, | parameters | |
| | | | |
| | Local identifier of the | | |
| | resource | | |
| | | | |
| | Conversation group ID, | | |
| | the synchronization | | |
| | level of the | | |
| | conversation | | |
| | | | |
| | Name of the target TP | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | Object class , package, | | |
| | operational state, usage | | |
| | state | | |
| | | | |
| | Partner connection, | | |
| | connection ID | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-43
+------------+------------------------------+--------------+----------------+
| APPN | Number of defined attributes | Change back | Attribute |
| transmis- | : 11 | | value Change |
| sion | | Change over | |
| group | Number of inherited | | Object |
| | attributes : 20 | Activate | creation |
| | | | |
| | o Defined Attributes | Deactivate | Object |
| | | | deletion |
| | Examples: CP-CP session | | |
| | support, propagation | | State change |
| | delay | | |
| | | | |
| | Cost per connect time, | | |
| | cost per byte | | |
| | transmitted, | | |
| | | | |
| | User defined weighting, | | |
| | the security of the TG. | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | Object class , package, | | |
| | operational state, usage | | |
| | state | | |
| | | | |
| | Partner connection, | | |
| | connection ID | | |
+------------+------------------------------+--------------+----------------+
| Logical | Number of defined attributes | Change back | Attribute |
| link | : 19 | | value Change |
| | | Change over | |
| | Number of inherited | | Object |
| | attributes : 22 | Activate | creation |
| | | | |
| | o Defined Attributes | Deactivate | Object |
| | | | deletion |
| | Examples: link name, | Deactivate | |
| | adapter numbers, port | when no user | State change |
| | ID, adjacent node type | | |
| | and name, | Deactivate | |
| | | with | |
| | Line type, adjacent link | parameters | |
| | station name and address | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | Object class , package, | | |
| | operational state, usage | | |
| | state | | |
| | | | |
| | Partner connection, | | |
| | connection ID | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-44
+------------+------------------------------+--------------+----------------+
| Port | Number of defined attributes | Activate | Attribute |
| | : 13 | | value Change |
| | | Deactivate | |
| | Number of inherited | | Object |
| | attributes : 22 | Change back | creation |
| | | | |
| | o Defined Attributes | Change over | Object |
| | | | deletion |
| | Examples: the name of | Deactivate | |
| | the local DLC, port ID, | with | State change |
| | adapter numbers, adapter | parameters | |
| | address | | LAN |
| | | Deactivate | communication |
| | send/receive window | when no user | alarm |
| | size, line type, link | | |
| | station role | | SDLC |
| | | | Communication |
| | o Inherited attributes | | alarm |
| | | | |
| | Object class , package, | | |
| | operational state, usage | | |
| | state | | |
| | | | |
| | Partner connection, | | |
| | connection ID | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-45
A.6 DATABASE MANAGER AGENT
___________________________
The Database Manager agent is part of the LAN NetView Agents Extended product.
It defines 6 object classes for use by management applications.
Appendix A. LAN NetView MIB Summary A-46
+---------------------------------------------------------------------------+
| Table A-6 (Page 1 of 4). Managed Objects for DATABASE MANAGER AGENT |
+------------+------------------------------+--------------+----------------+
| OBJECT | SUMMARY OF ATTRIBUTES | ACTIONS | NOTIFICATIONS |
+------------+------------------------------+--------------+----------------+
| Database | Number of defined attributes | Activate | Processing |
| | : 38 | | error alarm |
| | | Deactivate | |
| | Number of inherited | | |
| | attributes : 32 | Backup the | |
| | | DB | |
| | o Attribute groups | | |
| | | Reset the DB | |
| | - Database | configuration| |
| | configuration view | | |
| | | Restart the | |
| | Examples: code page, | database | |
| | if the database is | | |
| | in consistent state | Restore the | |
| | | database | |
| | If the roll-forward | | |
| | recovery is in | Roll Forward | |
| | progress | the database | |
| | | | |
| | - Database | | |
| | configuration update | | |
| | | | |
| | Examples: the size | | |
| | of the logs, the | | |
| | path of the log file | | |
| | | | |
| | Percentage of lock | | |
| | list allowed per | | |
| | application | | |
| | | | |
| | - Database status | | |
| | | | |
| | Examples: the time | | |
| | of the last backup, | | |
| | the number of users | | |
| | currently connected | | |
| | to the database, | | |
| | name of the database | | |
| | resource | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | Examples: Object class , | | |
| | package, operational | | |
| | state, usage state | | |
| | | | |
| | Resource alias, resource | | |
| | name | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-47
+------------+------------------------------+--------------+----------------+
| Database | Number of defined attributes | Reset DBM | Object |
| Manager | : 9 | configuration| creation |
| | | | |
| | Number of inherited | Activate | Object |
| | attributes : 33 | | deletion |
| | | Deactivate | |
| | o Attribute groups | | State change |
| | | | |
| | - DBM configuration | | Processing |
| | view | | error alarm |
| | | | |
| | Examples: node | | |
| | type,product | | |
| | version, product | | |
| | name | | |
| | | | |
| | - DBM configuration | | |
| | update | | |
| | | | |
| | Examples: the name | | |
| | of the workstation, | | |
| | number of concurrent | | |
| | active database | | |
| | allowed | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | Examples: Object class , | | |
| | package, operational | | |
| | state, usage state | | |
| | | | |
| | Product name, product | | |
| | version, current CSD | | |
| | level | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-48
+------------+------------------------------+--------------+----------------+
| DB | Number of defined attributes | | Processing |
| Directory | : 4 | | error alarm |
| Entry | | | |
| | Number of inherited | | |
| | attributes : 10 | | |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Examples: name of the | | |
| | drive and name of the | | |
| | node where the database | | |
| | resides | | |
| | | | |
| | If the database is | | |
| | remote or local | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | Examples: Object class , | | |
| | package, DBMS product | | |
| | type | | |
| | | | |
| | Resource alias, resource | | |
| | name | | |
+------------+------------------------------+--------------+----------------+
| Remote GW | Number of defined attributes | | Processing |
| Directory | : 3 | | error alarm |
| Entry | | | |
| | Number of inherited | | |
| | attributes : 10 | | |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Examples: DLL name of | | |
| | the application client, | | |
| | transaction program | | |
| | prefix | | |
| | | | |
| | SQLCODE mapping file | | |
| | name, resource name, | | |
| | resource alias | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | Examples: Object class , | | |
| | package, DBMS product | | |
| | type | | |
| | | | |
| | Resource alias, resource | | |
| | name | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-49
+------------+------------------------------+--------------+----------------+
| Remote | Number of defined attributes | | Processing |
| Node | : 10 | | error alarm |
| Directory | | | |
| Entry | Number of inherited | | |
| | attributes : 4 | | |
| | | | |
| | o Defined attributes | | |
| | | | |
| | Examples: remote node | | |
| | name, protocol, adapter, | | |
| | mode, partner LU | | |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | Examples: Object class , | | |
| | package | | |
+------------+------------------------------+--------------+----------------+
| DB Gateway | Number of defined attributes | | Object |
| | : 1 | | creation |
| | | | |
| | Number of inherited | | Object |
| | attributes : 31 | | deletion |
| | | | |
| | o Defined attributes | | State change |
| | | | |
| | A role attribute of | | Processing |
| | underlying DBMS | | error alarm |
| | | | |
| | o Inherited attributes | | |
| | | | |
| | Product name, product | | |
| | version, current CSD | | |
| | level, prior CSD level | | |
| | | | |
| | Usage status, | | |
| | operational state | | |
+------------+------------------------------+--------------+----------------+
Appendix A. LAN NetView MIB Summary A-50