rfc1514.txt
来自「中、英文RFC文档大全打包下载完全版 .」· 文本 代码 · 共 1,851 行 · 第 1/5 页
TXT
1,851 行
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."Grillo & Waldbusser [Page 7]RFC 1514 Host Resources MIB September 1993 ::= { hrStorage 3 } hrStorageEntry OBJECT-TYPE SYNTAX HrStorageEntry ACCESS not-accessible STATUS mandatory 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 INTEGER, hrStorageType OBJECT IDENTIFIER, hrStorageDescr DisplayString, hrStorageAllocationUnits INTEGER, hrStorageSize INTEGER, hrStorageUsed INTEGER, hrStorageAllocationFailures Counter } hrStorageIndex OBJECT-TYPE SYNTAX INTEGER (1..2147483647) ACCESS read-only STATUS mandatory DESCRIPTION "A unique value for each logical storage area contained by the host." ::= { hrStorageEntry 1 } hrStorageType OBJECT-TYPE SYNTAX OBJECT IDENTIFIER ACCESS read-only STATUS mandatory DESCRIPTION "The type of storage represented by this entry." ::= { hrStorageEntry 2 } hrStorageDescr OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "A description of the type and instance of the storage described by this entry."Grillo & Waldbusser [Page 8]RFC 1514 Host Resources MIB September 1993 ::= { hrStorageEntry 3 } hrStorageAllocationUnits OBJECT-TYPE SYNTAX INTEGER (1..2147483647) ACCESS read-only STATUS mandatory 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 INTEGER (0..2147483647) ACCESS read-write STATUS mandatory DESCRIPTION "The size of the storage represented by this entry, in units of hrStorageAllocationUnits." ::= { hrStorageEntry 5 } hrStorageUsed OBJECT-TYPE SYNTAX INTEGER (0..2147483647) ACCESS read-only STATUS mandatory DESCRIPTION "The amount of the storage represented by this entry that is allocated, in units of hrStorageAllocationUnits." ::= { hrStorageEntry 6 } hrStorageAllocationFailures OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory 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 Counter, that it does not have a defined initial value. However, it is recommended that this object be initialized to zero." ::= { hrStorageEntry 7 }Grillo & Waldbusser [Page 9]RFC 1514 Host Resources MIB September 1993 -- The Host Resources Device Group -- -- Implementation of this group is mandatory for all host systems. -- -- 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 for some device types, for use with hrDeviceType hrDeviceTypes OBJECT IDENTIFIER ::= { hrDevice 1 } hrDeviceOther OBJECT IDENTIFIER ::= { hrDeviceTypes 1 } hrDeviceUnknown OBJECT IDENTIFIER ::= { hrDeviceTypes 2 } hrDeviceProcessor OBJECT IDENTIFIER ::= { hrDeviceTypes 3 } hrDeviceNetwork OBJECT IDENTIFIER ::= { hrDeviceTypes 4 } hrDevicePrinter OBJECT IDENTIFIER ::= { hrDeviceTypes 5 } hrDeviceDiskStorage OBJECT IDENTIFIER ::= { hrDeviceTypes 6 } hrDeviceVideo OBJECT IDENTIFIER ::= { hrDeviceTypes 10 } hrDeviceAudio OBJECT IDENTIFIER ::= { hrDeviceTypes 11 } hrDeviceCoprocessor OBJECT IDENTIFIER ::= { hrDeviceTypes 12 } hrDeviceKeyboard OBJECT IDENTIFIER ::= { hrDeviceTypes 13 } hrDeviceModem OBJECT IDENTIFIER ::= { hrDeviceTypes 14 } hrDeviceParallelPort OBJECT IDENTIFIER ::= { hrDeviceTypes 15 } hrDevicePointing OBJECT IDENTIFIER ::= { hrDeviceTypes 16 } hrDeviceSerialPort OBJECT IDENTIFIER ::= { hrDeviceTypes 17 } hrDeviceTape OBJECT IDENTIFIER ::= { hrDeviceTypes 18 } hrDeviceClock OBJECT IDENTIFIER ::= { hrDeviceTypes 19 } hrDeviceVolatileMemory OBJECT IDENTIFIER ::= { hrDeviceTypes 20 } hrDeviceNonVolatileMemory OBJECT IDENTIFIER ::= { hrDeviceTypes 21 } hrDeviceTable OBJECT-TYPE SYNTAX SEQUENCE OF HrDeviceEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The (conceptual) table of devices contained by the host." ::= { hrDevice 2 } hrDeviceEntry OBJECT-TYPE SYNTAX HrDeviceEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A (conceptual) entry for one device contained byGrillo & Waldbusser [Page 10]RFC 1514 Host Resources MIB September 1993 the host. As an example, an instance of the hrDeviceType object might be named hrDeviceType.3" INDEX { hrDeviceIndex } ::= { hrDeviceTable 1 } HrDeviceEntry ::= SEQUENCE { hrDeviceIndex INTEGER, hrDeviceType OBJECT IDENTIFIER, hrDeviceDescr DisplayString, hrDeviceID ProductID, hrDeviceStatus INTEGER, hrDeviceErrors Counter } hrDeviceIndex OBJECT-TYPE SYNTAX INTEGER (1..2147483647) ACCESS read-only STATUS mandatory 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 OBJECT IDENTIFIER ACCESS read-only STATUS mandatory 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."Grillo & Waldbusser [Page 11]RFC 1514 Host Resources MIB September 1993 ::= { hrDeviceEntry 2 } hrDeviceDescr OBJECT-TYPE SYNTAX DisplayString (SIZE (0..64)) ACCESS read-only STATUS mandatory 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 ACCESS read-only STATUS mandatory DESCRIPTION "The product ID for this device." ::= { hrDeviceEntry 4 } hrDeviceStatus OBJECT-TYPE SYNTAX INTEGER { unknown(1), running(2), warning(3), testing(4), down(5) } ACCESS read-only STATUS mandatory 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 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 }Grillo & Waldbusser [Page 12]RFC 1514 Host Resources MIB September 1993 hrDeviceErrors OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of errors detected on this device. It should be noted that as this object has a SYNTAX of Counter, that it does not have a defined initial value. However, it is recommended that this object be initialized to zero." ::= { hrDeviceEntry 6 } hrProcessorTable OBJECT-TYPE SYNTAX SEQUENCE OF HrProcessorEntry ACCESS not-accessible STATUS mandatory 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 ACCESS not-accessible STATUS mandatory 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 INTEGER } hrProcessorFrwID OBJECT-TYPEGrillo & Waldbusser [Page 13]RFC 1514 Host Resources MIB September 1993 SYNTAX ProductID ACCESS read-only STATUS mandatory DESCRIPTION "The product ID of the firmware associated with the processor." ::= { hrProcessorEntry 1 }
⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?