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.

Legal Lengths:
8
,
11

DateAndTime

The host's notion of the local date and time of day.

Legal values:
1 .. 2147483647

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.

Legal Lengths:
0 .. 128

InternationalDisplayString

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.

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.

The number of process contexts currently loaded or
running on this system.

Legal values:
0 .. 2147483647

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.

Legal values:
0 .. 2147483647

KBytes

The amount of physical read-write main memory,
typically RAM, contained by the host.

Legal values:
1 .. 2147483647

The value of the hrSWRunIndex for the hrSWRunEntry
that represents the primary operating system running
on this host.  This object is useful for quickly and
uniquely identifying that primary operating system.

The value of sysUpTime when an entry in the
hrSWInstalledTable was last added, renamed, or
deleted.  Because this table is likely to contain many
entries, polling of this object allows a management
station to determine when re-downloading of the table
might be useful.

The value of sysUpTime when the hrSWInstalledTable
was last completely updated.  Because caching of this
data will be a popular implementation strategy,
retrieval of this object allows a management station
to obtain a guarantee that no data in this table is
older than the indicated time.

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.

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

AutonomousType

The type of storage represented by this entry.

Legal Lengths:
0 .. 255

DisplayString

A description of the type and instance of the storage
described by this entry.

Legal values:
1 .. 2147483647

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.

Legal values:
0 .. 2147483647

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.

Legal values:
0 .. 2147483647

The amount of the storage represented by this entry
that is allocated, in units of
hrStorageAllocationUnits.

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.

The (conceptual) table of devices contained by the
host.

A (conceptual) entry for one device contained by the
host.  As an example, an instance of the hrDeviceType
object might be named hrDeviceType.3

AutonomousType

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.

Legal Lengths:
0 .. 64

DisplayString

A textual description of this device, including the
device's manufacturer and revision, and optionally,
its serial number.

ProductID

The product ID for this device.

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.

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.

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'.

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

ProductID

The product ID of the firmware associated with the
processor.

Legal values:
0 .. 100

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.

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'.

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

Legal values:
0 .. 2147483647

InterfaceIndexOrZero

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.

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'.

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

The current status of this printer device.

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
     outputFull           12
     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.

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'.

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

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.

An indication of the type of media used in this long-
term storage device.

TruthValue

(ENUM list below)

Denotes whether or not the disk media may be removed
from the drive.

Legal values:
0 .. 2147483647

KBytes

The total size for this long-term storage device. If
the media is removable and is currently removed, this
value should be zero.

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.

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

Legal Lengths:
0 .. 128

InternationalDisplayString

A textual description of this partition.

A descriptor which uniquely represents this partition
to the responsible operating system.  On some systems,
this might take on a binary representation.

Legal values:
0 .. 2147483647

KBytes

The size of this partition.

Legal values:
0 .. 2147483647

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.

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.

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

Legal Lengths:
0 .. 128

InternationalDisplayString

The path name of the root of this file system.

Legal Lengths:
0 .. 128

InternationalDisplayString

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.

AutonomousType

The value of this object identifies the type of this
file system.

An indication if this file system is logically
configured by the operating system to be readable and
writable or only readable.  This does not represent
any local access-control policy, except one that is
applied to the file system as a whole.

TruthValue

(ENUM list below)

A flag indicating whether this file system is
bootable.

Legal values:
0 .. 2147483647

The index of the hrStorageEntry that represents
information about this file system.  If there is no
such information available, then this value shall be
zero.  The relevant storage entry will be useful in
tracking the percent usage of this file system and
diagnosing errors that may occur when it runs out of
space.

Legal Lengths:
8
,
11

DateAndTime

The last date at which this complete file system was
copied to another storage device for backup.  This
        information is useful for ensuring that backups are
        being performed regularly.
If this information is not known, then this variable
        shall have the value corresponding to January 1, year
        0000, 00:00:00.0, which is encoded as
        (hex)'00 00 01 01 00 00 00 00'.

Legal Lengths:
8
,
11

DateAndTime

The last date at which a portion of this file system
was copied to another storage device for backup.  This
information is useful for ensuring that backups are
being performed regularly.

If this information is not known, then this variable
shall have the value corresponding to January 1, year
0000, 00:00:00.0, which is encoded as
(hex)'00 00 01 01 00 00 00 00'.

The (conceptual) table of software running on the
host.

A (conceptual) entry for one piece of software
running on the host Note that because the installed
software table only contains information for software
stored locally on this host, not every piece of
running software will be found in the installed
software table.  This is true of software that was
loaded and run from a non-local source, such as a
network-mounted file system.

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

Legal Lengths:
0 .. 64

InternationalDisplayString

A textual description of this running piece of
software, including the manufacturer, revision,  and
the name by which it is commonly known.  If this
software was installed locally, this should be the
same string as used in the corresponding
hrSWInstalledName.

ProductID

The product ID of this running piece of software.

Legal Lengths:
0 .. 128

InternationalDisplayString

A description of the location on long-term storage
(e.g. a disk drive) from which this software was
loaded.

Legal Lengths:
0 .. 128

InternationalDisplayString

A description of the parameters supplied to this
software when it was initially loaded.

The type of this software.

The status of this running piece of software.
Setting this value to invalid(4) shall cause this
software to stop running and to be unloaded. Sets to
other values are not valid.

The (conceptual) table of running software
performance metrics.

A (conceptual) entry containing software performance
metrics.  As an example, an instance of the
hrSWRunPerfCPU object might be named
hrSWRunPerfCPU.1287

Legal values:
0 .. 2147483647

The number of centi-seconds of the total system's CPU
resources consumed by this process.  Note that on a
multi-processor system, this value may increment by
more than one centi-second in one centi-second of real
(wall clock) time.

Legal values:
0 .. 2147483647

KBytes

The total amount of real system memory allocated to
this process.

The (conceptual) table of software installed on this
host.

A (conceptual) entry for a piece of software
installed on this host.

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

Legal Lengths:
0 .. 64

InternationalDisplayString

A textual description of this installed piece of
software, including the manufacturer, revision, the
name by which it is commonly known, and optionally,
its serial number.

ProductID

The product ID of this installed piece of software.

The type of this software.

Legal Lengths:
8
,
11

DateAndTime

The last-modification date of this application as it
would appear in a directory listing.

If this information is not known, then this variable
shall have the value corresponding to January 1, year
0000, 00:00:00.0, which is encoded as
(hex)'00 00 01 01 00 00 00 00'.

Represents textual information taken from the NVT ASCII
character set, as defined in pages 4, 10-11 of RFC 854.
To summarize RFC 854, the NVT ASCII repertoire specifies:
  - the use of character codes 0-127 (decimal)
  - the graphics characters (32-126) are interpreted as
                US ASCII
  - NUL, LF, CR, BEL, BS, HT, VT and FF have the special
                meanings specified in RFC 854
  - the other 25 codes have no standard interpretation
  - the sequence 'CR LF' means newline
  - the sequence 'CR NUL' means carriage-return
  - an 'LF' not preceded by a 'CR' means moving to the
                same column on the next line.
  - the sequence 'CR x' for any x other than LF or NUL is
                illegal.  (Note that this also means that a string may
                end with either 'CR LF' or 'CR NUL', but not with CR.)
Any object defined using this syntax may not exceed 255
            characters in length.

Represents an independently extensible type identification
value.  It may, for example, indicate a particular sub-tree
with further MIB definitions, or define a particular type of
protocol or hardware.

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.

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)

Storage size, expressed in units of 1024 bytes.

A date-time specification.
field  octets  contents                  range
            -----  ------  --------                  -----
              1      1-2   year*                     0..65536
              2       3    month                     1..12
              3       4    day                       1..31
              4       5    hour                      0..23
              5       6    minutes                   0..59
              6       7    seconds                   0..60
                           (use 60 for leap-second)
              7       8    deci-seconds              0..9
              8       9    direction from UTC        '+' / '-'
              9      10    hours from UTC*           0..13
             10      11    minutes from UTC          0..59
* Notes:
            - the value of year is in network-byte order
            - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be
            displayed as:
                 1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone
            information (fields 8-10) is not present.

Represents a boolean value.

This textual convention is an extension of the
InterfaceIndex convention.  The latter defines a greater
than zero value used to identify an interface or interface
sub-layer in the managed system.  This extension permits the
additional value of zero.  the value zero is object-specific
and must therefore be defined as part of the description of
any object which uses this syntax.  Examples of the usage of
zero might include situations where interface was unknown,
or when none or all interfaces need to be referenced.