HOST-RESOURCES-MIB DEFINITIONS ::= BEGIN

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

TEXTUAL-CONVENTION, DisplayString, TruthValue, DateAndTime, AutonomousType FROM SNMPv2-TC

MODULE-COMPLIANCE, OBJECT-GROUP FROM 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 RFC document standards:
       Added Copyright notice, updated introduction to SNMP
       Framework, updated references section, added reference to
       RFC 2119, 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 } hrSWInstalled OBJECT 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