Computer management system and associated management information base

Abstract

A method of managing a plurality of networked manageable devices which include at least one file server having a system board, a drive array subsystem associated with the file server and a server manager installed in the file server for monitoring the system board from a manager console using a management information base or "MIB". First, second and third plurality of objects which describe the system board, the drive array subsystem and the server manager, respectively, are collected and assembled into a MIB. The assembled MIB is then used to manage the file server.

Claims

What is claimed is:

1. A method of managing, using a management application running on a management console, a plurality of networked manageable devices which include at least one file server using a constructed management information base, said at least one file server having a system board, a drive array subsystem associated with said file server and a server manager installed in said file server for monitoring said system board, comprising the steps of:

collecting a plurality of objects describing said system board in a first subMIB;

collecting a plurality of objects describing said drive array subsystem in a second subMIB;

collecting a plurality of objects describing said server manager in a third subMIB;

assembling said first subMIB containing said plurality of objects describing said system board, said second subMIB containing said second plurality of objects describing said drive array subsystem and said third subMIB containing said plurality of objects describing said server manager into a management information base ("MIB"); and

managing said file server from said management console using said assembled MIB by monitoring performance of said system board, said drive array subsystem and said server manager using said plurality of objects describing said system board, said drive array subsystem and said server manager respectively contained in said first subMIB, said second subMIB and said third subMIB.

2. A method of managing a plurality of networked manageable devices according to claim 1 wherein said system board is comprised of a plurality of components and has a software management agent installed therein to interface with said management console networked therewith and wherein the step of collecting said plurality of objects describing said system board into a first subMIB further comprises the step of organizing said first subMIB into two child groups, said first child group containing selected ones of said plurality of objects which describe a revision level of said software management agent installed on said system board and said second child group containing selected ones of said plurality of objects describe said components of said system board and wherein the step of managing said file server from said management console using said assembled MIB by monitoring performance of said system board, said drive array subsystem and said server manager using said plurality of objects describing said system board, said drive array subsystem and said server manager respectively contained in said first subMIB, said second subMIB and said third subMIB further comprises the steps of:

monitoring said revision level of said software management agent installed on said system board using said plurality of objects contained in said first child group of said first subMIB; and

monitoring said components of said system board using said plurality of objects contained in said second child group of said first subMIB.

3. A method of managing a plurality of networked manageable devices according to claim 1 wherein said system board is comprised of a plurality of components and wherein the step of collecting a plurality of objects describing said system board in a first subMIB further comprises the step of organizing said collected plurality of objects into said first subMIB and a fourth subMIB, said first subMIB and said fourth subMIB each containing selected ones of said plurality of objects describing said system board, said first subMIB containing objects describing components installed on said system board other than those described in said fourth subMIB and said fourth subMIB containing objects which describe those components specific to a manufacturer and wherein the step of managing said file server from said management console using said assembled MIB by monitoring performance of said system board, said drive array subsystem and said server manager using said plurality of objects describing said system board, said drive array subsystem and said server manager respectively contained in said first subMIB, said second subMIB and said third subMIB further comprises the steps of:

monitoring said components installed on said system board which are specific to a manufacturer using said plurality of objects contained in said first subMIB; and

monitoring said components installed on said system board which are not specific to a manufacturer using said plurality of objects contained in said fourth subMIB.

4. A method of managing a plurality of networked manageable devices according to claim 1 wherein a software management agent is installed in said system board to interface with said management console networked therewith and wherein the step of collecting said plurality of objects describing said system board into said first subMIB and a fourth subMIB further comprises the step of:

organizing said first subMIB into two child groups, said first child group containing selected ones of said plurality of objects describing a revision level of said software management agent installed on said system board and said second child group containing selected ones of said plurality of objects which describe said components of said system board other than those described in said fourth subMIB; and

organizing said second subMIB into two child groups, said first child group containing selected ones of said plurality of objects which describe a revision level of said software management agent installed on said system board and said second child group containing selected ones of said plurality of objects which describe those components specific to a manufacturer;

wherein the step of managing said file server from said management console using said assembled MIB by monitoring performance of said system board, said drive array subsystem and said server manager using said plurality of objects describing said system board, said drive array subsystem and said server manager respectively contained in said first subMIB, said second subMIB and said third subMIB further comprises the step of:

monitoring said revision level of said software management agent installed on said system board using said plurality of objects contained in said first child group of said first subMIB and said plurality of objects contained in said first child group of said fourth subMIB.

5. A method of managing a plurality of networked manageable devices according to claim 4 wherein the step of organizing said fourth subMIB to include a child group containing selected ones of said plurality of objects which describe those components of said system board specific to a manufacturer further comprises the step of organizing said child group into a plurality of children groups, said children groups including an interface child group which contains selected ones of said plurality of component objects which contain information specific to said software management agent, an asset management child group which contains selected ones of said plurality of component objects which contain asset management information, a security child group which contains selected ones of said plurality of component objects which contain information describing security features specific to said manufacturer and a system board child group which contains selected ones of said plurality of component objects which contain object instances describing said system board and wherein the step of managing said file server from said management console using said assembled MIB by monitoring performance of said system board, said drive array subsystem and said server manager using said plurality of objects describing said system board, said drive array subsystem and said server manager respectively contained in said first subMIB, said second subMIB and said third subMIB further comprises the steps of:

monitoring said software management agent installed on said system board using said plurality of objects contained in said interface child group of said fourth subMIB;

monitoring asset management information for said system board using said plurality of objects contained in said asset management child group of said fourth subMIB;

monitoring security information for said system board using said plurality of objects contained in said security child group of said fourth subMIB; and

monitoring said components of said system board using said plurality of objects contained in said system board child group of said fourth subMIB.

6. A method of managing a plurality of networked manageable devices according to claim 1 wherein said drive array subsystem is comprised of a plurality of components and has a software management agent installed therein to interface with said management console networked therewith and wherein the step of collecting said plurality of objects describing said drive array subsystem into a second subMIB further comprises the step of organizing said second subMIB into three child groups, said first child group containing selected ones of said plurality of objects which describe a revision level of said software management agent installed on said drive array subsystem, said second child group containing selected ones of said plurality of objects which describe said components of said drive array subsystem and said third child group containing selected ones of said plurality of objects which describes traps generated by said drive array subsystem and wherein the step of managing said file server from said management console using said assembled MIB by monitoring performance of said system board, said drive array subsystem and said server manager using said plurality of objects describing said system board, said drive array subsystem and said server manager respectively contained in said first subMIB, said second subMIB and said third subMIB further comprises the steps of:

monitoring said revision level of said software management agent installed on said drive array subsystem using said plurality of objects contained in said first child group of said second subMIB;

monitoring said components of said drive array subsystem using said plurality of objects contained in said second child group of said second subMIB;

monitoring said traps generated by said drive array subsystem using said plurality of objects contained in said third child group of said second subMIB.

7. A method of managing a plurality of networked manageable devices according to claim 6 wherein said drive array subsystem further comprises at least one controller and/or accelerator card and logical, physical and spare drives and wherein the step of organizing said second subMIB to include said second child group containing selected ones of said plurality of objects describing said components of said drive array subsystem further comprises the steps of:

organizing said second child group into a plurality of sub-child groups, said sub-child groups including an interface child group which contains selected ones of said plurality of component objects which contain information specific to said software management agent, a controller child group which contains selected ones of said plurality of component objects which contain information specific to said controllers and/or accelerator cards, a logical drive child group which contains selected ones of said plurality of component objects which contain information specific to said logical drive, a physical drive group which contains selected ones of said plurality of component objects which contain information specific to said logical drive and a spare drive child group which contains selected ones of said plurality of component objects which contain information specific to said spare drive and wherein the step of managing said file server from said management console using said assembled MIB by monitoring performance of said system board, said drive array subsystem and said server manager using said plurality of objects describing said system board, said drive array subsystem and said server manager respectively contained in said first subMIB, said second subMIB and said third subMIB further comprises the steps of:

monitoring said software management agent using said plurality of component objects contained in said interface child group;

monitoring said controllers and/or accelerator cards using said plurality of component objects contained in said controller child group;

monitoring said logical drive using said plurality of component objects contained in said logical drive child group;

monitoring said physical drive using said plurality of component objects contained in said physical drive child group; and

monitoring said spare drive using said plurality of component objects contained in said spare drive child group.

8. A method of managing a plurality of networked manageable devices according to claim 1 wherein said server manager is comprised of a plurality of components and has a software management agent installed therein to interface with said management console networked therewith and wherein the step of collecting said plurality of objects describing said server manager into a third subMIB further comprises the step of organizing said third subMIB into three child groups, said first child group containing selected ones of said plurality of objects which describe a revision level of said software management agent installed on said server manager, said second child group containing selected ones of said plurality of objects which describe said components of said server manager and said third child group containing selected ones of said plurality of objects which describe traps generated by said server manager and wherein the step of managing said file server from said management console using said assembled MIB by monitoring performance of said system board, said drive array subsystem and said server manager using said plurality of objects describing said system board, said drive array subsystem and said server manager respectively contained in said first subMIB, said second subMIB and said third subMIB further comprises the steps of:

monitoring said revision level of said software management agent installed in said server manager using said plurality of objects contained in said first child group of said third subMIB;

monitoring said components of said server manager using said plurality of objects contained in said second child group of said third subMIB; and

monitoring said traps generated by said server manager using said plurality of objects contained in said third child group of said third subMIB.

9. A method of managing a plurality of networked manageable devices according to claim 8 wherein said components of said server manager innately monitor said system board to collect objects for processing thereby, said server manager further comprises at least one asynchronous port for performing off-the-network alerting and wherein the step of organizing said third subMIB to include a second child group containing all of said plurality of objects describing said components of said server manager further comprises the step of organizing said child group into a plurality of sub-child groups, said sub-child groups including an interface child group containing selected ones of said plurality of component objects which contain information specific to said software management agent, a controller child group containing selected ones of said plurality of component objects which contain configuration information specific to said server manager, an object child group containing selected ones of said plurality of objects whose values represent objects innately monitored by said server manager and objects containing information describing said server manager, an asynchronous communication child group containing selected ones of said plurality of objects which contain information describing status of said asynchronous communication ports installed on said server manager and an alert child group containing selected ones of said plurality of objects which contain information on the off-the-network alerting capabilities of said server manager and wherein the step of managing said file server from said management console using said assembled MIB by monitoring performance of said system board, said drive array subsystem and said server manager by monitoring performance of said system board, said drive array subsystem and said server manager using said plurality of objects describing said system board, said drive array subsystem and said server manager respectively contained in said first subMIB, said second subMIB and said third subMIB further comprises the steps of:

monitoring said software management agent using said plurality of component objects contained in said interface child group;

monitoring said configuration of said server manager using said plurality of component objects contained in said controller child group;

monitoring operations of said server manager using said plurality of component objects contained in said object child group which describes said server manager and said plurality of component objects in said object child group related to objects innately monitored by said server manager;

monitoring said status of said asynchronous communication port of said server manager using said plurality of component objects contained in said asynchronous communication child group; and

monitoring said off-the-network alerting capabilities of said server manager using said plurality of component objects contained in said alert child group.

10. A method of managing, using a management application running on a management console, a plurality of networked manageable devices which include at least one file server using a constructed management information base, said at least one file server having a system board, a drive array subsystem associated with said file server and a server manager installed in said file server for monitoring said system board, comprising the steps of:

collecting a plurality of objects describing said system board;

collecting a plurality of objects describing said drive array subsystem;

collecting a plurality of objects describing said server manager;

assembling said plurality of objects describing said system board, said drive array subsystem and said server manager into a management information base ("MIB") having first, second, third and fourth subMIBs, said first subMIB organized to contain selected ones of said plurality of objects which describe said system board, said second subMIB containing selected ones of said plurality of objects which describe manufacturer specific components of said system board, said third subMIB containing selected ones of said plurality of objects which describe said drive array subsystem, and said fourth subMIB containing selected ones of said plurality of objects which describe said server manager; and

managing said file server from said management console using said assembled MIB by monitoring performance of said system board, said drive array subsystem and said server manager using said plurality of objects describing said system board, said manufacturer specific components of said system board, said drive array subsystem and said server manager respectively contained in said first subMIB, said second subMIB, said third subMIB and said fourth subMIB.

11. For a file server having a system board, a drive array subsystem associated with said file server and a server manager installed in said file server for monitoring said system board, a management system for managing said file server comprising:

a bus;

a management information base ("MIB") coupled to said bus, said MIB comprised of:

a first subMIB containing a plurality of objects describing said system board;

a second subMIB containing a plurality of objects describing said drive array subsystem; and

a third subMIB containing a plurality of objects describing said server manager;

a first software management agent installed in said system board and coupled to said bus, said first software management agent supporting said first subMIB by transporting said plurality of objects describing said system board to said first subMIB;

a second software management agent installed in said drive array subsystem and coupled to said bus, said second software management agent supporting said second subMIB by transporting said plurality of objects describing said drive array subsystem to said second subMIB;

a third software management agent installed in said server manager and coupled to said bus, said third software management agent supporting said third subMIB by transporting said plurality of objects describing said server manager to said third subMIB; and

a management application coupled to said system bus, said file server being managed by monitoring, using said management application, performance of said system board, said drive array subsystem and said server manager using said plurality of objects describing said system board, said drive array subsystem and said server manager respectively contained in said first subMIB, said second subMIB and said third subMIB.

12. A management system according to claim 11 wherein said drive array subsystem further comprises a plurality of components, wherein said second subMIB further comprises a first child group containing selected ones of said plurality of objects which describe a revision level of said second software management agent installed in said drive array subsystem, a second child group containing selected ones of said plurality of objects which describe said components of said drive array subsystem and a third child group containing selected ones of said plurality of objects which describe traps generated by said drive array subsystem, said file server being further managed by monitoring, using said management application, said revision level of said second software management agent, said components of said drive array subsystem and said traps generated by said drive array subsystem using said plurality of objects contained in said first, second and third child groups, and further comprising an alert log listing said traps generated by said drive array subsystem.

13. A management system according to claim 12 wherein said drive array subsystem further comprises at least one controller and/or accelerator card and logical, physical and spare drives and wherein second child group further comprises a first sub-child group containing selected ones of said plurality of component objects containing information specific to said second software management agent, a second sub-child group containing selected ones of said plurality of component objects containing information specific to said controllers and/or accelerator cards, a third sub-child group which contains selected ones of said plurality of component objects containing information specific to said logical drive, a fourth sub-child group which contains selected ones of said plurality of component objects containing information specific to said physical drive and a fifth sub-child group which contains selected ones of said plurality of component objects containing information specific to said spare drive, said file server being further managed by monitoring, using said management application, said second software management agent, said controllers and/or accelerator cards, said logical drive, said physical drive and said spare drive using said plurality of component objects contained in said first, second, third, fourth and fifth sub-child groups.

14. A management system according to claim 11 wherein said server manager further comprises a plurality of components, wherein said third subMIB further comprises a first child group containing selected ones of said plurality of objects which describe a revision level of said third software management agent installed in said server manager, a second child group containing selected ones of said plurality of objects which describe said components of said server manager and a third child group containing selected ones of said plurality of objects which describe traps generated by said server manager, said file server being further managed by monitoring, using said management application, said revision level of said third software management agent, said components of said server manager and said traps generated by said server manager using said plurality of objects contained in said first, second and third child groups, and further comprising an alert log listing said traps generated by said server manager.

15. A management system according to claim 14 wherein said server manager further comprises at least one asynchronous communication port and wherein said second child group further comprises a first component child group containing selected ones of said plurality of component objects which contain information specific to said server manager's software management agent, a second component child group containing selected ones of said plurality of component objects which contain objects which describe the configuration of said system manager, a third component child group containing selected ones of said plurality of component objects whose values represent objects innately monitored by said server manager and objects containing information describing said server manager, a fourth component child group containing selected ones of said plurality of component objects which contain information related to said asynchronous communication port of said server manager, and a fifth component child group containing selected ones of said plurality of component objects which contain information related to the off-the-network alert capabilities of said server manager, said file server being further managed by monitoring, using said management application, said third software management agent, said configuration, said server manager, said status of said asynchronous communication port and said off-the-network alert capabilities of said server manager using said plurality of component objects contained in said first, second, third, fourth and fifth component child groups.

16. A method of managing a plurality of networked manageable devices according to claim 10 wherein the step of assembling said plurality of objects describing said system board, said drive array subsystem and said server manager into a management information base ("MIB") having first, second, third and fourth subMIBs further comprises the step of organizing said third subMIB to include a traps child group which contains selected ones of said plurality of objects which describes traps generated by said drive array subsystem and wherein the step of managing said file server from said management console using said assembled MIB by monitoring performance of said system board, said drive array subsystem and said server manager using said plurality of objects describing said system board, said drive array subsystem and said server manager respectively contained in said first subMIB, said second subMIB, said third subMIB and said fourth subMIB further comprises the step of:

transporting traps generated by said drive array subsystem to said management application; and

notifying a network administrator located at said management consol of said traps transported from said drive array subsystem to said management application.

17. A method of managing a plurality of networked manageable devices according to claim 16 wherein a memory subsystem is coupled to said management application and further comprising the steps of:

transporting said objects which describes traps generated by said drive array subsystem transported to said management application to said memory subsystem; and

assembling said objects transported to said memory subsystem as an alert log.

18. A method of managing a plurality of networked manageable devices according to claim 10 wherein the step of assembling said plurality of objects describing said system board, said drive array subsystem and said server manager into a management information base ("MIB") having first, second, third and fourth subMIBs further comprises the step of organizing said fourth subMIB to include a traps child group which contains selected ones of said plurality of objects which describes traps generated by said server manager and wherein the step of managing said file server from said management console using said assembled MIB by monitoring performance of said system board, said drive array subsystem and said server manager using said plurality of objects describing said system board, said drive array subsystem and said server manager respectively contained in said first subMIB, said second subMIB, said third subMIB and said fourth subMIB further comprises the step of:

transporting traps generated by said server manager to said management application; and

notifying a network administrator located at said management consol of said traps transported from said server manager to said management application.

19. A method of managing a plurality of networked manageable devices according to claim 18 wherein a memory subsystem is coupled to said management application and further comprising the steps of:

transporting said objects which describes traps generated by said server manager and transported to said management application to said memory subsystem; and

assembling said objects transported to said memory subsystem as an alert log.

Description

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The invention relates to a computer management system and, more particularly, to a computer management system having plural instrumentation agents for querying manageable devices to collect object data and an associated enterprise management information base (or "MIB") for storing object data in accordance with a specified MIB architecture.

2. Description of Related Art

The Internet community has defined an organizational framework of data and provides a naming authority allowing any company or group to define information within the framework in a way that allows any or all of this data to coexist. Under the control of the International Telegraph and Telephone Consultative Committee (or "CCITT") and the International Organization for Standardization (or "ISO"), the organizational framework has been constructed as a tree. The root of the tree is managed by CCITT and ISO. Extending from the root of the tree are a series of branches defined by CCITT and ISO. However, while the branch is initially defined by the managing authority, authority for the branch may then be given to another organization for defining the child branches for that branch. FIG. 1 illustrates the structure of the organizational framework defined by the Internet community and is included here so that the relationship of the enterprise MIB subject of the present application and the remainder of the Internet community will be clear.

Every piece of information within the organizational framework is configured in a formal grammar and referred to by its full name so that it can be unambiguously specified, thereby making information transfers within an interoperable network system possible. A series of dotted decimal notations, each separated by periods, specifies all of the branches needed to reach a particular item. For example, all items originating in a private enterprise would be headed by the notation "1.3.6.1.4.1". From a specific private enterprise, an item would be identified using the name 1.3.6.1.4.1.XXX.YY where "XXX" is an identifier assigned to that enterprise by the ISO and "YY" is an identifier assigned to that particular item by enterprise "XXX" under the authority of the ISO.

Simple Network Management Protocol (or "SNMP") is a protocol widely used within the Internet community for interoperable network management The SNMP protocol defines a set of commands that a management application may use to retrieve or change the value of items that a management agent is making available. The Internet community also maintains a series of documents which describe the communication protocols used by the community. These documents are called "Request for Comments" and are commonly referred to as "RFCs". Each RFC is assigned a number to identify the document. For example, RFC 1212 defines the formal grammar for a SNMP MIB.

A MIB is a data base that describes a set of items that management applications and agents use to report and control managed devices. A description of a MIB starts with a line that states the name of the MIB being defined. Typically, the name of the MIB is followed by an import statement which allows the MIB writer to specify information from other well known MIBs that are referred to in the MIB being defined. Within a MIB is a structure for organizing managed items. To form the structure, the MIB defines a group or groups for organizing related pieces of information. A group is defined by stating a name for the group and showing how the group fits into the tree. Typically, all group definitions are placed immediately following the IMPORTS statement. Groups may contain information in the form of items or "objects", sub-groups, or a combination of the two. Similarly, each sub-group is configured like a group.

Within a group or sub-group, data may be organized in one of two basic methods. A scalar item is a single piece of information that is within a group. For example, the total memory in a server is a scalar item. A table is a structure for organizing data that requires more information to uniquely identify a single data item within a group of similar items. An example of an item that is best organized in a table is an EISA board ID. It is necessary for someone requesting an EISA board ID to specify the EISA board to which they are referring.

Each item, either scalar or part of a table, defined in a MIB includes a description which explains the item. Typically, the description includes SYNTAX, ACCESS, STATUS and DESCRIPTION clauses. The SYNTAX clause specifies the type of information which the item contains. Information types typically specified by the SYNTAX clause include INTEGER, OCTET STRING, Counter and DisplayString. INTEGER specifies that the value of the item should be interpreted as a number. OCTET STRING specifies that the value of the item should be interpreted as a string of octets, each having a value between 0 and 255. Counter specifies that the item is an INTEGER that has an implied range of zero to FFFFFFFF. DisplayString specifies that the item is an OCTET STRING where each octet is restricted to a printable ASCII character.

The ACCESS clause specifies the ways the item may be used and shows the actions which the agent may support for the item. ACCESS may be read-only, read-write or not-accessible. Read-only means that the value of the item may be retrieved by a management application but may not be altered. Read-write means that the item may be read and/or altered by a management application. Not-accessible is given as the access for organizational constructs that do not represent data items. Not-accessible is used only for table features and should not be used for a scaler item. The STATUS clause specifies whether the item is required for an agent that supports the defined group. A STATUS of mandatory means that the item will always be present if the defined group is supported by the agent. A STATUS of optional means that a particular implementation has the option of supporting the item. The DESCRIPTION clause contains a double quote delimited text description of the item. Finally, the item definition ends by specifying how the item fits into the MIB tree. The group the item belongs to is given, followed by the unique branch number within the group for the item.

To organize a table requires the use of two additional operators, the SEQUENCE operator and the SEQUENCE OF operator. The SEQUENCE operator allows the definition of a new type that consists of several standard types in a specific order. The SEQUENCE OF operator allows the definition of a list of zero or more of the same type of elements. A table is formed by defining a SEQUENCE, typically called a table entry. A table is defined as a SEQUENCE OF the table entry type. As there is no data that is uniquely referred to by the name of the table or entry, the STATUS of the table and the table entry is not-accessible. The INDEX clause specifies the items that can be used to uniquely identify an element in the table.

A MIB may also contain trap definitions. A trap is a notification sent by the SNMP agent to a management console. The trap is sent to inform the management console about an event that has occurred on the managed system. The trap definition begins with the name of the trap, followed by the term TRAP-TYPE. An ENTERPRISE clause follows to indicate the MIB in which the trap is defined. An optional VARIABLES clause may also be included to specify additional information that will be sent in the trap. Typically, the additional information contained in the VARIABLES clause will be items defined in the MIB identified in the ENTERPRISE clause. A DESCRIPTION clause which explains the significance of the trap and the conditions that would cause it to be sent follows. Finally, the trap is given a number to identify it. The number will be unique within the scope of the ENTERPRISE. Both the enterprise name and the trap number are used by the management station to uniquely determine the identity of a received trap.

SUMMARY OF THE INVENTION

In one embodiment, the present invention is of a method of managing a plurality of networked manageable devices which include at least one file server having a system board, a drive array subsystem associated with the file server and a server manager installed in the file server for monitoring the system board from a manager console using a management information base or "MIB". First, second and third plurality of objects which describe the system board, the drive array subsystem and the server manager, respectively, are collected and assembled into a MIB. The assembled MIB is then used to manage the file server. In further aspects of this embodiment of the invention, the collected plurality of objects are organized into a first subMIB containing selected ones of the objects which describe components of the system board, a second subMIB containing selected ones of the plurality of objects which describe those components specific to a manufacturer, a third subMIB containing selected ones of the objects which describe a drive array subsystem associated with the file server and a fourth subMIB containing selected ones of the objects which describe a server manager installed on the system board. Various ones of the subMIBs may be further organized to contain a first child group which contains selected ones of the plurality of objects which describe a revision level of a software management agent installed on the system board, drive array subsystem or server manager, respectively, a second child group containing selected ones of the plurality of objects which describe components of the system board, drive array subsystem, or server manager, respectively, and a third child group containing selected ones of the plurality of objects which describes traps generated by the drive array subsystem or the server manager, respectively.

In further aspects of this embodiment of the invention, the manufacturer specific component child group of the system board may be further organized to include an interface child group which contains selected ones of the plurality of component objects which contain information specific to a software management agent installed in said system board, an asset management child group which contains selected ones of the plurality of component objects which contain asset management information, a security child group which contains selected ones of the plurality of component objects which contain information describing security features specific to the manufacturer and a system board child group which contains selected ones of the plurality of component objects which contain object instances describing the system board.

In still further aspects of this embodiment of the invention, the drive array subsystem component child group may be further organized to include an interface child group which contains selected ones of the plurality of component objects which contain information specific to the drive array subsystem software management agent, a controller child group which contains selected ones of the plurality of component objects which contain information specific to controllers and/or accelerator cards associated with the drive array subsystem, a logical drive child group which contains selected ones of the plurality of component objects which contain information specific to a logical drive associated with the drive array subsystem, a physical drive child group which contains selected ones of the plurality of component objects which contain information specific to a logical drive associated with the drive array subsystem and a spare drive child group which contains selected ones of the plurality of component objects which contain information specific to a spare drive associated with the drive array subsystem.

In still yet further aspects of this embodiment of the invention, the server manager component group may be further organized to include an interface child group containing selected ones of the plurality of component objects which contain information specific to a software management agent installed in the server manager, a controller child group containing selected ones of the plurality of component objects which contain configuration information specific to the server manager, an object child group containing selected ones of the plurality of objects whose values represent objects innately monitored by the server board and objects containing information describing the server board, an asynchronous communication child group containing selected ones of the plurality of objects which contain information reporting the status of asynchronous communication ports installed on the server board and an alert group containing selected ones of the plurality of objects which contain information regarding the off-the-network alerting capabilities of the server manager.

In another embodiment, the present invention is of a management information base (or "MIB") useful for managing a file server having a system board, a drive array subsystem associated with the file server and a server manager installed in the file server for monitoring the system board. The MIB is comprised of a first subMIB containing a plurality of objects describing the system board, a second subMIB containing a plurality of objects describing the drive array subsystem and a third subMIB containing a plurality of objects describing the server manager. The subMIBs may be further comprised of a first child group containing selected ones of the plurality of objects which describe a revision level of the software management agent installed on the system board, drive array subsystem, or server manager, respectively, and a second child group containing selected ones of the plurality of objects which describe the components of the system board, drive array subsystem or server manager, respectively. A third child group containing selected ones of the plurality of objects which describe traps may also be provided for the drive array subsystem or server manager.

In further aspects of this embodiment of the invention, the component child group for the drive array subsystem may be further comprised of a first component child group containing selected ones of the plurality of component objects containing information specific to a software management agent installed in said drive array subsystem, a second child group containing selected ones of the plurality of component objects containing information specific to controllers and/or accelerator cards associated with said drive array subsystem, a third child group which contains selected ones of the plurality of component objects containing information specific to a logical drive associated with the drive array subsystem and a fourth child group which contains selected ones of the plurality of component objects containing information specific to the spare drive associated with the drive array subsystem.

In still further aspects of this embodiment of the invention, the component child group for the server manager may further comprise a first component child group containing selected ones of the plurality of component objects which contain information specific to a software management agent installed in the server manager, a second component child group containing selected ones of the plurality of component objects which contain objects which describe the configuration of the system manager, a third component child group containing selected ones of the plurality of component objects which contain information specific to objects collected by the server manager, a fourth component child group containing selected ones of the plurality of component objects which contain information related to an asynchronous communication port of the server manager, and a fifth child group containing selected ones of the plurality of component objects which contain information related to off-the-network alert capabilities of the server manager.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention may be better understood, and its numerous objects, features and advantages will become apparent to those skilled in the art by reference to the accompanying drawing, in which:

FIG. 1 is a tree illustrating the organizational framework defined by CCITT and ISO for an interoperable network of data;

FIG. 2 is a block diagram illustrating a computer management system and associated MIB constructed in accordance with the teachings of the present invention;

FIG. 3 is an expanded block diagram of the computer management system of FIG. 2;

FIG. 4A is a tree illustrating the organization of an enterprise MIB used in conjunction with the computer management system and associated MIB of FIGS. 2 and 3;

FIG. 4B is an inheritance tree illustrating a MIB revision group commonly configured for each subMIB of the enterprise MIB of FIG. 4A;

FIG. 4C is an inheritance tree illustrating a trap history group similarly configured for plural subMIBs of the enterprise MIB of FIG. 4A;

FIG. 5A is an inheritance tree illustrating a first subMIB of the enterprise MIB of FIG. 4A;

FIG. 5B is an inheritance tree illustrating a processor child group of a component group of the subMIB of FIG. 5A;

FIGS. 5C-1 through 5C-8 is an inheritance tree illustrating an EISA non-volatile memory child group of the component group of the subMIB of FIG. 5A;

FIG. 5D is an inheritance tree illustrating a ROM child group of the component group of the subMIB of FIG. 5A;

FIG. 5E is an inheritance tree illustrating a serial port child group of the component group of the subMIB of FIG. 5A;

FIG. 5F is an inheritance tree illustrating a parallel port child group of the component group of the subMIB of FIG. 5A;

FIG. 5G is an inheritance tree illustrating a floppy disk child group of the component group of the subMIB of FIG. 5A;

FIG. 5H is an inheritance tree illustrating a fixed disk child group of the component group of the subMIB of FIG. 5A;

FIG. 6A is an inheritance tree illustrating a second subMIB of the enterprise MIB of FIG. 4A;

FIG. 6B is an inheritance tree illustrating a system board child group of a component group of the subMIB of FIG. 6A;

FIG. 7A is an inheritance tree illustrating a third subMIB of the enterprise MIB of FIG. 4A;

FIG. 7B-1 through 7B-2 is an inheritance tree illustrating an interface child group of a component group of the subMIB of FIG. 7A;

FIG. 7C-1 through 7C-2 is an inheritance tree illustrating a controller child group of the component group of the subMIB of FIG. 7A;

FIG. 7D is an inheritance tree illustrating a logical drive child group of the component group of the subMIB of FIG. 7A;

FIG. 7E is an inheritance tree illustrating a spare drive child group of the component group of the subMIB of FIG. 7A;

FIG. 7F is an inheritance tree illustrating a physical drive child group of the component group of the subMIB of FIG. 7A;

FIG. 8A is an inheritance tree illustrating a fourth subMIB of the enterprise MIB of FIG. 4A;

FIG. 8B is an inheritance tree illustrating an interface child group of a component group of the subMIB of FIG. 8A;

FIG. 8C is an inheritance tree illustrating a controller child group of the component group of the subMIB of FIG. 8A;

FIG. 8D-1 through 8D-2 is an inheritance tree illustrating an object data child group of the component group of the subMIB of FIG. 8A;

FIG. 8E is an inheritance tree illustrating an asynchronous communication child group of the component group of the subMIB of FIG. 8A; and

FIG. 8F is an inheritance tree illustrating an alert child group of the component group of the subMIB of FIG. 8A.

DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT

Referring first to FIG. 2, and in accordance with the teachings of the present invention, a computer management system which uses a combination of "management" or "instrumentation" agents and an enterprise MIB to manage a manageable device or devices from a management console shall now be described in greater detail. The management system 8 includes at least one manageable device 10 to be managed at a manager station or console 12. Preferably, the manager console 12 should be a computer system having a 386 CPU, 6 Mbyte RAM, 30 Mbyte ROM, a VGA color or higher resolution graphics controller supported by Microsoft Windows, a network interface card compatible with the NetWare open data link interface (or "ODI"), a Microsoft Windows compatible mouse, a Microsoft Windows compatible printer and Microsoft Windows 3.0 or 3.1.

Although only one manageable device 10 is illustrated in FIG. 2, it is specifically contemplated any number or types of manageable devices 10 may be managed at the manager console 12. The manageable device or devices 10 may include any number or combination of intelligent hardware device capable of supporting a software configured management agent 18 therein for interacting with the management system 8 in a manner to be more fully described below. For example, a bridge for interconnecting similar LAN segments, a router for interconnecting dissimilar LANs, a concentrator connected to data terminal equipment (or "DTE") and a file server or other DTE are all manageable devices which may be managed by the management system. For ease of discussion, however, the remainder of this document will assume that the collection of manageable devices 10 interconnected with the manager console 12 for the management thereof consists of a single file server 10 containing plural manageable devices such as industry-standard architecture components, an EISA bus, an intelligent drive array subsystem and a server manager board. The manageable device 10 and the manager console 12 are interconnected by a network 14 which provides a communications pathway for information to be transferred between the two. For example, an ethernet or token ring type network would be suitable for use as the network 14. Furthermore, the network 14 may be a local area network (or "LAN"), a wide area network (or "WAN"), or, more typically, a collection of interconnected LANs and WANs, also known as an "internet".

Installed at the manager console 12 is shell software having a suitable management platform 15, for example, an application process interface (or "API") for the operation of the management application 16. For example, Microsoft Windows would be a suitable platform 15 from which the management application 16 may be launched. In one embodiment of the invention, the management application 16 may coexist with Netware Management System (or "NMS") software manufactured by Novell, Inc., Openview network manager software manufactured by Hewlett Packard or another third party network management systems. For example, it is specifically contemplated that the management application 16 may be launched from Novell's NetWare Management Map focussed on a selected server. Alternately, the management application 16 may operate independent from the NetWare Management System products if the file server 10 is running NetWare v.3.11 or higher.

Once launched, the management application 16 running on the platform 15 performs specific management tasks by interacting with the management agent 18. The management application 16 and the management agent 18 communicate over the network 14 using management application protocols within the TCP/IP protocol suite, preferably the Simple Network Management Protocol (or "SNMP"). Monitored data will be transferred from the managed device 10 to the management application 18 using the SNMP "get request" operation in which the current value(s) associated with a declared variable (or list of variables) relating to a managed object is requested or "polled" by the management application 16 and the "get-next-request" in which the next value associated with a variable, such as a table, that comprises a list of elements, is requested or "polled" by the management application 16. Asynchronous traps, for example, alerts and other fault conditions will be immediately transported from the managed device 10 to the management application 18 using the "trap" operation where a network administrator physically located at the manager console 12 would be notified, either audibly or visually, of the existence of, information regarding the cause of, and possible solutions to, the alert.

In this manner, the management agent 18 collects management information about the file server 10 or other manageable devices and provides that information, which is generally referred to as a management information base (or "MIB") to a network administrator physically located at the manager console 12. The management information provided to the network administrator can be used to monitor the performance of the file server 10 and to respond to alerts as they occur. In this manner, the network administrator can perform "on the network" management" management of the file server 10 or other manageable device. Other functions which can be performed by the network administrator using the management information include security management, fault analysis and configuration management.

Referring next to FIG. 3, the computer management system 8 will now be described in greater detail. As may now be seen, the file server 10 is now designated as a NetWare server, thereby indicating that the managed server 10 is running NetWare v3.11 or greater. Installed on the netware server 10 is an SNMP agent 28 for transporting data from a managed device or devices to the management application 16. The SNMP agent 28 is a collection of software capable of querying manageable devices and providing information to the management application 16 using operations defined as part of the SNMP protocol. Manageable devices such as ISA CMOS 20, the battery backed up RAM in the real time clock installed in the system board, EISA NVRAM 22, the battery backed up non-volatile memory containing the EISA configuration of the file server 10, server manager board 24, a management device which contains configuration and real time monitored information on the file server 10, and intelligent drive array controller 26, which contains configuration, real time monitor and performance array on the intelligent drive array 26, are instrumented for interfacing with the SNMP agent 28 using base system instrumentation agent 30, server manager instrumentation agent 32 and drive array instrumentation agent 34, respectively. Instrumentation agents 30, 32 and 34 are NetWare loadable modules (or "NLMs") used so that the information regarding the managed device can be transferred to the application 16. As will be more fully discussed below, these instrumentation agents for the managed devices support separate subMIBs for the managed devices, thereby permitting the organization of managed information described herein.

More specifically, the base system instrumentation agent 30 is NLM software connected to provide industry-standard architectural information about the system configuration. This information includes product and model information, processor type, diskette type, hard drive type, EISA board configuration, system ROM version, installed memory, video subsystem and serial and parallel port configurations. It may also provide product ID, serial number and security configuration.

The disk drive array instrumentation agent 32 is NLM software for managing the drive array controller 26. Again using SNMP, the drive array instrumentation agent 34 will gather information including controller configuration, Compaq 4-MB array accelerator write cache configuration and status, if installed, logical drive configuration and status, physical drive configuration and status and spare drive configuration and status.

Finally, the server manager instrumentation agent 32 is NLM software used to manage a server manager 24 and is necessary only if the file server 10 has a server manager board installed therein. A server manager board innately monitors and process objects indicative of computer system performance and actual and/or potential computer systems failures, determines alert conditions based upon the innately monitored and processed objects, reports alert conditions in either an in-band or out-of band mode and provides for corrective action to be taken from a remote location. The exact configuration of a server manager board is disclosed at length in the copending U.S. patent applications Ser. No. 07/720,259, filed Jun. 24, 1991, issued Nov. 22, 1994 as U.S. Pat. No. 5,367,670, entitled "Computer System Manager" and previously incorporated by reference. The information gathered by the server manager instrumentation agent 32 includes server manager board configuration information and monitored item information maintained on the server manager board.

From the SNMP agent, information which forms part of the MIB may be transported over the network 14 using the IPX or IP protocol stack to the manager console 12 where Novell SNMP DDE server software 36 is installed so that the management data can be received at or transmitted from the manager console. The manager console 12 is further provided with a Btreive database 38 where object information from the MIB gathered over time by the management application 16 may be stored for later access, either by the management application 16 or another application running on the manager console 12. For example, object information which would be transmitted to the btrieve database 38 for storage would be all alerts transmitted to the management application 16 in the form of traps where they would be assembled as an alert log and information received in response to the polling of monitored items which would be assembled in the btreive database 38 in a manner which would enable trend analysis and reporting.

Referring next to FIG. 4A, an enterprise MIB 232 subject of the present invention and located at branch 1..4.6.1.4.232 of the CCITT/ISO organization framework for data illustrated in FIG. 1 will now be described in greater detail. The enterprise MIB 232 defines the set of all manageable object instances and traps known to the agent, instrumentation agent and the user interface application included as part of the computer management system of FIGS. 2-3. The management application 16 uses the enterprise MIB 232's definition of object instances and traps to manage the manageable devices 10. The variables identified will be read by the management application 16 and be graphically displayed at the workstation 12. The asynchronous traps generated by the SNMP agent supported by the instrumentation will be collected and displayed by the application 16.

The enterprise MIB 232 is organized to include a number of subMIBs, each describing a component in a managed server. The subMIBS include a standard equipment subMIB located at branch 232.1, a manufacturer specific system subMIB located at branch 232.2, a drive array subMIB located at branch 232.3 and a server manager subMIB located at branch 232.4. Each subMIB 232.1, 232.2, 232.3, and 232.4 includes a mibRev childgroup located at branch 232.1.1, 232.2.1, 232.3.1 and 232.4.1, respectively, and a component child group located at branch 232.1.2, 232.2.2, 232.3.2 and 232.4.2, respectively. The drive array subMIB and the server manager subMIB also include a traps child group located at branch 232.3.3 and 232.4.3, respectively. Of these, the mibRev child group for a subMIB contains information about the revision of the enterprise 232 to which the SNMP agent conforms and includes an indication as to that subMIB's last revision, the component child group for a subMIB details all object instances for the components of that subMIB and the traps child group contains a trap log history which will enable the management application 16 to determine alerting events that have occurred within the computer system 8.

Referring next to FIG. 4B, the mibRev child group commonly configured for each subMIB of the enterprise MIB shall now be described in greater detail. Each mibRev child group is located at branch 232.M.1, where M=the subMIB containing that mibRev child group. In this embodiment of the invention, M=(1,2,3,4), thereby indicating that all of the subMIBS are provided with a mibREV child group. Each mibRev child group a major revision object located at branch 232.M.1.1 and a minor revision object located at branch 232.M.1.2. The management application 16 obtains this information from the management agent 18 to determine if they are both using the same definition for the MIB. If the major revision object indicates a revision change, a very significant change in the information supported by the subMIB has occurred and indicates that an upgrade should be made to ensure correct interpretation of data. For example, if the management application 16 and agent 18 for a subMIB are using a MIB definitions having different major revision level, the older of the two should be upgraded. However, if the minor revision object indicates a revision change, the revision should not significantly change the interpretation of data. The formal organization of the mibRev child group is as follows:

    ______________________________________
               Issue
    Patent No. Date      Title
    ______________________________________
    5,402,431  03/28/95  Innate Bus Monitoring System
                         for Computer System Manager
    07/720,258 06/24/91  In-band/Out-of-Band Alert
                         Delivery System for Computer
                         System Manager
    07/719,243 06/24/91  Remote Console Emulator for
                         Computer System Manager
    5,283,905  02/01/94  Power Supply for Computer
                         System Manager
    07/756,506 09/08/91  Remote System Reboot
    5,257,384  10/26/93  Asynchronous Protocol for
                         Computer System Manager
    5,309,563  05/03/94  Network Protocol for Computer
                         System Manager
    5,272,382  12/21/93  Power Supply for Computer
                         System Manager
    ______________________________________

    ______________________________________
    mibRevMajor
               OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The Major Revision level. A change in the
      major revision level represents a major change
      in the architecture of the MIB. A change in
      the major revision level may indicate a
      significant change in the information supported
      and/or the meaning of the supported
      information, correct interpretation of data may
      require a MIB document with the same major
      revision level."
    : := ( mibRev 1 )
    mibRevMinor
               OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The Minor Revision level. A change in the
      minor revision level may represent some minor
      additional support, no changes to any pre-
      existing information has occurred."
    : := ( mibRev 2 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    trapPkts OBJECT-TYPE
    SYNTAX     Counter
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The total number of trap packets issued by the
      agent for the Server Manager enterprise since
      the Server Manager SNMP agent was loaded."
    : := ( trap 1 )
    trapLogMaxSize
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The maximum number of entries that will
      currently be kept in the trap log. If the
      maximum size has been reached and a new trap
      occurs the oldest trap will be removed."
    : := ( trap 2 )
    trapLog  OBJECT-TYPE
    SYNTAX     SEQUENCE OF TrapLogEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "An ordered list of trap log entries
      (conceptually a queue). The trap log entries
      will be kept in the order in which they were
      generated with the most recent trap at index 1
      and the oldest trap entry at index
      trapLogMaxSize. If the maximum number size has
      been reached and a new trap occurs the oldest
      trap will be removed when the new trap is added
      so the trapMaxLogSize is not exceeded."
    : := ( trap 3 )
    trapLogEntry
                OBJECT-TYPE
    SYNTAX     TrapLogEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A description of a trap event."
    INDEX      ( trapLogIndex )
    : := ( trapLog 1 )
    trapLogEntry
             : := SEQUENCE (
    trapLogIndex
                INTEGER,
    trapType    INTEGER,
    trapTime    OCTET STRING (SIZE (0 . . . 6))
    trapLogIndex
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The value of this object uniquely identifies
      this trapLogEntry at this time. The most
      recent trap will have an index of 1 and the
      oldest trap will have an index of
      trapLogMaxSize. Because of the queue-like
      nature of the trapLog this particular trap
      event's index will change as new traps are
      issued."
    : := ( trapLogEntry 1 )
    trapType OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
     DESCRIPTION
      "The type of the trap event that this entry
      describes. This number refers to an entry in
      a list of traps enumerating the possible traps
      the Server Manager agent may issue."
    : := ( trapLogEntry 2 )
    trapTime OBJECT-TYPE
    SYNTAX     OCTET STRING (SIZE (0 . . . 6))
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The time of the trap event that this entry
      describes. The time is given in year (first
      octet), month, day of month, hour, minute,
      second (last octet) order."
    : : (trapLogEntry 3 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    Import              Defined by
    ______________________________________
    enterprises         RFC1155SMI
    DisplayString       RFC1158-MIB
    OBJECT-TYPE         RFC-1212
    ______________________________________

    ______________________________________
    processorTable
               OBJECT-TYPE
    SYNTAX     SEQUENCE OF ProcessorEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A list of the processors in the system. The
      main processor (if such a concept is valid for
      this machine) should be the first entry in the
      table."
    : := ( processor 1 )
    processorTable
               OBJECT-TYPE
    SYNTAX     ProcessorEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A description of a processor in the system."
    INDEX      ( processorUnitIndex )
    : := ( processorTable 1 )
    ProcessorEntry
                : := SEQUENCE (
    processorUnitIndex
                  INTEGER,
    processorSlot INTEGER,
    processorName DisplayString (SIZE(0 . . . 255)),
    processorSpeed
                  INTEGER
    processorUnitIndex
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This is a number that uniquely specifies a
      processor unit. A processing unit may be a set
      of processing chips that are on the same board
      or for other reasons work together as a unit.
    processorSlot
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This value represents the slot that this
      processor is in. If the slot cannot be
      determined the value of zero will be returned."
    : := ( processorEntry 2 )
    processorName
               OBJECT-TYPE
    SYNTAX     DisplayString (SIZE (0 . . . 255)
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This is a string that gives the name of
      the processor described in this entry.
      For example: 80386"
    : := ( processorEntry 3 )
    processorSpeed
               OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This is speed in megahertz of the
      processor described in this entry. Zero
      will be entered if this value is not
      available."
    : := ( processorEntry 4 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    coprocessorTable
                OBJECT-TYPE
    SYNTAX     SEQUENCE OF CoprocessorEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A list of the coprocessors in the system."
    : := ( processor 2 )
    coprocessorEntry
                OBJECT-TYPE
    SYNTAX     CoprocessorEntry
    ACCESS     non-accessible
    STATUS     mandatory
    DESCRIPTION
      "A description of a coprocessor in the system.
      The coprocessorUnitIndex of any entry in this
      table will equal the processorUnitIndex of the
      corresponding processor in the processor
      table."
    INDEX      (  c o p r o c e s s o r U n i t I n d e x ,
               coprocessorChipIndex )
    : := ( coprocessorTable 1 )
    CoprocessorEntry
                : :=SEQUENCE (
    coprocessorUnitIndex
                   INTEGER,
    coprocessorChipIndex
                   INTEGER,
    coprocessorSlot
                   INTEGER,
    coprocessorName
                   DisplayString
                   (SIZE 0 . . . 255)),
    coprocessorSpeed
                   INTEGER,
    coprocessorType
                   INTEGER
    coprocessorUnitIndex
                 OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This is a number that uniquely specifies a
      processor unit. A processing unit may be a set
      of processing chips that are on the same board
      for other reasons work together as a unit. The
      main processor unit (if there is one) will
      always have the lowest (first) index. this
      field can be used to associate processors with
      their corresponding coprocessors."
    : := ( coprocessorEntry 1 )
    coprocessorChipIndex
                 OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This is a number that uniquely specifies the
      processor chip. A processor chip is one
      specific processor that may or may not work
      with other processor chips in a processor unit.
      This field is used to distinguish between
      multiple coprocessors that are part of the same
      processor unit. For example, If a processor
      board contained a Intel 80386 processor with
      both a Intel 80387 and a Weitek 3167, both the
      80387 and the 3167 would have the same
      coprocessorUnitIndex (which would match the
      80386's different coprocessorChipIndex field
      values."
    : := ( coprocessorEntry 2 )
    coprocessorSlot
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This value represents the slot that this
      coprocessor is in. If the slot cannot be
      determined the value of zero will be returned."
    : := ( coprocessorEntry 3 )
    coprocessorName
                OBJECT-TYPE
    SYNTAX     DisplayString (SIZE (0 . . . 255)
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This is a string that gives the name of the
      processor described in this entry.
      For example:
      80387
      Weitek 3167"
    : := ( coprocessorEntry 4 )
    coprocessorSpeed
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This is speed in megahertz of the processor
      described in this entry. Zero will be returned
      if this value is not available."
    : := ( coprocessorEntry 5 )
    coprocessorType
                OBJECT-TYPE
    SYNTAX     INTEGER (
    other(1),
    embedded(2),
    external(3)
    )
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This value indicates if the coprocessor this
      entry is describing is embedded in the
       processor or external to the processor chip."
    : := ( coprocessorEntry 6 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    baseMemory    OBJECT-TYPE
    SYNTAX        INTEGER
    ACCESS        read-only
    STATUS        mandatory
    DESCRIPTION
      "The amount of base memory in kilobytes. A
      kilobyte is 1024 bytes."
    : := ( memory 1 )
    totalMemory   OBJECT-TYPE
    SYNTAX        INTEGER
    ACCESS        read-only
    STATUS        mandatory
    DESCRIPTION
      "The total amount of memory in kilobytes. A
      kilobyte is 1024 bytes"
    : := ( memory 2 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    isaCmosRaw    OBJECT-TYPE
    SYNTAX        OCTET STRING (SIZE (0 . . . 64))
    ACCESS        read-only
    STATUS        mandatory
    DESCRIPTION
      "The contents of the ISA CMOS."
    : := ( isaCmos 1 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    eisaInterruptTable
                OBJECT-TYPE
    SYNTAX     SEQUENCE OF EisaInterruptEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A list of EISA function interrupt
      configuration entries."
    : := ( eisaNvram 4 )
    eisaInterruptEntry
                OBJECT-TYPE
    SYNTAX     EisaInterruptEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A description of an EISA function interrupt
      configuration."
    INDEX      ( eisaInterruptSlotIndex,
               eisaInterruptFunctionIndex,
               eisaInterruptAllocationIndex )
    := ( eisaInterruptTable 1
    EisaInterruptEntry
                : := SEQUENCE (
    eisaInterruptSlotIndex
                       INTEGER,
    eisaInterruptFunctionIndex
                       INTEGER,
    eisaInterruptAllocationIndex
                       INTEGER,
    eisaInterruptNumber
                       INTEGER,
    eisaInterruptShare INTEGER,
    eisaInterruptTrigger
                       INTEGER
    eisaInterruptSlotIndex
                 OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The EISA slot number of the board
      that registered the interrupt
      configuration this entry describes."
    : := ( eisaInterruptEntry 1 )
    eisaInterruptFunction Index
                    OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The function in which this interrupt
      configuration was registered."
    : := ( eisaInterruptEntry 2 )
    eisaInterruptAllocationIndex
                    OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The index for this interrupt allocation entry
      in the EISA function block."
    : := ( eisaInterruptEntry 3 )
    eisaInterruptNumber
                 OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The interrupt described in this entry."
    : := ( eisaInterruptEntry 4 )
    eisaInterruptShare
                OBJECT-TYPE
    SYNTAX     INTEGER (
    nonshareable(1),
    shareable(2)
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This value indicates if the interrupt is
      shareable."
    : := ( eisaInterruptEntry 5 )
    eisaInterruptTrigger
                OBJECT-TYPE
    SYNTAX     INTEGER
    edged(1),
    level(2)
    )
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This value indicates if the interrupt is edge
      or level triggered."
    : := ( eisaInterruptEntry 6 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    eisaDmaTable
               OBJECT-TYPE
    SYNTAX     SEQUENCE OF EisaDmaEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A list of EISA function DMA configuration
      entries."
    : := ( eisaNvram 5 )
    eisaDmaEntry
               OBJECT-TYPE
    SYNTAX     EisaDmaEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A description of an EISA function DMA
      configuration."
    : := ( eisaDmaTable 1 )
    EisaDmaEntry
                : := SEQUENCE (
    eisaDmaSlotIndex
                    INTEGER,
    eisaDmaFunctionIndex
                    INTEGER,
    eisaDmaAllocationIndex
                    INTEGER,
    eisaDmaChannel  INTEGER,
    eisaDmaShare    INTEGER,
    eisaDmaTiming   INTEGER,
    eisaDmaTransferSize
                    INTEGER
    eisaDmaSlotIndex
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The EISA slot number of the board that
      registered the DMA configuration this entry
      describes."
    : := ( eisaDmaEntry 1 )
    eisaDmaFunctionIndex
                  OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The function in which this DMA configuration
      was registered."
    : := ( eisaDmaEntry 2 )
    eisaDmaAllocationIndex
                  OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The index for this DMA channel allocation
      entry in the EISA function block."
    : := ( eisaDmaEntry 3 )
    eisaDmaChannelIndex
                 OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The DMA channel described in this entry."
    : := ( eisaDmaEntry 4 )
    eisaDmaShare
                OBJECT-TYPE
    SYNTAX     INTEGER (
    nonshareable(1),
    shareable(2)
    )
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This value indicates if the DMA channel is
      shareable."
    : := ( eisaDmaEntry 5 )
    eisaDmaTiming
               OBJECT-TYPE
    SYNTAX     INTEGER (
    eisaTiming(1),
    typeA(2),
    typeB(3),
    burstTypeC(4)
    )
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This value indicates the timing (transfer
      rate) associated with this configuration of the
      DMA channel."
    : := ( eisaDmaEntry 6 )
    eisaDmaTransferSize
                 OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This value indicates the transfer size in bits
      used over this DMA channel."
    : := ( eisaDmaEntry 7 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    eisaPortTable
               OBJECT-TYPE
    SYNTAX     SEQUENCE OF EisaPortEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A list of EISA function port I/O configuration
      entries."
    : := ( eisaNvram 6 )
    eisaPortEntry
                OBJECT-TYPE
    SYNTAX     EisaPortEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A description of an EISA function Port I/O
      configuration."
    INDEX      (eisaPortSlotIndex, eisaPortFunctionIndex,
               eisaPortAllocationIndex
    : := ( eisaPortTable 1 )
    EisaPortEntry
                : := SEQUENCE (
    eisaPortSlotIndex
                    INTEGER,
    eisaPortFunctionIndex
                    INTEGER,
    eisaPortAllocationIndex
                    INTEGER,
    eisaPortAddress INTEGER,
    eisaPortShare   INTEGER,
    eisaPortSize    INTEGER
    eisaPortSlotIndex
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The EISA slot number of the board that
      registered the I/O port configuration this
      entry describes."
    : := ( eisaPortEntry 1 )
    eisaPortFunctionIndex
                 OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The function in which this I/O port range
      configuration was registered."
    : := ( eisaPortEntry 2 )
    eisaPortAllocationIndex
                  OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The index for this I/O port range allocation
      entry in the EISA function block."
    : := ( eisaPortEntry 3 )
    eisaPortAddress
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The I/O port address being described in
      this entry."
    : := ( eisaPortEntry 4 )
    eisaPortShare
               OBJECT-TYPE
    SYNTAX     INTEGER (
    nonshareable(1),
    shareable(2)
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This value indicates if the Port channel is
      shareable."
    : := ( eisaPortEntry 5 )
    eisaPortSize
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The number of sequential ports starting at the
      eisaPortAddrIndex that are be configured."
    : := ( eisaPortEntry 6 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    eisaFreeFormTable
                OBJECT-TYPE
    SYNTAX     SEQUENCE OF EisaFreeFormEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A list of EISA function free form entries."
    : := ( eisaNvram 7 )
    eisaFreeFormEntry
                  OBJECT-TYPE
    SYNTAX     EisaFreeFormEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A description of an EISA function free form."
    INDEX      ( eisaFreeFormSlotIndex,
               eisaFreeFormFunctionIndex )
    : := ( eisaFreeFormTable 1 )
    EisaPortEntry
                : := SEQUENCE (
    eisaFreeFormSlotIndex
                      INTEGER,
    eisaFreeFormFunctionIndex
                      INTEGER,
    eisaFreeFormValue OCTET STRING
                      (SIZE (0 . . . 25))
    eisaFreeFormSlotIndex
                  OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The EISA slot number of the board that
      registered the free form information this entry
      describes."
    : := ( eisaFreeFormEntry 1 )
    eisaFreeFormFunctionIndex
                    OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The function in which this free form was
      registered."
    : := ( eisaFreeFormEntry 2 )
    eisaFreeFormValue
                OBJECT-TYPE
    SYNTAX     OCTET STRING (SIZE (0 . . . 205)
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The free form value."
    : := ( eisaFreeFormEntry 3 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    eisaInitTable
               OBJECT-TYPE
    SYNTAX     SEQUENCE OF EisaInitEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A list of EISA function port initialization
      entries."
    : := ( eisaNvram 8 )
    eisaInitEntry
                OBJECT-TYPE
    SYNTAX     EisaInitEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A description of an EISA function port
      initialization."
    INDEX      (eisaInitSlotIndex, eisaInitFunctionIndex,
               eisaInitAllocationIndex)
    : := ( eisaInitTable 1 )
    EisaInitEntry
                : := SEQUENCE (
    eisaInitSlotIndex
                    INTEGER,
    eisaInitFunctionIndex
                    INTEGER,
    eisaInitAllocationIndex
                    INTEGER,
    eisaInitUseMask INTEGER,
    eisaInitAccess  INTEGER,
    eisaInitAddress INTEGER,
    eisaInitPortValue
                    INTEGER,
    eisaInitPortMask
                    INTEGER
    eisaInitSlotIndex
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The EISA slot number of the board that
      registered the port initialization this entry
      describes."
    : := ( eisaInitEntry 1 )
    eisaInitFunctionIndex
                 OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The function in which this port initialization
      was registered."
    : := ( eisaInitEntry 2 )
    eisaInitAllocationIndex
                  OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The index for this port initialization entry
      in the EISA function block."
    : := ( eisaInitEntry 3 )
    eisaInitUseMask
                OBJECT-TYPE
    SYNTAX     INTEGER (
    useValueOnly(1),
    useValueAndMask(2)
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This indicates if a mask will be used when
      performing initialization."
    : := ( eisaInitEntry 4 )
    eisaInitAccess
                OBJECT-TYPE
    SYNTAX     INTEGER (
    eightBitAddress(1),
    sixteenBitAddress(2)
    thirtyTwoBitAddress (3)
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This value indicates the number of bits this
      entry initializes."
    : := ( eisaInitEntry 5 )
    eisaInitAddress
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This value indicates the port address
      this entry initializes."
    : := ( eisaInitEntry 6 )
    eisaInitPortValue
               OBJECT-TYPE
    SYNTAX      INTEGER
    ACCESS      read-only
    STATUS      mandatory
    DESCRIPTION
      "This value indicates the value this entry
      initializes the port to."
    : := ( eisaInitEntry 7 )
    eisaInitPortMask
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "This value indicates the mask to use when
      performing initialization."
    : := ( eisaInitEntry 8 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    systemRomVersion
                OBJECT-TYPE
    SYNTAX     DisplayString (SIZE (0 . . . 255))
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The system ROM manufacturer, family, and
      version information."
    : := ( rom 1 )
    optionRomTable
               OBJECT-TYPE
    SYNTAX     SEQUENCE OF OptionSlotEntry
    ACCESS     not-accessible
    STATUS     optional
    DESCRIPTION
      "A table of option ROM descriptions."
    : := ( rom 2 )
    optionRomEntry
               OBJECT-TYPE
    SYNTAX     OptionRomEntry
    ACCESS     not-accessible
    STATUS     optional
    DESCRIPTION
      "An option ROM description."
    INDEX      ( optionRomStartAddrIndex )
    : := ( optionRomTable 1 )
    OptionRomEntry
                : :-SEQUENCE (
    optionRomStartAddrIndex
                      INTEGER,
    optionRomSize     INTEGER
    optionRomStartAddrIndex
                   OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     optional
    DESCRIPTION
      "The starting address of the option ROM."
    : := ( optionRomEntry 1 )
    optionRomSize
               OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     optional
    DESCRIPTION
      "The size in bytes of the option ROM."
    : := ( optionRomEntry 2 )
    biosRomDataRaw
               OBJECT-TYPE
    SYNTAX     OCTET STRING (SIZE (0 . . . 256))
    ACCESS     read-only
    STATUS     optional
    DESCRIPTION
      "The BIOS ROM data area. This may be the
      current contents a copy of the BIOS ROM data
      area from when the SNMP agent was loaded."
    : := ( rom 3 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    keyboarddescription
                   OBJECT-TYPE
    SYNTAX        DisplayString (SIZE (0 . . . 255))
    ACCESS        read-only
    STATUS        mandatory
    DESCRIPTION
      "A description of the keyboard"
    : := ( keyboard 1)
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    videodescription
                   OBJECT-TYPE
    SYNTAX        DisplayString (SIZE (0 . . . 255))
    ACCESS        read-only
    STATUS        mandatory
    DESCRIPTION
      "A description of the video system in the
      computer. This may include the manufacturer,
      board name, modes supported, etc . . ."
    : := ( video 1 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    serialPortTable
                OBJECT-TYPE
    SYNTAX     SEQUENCE OF SerialPortEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A table of serial port descriptions."
    : := ( serialPort 1 )
    serialPortIndex
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "A description of a serial port."
    INDEX   ( serialPortIndex )
    : := ( serialPortTable 1 )
    SerialPortEntry
                : := SEQUENCE
    serialPortIndex
                  INTEGER,
    serialPortAddr
                  INTEGER,
    serialPortDesc
                  DisplayString (SIZE (0 . . . 255))
    serialPortIndex
                  OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "An index that uniquely specifies this entry."
    : := ( serialPortEntry 1)
    serialPortAddr
               OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The I/O port address used by this serial
      port."
    : := ( serialPortEntry 2 )
    serialPortDesc
               OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "A text description of further information
      known about the serial port. This may be an
      empty string if no further information is
      known."
    : := ( serialPortEntry 3 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    parallelPortTable
                OBJECT-TYPE
    SYNTAX     SEQUENCE OF ParallelPortEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A table of parallel port descriptions."
    : := ( parallelport 1 )
    parallelPortEntry
                OBJECT-TYPE
    SYNTAX     ParallelPortEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A description of a parallel port."
    INDEX   ( parallelPortIndex )
    : := ( parallelPortTable 1 )
    ParallelPortEntry
               : :-SEQUENCE (
    parallelPortIndex
                 INTEGER,
    parallelPortAddr
                 INTEGER,
    parallelPortDesc
                 DisplayString (SIZE (0 . . . 255))
    parallelPortIndex
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "An index that uniquely specifies this entry."
    : := ( parallelPortEntry 1 )
    parallelPortAddr
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The I/O port address used by this parallel
      port."
    : := ( parallelPortEntry 2 )
    parallelPortDesc
                OBJECT-TYPE
    SYNTAX     displaystring (SIZE (0 . . . 255))
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "A text description of further information
      known abut the parallel port. This may be an
      empty string if no further information is
      known."
    : := (parallelPortEntry 3 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    floppyDisketteTable
                OBJECT-TYPE
    SYNTAX     SEQUENCE OF FloppyDisketteEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A table of floppy drive descriptions."
    : := ( floppydiskette 1 )
    floppyDisketteEntry
                OBJECT-TYPE
    SYNTAX     FloppyDisketteEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A floppy drive description."
    INDEX   ( floppydisketteindex )
    : := ( floppyDisketteTable 1 )
    FloppyDisketteEntry)
                 : := SEQUENCE (
    floppyDisketteIndex
                  INTEGER,
    floppyDisketteType
                  INTEGER
    floppyDisketteIndex
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "An index that uniquely specifies this entry.
      If possible, this field will map directly to
      the drive letter (1 for A:, 2 for B:)."
    : := ( floppyDisketteEntry 1 )
    floppyDiskettetype
                OBJECT-TYPE
    SYNTAX     INTEGER (
    drive360k(1),
    drive1200k(2),
    drive720k(3),
    drive1440k(4)
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The type (capacity) of the floppy drive. The
      following values are valid:
      drive360k (1) This is a 360 kilobyte, 5.25
      inch floppy drive.
      drive1200k (2) This is a 1.2 megabyte, 5.25
      inch floppy drive.
      drive720k (3) This is a 720 kilobyte, 3.5 inch
      floppy drive.
      drive1440k (4) This is a 1.44 megabyte, 3.5
      inch floppy drive."
    : := ( floppyDisketteEntry 2 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    fixedDiskTable
                OBJECT-TYPE
    SYNTAX     SEQUENCE OF FixedDiskEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A table of ST-506 interface accessible fixed
      disk descriptions."
    : := ( fixeddisk 1 )
    fixedDiskEntry
                OBJECT-TYPE
    SYNTAX     fixedDiskEntry
    ACCESS     not-accessible
    STATUS     mandatory
    DESCRIPTION
      "A fixed disk description."
    INDEX   ( fixedDiskIndex )
    : := ( fixedDiskTable 1)
    FixedDiskEntry
               ::= SEQUENCE (
    fixedDiskIndex   INTEGER,
    fixedDiskType    INTEGER,
    fixedDiskCylinders
                     INTEGER,
    fixedDiskHeads   INTEGER,
    fixedDiskSectorsPerTrack
                     INTEGER,
    fixedDiskCapacity
                     INTEGER
    fixedDiskIndex
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "An index that uniquely specifies this entry.
      Each possible index value indicates a special
      drive as shown in the table below:
    fiskDiskIndex
                 IDE/ESDI Controller
                                  Drive Unit
    ______________________________________
    1            Primary          1
    2            Primary          2
    3            Secondary        1
    4            Secondary        2
      Any other index value would be implementation
      specific."
    : := ( fixedDiskEntry 1 )
    fixedDiskType
               OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The drive type."
    : := ( fixedDiskEntry 2 )
    fixedDiskCylinders
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The number of cylinders on the drive."
    : := ( fixedDiskEntry 3 )
    fixedDiskHeads
               OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The number of heads on the drive."
    : := ( fixedDiskEntry 4 )
    fixedDiskSectorsPerTrack
                   OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The number of sectors per tract on the drive."
    : := ( fixedDiskEntry 5 )
    fixedDiskCapacity
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The capacity of the drive in megabytes."
    : := ( fixedDiskEntry 6 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    Import              Defined by
    ______________________________________
    enterprises         RFC1155-SMI
    Counter             RFC1155-SMI
    Gauge               RFC1155-SMI
    TimeTicks           RFC1155-SMI
    DisplayString       RFC1158-MIB
    OBJECT-TYPE         RFC-1212
    ______________________________________

    ______________________________________
    systemSerialNumber
                  OBJECT-TYPE
    SYNTAX       DisplayString (SIZE (0 . . . 255))
    ACCESS       read-only
    STATUS       mandatory
    DESCRIPTION
      "The serial number of the system unit. The
      string will be empty if the system does not
      report the serial number function."
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    powerOnPassword
                OBJECT-TYPE
    SYNTAX     INTEGER   (
    other(1),
    disabled(2),
    enabled (3)
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The state of the power on password feature."
    : := ( security 1 )
    networkServerMode
                 OBJECT-TYPE
    SYNTAX     INTEGER   (
    other(1),
    disabled(2),
    enabled (3)
    )
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The state of the network server mode feature."
    : := ( security 2 )
    quickLockPassword
                OBJECT-TYPE
    SYNTAX     INTEGER   (
    other(1),
    disabled(2),
    enabled (3)
    )
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The state of the quicklock password feature."
    : := ( security 3 )
    quickBlankScreen
                OBJECT-TYPE
    SYNTAX     INTEGER   (
    other(1),
    disabled(2),
    enabled (3)
    )
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The state of the quicklock blank screen
      feature."
    : := ( security 4 )
    disketteBootcontrol
                 OBJECT-TYPE
    SYNTAX     INTEGER   (
    other(1),
    disabled(2),
    enabled (3)
    )
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The state of the diskette boot control
      feature."
    : := ( security 5 )
    serialPortAControl
                  OBJECT-TYPE
    SYNTAX     INTEGER   (
    other(1),
    disabled(2),
    enabled (3)
    )
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The state of the access control for the
      primary serial port interface embedded in the
      Compaq system board."
    : := ( security 6 )
    serialPortBControl
                 OBJECT-TYPE
    SYNTAX     INTEGER   (
    other(1),
    disabled(2),
    enabled (3)
    )
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The state of the access control for the
      secondary serial port interface embedded in the
      Compaq system board."
    : := ( security 7 )
    parallelPortControl
                 OBJECT-TYPE
    SYNTAX     INTEGER   (
    other(1),
    disabled(2),
    enabled (3)
    )
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The state of the access control for the
      parallel port interface embedded in the Compaq
      system board."
    : := ( security 8 )
    floppyDisketteControl
                 OBJECT-TYPE
    SYNTAX     INTEGER   (
    other(1),
    disabled(2),
    enabled (3)
    )
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The state of the access control for the floppy
      diskette interface embedded in the Compaq
      system board."
    : := ( security 9 )
    fixedDiskControl
                 OBJECT-TYPE
    SYNTAX     INTEGER   (
    other(1),
    disabled(2),
    enabled (3)
    )
    ACCESS     read-only
    STATUS     mandatory
    DESCRIPTION
      "The state of the access control for the fixed
      disk interface embedded in the Compaq system
      board."
    : := ( security 10 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    machineId     OBJECT-TYPE
    SYNTAX       INTEGER
    ACCESS       read-only
    STATUS       mandatory
    DESCRIPTION
      "The machine ID."
    : := ( systemBoard 1 )
    machineProductName
                   OBJECT-TYPE
    SYNTAX       DisplayString (SIZE (0 . . . 255))
    ACCESS       read-only
    STATUS       mandatory
    DESCRIPTION
      "The machine product name."
    : := ( systemBoard 2 )
    auxiliaryInput
                  OBJECT-TYPE
    SYNTAX       INTEGER   (
           other(1),
           disabled(2),
           enabled (3)
           )
    ACCESS        read-only
    STATUS        mandatory
    DESCRIPTION
      "The state of the auxiliary input (pointing)
      device."
    : := ( systemBoard 4 )
    ______________________________________
      .COPYRGT.1992 Compaq Computer Corporation

    ______________________________________
    memoryModuleTable
                 OBJECT-TYPE
    SYNTAX     SEQUENCE OF MemoryModuleEntry
    ACCESS     not-accessible
    STATUS     optional
    DESCRIPTION
      "The table of memory module descriptions."
    : := ( systemBoard 5 )
    memoryModuleEntry
                 OBJECT-TYPE
    SYNTAX     MemoryModuleEntry
    ACCESS     not-accessible
    STATUS     optional
    DESCRIPTION
      "A memory module description."
    : := ( memoryModuleTable 1 )
    MemoryModuleEntry
                  : := SEQUENCE   (
    memoryBoardIndex
                   INTEGER,
    memoryModuleIndex
                   INTEGER,
    memoryModuleSize
                   INTEGER
    memoryBoardIndex
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     optional
    DESCRIPTION
      "The slot in which the memory board is
      installed."
    : := ( memoryModuleEntry 1 )
    memoryModuleIndex
                 OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     optional
    DESCRIPTION
      "The memory module number."
    : := ( memoryModuleEntry 2 )
    memoryModuleSize
                OBJECT-TYPE
    SYNTAX     INTEGER
    ACCESS     read-only
    STATUS     optional
    DESCRIPTION
      "Module memory size in kilobytes. A kilobyte
      of memory i