|
|
|
|
|
|
|
|
HP SNMP/XL User's Guide: HP 3000 MPE/iX Computer Systems > Appendix B Supported MIB Objects
Non-Standard HP Extended MIB Objects |
|
The MIB defined in this section is consistent with the Internet Activity Board's (IAB's) network management strategy. The next section contains the specification of all HP object types contained in the MIB. The object types are defined using the following fields: The abstract syntax for the object type, presented using ASN.1. This must resolve to an instance of the ASN.1 type Object Syntax defined in the SMI. A textual description of the semantics of the object type. Implementations should ensure that their interpretation of the object type fulfills this definition since this MIB is intended for use in multi-vendor environments. As such it is vital that object types have consistent meaning across all machines. HP-MIB{iso org(3) dod(6) internet(1) private(4) enterprises(1) 11} DEFINITIONS ::= BEGIN IMPORTS private, enterprises, OBJECT-TYPE, Counter, NetworkAddress, Gauge, FROM RFC 1155-SMI;
END SYNTAX: SEQUENCE OF Ieee8023MacEntry ACCESS: read-only STATUS: mandatory DESCRIPTION: "A list of IEEE 802.3 Interface entries." ::= { ieee8023Mac 1 }: +
ACCESS: read-only STATUS: mandatory DESCRIPTION, "An interface entry containing objects for the IEEE 802.3 networking layer." ::= { ieee8023MacTable 1 }: + SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex." ::= { ieee8023MacEntry 1 }: + SYNTAX: Counter ACCESS: read-only STATUS: mandatory DESCRIPTION: "Number of frames successfully transmitted." ::= { ieee8023MacEntry 2 }: + SYNTAX: Counter ACCESS: read-only STATUS: mandatory DESCRIPTION: "Number of frames not transmitted." ::= { ieee8023MacEntry 3 }: + SYNTAX: Counter ACCESS: read-only STATUS: mandatory DESCRIPTION: "Number of frames deferred because the medium was busy." ::= { ieee8023MacEntry 4 }: + SYNTAX: Counter ACCESS: read-only STATUS: mandatory DESCRIPTION: "Total number of transmit attempts that were retransmitted due to collisions." ::= { ieee8023MacEntry 5}: + SYNTAX: Counter ACCESS: read-only STATUS: mandatory DESCRIPTION: "Number of transmit attempts that are involved in a single collision and are subsequently transmitted successfully." ::= { ieee8023MacEntry 6}: + SYNTAX: Counter ACCESS: read-only STATUS: mandatory DESCRIPTION: "Number of transmit attempts that are involved in between 2 and 15 collision attempts and are subsequently transmitted successfully." ::= { ieee8023MacEntry 7}: + SYNTAX: Counter ACCESS: read-only STATUS: mandatory DESCRIPTION: "Number of transmit attempts that are involved in more than 15 collision attempts and are subsequently transmitted successfully." ::= { ieee8023MacEntry 8}: + SYNTAX: Counter ACCESS: read-only STATUS: mandatory DESCRIPTION: "Number of transmit attempts aborted because a collision occurred after the allotted channel time had elapsed." ::= { ieee8023MacEntry 9 }: + SYNTAX: Counter ACCESS: read-only STATUS: mandatory DESCRIPTION: "Number of times that carrier sense was lost when attempting to transmit." ::= { ieee8023MacEntry 10 }: + SYNTAX: Counter ACCESS: read-only STATUS: mandatory DESCRIPTION: "Number of times no heart beat was indicated after a transmission." ::= { ieee8023MacEntry 11 }: + SYNTAX: Counter ACCESS: read-only STATUS: mandatory DESCRIPTION: "Number of frames successfully received." ::= { ieee8023MacEntry 12 }: + SYNTAX: Counter ACCESS: read-only STATUS: mandatory DESCRIPTION: "Number of frames received that were not delivered because the software buffer was overrun when frames were sent faster than they could be received." ::= { ieee8023MacEntry 13 }: + SYNTAX: Counter ACCESS: read-only STATUS: mandatory DESCRIPTION: "Number of Cyclical Redundancy Check (CRC) errors detected." ::= { ieee8023MacEntry 14 }: + SYNTAX: Counter ACCESS: read-only STATUS: mandatory DESCRIPTION: "Number of frames received that were both misaligned and had bad CRC." ::= { ieee8023MacEntry 15 }: + SYNTAX: Counter ACCESS: read-only STATUS: mandatory DESCRIPTION: "Number of frames received that were lost due to lack of resources." ::= { ieee8023MacEntry 16 }: + SYNTAX: Counter ACCESS: read-only STATUS: mandatory DESCRIPTION: "Number of frames received with errors in the control field." ::= { ieee8023MacEntry 17 }: + SYNTAX: Counter ACCESS: read-only STATUS: mandatory DESCRIPTION: "Number of frames dropped because the type field or sap field referenced an invalid protocol." ::= { ieee8023MacEntry 18 }: + SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "The number of volumes that are currently mounted on the system." ::= { volume 1 } SYNTAX: SEQUENCE OF volumeEntryACCESS: read-only STATUS: mandatory DESCRIPTION: "Volume table." ::= { volume 2 } SYNTAX: volumeEntry ACCESS: read-only STATUS: mandatory DESCRIPTION: "Each entry contains objects that define the volume." ::= { volumeTable 1 }
SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "The logical device number for the volume." ::= { volumeEntry 1 } SYNTAX: DisplayString ACCESS: read-only STATUS: mandatory DESCRIPTION: This is the volume set name combined with the member name that uniquely distinguishes the actual volume on the system.: ::= { volumeEntry 2 } SYNTAX: DisplayString ACCESS: read-only STATUS: mandatory DESCRIPTION: "The type of the actual hardware device, e.g. HP7935." ::= { volumeEntry 3 } SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "The logical sector size of the volume in bytes." ::= { volumeEntry 4 }
ACCESS: read-only STATUS: mandatory DESCRIPTION: "The type of volume set." ::= { volumeEntry 5 } SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "The capacity of the volume in sectors." ::= { volumeEntry 6 } SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "The total overhead which consists of everything on a volume that is not set aside for file space use. This includes volume label, file label table, directory, volume set information table, free space map, transient space, and transaction management overhead." ::= { volumeEntry 7 } SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "The total MPE transient space overhead for the volume." ::= { volumeEntry 8 } SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "The configured maximum transient space for the volume." ::= { volumeEntry 9 } SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "The directory space overhead that is reserved for accounting information." ::= { volumeEntry 10 } SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "The file label overhead for this volume." ::= { volumeEntry 11 } SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "The transaction management overhead for this volume." ::= { volumeEntry 12 } SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "The spool file disk usage which consists of the volume space that is used by hidden spool files that are not part of the permanent file space." ::= { volumeEntry 13 } SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "The space used for permanent files on this volume." ::= { volumeEntry 14 } SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "The space used for temporary files on this volume." ::= { volumeEntry 15 } SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "The total free space for the volume." ::= { volumeEntry 16 } SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "The largest contiguous free space area on the volume." ::= { volumeEntry 17 } SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "Number of processors currently active in the system. A processor is considered active if it is capable of being dispatched." ::= { processor 1 } SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "The number of processors physically present in the system." ::= { processor 2 }
ACCESS: read-only STATUS: mandatory DESCRIPTION: "Setting this object to 1 will result in the measurement interface being turned on for the global processor statistics which will increase the amount of CPU used by the SNMP/XL Agent. Setting this object to 0 will cause the measurement interface to be disabled for the global processor statistics. When the measurement interface is enabled, the cpuUtilization object described below may be obtained." ::= { processor 3 } SYNTAX: INTEGER ACCESS: read-only STATUS: mandatory DESCRIPTION: "The overall CPU utilization percentage on the system. If the system has more than one processor, the value returned is averaged out over all of the processors that are present. The measurement interface must be enabled in order to get a valid value returned for this object (see above object). The number returned is the percentage of the CPU that was used since the last time the number was sampled. This value is consistent with various HP performance tools such as Glance/XL. If the measurement interface is not enabled, the value returned will be 0." ::= { processor 4 } SYNTAX: Gauge ACCESS: read-only STATUS: mandatory DESCRIPTION: "The number of trap destinations." ::= { trap 1 }: + SYNTAX: SEQUENCE OF TrapDestinationEntry ACCESS: read-write STATUS: mandatory DESCRIPTION: "List of addresses to which the agent sends traps." ::= { trap 2 }: +
ACCESS: read-write STATUS: mandatory DESCRIPTION: "Each entry contains the address to which the agent sends traps." ::= { trapDestinationTable 1 }: + The names for all object types in the HP-MIB are defined explicitly either in the Internet-standard MIB or in other documents which conform to the naming conventions of the Structure of Management Information (SMI). The SMI requires that conformant management protocols define mechanisms for identifying individual instances of those object types for a particular network element. Each instance of any object type defined in the MIB is identified in SNMP operations by a unique name called its "variable name." In general, the name of an SNMP variable is an OBJECT IDENTIFIER of the form x.y, where x is the name of a non-aggregate object type defined in the MIB and y is an OBJECT IDENTIFIER fragment that, in a way specific to the named object type, identifies the desired instance. The type-specific naming of object instances is defined below for a number of classes of object types. Instances of an object type to which none of the following naming conventions are applicable are named by OBJECT IDENTIFIERs of the form x.0, where x is the name of said object type in the MIB definition. For example, suppose one wanted to identify an instance of the variable sysDescr in the Internet-standard MIB. The object class for sysDescr would look like:
Hence, the object type, x, would be 1.3.6.1.2.1.1.1 to which is appended an instance sub-identifier of 0. That is, 1.3.6.1.2.1.1.1.0 identifies the one and only instance of sysDescr. The name of an ethernet-like interface, s, is the OBJECT IDENTIFIER value of the form i, where i has the value of that instance of the ifIndex object type associated with s. For each object type, t, for which the defined name, n, has a prefix of ieee8023MacTableEntry, an instance, i, of t is named by an OBJECT IDENTIFIER of the form n.s, where s is the name of the ethernet-like interface about which i represents information. For example, suppose one wanted to identify the instance of the variable ieee8023MacNotTransmitted, associated with interface 2. Accordingly, ieee8023MacNotTransmitted.2 would identify the desired instance. The name of a trap destination, x, is the OBJECT IDENTIFIER of the form a.b.c.d such that a.b.c.d is the value (in the familiar "dot" notation) of that instance of the trapDestination object type associated with x. For each object type, t, for which the defined name, n, has a prefix of trapDestinationEntry, an instance, i, of t is named by an OBJECT IDENTIFIER of the form n.y, where y is the name of the trap destination about which i represents information. For example, suppose one wanted to find out if the agent is sending traps to 15.2.112.113. Accordingly, trapDestination.15.2.112.113 would identify the desired instance. Note that if the entry does not exist, trapDestination will return the value 0.0.0.0, rather than noSuchName. The name of a logical disk drive volume, s, is the OBJECT IDENTIFIER value of the form i, where i has the value of that instance of the volumeLDEV object type associated with s. For each object type, t, for which the defined name, n, has a prefix of volumeEntry, an instance, i, of t is named by an OBJECT IDENTIFIER of the form n.s, where s is the name of the logical disk drive volume about which i represents information. For example, suppose one wanted to identify the instance of the variable volumeName, associated with volume 2. Accordingly, volumeName.2 would identify the desired instance. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||
|
|
|
|||||||||
|
|||||||||
