Network Working Group;;;S. Waldbusser
Request for Comments: 2790;;;LUCent Technologies Inc.
Obsoletes: 1514;;;;;P. Grillo
Category: Standards Track;;WeSync.com
March 2000

Host Resources MIB

Status of this Memo

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.; Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol.; Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2000).; All Rights Reserved.

Abstract

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
This memo obsoletes RFC1514, the "Host Resources MIB". This memo
extends that specification by clarifying changes based on
implementation and deployment eXPerience and documenting the Host
Resources MIB in SMIv2 format while remaining semantically identical
to the existing SMIv1-based MIB.

This memo defines a MIB for use with managing host systems.; The term

"host" is construed to mean any computer that communicates with other
similar computers attached to the internet and that is directly used
by one or more human beings. Although this MIB does not necessarily
apply to devices whose primary function is communications services
(e.g., terminal servers, routers, bridges, monitoring equipment),
such relevance is not explicitly precluded.; This MIB instruments
attributes common to all internet hosts including, for example, both
personal computers and systems that run variants of Unix.

Table of Contents

1 The SNMP Management Framework ............................;2
2 Host Resources MIB .......................................;3
3 IANA Considerations ......................................;4
4 Definitions ..............................................;4
4.1 Textual Conventions ....................................;6
4.2 The Host Resources System Group ........................;7
4.3 The Host Resources Storage Group .......................;9
4.4 The Host Resources Device Group ........................12
4.5 The Host Resources Running Software Group ..............26
4.6 The Host Resources; Running; Software; Performance
Group .................................................29
4.7 The Host Resources Installed Software Group ............30
4.8 Conformance Definitions ................................33
5 Type Definitions .........................................36
6 Internationalization Considerations ......................44
7 Security Considerations ..................................45
8 References ...............................................46
9 Acknowledgments ..........................................48
10 Authors" Addresses ......................................49
11 Intellectual Property ...................................49
12 Full Copyright Statement ................................50

1.; The SNMP Management Framework

The SNMP Management Framework presently consists of five major
components:

oAn overall architecture, described in RFC2571 [RFC2571].

oMechanisms for describing and naming objects and events for the

;;;;purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in STD
16, RFC1155 [RFC1155], STD 16, RFC1212 [RFC1212] and RFC1215
[RFC1215]. The second version, called SMIv2, is described in STD
58, RFC2578 [RFC2578], RFC2579 [RFC2579] and RFC2580
[RFC2580].

oMessage protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC1157 [RFC1157]. A second version of the
SNMP message protocol, which is not an Internet standards track
protocol, is called SNMPv2c and described in RFC1901 [RFC1901]
and RFC1906 [RFC1906]. The third version of the message protocol
is called SNMPv3 and described in RFC1906 [RFC1906], RFC2572
[RFC2572] and RFC2574 [RFC2574].

oProtocol operations for Accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC1157 [RFC1157]. A second set of protocol
operations and associated PDU formats is described in RFC1905
[RFC1905].

oA set of fundamental applications described in RFC2573 [RFC2573]
and the view-based access control mechanism described in RFC2575
[RFC2575].

A more detailed introduction to the current SNMP Management Framework
can be found in RFC2570 [RFC2570].

Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB.; Objects in the MIB are
defined using the mechanisms defined in the SMI.

This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in

SMIv1 during the translation process.; However, this loss of machine
readable information is not considered to change the semantics of the
MIB.

2.; Host Resources MIB

The Host Resources MIB defines a uniform set of objects useful for
the management of host computers.; Host computers are independent of
the operating system, network services, or any software application.

The Host Resources MIB defines objects which are common across many
computer system architectures.

In addition, there are objects in the SNMPv2-MIB [RFC1907] and IF-MIB
[RFC2233] which also provide host management functionality.
Implementation of the System and Interfaces groups is mandatory for
implementors of the Host Resources MIB.

The key Words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED","MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].

3.; IANA Considerations

This MIB contains type definitions for storage types, device types,
and file system types for use as values for the hrStorageType,
hrDeviceType, and hrFSType objects, respectively. As new computing
technologies are developed, new types need to be registered for these
technologies. The IANA (Internet Assigned Numbers Authority) is
designated as the registration authority for new registrations beyond
those published in this document. The IANA will maintain the HOST-
RESOURCES-TYPES module as new registrations are added and publish new
versions of this module.

Given the large number of such technologies and potential confusion
in naming of these technologies (such as a technology known by two
names or a name and an acronym), there is a real danger that more
than one registration might be created for what is essentially the
same technology. In order to ensure that future type registrations
are performed correctly, applications for new types will be reviewed
by a Designated Expert appointed by the IESG.

4.; Definitions

HOST-RESOURCES-MIB DEFINITIONS ::= BEGIN

IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2,
Integer32, Counter32, Gauge32, TimeTicks; FROM SNMPv2-SMI

TEXTUAL-CONVENTION, DisplayString,
TruthValue, DateAndTime, AutonomousTypeFROM SNMPv2-TC

MODULE-COMPLIANCE, OBJECT-GROUPFROM SNMPv2-CONF

InterfaceIndexOrZero;;;FROM IF-MIB;

hostResourcesMibModule MODULE-IDENTITY

;;;LAST-UPDATED "200003060000Z";-- 6 March 2000
ORGANIZATION "IETF Host Resources MIB Working Group"
CONTACT-INFO
"Steve Waldbusser
Postal: Lucent Technologies, Inc.
1213 Innsbruck Dr.
Sunnyvale, CA 94089
USA
Phone:; 650-318-1251
Fax:;650-318-1633
Email:; waldbusser@lucent.com

In addition, the Host Resources MIB mailing list is
dedicated to discussion of this MIB. To join the
mailing list, send a request message to
hostmib-request@andrew.cmu.edu. The mailing list
address is hostmib@andrew.cmu.edu."

DESCRIPTION
"This MIB is for use in managing host systems. The term
`host" is construed to mean any computer that communicates
with other similar computers attached to the internet and
that is directly used by one or more human beings. Although
this MIB does not necessarily apply to devices whose primary
function is communications services (e.g., terminal servers,
routers, bridges, monitoring equipment), such relevance is
not explicitly precluded.; This MIB instruments attributes
common to all internet hosts including, for example, both
personal computers and systems that run variants of Unix."

REVISION "200003060000Z";;;;;-- 6 March 2000

;;;DESCRIPTION
"Clarifications and bug fixes based on implementation
experience.; This revision was also reformatted in the SMIv2
format. The revisions made were:

New RFCdocument standards:
Added Copyright notice, updated introduction to SNMP
Framework, updated references section, added reference to
RFC2119, and added a meaningful Security Considerations
section.

New IANA considerations section for registration of new types

Conversion to new SMIv2 syntax for the following types and
macros:
Counter32, Integer32, Gauge32, MODULE-IDENTITY,
OBJECT-TYPE, TEXTUAL-CONVENTION, OBJECT-IDENTITY,
MODULE-COMPLIANCE, OBJECT-GROUP

Used new Textual Conventions:
TruthValue, DateAndTime, AutonomousType,
InterfaceIndexOrZero

Fixed typo in hrPrinterStatus.

Added missing error bits to hrPrinterDetectedErrorState and
clarified confusion resulting from suggested mappings to
hrPrinterStatus.

Clarified that size of objects of type
InternationalDisplayString is number of octets, not number
of encoded symbols.

Clarified the use of the following objects based on
implementation experience:
hrSystemInitialLoadDevice, hrSystemInitialLoadParameters,
hrMemorySize, hrStorageSize, hrStorageAllocationFailures,

;;;hrDeviceErrors, hrProcessorLoad, hrNetworkIfIndex,
hrDiskStorageCapacity, hrSWRunStatus, hrSWRunPerfCPU,
and hrSWInstalledDate.

Clarified implementation technique for hrSWInstalledTable.

Used new AUGMENTS clause for hrSWRunPerfTable.

Added Internationalization Considerations section.

This revision published as RFC2790."

REVISION "9910202200Z";-- 20 October, 1999
DESCRIPTION
"The original version of this MIB, published as
RFC1514."
::= { hrMIBAdminInfo 1 }

host;;OBJECT IDENTIFIER ::= { mib-2 25 }

hrSystem;;;;;OBJECT IDENTIFIER ::= { host 1 }
hrStorage;;;;OBJECT IDENTIFIER ::= { host 2 }
hrDevice;;;;;OBJECT IDENTIFIER ::= { host 3 }
hrSWRun OBJECT IDENTIFIER ::= { host 4 }
hrSWRunPerf;;OBJECT IDENTIFIER ::= { host 5 }
hrSWInstalledOBJECT IDENTIFIER ::= { host 6 }
hrMIBAdminInfo; OBJECT IDENTIFIER ::= { host 7 }

-- textual conventions

KBytes ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Storage size, expressed in units of 1024 bytes."
SYNTAX Integer32 (0..2147483647)

ProductID ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention is intended to identify the

manufacturer, model, and version of a specific
hardware or software product.; It is suggested that
these OBJECT IDENTIFIERs are allocated such that all
products from a particular manufacturer are registered

under a suBTree distinct to that manufacturer.; In
addition, all versions of a product should be
registered under a subtree distinct to that product.
With this strategy, a management station may uniquely
determine the manufacturer and/or model of a product
whose productID is unknown to the management station.
Objects of this type may be useful for inventory
purposes or for automatically detecting
incompatibilities or version mismatches between
various hardware and software components on a system.

For example, the product ID for the ACME 4860 66MHz
clock doubled processor might be:
enterprises.acme.acmeProcessors.a4860DX2.MHz66

A software product might be registered as:
enterprises.acme.acmeOperatingSystems.acmeDOS.six(6).one(1)
"
SYNTAX OBJECT IDENTIFIER

-- unknownProduct will be used for any unknown ProductID
-- unknownProduct OBJECT IDENTIFIER ::= { 0 0 }

InternationalDisplayString ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type is used to model textual information
in some character set.; A network management station
should use a local algorithm to determine which
character set is in use and how it should be
displayed.; Note that this character set may be
encoded with more than one octet per symbol, but will
most often be NVT ASCII. When a size clause is

specified for an object of this type, the size refers
to the length in octets, not the number of symbols."
SYNTAX OCTET STRING

-- The Host Resources System Group

hrSystemUptime OBJECT-TYPE
SYNTAX;;TimeTicks
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION

"The amount of time since this host was last
initialized.; Note that this is different from
sysUpTime in the SNMPv2-MIB [RFC1907] because
sysUpTime is the uptime of the network management
portion of the system."
::= { hrSystem 1 }

hrSystemDate OBJECT-TYPE
SYNTAX;;DateAndTime
MAX-ACCESS read-write
STATUS;;current
DESCRIPTION
"The host"s notion of the local date and time of day."
::= { hrSystem 2 }

hrSystemInitialLoadDevice OBJECT-TYPE
SYNTAX;;Integer32 (1..2147483647)
MAX-ACCESS read-write
STATUS;;current
DESCRIPTION
"The index of the hrDeviceEntry for the device from
which this host is configured to load its initial
operating system configuration (i.e., which operating
system code and/or boot parameters).

Note that writing to this object just changes the
configuration that will be used the next time the
operating system is loaded and does not actually cause
the reload to occur."

;;;;::= { hrSystem 3 }

hrSystemInitialLoadParameters OBJECT-TYPE
SYNTAX;;InternationalDisplayString (SIZE (0..128))
MAX-ACCESS read-write
STATUS;;current
DESCRIPTION
"This object contains the parameters (e.g. a pathname
and parameter) supplied to the load device when
requesting the initial operating system configuration
from that device.

Note that writing to this object just changes the
configuration that will be used the next time the
operating system is loaded and does not actually cause
the reload to occur."
::= { hrSystem 4 }

hrSystemNumUsers OBJECT-TYPE

SYNTAX;;Gauge32
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"The number of user sessions for which this host is
storing state information.; A session is a collection
of processes requiring a single act of user
authentication and possibly subject to collective job
control."
::= { hrSystem 5 }

hrSystemProcesses OBJECT-TYPE
SYNTAX;;Gauge32
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"The number of process contexts currently loaded or
running on this system."
::= { hrSystem 6 }

hrSystemMaxProcesses OBJECT-TYPE
SYNTAX;;Integer32 (0..2147483647)
MAX-ACCESS read-only

;;;;STATUS;;current
DESCRIPTION
"The maximum number of process contexts this system
can support.; If there is no fixed maximum, the value
should be zero.; On systems that have a fixed maximum,
this object can help diagnose failures that occur when
this maximum is reached."
::= { hrSystem 7 }

-- The Host Resources Storage Group

-- Registration point for storage types, for use with hrStorageType.
-- These are defined in the HOST-RESOURCES-TYPES module.
hrStorageTypes; OBJECT IDENTIFIER ::= { hrStorage 1 }

hrMemorySize OBJECT-TYPE
SYNTAX;;KBytes
UNITS;;;"KBytes"
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"The amount of physical read-write main memory,
typically RAM, contained by the host."
::= { hrStorage 2 }

hrStorageTable OBJECT-TYPE
SYNTAX;;SEQUENCE OF HrStorageEntry
MAX-ACCESS not-accessible
STATUS;;current
DESCRIPTION
"The (conceptual) table of logical storage areas on
the host.

An entry shall be placed in the storage table for each
logical area of storage that is allocated and has
fixed resource limits.; The amount of storage
represented in an entity is the amount actually usable
by the requesting entity, and excludes loss due to
formatting or file system reference information.

These entries are associated with logical storage

areas, as might be seen by an application, rather than
physical storage entities which are typically seen by
an operating system.; Storage such as tapes and
floppies without file systems on them are typically
not allocated in chunks by the operating system to
requesting applications, and therefore shouldn"t
appear in this table.; Examples of valid storage for
this table include disk partitions, file systems, ram
(for some architectures this is further segmented into
regular memory, extended memory, and so on), backing
store for virtual memory (`swap space").

This table is intended to be a useful diagnostic for
`out of memory" and `out of buffers" types of
failures.; In addition, it can be a useful performance
monitoring tool for tracking memory, disk, or buffer
usage."
::= { hrStorage 3 }

hrStorageEntry OBJECT-TYPE
SYNTAX;;HrStorageEntry
MAX-ACCESS not-accessible
STATUS;;current
DESCRIPTION
"A (conceptual) entry for one logical storage area on
the host.; As an example, an instance of the
hrStorageType object might be named hrStorageType.3"
INDEX { hrStorageIndex }
::= { hrStorageTable 1 }

HrStorageEntry ::= SEQUENCE {
hrStorageIndex;;;;Integer32,

hrStorageType;;;;;AutonomousType,

hrStorageDescr;;;;DisplayString,
hrStorageAllocationUnits;;Integer32,
hrStorageSize;;;;;Integer32,
hrStorageUsed;;;;;Integer32,
hrStorageAllocationFailures; Counter32
}

hrStorageIndex OBJECT-TYPE
SYNTAX;;Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"A unique value for each logical storage area
contained by the host."
::= { hrStorageEntry 1 }

hrStorageType OBJECT-TYPE
SYNTAX;;AutonomousType
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"The type of storage represented by this entry."
::= { hrStorageEntry 2 }

hrStorageDescr OBJECT-TYPE
SYNTAX;;DisplayString
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"A description of the type and instance of the storage
described by this entry."
::= { hrStorageEntry 3 }

hrStorageAllocationUnits OBJECT-TYPE
SYNTAX;;Integer32 (1..2147483647)
UNITS;;;"Bytes"
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"The size, in bytes, of the data objects allocated

from this pool.; If this entry is monitoring sectors,
blocks, buffers, or packets, for example, this number
will commonly be greater than one.; Otherwise this
number will typically be one."
::= { hrStorageEntry 4 }

hrStorageSize OBJECT-TYPE

SYNTAX;;Integer32 (0..2147483647)
MAX-ACCESS read-write
STATUS;;current
DESCRIPTION
"The size of the storage represented by this entry, in
units of hrStorageAllocationUnits. This object is
writable to allow remote configuration of the size of
the storage area in those cases where such an
operation makes sense and is possible on the
underlying system. For example, the amount of main
memory allocated to a buffer pool might be modified or
the amount of disk space allocated to virtual memory
might be modified."
::= { hrStorageEntry 5 }

hrStorageUsed OBJECT-TYPE
SYNTAX;;Integer32 (0..2147483647)
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"The amount of the storage represented by this entry
that is allocated, in units of
hrStorageAllocationUnits."
::= { hrStorageEntry 6 }

hrStorageAllocationFailures OBJECT-TYPE
SYNTAX;;Counter32
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"The number of requests for storage represented by

this entry that could not be honored due to not enough
storage.; It should be noted that as this object has a
SYNTAX of Counter32, that it does not have a defined
initial value.; However, it is recommended that this
object be initialized to zero, even though management
stations must not depend on such an initialization."
::= { hrStorageEntry 7 }

-- The Host Resources Device Group
--
-- The device group is useful for identifying and diagnosing the
-- devices on a system.; The hrDeviceTable contains common
-- information for any type of device.; In addition, some devices
-- have device-specific tables for more detailed information.; More
-- such tables may be defined in the future for other device types.

-- Registration point for device types, for use with hrDeviceType.

-- These are defined in the HOST-RESOURCES-TYPES module.
hrDeviceTypes;;OBJECT IDENTIFIER ::= { hrDevice 1 }

hrDeviceTable OBJECT-TYPE
SYNTAX;;SEQUENCE OF HrDeviceEntry
MAX-ACCESS not-accessible
STATUS;;current
DESCRIPTION
"The (conceptual) table of devices contained by the
host."
::= { hrDevice 2 }

hrDeviceEntry OBJECT-TYPE
SYNTAX;;HrDeviceEntry
MAX-ACCESS not-accessible
STATUS;;current
DESCRIPTION
"A (conceptual) entry for one device contained by the
host.; As an example, an instance of the hrDeviceType
object might be named hrDeviceType.3"
INDEX { hrDeviceIndex }
::= { hrDeviceTable 1 }

HrDeviceEntry ::= SEQUENCE {

hrDeviceIndexInteger32,
hrDeviceType;AutonomousType,
hrDeviceDescrDisplayString,
hrDeviceID;;;ProductID,
hrDeviceStatus; INTEGER,
hrDeviceErrors; Counter32
}

hrDeviceIndex OBJECT-TYPE
SYNTAX;;Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"A unique value for each device contained by the host.
The value for each device must remain constant at
least from one re-initialization of the agent to the
next re-initialization."
::= { hrDeviceEntry 1 }

hrDeviceType OBJECT-TYPE
SYNTAX;;AutonomousType
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION

"An indication of the type of device.

If this value is
`hrDeviceProcessor { hrDeviceTypes 3 }" then an entry
exists in the hrProcessorTable which corresponds to
this device.

If this value is
`hrDeviceNetwork { hrDeviceTypes 4 }", then an entry
exists in the hrNetworkTable which corresponds to this
device.

If this value is

`hrDevicePrinter { hrDeviceTypes 5 }", then an entry
exists in the hrPrinterTable which corresponds to this
device.

If this value is
`hrDeviceDiskStorage { hrDeviceTypes 6 }", then an
entry exists in the hrDiskStorageTable which
corresponds to this device."
::= { hrDeviceEntry 2 }

hrDeviceDescr OBJECT-TYPE
SYNTAX;;DisplayString (SIZE (0..64))
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"A textual description of this device, including the
device"s manufacturer and revision, and optionally,
its serial number."
::= { hrDeviceEntry 3 }

hrDeviceID OBJECT-TYPE
SYNTAX;;ProductID
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"The product ID for this device."
::= { hrDeviceEntry 4 }

hrDeviceStatus OBJECT-TYPE
SYNTAX;;INTEGER {
unknown(1),
running(2),
warning(3),
testing(4),
down(5)

}
MAX-ACCESS read-only
STATUS;;current

;;;;DESCRIPTION
"The current operational state of the device described
by this row of the table.; A value unknown(1)
indicates that the current state of the device is
unknown.; running(2) indicates that the device is up
and running and that no unusual error conditions are
known.; The warning(3) state indicates that agent has
been informed of an unusual error condition by the
operational software (e.g., a disk device driver) but
that the device is still "operational".; An example
would be a high number of soft errors on a disk.; A
value of testing(4), indicates that the device is not
available for use because it is in the testing state.
The state of down(5) is used only when the agent has
been informed that the device is not available for any
use."
::= { hrDeviceEntry 5 }

hrDeviceErrors OBJECT-TYPE
SYNTAX;;Counter32
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"The number of errors detected on this device.; It
should be noted that as this object has a SYNTAX of
Counter32, that it does not have a defined initial
value.; However, it is recommended that this object be
initialized to zero, even though management stations
must not depend on such an initialization."
::= { hrDeviceEntry 6 }

hrProcessorTable OBJECT-TYPE
SYNTAX;;SEQUENCE OF HrProcessorEntry

;;;;MAX-ACCESS not-accessible
STATUS;;current
DESCRIPTION
"The (conceptual) table of processors contained by the
host.

Note that this table is potentially sparse: a
(conceptual) entry exists only if the correspondent
value of the hrDeviceType object is
`hrDeviceProcessor"."
::= { hrDevice 3 }

hrProcessorEntry OBJECT-TYPE
SYNTAX;;HrProcessorEntry
MAX-ACCESS not-accessible
STATUS;;current
DESCRIPTION
"A (conceptual) entry for one processor contained by
the host.; The hrDeviceIndex in the index represents
the entry in the hrDeviceTable that corresponds to the
hrProcessorEntry.

As an example of how objects in this table are named,
an instance of the hrProcessorFrwID object might be
named hrProcessorFrwID.3"
INDEX { hrDeviceIndex }
::= { hrProcessorTable 1 }

HrProcessorEntry ::= SEQUENCE {
hrProcessorFrwID;ProductID,
hrProcessorLoad;;Integer32
}

hrProcessorFrwID OBJECT-TYPE
SYNTAX;;ProductID
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"The product ID of the firmware associated with the
processor."

;;;;::= { hrProcessorEntry 1 }

hrProcessorLoad OBJECT-TYPE
SYNTAX;;Integer32 (0..100)
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"The average, over the last minute, of the percentage
of time that this processor was not idle.
Implementations may approximate this one minute
smoothing period if necessary."
::= { hrProcessorEntry 2 }

hrNetworkTable OBJECT-TYPE
SYNTAX;;SEQUENCE OF HrNetworkEntry
MAX-ACCESS not-accessible
STATUS;;current
DESCRIPTION
"The (conceptual) table of network devices contained
by the host.

Note that this table is potentially sparse: a
(conceptual) entry exists only if the correspondent
value of the hrDeviceType object is
`hrDeviceNetwork"."
::= { hrDevice 4 }

hrNetworkEntry OBJECT-TYPE
SYNTAX;;HrNetworkEntry
MAX-ACCESS not-accessible
STATUS;;current
DESCRIPTION
"A (conceptual) entry for one network device contained
by the host.; The hrDeviceIndex in the index
represents the entry in the hrDeviceTable that
corresponds to the hrNetworkEntry.

As an example of how objects in this table are named,
an instance of the hrNetworkIfIndex object might be
named hrNetworkIfIndex.3"

;;;;INDEX { hrDeviceIndex }
::= { hrNetworkTable 1 }

HrNetworkEntry ::= SEQUENCE {
hrNetworkIfIndex;InterfaceIndexOrZero
}

hrNetworkIfIndex OBJECT-TYPE
SYNTAX;;InterfaceIndexOrZero
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"The value of ifIndex which corresponds to this
network device. If this device is not represented in
the ifTable, then this value shall be zero."
::= { hrNetworkEntry 1 }

hrPrinterTable OBJECT-TYPE
SYNTAX;;SEQUENCE OF HrPrinterEntry
MAX-ACCESS not-accessible
STATUS;;current
DESCRIPTION
"The (conceptual) table of printers local to the host.

Note that this table is potentially sparse: a
(conceptual) entry exists only if the correspondent
value of the hrDeviceType object is
`hrDevicePrinter"."
::= { hrDevice 5 }

hrPrinterEntry OBJECT-TYPE
SYNTAX;;HrPrinterEntry
MAX-ACCESS not-accessible
STATUS;;current
DESCRIPTION
"A (conceptual) entry for one printer local to the
host.; The hrDeviceIndex in the index represents the
entry in the hrDeviceTable that corresponds to the
hrPrinterEntry.

As an example of how objects in this table are named,
an instance of the hrPrinterStatus object might be

named hrPrinterStatus.3"
INDEX { hrDeviceIndex }
::= { hrPrinterTable 1 }

HrPrinterEntry ::= SEQUENCE {
hrPrinterStatus;;INTEGER,
hrPrinterDetectedErrorState OCTET STRING
}

hrPrinterStatus OBJECT-TYPE
SYNTAX;;INTEGER {
other(1),
unknown(2),
idle(3),
printing(4),
warmup(5)
}
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"The current status of this printer device."
::= { hrPrinterEntry 1 }

hrPrinterDetectedErrorState OBJECT-TYPE
SYNTAX;;OCTET STRING
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"This object represents any error conditions detected
by the printer.; The error conditions are encoded as
bits in an octet string, with the following
definitions:

Condition Bit #

lowPaper;;;0

noPaper;;;;1

;;;;;lowToner;;;2
noToner;;;;3
doorOpen;;;4
jammed;;;;;5
offline;;;;6
serviceRequested;;;7
inputTrayMissing;;;8
outputTrayMissing;;9
markerSupplyMissing; 10
outputNearFull;;;;11
outputFull12
inputTrayEmpty;;;;13
overduePreventMaint; 14

Bits are numbered starting with the most significant
bit of the first byte being bit 0, the least
significant bit of the first byte being bit 7, the
most significant bit of the second byte being bit 8,
and so on.; A one bit encodes that the condition was
detected, while a zero bit encodes that the condition
was not detected.

This object is useful for alerting an operator to
specific warning or error conditions that may occur,

especially those requiring human intervention."
::= { hrPrinterEntry 2 }

hrDiskStorageTable OBJECT-TYPE
SYNTAX;;SEQUENCE OF HrDiskStorageEntry
MAX-ACCESS not-accessible
STATUS;;current
DESCRIPTION
"The (conceptual) table of long-term storage devices
contained by the host.; In particular, disk devices
accessed remotely over a network are not included
here.

Note that this table is potentially sparse: a
(conceptual) entry exists only if the correspondent
value of the hrDeviceType object is
`hrDeviceDiskStorage"."
::= { hrDevice 6 }

hrDiskStorageEntry OBJECT-TYPE
SYNTAX;;HrDiskStorageEntry
MAX-ACCESS not-accessible
STATUS;;current

DESCRIPTION
"A (conceptual) entry for one long-term storage device
contained by the host.; The hrDeviceIndex in the index
represents the entry in the hrDeviceTable that
corresponds to the hrDiskStorageEntry. As an example,
an instance of the hrDiskStorageCapacity object might
be named hrDiskStorageCapacity.3"
INDEX { hrDeviceIndex }
::= { hrDiskStorageTable 1 }

HrDiskStorageEntry ::= SEQUENCE {
hrDiskStorageAccess INTEGER,
hrDiskStorageMedia; INTEGER,
hrDiskStorageRemoveble;;;TruthValue,

hrDiskStorageCapacity;;;;KBytes
}

hrDiskStorageAccess OBJECT-TYPE
SYNTAX;;INTEGER {
readWrite(1),
readOnly(2)
}
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"An indication if this long-term storage device is
readable and writable or only readable.; This should
reflect the media type, any write-protect mechanism,
and any device configuration that affects the entire
device."
::= { hrDiskStorageEntry 1 }

hrDiskStorageMedia OBJECT-TYPE
SYNTAX;;INTEGER {
other(1),
unknown(2),
hardDisk(3),
floppyDisk(4),
opticalDiskROM(5),
opticalDiskWORM(6),;;-- Write Once Read Many
opticalDiskRW(7),
ramDisk(8)
}
MAX-ACCESS read-only

;;;;STATUS;;current
DESCRIPTION
"An indication of the type of media used in this long-
term storage device."

::= { hrDiskStorageEntry 2 }

hrDiskStorageRemoveble OBJECT-TYPE
SYNTAX;;TruthValue
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"Denotes whether or not the disk media may be removed
from the drive."
::= { hrDiskStorageEntry 3 }

hrDiskStorageCapacity OBJECT-TYPE
SYNTAX;;KBytes
UNITS;;;"KBytes"
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"The total size for this long-term storage device. If
the media is removable and is currently removed, this
value should be zero."
::= { hrDiskStorageEntry 4 }

hrPartitionTable OBJECT-TYPE
SYNTAX;;SEQUENCE OF HrPartitionEntry
MAX-ACCESS not-accessible
STATUS;;current
DESCRIPTION
"The (conceptual) table of partitions for long-term
storage devices contained by the host.; In particular,
partitions accessed remotely over a network are not
included here."
::= { hrDevice 7 }

hrPartitionEntry OBJECT-TYPE
SYNTAX;;HrPartitionEntry
MAX-ACCESS not-accessible
STATUS;;current
DESCRIPTION
"A (conceptual) entry for one partition.; The

hrDeviceIndex in the index represents the entry in the
hrDeviceTable that corresponds to the
hrPartitionEntry.

As an example of how objects in this table are named,
an instance of the hrPartitionSize object might be
named hrPartitionSize.3.1"
INDEX { hrDeviceIndex, hrPartitionIndex }
::= { hrPartitionTable 1 }

HrPartitionEntry ::= SEQUENCE {
hrPartitionIndex;;;;;Integer32,
hrPartitionLabel;;;;;InternationalDisplayString,
hrPartitionIDOCTET STRING,
hrPartitionSize KBytes,
hrPartitionFSIndex;;;Integer32
}

hrPartitionIndex OBJECT-TYPE
SYNTAX;;Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"A unique value for each partition on this long-term
storage device.; The value for each long-term storage
device must remain constant at least from one re-
initialization of the agent to the next re-
initialization."
::= { hrPartitionEntry 1 }

hrPartitionLabel OBJECT-TYPE
SYNTAX;;InternationalDisplayString (SIZE (0..128))
MAX-ACCESS read-only
STATUS;;current

;;;;DESCRIPTION
"A textual description of this partition."
::= { hrPartitionEntry 2 }

hrPartitionID OBJECT-TYPE
SYNTAX;;OCTET STRING
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"A descriptor which uniquely represents this partition
to the responsible operating system.; On some systems,
this might take on a binary representation."
::= { hrPartitionEntry 3 }

hrPartitionSize OBJECT-TYPE
SYNTAX;;KBytes
UNITS;;;"KBytes"
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"The size of this partition."
::= { hrPartitionEntry 4 }

hrPartitionFSIndex OBJECT-TYPE

SYNTAX;;Integer32 (0..2147483647)
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"The index of the file system mounted on this
partition.; If no file system is mounted on this
partition, then this value shall be zero.; Note that
multiple partitions may point to one file system,
denoting that that file system resides on those
partitions.; Multiple file systems may not reside on
one partition."
::= { hrPartitionEntry 5 }

-- The File System Table

-- Registration point for popular File System types,
-- for use with hrFSType. These are defined in the
-- HOST-RESOURCES-TYPES module.
hrFSTypes;;;;OBJECT IDENTIFIER ::= { hrDevice 9 }

hrFSTable OBJECT-TYPE

;;;;SYNTAX;;SEQUENCE OF HrFSEntry
MAX-ACCESS not-accessible
STATUS;;current
DESCRIPTION
"The (conceptual) table of file systems local to this
host or remotely mounted from a file server.; File
systems that are in only one user"s environment on a
multi-user system will not be included in this table."
::= { hrDevice 8 }

hrFSEntry OBJECT-TYPE
SYNTAX;;HrFSEntry
MAX-ACCESS not-accessible
STATUS;;current
DESCRIPTION
"A (conceptual) entry for one file system local to
this host or remotely mounted from a file server.
File systems that are in only one user"s environment
on a multi-user system will not be included in this
table.

As an example of how objects in this table are named,
an instance of the hrFSMountPoint object might be
named hrFSMountPoint.3"
INDEX { hrFSIndex }
::= { hrFSTable 1 }

HrFSEntry ::= SEQUENCE {
hrFSIndexInteger32,
hrFSMountPoint;;;InternationalDisplayString,
hrFSRemoteMountPoint;;;;;InternationalDisplayString,
hrFSType;AutonomousType,
hrFSAccess; INTEGER,

hrFSBootable;;;;;TruthValue,
hrFSStorageIndex;Integer32,
hrFSLastFullBackupDate;;;DateAndTime,
hrFSLastPartialBackupDateDateAndTime
}

hrFSIndex OBJECT-TYPE
SYNTAX;;Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"A unique value for each file system local to this
host.; The value for each file system must remain
constant at least from one re-initialization of the
agent to the next re-initialization."
::= { hrFSEntry 1 }

hrFSMountPoint OBJECT-TYPE
SYNTAX;;InternationalDisplayString (SIZE(0..128))
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"The path name of the root of this file system."
::= { hrFSEntry 2 }

hrFSRemoteMountPoint OBJECT-TYPE
SYNTAX;;InternationalDisplayString (SIZE(0..128))
MAX-ACCESS read-only
STATUS;;current
DESCRIPTION
"A description of the name and/or address of the
server that this file system is mounted from.; This
may also include parameters such as the mount point on
the remote file system.; If this is not a remote file
system, this string should have a length of zero."
::= { hrFSEntry 3 }

hrFSType OBJECT-TYPE