MIBs Provided with TCP/IP Services
2.1 Overview of the Host Resources MIB
hrFSLastFullBackupDate
hrFSLastPartialBackupDate
hrStorageSize
hrSWRunStatus
hrSystemDate
hrSystemInitialLoadDevice
hrSystemInitialLoadParameters
Note
For objects that are not implemented, the Host Resources MIB returns a
NoSuchObject
error status.
TCP/IP Services supports the objects in the Host Resources MIB as follows:
•
The
hrDeviceTable
includes all the devices known to the OpenVMS host
except those with the following characteristics:
Off line
Remote
UCB marked delete-on-zero-reference-count
Mailbox device
Device with remote terminal (DEV$M_RTT characteristic)
Template terminal-class device
LAT device (begins with _LT)
Virtual terminal device (begins with _VT)
Pseudoterminal device (begins with _FT)
Data items in the
hrDeviceTable
group have the following restrictions:
–
hrDeviceID
is always null OID (0.0).
–
hrDeviceErrors
is coded as follows:
Code
Condition
warning (3)
Error logging is in progress (OpenVMS UCB value UCB$M_
ERLOGIP).
running (2)
Software is valid and no error logging is in progress (OpenVMS
UCB value UCB$M_VALID).
unknown (1)
Any other OpenVMS status.
The
hrDeviceTable
now includes template devices (for example, DNFS0 for
NFS and DAD0 for virtual devices).
For network devices, only the template devices (those with unit number 0)
are displayed.
•
hrFSMountPoint
(1.3.6.1.2.1.25.3.8.1.2) is DNFSn. The device may change
between restarts or after a dismount/mount procedure.
•
In the
hrFSTable
group, if no file systems are mounted through NFS or
no information is accessible, a
"no such instance"
status is returned for a
get
request. Browsers respond differently to this message. For example,
2–4 MIBs Provided with TCP/IP Services