MIBs Provided with TCP/IP Services 2.1 Overview of the Host Resources MIB
TCPIP$SNMP_REQUEST.EXE responds with no output and returns directly to the DCL prompt.
After an NFS mount, the following information is returned in response to a Get request. The data items implemented for OpenVMS (refer to RFC 1514) are:
–hrFSIndex.
–hrFSMountPoint is the local DNFS device name.
–hrFSRemoteMountPoint is the remote file system.
–hrFSType is implemented as:
•OID 1.3.6.1.2.1.25.3.9.1, for OpenVMS if the file system is not a UNIX style container file system.
•hrFSNFS, OID 1.3.6.1.2.1.25.3.9.14, if the file system is a TCP/IP Services container file system or a UNIX host.
–hrFSAccess, as defined in RFC 1514.
–hrFSBootable is always HRM_FALSE (integer 2).
–hrFSStorageIndex is always 0.
–hrFSLastFullBackupDate is unknown time. This entry is encoded according to RFC 1514 as a hexadecimal value
–hrFSLastPartialBackupDate is unknown time. This information is not available for OpenVMS systems. Instead, hexadecimal value
•hrProcessorFrwID (OID prefix 1.3.6.1.2.1.25.3.3.1.1) is not implemented on OpenVMS VAX. On this type of system, it returns standard null OID (0.0). For example:
1.3.6.1.2.1.25.3.3.1.1.1 = 0.0
For OpenVMS Alpha (firmware version
1.3.6.1.2.1.25.3.3.1.1.1 = 1.3.6.1.2.1.25.3.3.1.1.1.5.56.7
•Data items in the hrDiskStorage table have the following restrictions:
–hrDiskStorageMediais always ‘‘unknown’’ (2).
–hrDiskStorageRemoveble is always ‘‘false’’ (2). Note the incorrect spelling of ‘‘removable’’ in hrDiskStorageRemoveble (from RFC 1514).
•hrStorageType always contains the value of hrStorageFixedDisk
(1.3.6.1.2.1.25.2.1.4).
2.2Overview of MIB II
The Standard MIB (MIB II) described in RFC 1213 defines a set of objects useful for managing TCP/IP Internet entities. MIB II supports network monitoring and managing from the Transport layer down to the Physical layer of the TCP/IP internet stack. This MIB also provides information on how connections are established and how packets are routed through the Internet. For more information about MIB architecture, see Section 3.2.
MIBs Provided with TCP/IP Services
