7 Network Working Group S. Waldbusser
8 Request for Comments: 2790 Lucent Technologies Inc.
9 Obsoletes: 1514 P. Grillo
10 Category: Standards Track WeSync.com
18 This document specifies an Internet standards track protocol for the
19 Internet community, and requests discussion and suggestions for
20 improvements. Please refer to the current edition of the "Internet
21 Official Protocol Standards" (STD 1) for the standardization state
22 and status of this protocol. Distribution of this memo is unlimited.
26 Copyright (C) The Internet Society (2000). All Rights Reserved.
30 This memo defines a portion of the Management Information Base (MIB)
31 for use with network management protocols in the Internet community.
32 This memo obsoletes RFC 1514, the "Host Resources MIB". This memo
33 extends that specification by clarifying changes based on
34 implementation and deployment experience and documenting the Host
35 Resources MIB in SMIv2 format while remaining semantically identical
36 to the existing SMIv1-based MIB.
38 This memo defines a MIB for use with managing host systems. The term
39 "host" is construed to mean any computer that communicates with other
40 similar computers attached to the internet and that is directly used
41 by one or more human beings. Although this MIB does not necessarily
42 apply to devices whose primary function is communications services
43 (e.g., terminal servers, routers, bridges, monitoring equipment),
44 such relevance is not explicitly precluded. This MIB instruments
45 attributes common to all internet hosts including, for example, both
46 personal computers and systems that run variants of Unix.
58 Waldbusser & Grillo Standards Track [Page 1]
60 RFC 2790 Host Resources MIB March 2000
65 1 The SNMP Management Framework ............................ 2
66 2 Host Resources MIB ....................................... 3
67 3 IANA Considerations ...................................... 4
68 4 Definitions .............................................. 4
69 4.1 Textual Conventions .................................... 6
70 4.2 The Host Resources System Group ........................ 7
71 4.3 The Host Resources Storage Group ....................... 9
72 4.4 The Host Resources Device Group ........................ 12
73 4.5 The Host Resources Running Software Group .............. 26
74 4.6 The Host Resources Running Software Performance
75 Group ................................................. 29
76 4.7 The Host Resources Installed Software Group ............ 30
77 4.8 Conformance Definitions ................................ 33
78 5 Type Definitions ......................................... 36
79 6 Internationalization Considerations ...................... 44
80 7 Security Considerations .................................. 45
81 8 References ............................................... 46
82 9 Acknowledgments .......................................... 48
83 10 Authors' Addresses ...................................... 49
84 11 Intellectual Property ................................... 49
85 12 Full Copyright Statement ................................ 50
87 1. The SNMP Management Framework
89 The SNMP Management Framework presently consists of five major
92 o An overall architecture, described in RFC 2571 [RFC2571].
94 o Mechanisms for describing and naming objects and events for the
95 purpose of management. The first version of this Structure of
96 Management Information (SMI) is called SMIv1 and described in STD
97 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215
98 [RFC1215]. The second version, called SMIv2, is described in STD
99 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580
102 o Message protocols for transferring management information. The
103 first version of the SNMP message protocol is called SNMPv1 and
104 described in STD 15, RFC 1157 [RFC1157]. A second version of the
105 SNMP message protocol, which is not an Internet standards track
106 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901]
107 and RFC 1906 [RFC1906]. The third version of the message protocol
108 is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572
109 [RFC2572] and RFC 2574 [RFC2574].
114 Waldbusser & Grillo Standards Track [Page 2]
116 RFC 2790 Host Resources MIB March 2000
119 o Protocol operations for accessing management information. The
120 first set of protocol operations and associated PDU formats is
121 described in STD 15, RFC 1157 [RFC1157]. A second set of protocol
122 operations and associated PDU formats is described in RFC 1905
125 o A set of fundamental applications described in RFC 2573 [RFC2573]
126 and the view-based access control mechanism described in RFC 2575
129 A more detailed introduction to the current SNMP Management Framework
130 can be found in RFC 2570 [RFC2570].
132 Managed objects are accessed via a virtual information store, termed
133 the Management Information Base or MIB. Objects in the MIB are
134 defined using the mechanisms defined in the SMI.
136 This memo specifies a MIB module that is compliant to the SMIv2. A
137 MIB conforming to the SMIv1 can be produced through the appropriate
138 translations. The resulting translated MIB must be semantically
139 equivalent, except where objects or events are omitted because no
140 translation is possible (use of Counter64). Some machine readable
141 information in SMIv2 will be converted into textual descriptions in
142 SMIv1 during the translation process. However, this loss of machine
143 readable information is not considered to change the semantics of the
146 2. Host Resources MIB
148 The Host Resources MIB defines a uniform set of objects useful for
149 the management of host computers. Host computers are independent of
150 the operating system, network services, or any software application.
152 The Host Resources MIB defines objects which are common across many
153 computer system architectures.
155 In addition, there are objects in the SNMPv2-MIB [RFC1907] and IF-MIB
156 [RFC2233] which also provide host management functionality.
157 Implementation of the System and Interfaces groups is mandatory for
158 implementors of the Host Resources MIB.
160 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
161 "SHOULD", "SHOULD NOT", "RECOMMENDED","MAY", and "OPTIONAL" in this
162 document are to be interpreted as described in [RFC2119].
170 Waldbusser & Grillo Standards Track [Page 3]
172 RFC 2790 Host Resources MIB March 2000
175 3. IANA Considerations
177 This MIB contains type definitions for storage types, device types,
178 and file system types for use as values for the hrStorageType,
179 hrDeviceType, and hrFSType objects, respectively. As new computing
180 technologies are developed, new types need to be registered for these
181 technologies. The IANA (Internet Assigned Numbers Authority) is
182 designated as the registration authority for new registrations beyond
183 those published in this document. The IANA will maintain the HOST-
184 RESOURCES-TYPES module as new registrations are added and publish new
185 versions of this module.
187 Given the large number of such technologies and potential confusion
188 in naming of these technologies (such as a technology known by two
189 names or a name and an acronym), there is a real danger that more
190 than one registration might be created for what is essentially the
191 same technology. In order to ensure that future type registrations
192 are performed correctly, applications for new types will be reviewed
193 by a Designated Expert appointed by the IESG.
197 HOST-RESOURCES-MIB DEFINITIONS ::= BEGIN
200 MODULE-IDENTITY, OBJECT-TYPE, mib-2,
201 Integer32, Counter32, Gauge32, TimeTicks FROM SNMPv2-SMI
203 TEXTUAL-CONVENTION, DisplayString,
204 TruthValue, DateAndTime, AutonomousType FROM SNMPv2-TC
206 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
208 InterfaceIndexOrZero FROM IF-MIB;
210 hostResourcesMibModule MODULE-IDENTITY
211 LAST-UPDATED "200003060000Z" -- 6 March 2000
212 ORGANIZATION "IETF Host Resources MIB Working Group"
215 Postal: Lucent Technologies, Inc.
221 Email: waldbusser@lucent.com
226 Waldbusser & Grillo Standards Track [Page 4]
228 RFC 2790 Host Resources MIB March 2000
231 In addition, the Host Resources MIB mailing list is
232 dedicated to discussion of this MIB. To join the
233 mailing list, send a request message to
234 hostmib-request@andrew.cmu.edu. The mailing list
235 address is hostmib@andrew.cmu.edu."
238 "This MIB is for use in managing host systems. The term
239 `host' is construed to mean any computer that communicates
240 with other similar computers attached to the internet and
241 that is directly used by one or more human beings. Although
242 this MIB does not necessarily apply to devices whose primary
243 function is communications services (e.g., terminal servers,
244 routers, bridges, monitoring equipment), such relevance is
245 not explicitly precluded. This MIB instruments attributes
246 common to all internet hosts including, for example, both
247 personal computers and systems that run variants of Unix."
249 REVISION "200003060000Z" -- 6 March 2000
251 "Clarifications and bug fixes based on implementation
252 experience. This revision was also reformatted in the SMIv2
253 format. The revisions made were:
255 New RFC document standards:
256 Added Copyright notice, updated introduction to SNMP
257 Framework, updated references section, added reference to
258 RFC 2119, and added a meaningful Security Considerations
261 New IANA considerations section for registration of new types
263 Conversion to new SMIv2 syntax for the following types and
265 Counter32, Integer32, Gauge32, MODULE-IDENTITY,
266 OBJECT-TYPE, TEXTUAL-CONVENTION, OBJECT-IDENTITY,
267 MODULE-COMPLIANCE, OBJECT-GROUP
269 Used new Textual Conventions:
270 TruthValue, DateAndTime, AutonomousType,
273 Fixed typo in hrPrinterStatus.
275 Added missing error bits to hrPrinterDetectedErrorState and
276 clarified confusion resulting from suggested mappings to
282 Waldbusser & Grillo Standards Track [Page 5]
284 RFC 2790 Host Resources MIB March 2000
287 Clarified that size of objects of type
288 InternationalDisplayString is number of octets, not number
291 Clarified the use of the following objects based on
292 implementation experience:
293 hrSystemInitialLoadDevice, hrSystemInitialLoadParameters,
294 hrMemorySize, hrStorageSize, hrStorageAllocationFailures,
295 hrDeviceErrors, hrProcessorLoad, hrNetworkIfIndex,
296 hrDiskStorageCapacity, hrSWRunStatus, hrSWRunPerfCPU,
297 and hrSWInstalledDate.
299 Clarified implementation technique for hrSWInstalledTable.
301 Used new AUGMENTS clause for hrSWRunPerfTable.
303 Added Internationalization Considerations section.
305 This revision published as RFC2790."
307 REVISION "9910202200Z" -- 20 October, 1999
309 "The original version of this MIB, published as
311 ::= { hrMIBAdminInfo 1 }
313 host OBJECT IDENTIFIER ::= { mib-2 25 }
315 hrSystem OBJECT IDENTIFIER ::= { host 1 }
316 hrStorage OBJECT IDENTIFIER ::= { host 2 }
317 hrDevice OBJECT IDENTIFIER ::= { host 3 }
318 hrSWRun OBJECT IDENTIFIER ::= { host 4 }
319 hrSWRunPerf OBJECT IDENTIFIER ::= { host 5 }
320 hrSWInstalled OBJECT IDENTIFIER ::= { host 6 }
321 hrMIBAdminInfo OBJECT IDENTIFIER ::= { host 7 }
323 -- textual conventions
325 KBytes ::= TEXTUAL-CONVENTION
328 "Storage size, expressed in units of 1024 bytes."
329 SYNTAX Integer32 (0..2147483647)
331 ProductID ::= TEXTUAL-CONVENTION
334 "This textual convention is intended to identify the
338 Waldbusser & Grillo Standards Track [Page 6]
340 RFC 2790 Host Resources MIB March 2000
343 manufacturer, model, and version of a specific
344 hardware or software product. It is suggested that
345 these OBJECT IDENTIFIERs are allocated such that all
346 products from a particular manufacturer are registered
347 under a subtree distinct to that manufacturer. In
348 addition, all versions of a product should be
349 registered under a subtree distinct to that product.
350 With this strategy, a management station may uniquely
351 determine the manufacturer and/or model of a product
352 whose productID is unknown to the management station.
353 Objects of this type may be useful for inventory
354 purposes or for automatically detecting
355 incompatibilities or version mismatches between
356 various hardware and software components on a system.
358 For example, the product ID for the ACME 4860 66MHz
359 clock doubled processor might be:
360 enterprises.acme.acmeProcessors.a4860DX2.MHz66
362 A software product might be registered as:
363 enterprises.acme.acmeOperatingSystems.acmeDOS.six(6).one(1)
365 SYNTAX OBJECT IDENTIFIER
367 -- unknownProduct will be used for any unknown ProductID
368 -- unknownProduct OBJECT IDENTIFIER ::= { 0 0 }
370 InternationalDisplayString ::= TEXTUAL-CONVENTION
373 "This data type is used to model textual information
374 in some character set. A network management station
375 should use a local algorithm to determine which
376 character set is in use and how it should be
377 displayed. Note that this character set may be
378 encoded with more than one octet per symbol, but will
379 most often be NVT ASCII. When a size clause is
380 specified for an object of this type, the size refers
381 to the length in octets, not the number of symbols."
384 -- The Host Resources System Group
386 hrSystemUptime OBJECT-TYPE
394 Waldbusser & Grillo Standards Track [Page 7]
396 RFC 2790 Host Resources MIB March 2000
399 "The amount of time since this host was last
400 initialized. Note that this is different from
401 sysUpTime in the SNMPv2-MIB [RFC1907] because
402 sysUpTime is the uptime of the network management
403 portion of the system."
406 hrSystemDate OBJECT-TYPE
408 MAX-ACCESS read-write
411 "The host's notion of the local date and time of day."
414 hrSystemInitialLoadDevice OBJECT-TYPE
415 SYNTAX Integer32 (1..2147483647)
416 MAX-ACCESS read-write
419 "The index of the hrDeviceEntry for the device from
420 which this host is configured to load its initial
421 operating system configuration (i.e., which operating
422 system code and/or boot parameters).
424 Note that writing to this object just changes the
425 configuration that will be used the next time the
426 operating system is loaded and does not actually cause
427 the reload to occur."
430 hrSystemInitialLoadParameters OBJECT-TYPE
431 SYNTAX InternationalDisplayString (SIZE (0..128))
432 MAX-ACCESS read-write
435 "This object contains the parameters (e.g. a pathname
436 and parameter) supplied to the load device when
437 requesting the initial operating system configuration
440 Note that writing to this object just changes the
441 configuration that will be used the next time the
442 operating system is loaded and does not actually cause
443 the reload to occur."
446 hrSystemNumUsers OBJECT-TYPE
450 Waldbusser & Grillo Standards Track [Page 8]
452 RFC 2790 Host Resources MIB March 2000
459 "The number of user sessions for which this host is
460 storing state information. A session is a collection
461 of processes requiring a single act of user
462 authentication and possibly subject to collective job
466 hrSystemProcesses OBJECT-TYPE
471 "The number of process contexts currently loaded or
472 running on this system."
475 hrSystemMaxProcesses OBJECT-TYPE
476 SYNTAX Integer32 (0..2147483647)
480 "The maximum number of process contexts this system
481 can support. If there is no fixed maximum, the value
482 should be zero. On systems that have a fixed maximum,
483 this object can help diagnose failures that occur when
484 this maximum is reached."
487 -- The Host Resources Storage Group
489 -- Registration point for storage types, for use with hrStorageType.
490 -- These are defined in the HOST-RESOURCES-TYPES module.
491 hrStorageTypes OBJECT IDENTIFIER ::= { hrStorage 1 }
493 hrMemorySize OBJECT-TYPE
499 "The amount of physical read-write main memory,
500 typically RAM, contained by the host."
506 Waldbusser & Grillo Standards Track [Page 9]
508 RFC 2790 Host Resources MIB March 2000
511 hrStorageTable OBJECT-TYPE
512 SYNTAX SEQUENCE OF HrStorageEntry
513 MAX-ACCESS not-accessible
516 "The (conceptual) table of logical storage areas on
519 An entry shall be placed in the storage table for each
520 logical area of storage that is allocated and has
521 fixed resource limits. The amount of storage
522 represented in an entity is the amount actually usable
523 by the requesting entity, and excludes loss due to
524 formatting or file system reference information.
526 These entries are associated with logical storage
527 areas, as might be seen by an application, rather than
528 physical storage entities which are typically seen by
529 an operating system. Storage such as tapes and
530 floppies without file systems on them are typically
531 not allocated in chunks by the operating system to
532 requesting applications, and therefore shouldn't
533 appear in this table. Examples of valid storage for
534 this table include disk partitions, file systems, ram
535 (for some architectures this is further segmented into
536 regular memory, extended memory, and so on), backing
537 store for virtual memory (`swap space').
539 This table is intended to be a useful diagnostic for
540 `out of memory' and `out of buffers' types of
541 failures. In addition, it can be a useful performance
542 monitoring tool for tracking memory, disk, or buffer
546 hrStorageEntry OBJECT-TYPE
547 SYNTAX HrStorageEntry
548 MAX-ACCESS not-accessible
551 "A (conceptual) entry for one logical storage area on
552 the host. As an example, an instance of the
553 hrStorageType object might be named hrStorageType.3"
554 INDEX { hrStorageIndex }
555 ::= { hrStorageTable 1 }
557 HrStorageEntry ::= SEQUENCE {
558 hrStorageIndex Integer32,
562 Waldbusser & Grillo Standards Track [Page 10]
564 RFC 2790 Host Resources MIB March 2000
567 hrStorageType AutonomousType,
568 hrStorageDescr DisplayString,
569 hrStorageAllocationUnits Integer32,
570 hrStorageSize Integer32,
571 hrStorageUsed Integer32,
572 hrStorageAllocationFailures Counter32
575 hrStorageIndex OBJECT-TYPE
576 SYNTAX Integer32 (1..2147483647)
580 "A unique value for each logical storage area
581 contained by the host."
582 ::= { hrStorageEntry 1 }
584 hrStorageType OBJECT-TYPE
585 SYNTAX AutonomousType
589 "The type of storage represented by this entry."
590 ::= { hrStorageEntry 2 }
592 hrStorageDescr OBJECT-TYPE
597 "A description of the type and instance of the storage
598 described by this entry."
599 ::= { hrStorageEntry 3 }
601 hrStorageAllocationUnits OBJECT-TYPE
602 SYNTAX Integer32 (1..2147483647)
607 "The size, in bytes, of the data objects allocated
608 from this pool. If this entry is monitoring sectors,
609 blocks, buffers, or packets, for example, this number
610 will commonly be greater than one. Otherwise this
611 number will typically be one."
612 ::= { hrStorageEntry 4 }
614 hrStorageSize OBJECT-TYPE
618 Waldbusser & Grillo Standards Track [Page 11]
620 RFC 2790 Host Resources MIB March 2000
623 SYNTAX Integer32 (0..2147483647)
624 MAX-ACCESS read-write
627 "The size of the storage represented by this entry, in
628 units of hrStorageAllocationUnits. This object is
629 writable to allow remote configuration of the size of
630 the storage area in those cases where such an
631 operation makes sense and is possible on the
632 underlying system. For example, the amount of main
633 memory allocated to a buffer pool might be modified or
634 the amount of disk space allocated to virtual memory
636 ::= { hrStorageEntry 5 }
638 hrStorageUsed OBJECT-TYPE
639 SYNTAX Integer32 (0..2147483647)
643 "The amount of the storage represented by this entry
644 that is allocated, in units of
645 hrStorageAllocationUnits."
646 ::= { hrStorageEntry 6 }
648 hrStorageAllocationFailures OBJECT-TYPE
653 "The number of requests for storage represented by
654 this entry that could not be honored due to not enough
655 storage. It should be noted that as this object has a
656 SYNTAX of Counter32, that it does not have a defined
657 initial value. However, it is recommended that this
658 object be initialized to zero, even though management
659 stations must not depend on such an initialization."
660 ::= { hrStorageEntry 7 }
662 -- The Host Resources Device Group
664 -- The device group is useful for identifying and diagnosing the
665 -- devices on a system. The hrDeviceTable contains common
666 -- information for any type of device. In addition, some devices
667 -- have device-specific tables for more detailed information. More
668 -- such tables may be defined in the future for other device types.
670 -- Registration point for device types, for use with hrDeviceType.
674 Waldbusser & Grillo Standards Track [Page 12]
676 RFC 2790 Host Resources MIB March 2000
679 -- These are defined in the HOST-RESOURCES-TYPES module.
680 hrDeviceTypes OBJECT IDENTIFIER ::= { hrDevice 1 }
682 hrDeviceTable OBJECT-TYPE
683 SYNTAX SEQUENCE OF HrDeviceEntry
684 MAX-ACCESS not-accessible
687 "The (conceptual) table of devices contained by the
691 hrDeviceEntry OBJECT-TYPE
693 MAX-ACCESS not-accessible
696 "A (conceptual) entry for one device contained by the
697 host. As an example, an instance of the hrDeviceType
698 object might be named hrDeviceType.3"
699 INDEX { hrDeviceIndex }
700 ::= { hrDeviceTable 1 }
702 HrDeviceEntry ::= SEQUENCE {
703 hrDeviceIndex Integer32,
704 hrDeviceType AutonomousType,
705 hrDeviceDescr DisplayString,
706 hrDeviceID ProductID,
707 hrDeviceStatus INTEGER,
708 hrDeviceErrors Counter32
711 hrDeviceIndex OBJECT-TYPE
712 SYNTAX Integer32 (1..2147483647)
716 "A unique value for each device contained by the host.
717 The value for each device must remain constant at
718 least from one re-initialization of the agent to the
719 next re-initialization."
720 ::= { hrDeviceEntry 1 }
722 hrDeviceType OBJECT-TYPE
723 SYNTAX AutonomousType
730 Waldbusser & Grillo Standards Track [Page 13]
732 RFC 2790 Host Resources MIB March 2000
735 "An indication of the type of device.
738 `hrDeviceProcessor { hrDeviceTypes 3 }' then an entry
739 exists in the hrProcessorTable which corresponds to
743 `hrDeviceNetwork { hrDeviceTypes 4 }', then an entry
744 exists in the hrNetworkTable which corresponds to this
748 `hrDevicePrinter { hrDeviceTypes 5 }', then an entry
749 exists in the hrPrinterTable which corresponds to this
753 `hrDeviceDiskStorage { hrDeviceTypes 6 }', then an
754 entry exists in the hrDiskStorageTable which
755 corresponds to this device."
756 ::= { hrDeviceEntry 2 }
758 hrDeviceDescr OBJECT-TYPE
759 SYNTAX DisplayString (SIZE (0..64))
763 "A textual description of this device, including the
764 device's manufacturer and revision, and optionally,
766 ::= { hrDeviceEntry 3 }
768 hrDeviceID OBJECT-TYPE
773 "The product ID for this device."
774 ::= { hrDeviceEntry 4 }
776 hrDeviceStatus OBJECT-TYPE
786 Waldbusser & Grillo Standards Track [Page 14]
788 RFC 2790 Host Resources MIB March 2000
795 "The current operational state of the device described
796 by this row of the table. A value unknown(1)
797 indicates that the current state of the device is
798 unknown. running(2) indicates that the device is up
799 and running and that no unusual error conditions are
800 known. The warning(3) state indicates that agent has
801 been informed of an unusual error condition by the
802 operational software (e.g., a disk device driver) but
803 that the device is still 'operational'. An example
804 would be a high number of soft errors on a disk. A
805 value of testing(4), indicates that the device is not
806 available for use because it is in the testing state.
807 The state of down(5) is used only when the agent has
808 been informed that the device is not available for any
810 ::= { hrDeviceEntry 5 }
812 hrDeviceErrors OBJECT-TYPE
817 "The number of errors detected on this device. It
818 should be noted that as this object has a SYNTAX of
819 Counter32, that it does not have a defined initial
820 value. However, it is recommended that this object be
821 initialized to zero, even though management stations
822 must not depend on such an initialization."
823 ::= { hrDeviceEntry 6 }
825 hrProcessorTable OBJECT-TYPE
826 SYNTAX SEQUENCE OF HrProcessorEntry
827 MAX-ACCESS not-accessible
830 "The (conceptual) table of processors contained by the
833 Note that this table is potentially sparse: a
834 (conceptual) entry exists only if the correspondent
835 value of the hrDeviceType object is
836 `hrDeviceProcessor'."
842 Waldbusser & Grillo Standards Track [Page 15]
844 RFC 2790 Host Resources MIB March 2000
847 hrProcessorEntry OBJECT-TYPE
848 SYNTAX HrProcessorEntry
849 MAX-ACCESS not-accessible
852 "A (conceptual) entry for one processor contained by
853 the host. The hrDeviceIndex in the index represents
854 the entry in the hrDeviceTable that corresponds to the
857 As an example of how objects in this table are named,
858 an instance of the hrProcessorFrwID object might be
859 named hrProcessorFrwID.3"
860 INDEX { hrDeviceIndex }
861 ::= { hrProcessorTable 1 }
863 HrProcessorEntry ::= SEQUENCE {
864 hrProcessorFrwID ProductID,
865 hrProcessorLoad Integer32
868 hrProcessorFrwID OBJECT-TYPE
873 "The product ID of the firmware associated with the
875 ::= { hrProcessorEntry 1 }
877 hrProcessorLoad OBJECT-TYPE
878 SYNTAX Integer32 (0..100)
882 "The average, over the last minute, of the percentage
883 of time that this processor was not idle.
884 Implementations may approximate this one minute
885 smoothing period if necessary."
886 ::= { hrProcessorEntry 2 }
888 hrNetworkTable OBJECT-TYPE
889 SYNTAX SEQUENCE OF HrNetworkEntry
890 MAX-ACCESS not-accessible
893 "The (conceptual) table of network devices contained
898 Waldbusser & Grillo Standards Track [Page 16]
900 RFC 2790 Host Resources MIB March 2000
903 Note that this table is potentially sparse: a
904 (conceptual) entry exists only if the correspondent
905 value of the hrDeviceType object is
909 hrNetworkEntry OBJECT-TYPE
910 SYNTAX HrNetworkEntry
911 MAX-ACCESS not-accessible
914 "A (conceptual) entry for one network device contained
915 by the host. The hrDeviceIndex in the index
916 represents the entry in the hrDeviceTable that
917 corresponds to the hrNetworkEntry.
919 As an example of how objects in this table are named,
920 an instance of the hrNetworkIfIndex object might be
921 named hrNetworkIfIndex.3"
922 INDEX { hrDeviceIndex }
923 ::= { hrNetworkTable 1 }
925 HrNetworkEntry ::= SEQUENCE {
926 hrNetworkIfIndex InterfaceIndexOrZero
929 hrNetworkIfIndex OBJECT-TYPE
930 SYNTAX InterfaceIndexOrZero
934 "The value of ifIndex which corresponds to this
935 network device. If this device is not represented in
936 the ifTable, then this value shall be zero."
937 ::= { hrNetworkEntry 1 }
939 hrPrinterTable OBJECT-TYPE
940 SYNTAX SEQUENCE OF HrPrinterEntry
941 MAX-ACCESS not-accessible
944 "The (conceptual) table of printers local to the host.
946 Note that this table is potentially sparse: a
947 (conceptual) entry exists only if the correspondent
948 value of the hrDeviceType object is
954 Waldbusser & Grillo Standards Track [Page 17]
956 RFC 2790 Host Resources MIB March 2000
959 hrPrinterEntry OBJECT-TYPE
960 SYNTAX HrPrinterEntry
961 MAX-ACCESS not-accessible
964 "A (conceptual) entry for one printer local to the
965 host. The hrDeviceIndex in the index represents the
966 entry in the hrDeviceTable that corresponds to the
969 As an example of how objects in this table are named,
970 an instance of the hrPrinterStatus object might be
971 named hrPrinterStatus.3"
972 INDEX { hrDeviceIndex }
973 ::= { hrPrinterTable 1 }
975 HrPrinterEntry ::= SEQUENCE {
976 hrPrinterStatus INTEGER,
977 hrPrinterDetectedErrorState OCTET STRING
980 hrPrinterStatus OBJECT-TYPE
991 "The current status of this printer device."
992 ::= { hrPrinterEntry 1 }
994 hrPrinterDetectedErrorState OBJECT-TYPE
999 "This object represents any error conditions detected
1000 by the printer. The error conditions are encoded as
1001 bits in an octet string, with the following
1010 Waldbusser & Grillo Standards Track [Page 18]
1012 RFC 2790 Host Resources MIB March 2000
1024 markerSupplyMissing 10
1028 overduePreventMaint 14
1030 Bits are numbered starting with the most significant
1031 bit of the first byte being bit 0, the least
1032 significant bit of the first byte being bit 7, the
1033 most significant bit of the second byte being bit 8,
1034 and so on. A one bit encodes that the condition was
1035 detected, while a zero bit encodes that the condition
1038 This object is useful for alerting an operator to
1039 specific warning or error conditions that may occur,
1040 especially those requiring human intervention."
1041 ::= { hrPrinterEntry 2 }
1043 hrDiskStorageTable OBJECT-TYPE
1044 SYNTAX SEQUENCE OF HrDiskStorageEntry
1045 MAX-ACCESS not-accessible
1048 "The (conceptual) table of long-term storage devices
1049 contained by the host. In particular, disk devices
1050 accessed remotely over a network are not included
1053 Note that this table is potentially sparse: a
1054 (conceptual) entry exists only if the correspondent
1055 value of the hrDeviceType object is
1056 `hrDeviceDiskStorage'."
1059 hrDiskStorageEntry OBJECT-TYPE
1060 SYNTAX HrDiskStorageEntry
1061 MAX-ACCESS not-accessible
1066 Waldbusser & Grillo Standards Track [Page 19]
1068 RFC 2790 Host Resources MIB March 2000
1072 "A (conceptual) entry for one long-term storage device
1073 contained by the host. The hrDeviceIndex in the index
1074 represents the entry in the hrDeviceTable that
1075 corresponds to the hrDiskStorageEntry. As an example,
1076 an instance of the hrDiskStorageCapacity object might
1077 be named hrDiskStorageCapacity.3"
1078 INDEX { hrDeviceIndex }
1079 ::= { hrDiskStorageTable 1 }
1081 HrDiskStorageEntry ::= SEQUENCE {
1082 hrDiskStorageAccess INTEGER,
1083 hrDiskStorageMedia INTEGER,
1084 hrDiskStorageRemoveble TruthValue,
1085 hrDiskStorageCapacity KBytes
1088 hrDiskStorageAccess OBJECT-TYPE
1093 MAX-ACCESS read-only
1096 "An indication if this long-term storage device is
1097 readable and writable or only readable. This should
1098 reflect the media type, any write-protect mechanism,
1099 and any device configuration that affects the entire
1101 ::= { hrDiskStorageEntry 1 }
1103 hrDiskStorageMedia OBJECT-TYPE
1110 opticalDiskWORM(6), -- Write Once Read Many
1114 MAX-ACCESS read-only
1117 "An indication of the type of media used in this long-
1118 term storage device."
1122 Waldbusser & Grillo Standards Track [Page 20]
1124 RFC 2790 Host Resources MIB March 2000
1127 ::= { hrDiskStorageEntry 2 }
1129 hrDiskStorageRemoveble OBJECT-TYPE
1131 MAX-ACCESS read-only
1134 "Denotes whether or not the disk media may be removed
1136 ::= { hrDiskStorageEntry 3 }
1138 hrDiskStorageCapacity OBJECT-TYPE
1141 MAX-ACCESS read-only
1144 "The total size for this long-term storage device. If
1145 the media is removable and is currently removed, this
1146 value should be zero."
1147 ::= { hrDiskStorageEntry 4 }
1149 hrPartitionTable OBJECT-TYPE
1150 SYNTAX SEQUENCE OF HrPartitionEntry
1151 MAX-ACCESS not-accessible
1154 "The (conceptual) table of partitions for long-term
1155 storage devices contained by the host. In particular,
1156 partitions accessed remotely over a network are not
1160 hrPartitionEntry OBJECT-TYPE
1161 SYNTAX HrPartitionEntry
1162 MAX-ACCESS not-accessible
1165 "A (conceptual) entry for one partition. The
1166 hrDeviceIndex in the index represents the entry in the
1167 hrDeviceTable that corresponds to the
1170 As an example of how objects in this table are named,
1171 an instance of the hrPartitionSize object might be
1172 named hrPartitionSize.3.1"
1173 INDEX { hrDeviceIndex, hrPartitionIndex }
1174 ::= { hrPartitionTable 1 }
1178 Waldbusser & Grillo Standards Track [Page 21]
1180 RFC 2790 Host Resources MIB March 2000
1183 HrPartitionEntry ::= SEQUENCE {
1184 hrPartitionIndex Integer32,
1185 hrPartitionLabel InternationalDisplayString,
1186 hrPartitionID OCTET STRING,
1187 hrPartitionSize KBytes,
1188 hrPartitionFSIndex Integer32
1191 hrPartitionIndex OBJECT-TYPE
1192 SYNTAX Integer32 (1..2147483647)
1193 MAX-ACCESS read-only
1196 "A unique value for each partition on this long-term
1197 storage device. The value for each long-term storage
1198 device must remain constant at least from one re-
1199 initialization of the agent to the next re-
1201 ::= { hrPartitionEntry 1 }
1203 hrPartitionLabel OBJECT-TYPE
1204 SYNTAX InternationalDisplayString (SIZE (0..128))
1205 MAX-ACCESS read-only
1208 "A textual description of this partition."
1209 ::= { hrPartitionEntry 2 }
1211 hrPartitionID OBJECT-TYPE
1213 MAX-ACCESS read-only
1216 "A descriptor which uniquely represents this partition
1217 to the responsible operating system. On some systems,
1218 this might take on a binary representation."
1219 ::= { hrPartitionEntry 3 }
1221 hrPartitionSize OBJECT-TYPE
1224 MAX-ACCESS read-only
1227 "The size of this partition."
1228 ::= { hrPartitionEntry 4 }
1230 hrPartitionFSIndex OBJECT-TYPE
1234 Waldbusser & Grillo Standards Track [Page 22]
1236 RFC 2790 Host Resources MIB March 2000
1239 SYNTAX Integer32 (0..2147483647)
1240 MAX-ACCESS read-only
1243 "The index of the file system mounted on this
1244 partition. If no file system is mounted on this
1245 partition, then this value shall be zero. Note that
1246 multiple partitions may point to one file system,
1247 denoting that that file system resides on those
1248 partitions. Multiple file systems may not reside on
1250 ::= { hrPartitionEntry 5 }
1252 -- The File System Table
1254 -- Registration point for popular File System types,
1255 -- for use with hrFSType. These are defined in the
1256 -- HOST-RESOURCES-TYPES module.
1257 hrFSTypes OBJECT IDENTIFIER ::= { hrDevice 9 }
1259 hrFSTable OBJECT-TYPE
1260 SYNTAX SEQUENCE OF HrFSEntry
1261 MAX-ACCESS not-accessible
1264 "The (conceptual) table of file systems local to this
1265 host or remotely mounted from a file server. File
1266 systems that are in only one user's environment on a
1267 multi-user system will not be included in this table."
1270 hrFSEntry OBJECT-TYPE
1272 MAX-ACCESS not-accessible
1275 "A (conceptual) entry for one file system local to
1276 this host or remotely mounted from a file server.
1277 File systems that are in only one user's environment
1278 on a multi-user system will not be included in this
1281 As an example of how objects in this table are named,
1282 an instance of the hrFSMountPoint object might be
1283 named hrFSMountPoint.3"
1290 Waldbusser & Grillo Standards Track [Page 23]
1292 RFC 2790 Host Resources MIB March 2000
1295 HrFSEntry ::= SEQUENCE {
1296 hrFSIndex Integer32,
1297 hrFSMountPoint InternationalDisplayString,
1298 hrFSRemoteMountPoint InternationalDisplayString,
1299 hrFSType AutonomousType,
1301 hrFSBootable TruthValue,
1302 hrFSStorageIndex Integer32,
1303 hrFSLastFullBackupDate DateAndTime,
1304 hrFSLastPartialBackupDate DateAndTime
1307 hrFSIndex OBJECT-TYPE
1308 SYNTAX Integer32 (1..2147483647)
1309 MAX-ACCESS read-only
1312 "A unique value for each file system local to this
1313 host. The value for each file system must remain
1314 constant at least from one re-initialization of the
1315 agent to the next re-initialization."
1318 hrFSMountPoint OBJECT-TYPE
1319 SYNTAX InternationalDisplayString (SIZE(0..128))
1320 MAX-ACCESS read-only
1323 "The path name of the root of this file system."
1326 hrFSRemoteMountPoint OBJECT-TYPE
1327 SYNTAX InternationalDisplayString (SIZE(0..128))
1328 MAX-ACCESS read-only
1331 "A description of the name and/or address of the
1332 server that this file system is mounted from. This
1333 may also include parameters such as the mount point on
1334 the remote file system. If this is not a remote file
1335 system, this string should have a length of zero."
1338 hrFSType OBJECT-TYPE
1339 SYNTAX AutonomousType
1340 MAX-ACCESS read-only
1346 Waldbusser & Grillo Standards Track [Page 24]
1348 RFC 2790 Host Resources MIB March 2000
1351 "The value of this object identifies the type of this
1355 hrFSAccess OBJECT-TYPE
1360 MAX-ACCESS read-only
1363 "An indication if this file system is logically
1364 configured by the operating system to be readable and
1365 writable or only readable. This does not represent
1366 any local access-control policy, except one that is
1367 applied to the file system as a whole."
1370 hrFSBootable OBJECT-TYPE
1372 MAX-ACCESS read-only
1375 "A flag indicating whether this file system is
1379 hrFSStorageIndex OBJECT-TYPE
1380 SYNTAX Integer32 (0..2147483647)
1381 MAX-ACCESS read-only
1384 "The index of the hrStorageEntry that represents
1385 information about this file system. If there is no
1386 such information available, then this value shall be
1387 zero. The relevant storage entry will be useful in
1388 tracking the percent usage of this file system and
1389 diagnosing errors that may occur when it runs out of
1393 hrFSLastFullBackupDate OBJECT-TYPE
1395 MAX-ACCESS read-write
1398 "The last date at which this complete file system was
1402 Waldbusser & Grillo Standards Track [Page 25]
1404 RFC 2790 Host Resources MIB March 2000
1407 copied to another storage device for backup. This
1408 information is useful for ensuring that backups are
1409 being performed regularly.
1411 If this information is not known, then this variable
1412 shall have the value corresponding to January 1, year
1413 0000, 00:00:00.0, which is encoded as
1414 (hex)'00 00 01 01 00 00 00 00'."
1417 hrFSLastPartialBackupDate OBJECT-TYPE
1419 MAX-ACCESS read-write
1422 "The last date at which a portion of this file system
1423 was copied to another storage device for backup. This
1424 information is useful for ensuring that backups are
1425 being performed regularly.
1427 If this information is not known, then this variable
1428 shall have the value corresponding to January 1, year
1429 0000, 00:00:00.0, which is encoded as
1430 (hex)'00 00 01 01 00 00 00 00'."
1433 -- The Host Resources Running Software Group
1435 -- The hrSWRunTable contains an entry for each distinct piece of
1436 -- software that is running or loaded into physical or virtual
1437 -- memory in preparation for running. This includes the host's
1438 -- operating system, device drivers, and applications.
1440 hrSWOSIndex OBJECT-TYPE
1441 SYNTAX Integer32 (1..2147483647)
1442 MAX-ACCESS read-only
1445 "The value of the hrSWRunIndex for the hrSWRunEntry
1446 that represents the primary operating system running
1447 on this host. This object is useful for quickly and
1448 uniquely identifying that primary operating system."
1451 hrSWRunTable OBJECT-TYPE
1452 SYNTAX SEQUENCE OF HrSWRunEntry
1453 MAX-ACCESS not-accessible
1458 Waldbusser & Grillo Standards Track [Page 26]
1460 RFC 2790 Host Resources MIB March 2000
1464 "The (conceptual) table of software running on the
1468 hrSWRunEntry OBJECT-TYPE
1470 MAX-ACCESS not-accessible
1473 "A (conceptual) entry for one piece of software
1474 running on the host Note that because the installed
1475 software table only contains information for software
1476 stored locally on this host, not every piece of
1477 running software will be found in the installed
1478 software table. This is true of software that was
1479 loaded and run from a non-local source, such as a
1480 network-mounted file system.
1482 As an example of how objects in this table are named,
1483 an instance of the hrSWRunName object might be named
1485 INDEX { hrSWRunIndex }
1486 ::= { hrSWRunTable 1 }
1488 HrSWRunEntry ::= SEQUENCE {
1489 hrSWRunIndex Integer32,
1490 hrSWRunName InternationalDisplayString,
1491 hrSWRunID ProductID,
1492 hrSWRunPath InternationalDisplayString,
1493 hrSWRunParameters InternationalDisplayString,
1494 hrSWRunType INTEGER,
1495 hrSWRunStatus INTEGER
1498 hrSWRunIndex OBJECT-TYPE
1499 SYNTAX Integer32 (1..2147483647)
1500 MAX-ACCESS read-only
1503 "A unique value for each piece of software running on
1504 the host. Wherever possible, this should be the
1505 system's native, unique identification number."
1506 ::= { hrSWRunEntry 1 }
1508 hrSWRunName OBJECT-TYPE
1509 SYNTAX InternationalDisplayString (SIZE (0..64))
1510 MAX-ACCESS read-only
1514 Waldbusser & Grillo Standards Track [Page 27]
1516 RFC 2790 Host Resources MIB March 2000
1521 "A textual description of this running piece of
1522 software, including the manufacturer, revision, and
1523 the name by which it is commonly known. If this
1524 software was installed locally, this should be the
1525 same string as used in the corresponding
1527 ::= { hrSWRunEntry 2 }
1529 hrSWRunID OBJECT-TYPE
1531 MAX-ACCESS read-only
1534 "The product ID of this running piece of software."
1535 ::= { hrSWRunEntry 3 }
1537 hrSWRunPath OBJECT-TYPE
1538 SYNTAX InternationalDisplayString (SIZE(0..128))
1539 MAX-ACCESS read-only
1542 "A description of the location on long-term storage
1543 (e.g. a disk drive) from which this software was
1545 ::= { hrSWRunEntry 4 }
1547 hrSWRunParameters OBJECT-TYPE
1548 SYNTAX InternationalDisplayString (SIZE(0..128))
1549 MAX-ACCESS read-only
1552 "A description of the parameters supplied to this
1553 software when it was initially loaded."
1554 ::= { hrSWRunEntry 5 }
1556 hrSWRunType OBJECT-TYPE
1563 MAX-ACCESS read-only
1566 "The type of this software."
1570 Waldbusser & Grillo Standards Track [Page 28]
1572 RFC 2790 Host Resources MIB March 2000
1575 ::= { hrSWRunEntry 6 }
1577 hrSWRunStatus OBJECT-TYPE
1580 runnable(2), -- waiting for resource
1581 -- (i.e., CPU, memory, IO)
1582 notRunnable(3), -- loaded but waiting for event
1583 invalid(4) -- not loaded
1585 MAX-ACCESS read-write
1588 "The status of this running piece of software.
1589 Setting this value to invalid(4) shall cause this
1590 software to stop running and to be unloaded. Sets to
1591 other values are not valid."
1592 ::= { hrSWRunEntry 7 }
1594 -- The Host Resources Running Software Performance Group
1596 -- The hrSWRunPerfTable contains an entry corresponding to
1597 -- each entry in the hrSWRunTable.
1599 hrSWRunPerfTable OBJECT-TYPE
1600 SYNTAX SEQUENCE OF HrSWRunPerfEntry
1601 MAX-ACCESS not-accessible
1604 "The (conceptual) table of running software
1605 performance metrics."
1606 ::= { hrSWRunPerf 1 }
1608 hrSWRunPerfEntry OBJECT-TYPE
1609 SYNTAX HrSWRunPerfEntry
1610 MAX-ACCESS not-accessible
1613 "A (conceptual) entry containing software performance
1614 metrics. As an example, an instance of the
1615 hrSWRunPerfCPU object might be named
1616 hrSWRunPerfCPU.1287"
1617 AUGMENTS { hrSWRunEntry } -- This table augments information in
1618 -- the hrSWRunTable.
1619 ::= { hrSWRunPerfTable 1 }
1621 HrSWRunPerfEntry ::= SEQUENCE {
1622 hrSWRunPerfCPU Integer32,
1626 Waldbusser & Grillo Standards Track [Page 29]
1628 RFC 2790 Host Resources MIB March 2000
1631 hrSWRunPerfMem KBytes
1634 hrSWRunPerfCPU OBJECT-TYPE
1635 SYNTAX Integer32 (0..2147483647)
1636 MAX-ACCESS read-only
1639 "The number of centi-seconds of the total system's CPU
1640 resources consumed by this process. Note that on a
1641 multi-processor system, this value may increment by
1642 more than one centi-second in one centi-second of real
1644 ::= { hrSWRunPerfEntry 1 }
1646 hrSWRunPerfMem OBJECT-TYPE
1649 MAX-ACCESS read-only
1652 "The total amount of real system memory allocated to
1654 ::= { hrSWRunPerfEntry 2 }
1656 -- The Host Resources Installed Software Group
1658 -- The hrSWInstalledTable contains an entry for each piece
1659 -- of software installed in long-term storage (e.g. a disk
1660 -- drive) locally on this host. Note that this does not
1661 -- include software loadable remotely from a network
1664 -- Different implementations may track software in varying
1665 -- ways. For example, while some implementations may track
1666 -- executable files as distinct pieces of software, other
1667 -- implementations may use other strategies such as keeping
1668 -- track of software "packages" (e.g., related groups of files)
1669 -- or keeping track of system or application "patches".
1671 -- This table is useful for identifying and inventorying
1672 -- software on a host and for diagnosing incompatibility
1673 -- and version mismatch problems between various pieces
1674 -- of hardware and software.
1676 hrSWInstalledLastChange OBJECT-TYPE
1678 MAX-ACCESS read-only
1682 Waldbusser & Grillo Standards Track [Page 30]
1684 RFC 2790 Host Resources MIB March 2000
1689 "The value of sysUpTime when an entry in the
1690 hrSWInstalledTable was last added, renamed, or
1691 deleted. Because this table is likely to contain many
1692 entries, polling of this object allows a management
1693 station to determine when re-downloading of the table
1695 ::= { hrSWInstalled 1 }
1697 hrSWInstalledLastUpdateTime OBJECT-TYPE
1699 MAX-ACCESS read-only
1702 "The value of sysUpTime when the hrSWInstalledTable
1703 was last completely updated. Because caching of this
1704 data will be a popular implementation strategy,
1705 retrieval of this object allows a management station
1706 to obtain a guarantee that no data in this table is
1707 older than the indicated time."
1708 ::= { hrSWInstalled 2 }
1710 hrSWInstalledTable OBJECT-TYPE
1711 SYNTAX SEQUENCE OF HrSWInstalledEntry
1712 MAX-ACCESS not-accessible
1715 "The (conceptual) table of software installed on this
1717 ::= { hrSWInstalled 3 }
1719 hrSWInstalledEntry OBJECT-TYPE
1720 SYNTAX HrSWInstalledEntry
1721 MAX-ACCESS not-accessible
1724 "A (conceptual) entry for a piece of software
1725 installed on this host.
1727 As an example of how objects in this table are named,
1728 an instance of the hrSWInstalledName object might be
1729 named hrSWInstalledName.96"
1730 INDEX { hrSWInstalledIndex }
1731 ::= { hrSWInstalledTable 1 }
1733 HrSWInstalledEntry ::= SEQUENCE {
1734 hrSWInstalledIndex Integer32,
1738 Waldbusser & Grillo Standards Track [Page 31]
1740 RFC 2790 Host Resources MIB March 2000
1743 hrSWInstalledName InternationalDisplayString,
1744 hrSWInstalledID ProductID,
1745 hrSWInstalledType INTEGER,
1746 hrSWInstalledDate DateAndTime
1749 hrSWInstalledIndex OBJECT-TYPE
1750 SYNTAX Integer32 (1..2147483647)
1751 MAX-ACCESS read-only
1754 "A unique value for each piece of software installed
1755 on the host. This value shall be in the range from 1
1756 to the number of pieces of software installed on the
1758 ::= { hrSWInstalledEntry 1 }
1760 hrSWInstalledName OBJECT-TYPE
1761 SYNTAX InternationalDisplayString (SIZE (0..64))
1762 MAX-ACCESS read-only
1765 "A textual description of this installed piece of
1766 software, including the manufacturer, revision, the
1767 name by which it is commonly known, and optionally,
1769 ::= { hrSWInstalledEntry 2 }
1771 hrSWInstalledID OBJECT-TYPE
1773 MAX-ACCESS read-only
1776 "The product ID of this installed piece of software."
1777 ::= { hrSWInstalledEntry 3 }
1779 hrSWInstalledType OBJECT-TYPE
1786 MAX-ACCESS read-only
1789 "The type of this software."
1790 ::= { hrSWInstalledEntry 4 }
1794 Waldbusser & Grillo Standards Track [Page 32]
1796 RFC 2790 Host Resources MIB March 2000
1799 hrSWInstalledDate OBJECT-TYPE
1801 MAX-ACCESS read-only
1804 "The last-modification date of this application as it
1805 would appear in a directory listing.
1807 If this information is not known, then this variable
1808 shall have the value corresponding to January 1, year
1809 0000, 00:00:00.0, which is encoded as
1810 (hex)'00 00 01 01 00 00 00 00'."
1811 ::= { hrSWInstalledEntry 5 }
1813 -- Conformance information
1815 hrMIBCompliances OBJECT IDENTIFIER ::= { hrMIBAdminInfo 2 }
1816 hrMIBGroups OBJECT IDENTIFIER ::= { hrMIBAdminInfo 3 }
1818 -- Compliance Statements
1819 hrMIBCompliance MODULE-COMPLIANCE
1822 "The requirements for conformance to the Host Resources MIB."
1823 MODULE -- this module
1824 MANDATORY-GROUPS { hrSystemGroup, hrStorageGroup,
1828 MIN-ACCESS read-only
1830 "Write access is not required."
1832 OBJECT hrSystemInitialLoadDevice
1833 MIN-ACCESS read-only
1835 "Write access is not required."
1837 OBJECT hrSystemInitialLoadParameters
1838 MIN-ACCESS read-only
1840 "Write access is not required."
1842 OBJECT hrStorageSize
1843 MIN-ACCESS read-only
1845 "Write access is not required."
1850 Waldbusser & Grillo Standards Track [Page 33]
1852 RFC 2790 Host Resources MIB March 2000
1855 OBJECT hrFSLastFullBackupDate
1856 MIN-ACCESS read-only
1858 "Write access is not required."
1860 OBJECT hrFSLastPartialBackupDate
1861 MIN-ACCESS read-only
1863 "Write access is not required."
1867 "The Running Software Group. Implementation
1868 of this group is mandatory only when the
1869 hrSWRunPerfGroup is implemented."
1871 OBJECT hrSWRunStatus
1872 MIN-ACCESS read-only
1874 "Write access is not required."
1876 GROUP hrSWRunPerfGroup
1878 "The Running Software Performance Group.
1879 Implementation of this group is at the discretion
1880 of the implementor."
1882 GROUP hrSWInstalledGroup
1884 "The Installed Software Group.
1885 Implementation of this group is at the discretion
1886 of the implementor."
1888 ::= { hrMIBCompliances 1 }
1890 hrSystemGroup OBJECT-GROUP
1892 hrSystemUptime, hrSystemDate,
1893 hrSystemInitialLoadDevice,
1894 hrSystemInitialLoadParameters,
1895 hrSystemNumUsers, hrSystemProcesses,
1896 hrSystemMaxProcesses
1900 "The Host Resources System Group."
1901 ::= { hrMIBGroups 1 }
1906 Waldbusser & Grillo Standards Track [Page 34]
1908 RFC 2790 Host Resources MIB March 2000
1911 hrStorageGroup OBJECT-GROUP
1913 hrMemorySize, hrStorageIndex, hrStorageType,
1914 hrStorageDescr, hrStorageAllocationUnits,
1915 hrStorageSize, hrStorageUsed,
1916 hrStorageAllocationFailures
1920 "The Host Resources Storage Group."
1921 ::= { hrMIBGroups 2 }
1923 hrDeviceGroup OBJECT-GROUP
1925 hrDeviceIndex, hrDeviceType, hrDeviceDescr,
1926 hrDeviceID, hrDeviceStatus, hrDeviceErrors,
1927 hrProcessorFrwID, hrProcessorLoad,
1928 hrNetworkIfIndex, hrPrinterStatus,
1929 hrPrinterDetectedErrorState,
1930 hrDiskStorageAccess, hrDiskStorageMedia,
1931 hrDiskStorageRemoveble, hrDiskStorageCapacity,
1932 hrPartitionIndex, hrPartitionLabel,
1933 hrPartitionID, hrPartitionSize,
1934 hrPartitionFSIndex, hrFSIndex, hrFSMountPoint,
1935 hrFSRemoteMountPoint, hrFSType, hrFSAccess,
1936 hrFSBootable, hrFSStorageIndex,
1937 hrFSLastFullBackupDate,
1938 hrFSLastPartialBackupDate
1942 "The Host Resources Device Group."
1943 ::= { hrMIBGroups 3 }
1945 hrSWRunGroup OBJECT-GROUP
1947 hrSWOSIndex, hrSWRunIndex, hrSWRunName,
1948 hrSWRunID, hrSWRunPath, hrSWRunParameters,
1949 hrSWRunType, hrSWRunStatus
1953 "The Host Resources Running Software Group."
1954 ::= { hrMIBGroups 4 }
1956 hrSWRunPerfGroup OBJECT-GROUP
1957 OBJECTS { hrSWRunPerfCPU, hrSWRunPerfMem }
1962 Waldbusser & Grillo Standards Track [Page 35]
1964 RFC 2790 Host Resources MIB March 2000
1968 "The Host Resources Running Software
1970 ::= { hrMIBGroups 5 }
1972 hrSWInstalledGroup OBJECT-GROUP
1974 hrSWInstalledLastChange,
1975 hrSWInstalledLastUpdateTime,
1976 hrSWInstalledIndex, hrSWInstalledName,
1977 hrSWInstalledID, hrSWInstalledType,
1982 "The Host Resources Installed Software Group."
1983 ::= { hrMIBGroups 6 }
1989 HOST-RESOURCES-TYPES DEFINITIONS ::= BEGIN
1992 MODULE-IDENTITY, OBJECT-IDENTITY FROM SNMPv2-SMI
1993 hrMIBAdminInfo, hrStorage, hrDevice FROM HOST-RESOURCES-MIB;
1995 hostResourcesTypesModule MODULE-IDENTITY
1996 LAST-UPDATED "200003060000Z" -- 6 March, 2000
1997 ORGANIZATION "IETF Host Resources MIB Working Group"
2000 Postal: Lucent Technologies, Inc.
2006 Email: waldbusser@ins.com
2008 In addition, the Host Resources MIB mailing list is dedicated
2009 to discussion of this MIB. To join the mailing list, send a
2010 request message to hostmib-request@andrew.cmu.edu. The mailing
2011 list address is hostmib@andrew.cmu.edu."
2013 "This MIB module registers type definitions for
2014 storage types, device types, and file system types.
2018 Waldbusser & Grillo Standards Track [Page 36]
2020 RFC 2790 Host Resources MIB March 2000
2023 After the initial revision, this module will be
2024 maintained by IANA."
2025 REVISION "200003060000Z" -- 6 March 2000
2027 "The original version of this module, published as RFC
2029 ::= { hrMIBAdminInfo 4 }
2031 -- Registrations for some storage types, for use with hrStorageType
2032 hrStorageTypes OBJECT IDENTIFIER ::= { hrStorage 1 }
2034 hrStorageOther OBJECT-IDENTITY
2037 "The storage type identifier used when no other defined
2038 type is appropriate."
2039 ::= { hrStorageTypes 1 }
2041 hrStorageRam OBJECT-IDENTITY
2044 "The storage type identifier used for RAM."
2045 ::= { hrStorageTypes 2 }
2047 hrStorageVirtualMemory OBJECT-IDENTITY
2050 "The storage type identifier used for virtual memory,
2051 temporary storage of swapped or paged memory."
2052 ::= { hrStorageTypes 3 }
2054 hrStorageFixedDisk OBJECT-IDENTITY
2057 "The storage type identifier used for non-removable
2058 rigid rotating magnetic storage devices."
2059 ::= { hrStorageTypes 4 }
2061 hrStorageRemovableDisk OBJECT-IDENTITY
2064 "The storage type identifier used for removable rigid
2065 rotating magnetic storage devices."
2066 ::= { hrStorageTypes 5 }
2068 hrStorageFloppyDisk OBJECT-IDENTITY
2074 Waldbusser & Grillo Standards Track [Page 37]
2076 RFC 2790 Host Resources MIB March 2000
2079 "The storage type identifier used for non-rigid rotating
2080 magnetic storage devices."
2081 ::= { hrStorageTypes 6 }
2083 hrStorageCompactDisc OBJECT-IDENTITY
2086 "The storage type identifier used for read-only rotating
2087 optical storage devices."
2088 ::= { hrStorageTypes 7 }
2090 hrStorageRamDisk OBJECT-IDENTITY
2093 "The storage type identifier used for a file system that
2095 ::= { hrStorageTypes 8 }
2097 hrStorageFlashMemory OBJECT-IDENTITY
2100 "The storage type identifier used for flash memory."
2101 ::= { hrStorageTypes 9 }
2103 hrStorageNetworkDisk OBJECT-IDENTITY
2106 "The storage type identifier used for a
2107 networked file system."
2108 ::= { hrStorageTypes 10 }
2110 -- Registrations for some device types, for use with hrDeviceType
2111 hrDeviceTypes OBJECT IDENTIFIER ::= { hrDevice 1 }
2113 hrDeviceOther OBJECT-IDENTITY
2116 "The device type identifier used when no other defined
2117 type is appropriate."
2118 ::= { hrDeviceTypes 1 }
2120 hrDeviceUnknown OBJECT-IDENTITY
2123 "The device type identifier used when the device type is
2125 ::= { hrDeviceTypes 2 }
2130 Waldbusser & Grillo Standards Track [Page 38]
2132 RFC 2790 Host Resources MIB March 2000
2135 hrDeviceProcessor OBJECT-IDENTITY
2138 "The device type identifier used for a CPU."
2139 ::= { hrDeviceTypes 3 }
2141 hrDeviceNetwork OBJECT-IDENTITY
2144 "The device type identifier used for a network interface."
2145 ::= { hrDeviceTypes 4 }
2147 hrDevicePrinter OBJECT-IDENTITY
2150 "The device type identifier used for a printer."
2151 ::= { hrDeviceTypes 5 }
2153 hrDeviceDiskStorage OBJECT-IDENTITY
2156 "The device type identifier used for a disk drive."
2157 ::= { hrDeviceTypes 6 }
2159 hrDeviceVideo OBJECT-IDENTITY
2162 "The device type identifier used for a video device."
2163 ::= { hrDeviceTypes 10 }
2165 hrDeviceAudio OBJECT-IDENTITY
2168 "The device type identifier used for an audio device."
2169 ::= { hrDeviceTypes 11 }
2171 hrDeviceCoprocessor OBJECT-IDENTITY
2174 "The device type identifier used for a co-processor."
2175 ::= { hrDeviceTypes 12 }
2177 hrDeviceKeyboard OBJECT-IDENTITY
2180 "The device type identifier used for a keyboard device."
2181 ::= { hrDeviceTypes 13 }
2186 Waldbusser & Grillo Standards Track [Page 39]
2188 RFC 2790 Host Resources MIB March 2000
2191 hrDeviceModem OBJECT-IDENTITY
2194 "The device type identifier used for a modem."
2195 ::= { hrDeviceTypes 14 }
2197 hrDeviceParallelPort OBJECT-IDENTITY
2200 "The device type identifier used for a parallel port."
2201 ::= { hrDeviceTypes 15 }
2203 hrDevicePointing OBJECT-IDENTITY
2206 "The device type identifier used for a pointing device
2208 ::= { hrDeviceTypes 16 }
2210 hrDeviceSerialPort OBJECT-IDENTITY
2213 "The device type identifier used for a serial port."
2214 ::= { hrDeviceTypes 17 }
2216 hrDeviceTape OBJECT-IDENTITY
2219 "The device type identifier used for a tape storage device."
2220 ::= { hrDeviceTypes 18 }
2222 hrDeviceClock OBJECT-IDENTITY
2225 "The device type identifier used for a clock device."
2226 ::= { hrDeviceTypes 19 }
2228 hrDeviceVolatileMemory OBJECT-IDENTITY
2231 "The device type identifier used for a volatile memory
2233 ::= { hrDeviceTypes 20 }
2235 hrDeviceNonVolatileMemory OBJECT-IDENTITY
2238 "The device type identifier used for a non-volatile memory
2242 Waldbusser & Grillo Standards Track [Page 40]
2244 RFC 2790 Host Resources MIB March 2000
2248 ::= { hrDeviceTypes 21 }
2250 -- Registrations for some popular File System types,
2251 -- for use with hrFSType.
2252 hrFSTypes OBJECT IDENTIFIER ::= { hrDevice 9 }
2254 hrFSOther OBJECT-IDENTITY
2257 "The file system type identifier used when no other
2258 defined type is appropriate."
2261 hrFSUnknown OBJECT-IDENTITY
2264 "The file system type identifier used when the type of
2265 file system is unknown."
2268 hrFSBerkeleyFFS OBJECT-IDENTITY
2271 "The file system type identifier used for the
2272 Berkeley Fast File System."
2275 hrFSSys5FS OBJECT-IDENTITY
2278 "The file system type identifier used for the
2279 System V File System."
2282 hrFSFat OBJECT-IDENTITY
2285 "The file system type identifier used for
2286 DOS's FAT file system."
2289 hrFSHPFS OBJECT-IDENTITY
2292 "The file system type identifier used for OS/2's
2293 High Performance File System."
2298 Waldbusser & Grillo Standards Track [Page 41]
2300 RFC 2790 Host Resources MIB March 2000
2303 hrFSHFS OBJECT-IDENTITY
2306 "The file system type identifier used for the
2307 Macintosh Hierarchical File System."
2310 hrFSMFS OBJECT-IDENTITY
2313 "The file system type identifier used for the
2314 Macintosh File System."
2317 hrFSNTFS OBJECT-IDENTITY
2320 "The file system type identifier used for the
2321 Windows NT File System."
2324 hrFSVNode OBJECT-IDENTITY
2327 "The file system type identifier used for the
2329 ::= { hrFSTypes 10 }
2331 hrFSJournaled OBJECT-IDENTITY
2334 "The file system type identifier used for the
2335 Journaled File System."
2336 ::= { hrFSTypes 11 }
2338 hrFSiso9660 OBJECT-IDENTITY
2341 "The file system type identifier used for the
2342 ISO 9660 File System for CD's."
2343 ::= { hrFSTypes 12 }
2345 hrFSRockRidge OBJECT-IDENTITY
2348 "The file system type identifier used for the
2349 RockRidge File System for CD's."
2350 ::= { hrFSTypes 13 }
2354 Waldbusser & Grillo Standards Track [Page 42]
2356 RFC 2790 Host Resources MIB March 2000
2359 hrFSNFS OBJECT-IDENTITY
2362 "The file system type identifier used for the
2364 ::= { hrFSTypes 14 }
2366 hrFSNetware OBJECT-IDENTITY
2369 "The file system type identifier used for the
2370 Netware File System."
2371 ::= { hrFSTypes 15 }
2373 hrFSAFS OBJECT-IDENTITY
2376 "The file system type identifier used for the
2377 Andrew File System."
2378 ::= { hrFSTypes 16 }
2380 hrFSDFS OBJECT-IDENTITY
2383 "The file system type identifier used for the
2384 OSF DCE Distributed File System."
2385 ::= { hrFSTypes 17 }
2387 hrFSAppleshare OBJECT-IDENTITY
2390 "The file system type identifier used for the
2391 AppleShare File System."
2392 ::= { hrFSTypes 18 }
2394 hrFSRFS OBJECT-IDENTITY
2397 "The file system type identifier used for the
2399 ::= { hrFSTypes 19 }
2401 hrFSDGCFS OBJECT-IDENTITY
2404 "The file system type identifier used for the
2405 Data General DGCFS."
2406 ::= { hrFSTypes 20 }
2410 Waldbusser & Grillo Standards Track [Page 43]
2412 RFC 2790 Host Resources MIB March 2000
2415 hrFSBFS OBJECT-IDENTITY
2418 "The file system type identifier used for the
2419 SVR4 Boot File System."
2420 ::= { hrFSTypes 21 }
2422 hrFSFAT32 OBJECT-IDENTITY
2425 "The file system type identifier used for the
2426 Windows FAT32 File System."
2427 ::= { hrFSTypes 22 }
2429 hrFSLinuxExt2 OBJECT-IDENTITY
2432 "The file system type identifier used for the
2433 Linux EXT2 File System."
2434 ::= { hrFSTypes 23 }
2438 6. Internationalization Considerations
2440 This MIB has many objects that identify file-system pathnames on the
2441 managed host. Many file systems allow pathnames to be encoded in a
2442 variety of character sets (other than ASCII), but do not support the
2443 encoding of the actual character set used with the pathname. The
2444 implementation strategy is that user interfaces (i.e. character-based
2445 shells or graphical applications) will have configuration options
2446 that control with which character set they will interpret and display
2447 all pathnames. This is often a per-user configuration (e.g. an
2448 environment variable), so that users using different languages and
2449 character sets on a multi-user system may each work effectively with
2450 their preferred character set. A human usually controls this
2451 configuration. If an application is not configured or is configured
2452 incorrectly, it will often have trouble displaying pathnames in the
2453 intended character set.
2455 This situation made it important for this MIB to handle two issues:
2457 1) Pathname objects must be able to transfer a variety of character
2458 sets with potentially multi-byte encodings; and,
2466 Waldbusser & Grillo Standards Track [Page 44]
2468 RFC 2790 Host Resources MIB March 2000
2471 2) HostMIB agents will generally not be correctly configured for the
2472 appropriate character set to be used for all files on the system,
2473 particularly on a system with multiple users using different
2474 character sets. It was thus impossible to mandate that the agent
2475 tag pathnames with the character set in use.
2477 These issues were solved with the introduction of the
2478 InternationalDisplayString textual convention, which supports multi-
2479 byte encodings. Network management stations should use a local
2480 algorithm to determine which character set is in use and how it
2481 should be displayed. It is expected that network management station
2482 applications will rely on human configuration to choose which
2483 character set in which to interpret InternationalDisplayString
2484 objects, much like an application running locally on that host.
2486 7. Security Considerations
2488 There are a number of management objects defined in this MIB that
2489 have a MAX-ACCESS clause of read-write. Such objects may be
2490 considered sensitive or vulnerable in some network environments. The
2491 support for SET operations in a non-secure environment without proper
2492 protection can have a negative effect on system operations.
2494 There are a number of managed objects in this MIB that may contain
2495 sensitive information. The objects in the Running Software Group list
2496 information about running software on the system (including the
2497 operating system software and version). Some may wish not to
2498 disclose to others what software they are running. Further, an
2499 inventory of the running software and versions may be helpful to an
2500 attacker who hopes to exploit software bugs in certain applications.
2501 The same issues exist for the objects in the Installed Software
2504 It is thus important to control even GET access to these objects and
2505 possibly to even encrypt the values of these object when sending them
2506 over the network via SNMP. Not all versions of SNMP provide features
2507 for such a secure environment.
2509 SNMPv1 by itself is not a secure environment. Even if the network
2510 itself is secure (for example by using IPSec), even then, there is no
2511 control as to who on the secure network is allowed to access and
2512 GET/SET (read/change/create/delete) the objects in this MIB.
2514 It is recommended that the implementers consider the security
2515 features as provided by the SNMPv3 framework. Specifically, the use
2516 of the User-based Security Model RFC 2574 [RFC2574] and the View-
2517 based Access Control Model RFC 2575 [RFC2575] is recommended.
2522 Waldbusser & Grillo Standards Track [Page 45]
2524 RFC 2790 Host Resources MIB March 2000
2527 It is then a customer/user responsibility to ensure that the SNMP
2528 entity giving access to an instance of this MIB, is properly
2529 configured to give access to the objects only to those principals
2530 (users) that have legitimate rights to indeed GET or SET
2531 (change/create/delete) them.
2535 [RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An
2536 Architecture for Describing SNMP Management Frameworks",
2537 RFC 2571, April 1999.
2539 [RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification
2540 of Management Information for TCP/IP-based Internets",
2541 STD 16, RFC 1155, May 1990.
2543 [RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions",
2544 STD 16, RFC 1212, March 1991.
2546 [RFC1215] Rose, M., "A Convention for Defining Traps for use with
2547 the SNMP", RFC 1215, March 1991.
2549 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
2550 Rose, M. and S. Waldbusser, "Structure of Management
2551 Information Version 2 (SMIv2)", STD 58, RFC 2578, April
2554 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
2555 Rose, M. and S. Waldbusser, "Textual Conventions for
2556 SMIv2", STD 58, RFC 2579, April 1999.
2558 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
2559 Rose, M. and S. Waldbusser, "Conformance Statements for
2560 SMIv2", STD 58, RFC 2580, April 1999.
2562 [RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin,
2563 "Simple Network Management Protocol", STD 15, RFC 1157,
2566 [RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
2567 "Introduction to Community-based SNMPv2", RFC 1901,
2570 [RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
2571 "Transport Mappings for Version 2 of the Simple Network
2572 Management Protocol (SNMPv2)", RFC 1906, January 1996.
2578 Waldbusser & Grillo Standards Track [Page 46]
2580 RFC 2790 Host Resources MIB March 2000
2583 [RFC2572] Case, J., Harrington D., Presuhn R. and B. Wijnen,
2584 "Message Processing and Dispatching for the Simple
2585 Network Management Protocol (SNMP)", RFC 2572, April 1999
2587 [RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model
2588 (USM) for version 3 of the Simple Network Management
2589 Protocol (SNMPv3)", RFC 2574, April 1999.
2591 [RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
2592 "Protocol Operations for Version 2 of the Simple Network
2593 Management Protocol (SNMPv2)", RFC 1905, January 1996.
2595 [RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3
2596 Applications", RFC 2573, April 1999.
2598 [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
2599 Access Control Model (VACM) for the Simple Network
2600 Management Protocol (SNMP)", RFC 2575, April 1999.
2602 [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart,
2603 "Introduction to Version 3 of the Internet- standard
2604 Network Management Framework", RFC 2570, April 1999.
2606 [RFC1907] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
2607 "Management Information Base for Version 2 of the Simple
2608 Network Management Protocol (SNMPv2)", RFC 1907, January
2611 [RFC2233] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
2612 MIB", RFC 2233, November 1997.
2614 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
2615 Requirement Levels", BCP 14, RFC 2119, March 1997.
2634 Waldbusser & Grillo Standards Track [Page 47]
2636 RFC 2790 Host Resources MIB March 2000
2641 This document was produced by the Host Resources MIB working group.
2643 Bobby Krupczak's efforts were particularly helpful in the creation of
2644 the draft standard version of this document.
2646 In addition, the authors gratefully acknowledge the comments of the
2647 following individuals:
2649 Amatzia Ben-Artzi NetManage
2650 Ron Bergman Hitachi, Inc.
2651 Steve Bostock Novell
2652 Stephen Bush GE Information Systems
2653 Jeff Case SNMP Research
2654 Chuck Davin Bellcore
2655 Ray Edgarton Bell Atlantic
2656 Mike Erlinger Aerospace Corporation
2657 Tim Farley Magee Enterprises
2658 Mark Kepke Hewlett Packard
2659 Bobby Krupczak Empire Technologies, Inc.
2660 Cheryl Krupczak Empire Technologies, Inc.
2661 Harry Lewis IBM Corp.
2662 Keith McCloghrie Cisco Systems
2663 Greg Minshall Novell
2664 Steve Moulton SNMP Research
2665 Dave Perkins Synoptics
2666 Ed Reeder Objective Systems Integrators
2667 Mike Ritter Apple Computer
2668 Marshall Rose Dover Beach Consulting
2670 Rodney Thayer Sable Technology
2672 Dean Throop Data General
2674 Lloyd Young Lexmark International
2690 Waldbusser & Grillo Standards Track [Page 48]
2692 RFC 2790 Host Resources MIB March 2000
2695 10. Authors' Addresses
2699 1001 SW Fifth Ave, Fifth Floor
2704 email: pete@wesync.com
2705 Phone: +1 503 827 6717
2709 Lucent Technologies, Inc.
2713 Phone: +1 650 318 1251
2714 Fax: +1 650 318 1633
2715 EMail: waldbusser@ins.com
2717 11. Intellectual Property
2719 The IETF takes no position regarding the validity or scope of
2720 any intellectual property or other rights that might be
2721 claimed to pertain to the implementation or use of the
2722 technology described in this document or the extent to which
2723 any license under such rights might or might not be available;
2724 neither does it represent that it has made any effort to
2725 identify any such rights. Information on the IETF's
2726 procedures with respect to rights in standards-track and
2727 standards-related documentation can be found in BCP-11.
2728 Copies of claims of rights made available for publication and
2729 any assurances of licenses to be made available, or the result
2730 of an attempt made to obtain a general license or permission
2731 for the use of such proprietary rights by implementors or
2732 users of this specification can be obtained from the IETF
2735 The IETF invites any interested party to bring to its
2736 attention any copyrights, patents or patent applications, or
2737 other proprietary rights which may cover technology that may
2738 be required to practice this standard. Please address the
2739 information to the IETF Executive Director.
2746 Waldbusser & Grillo Standards Track [Page 49]
2748 RFC 2790 Host Resources MIB March 2000
2751 12. Full Copyright Statement
2753 Copyright (C) The Internet Society (2000). All Rights Reserved.
2755 This document and translations of it may be copied and furnished to
2756 others, and derivative works that comment on or otherwise explain it
2757 or assist in its implementation may be prepared, copied, published
2758 and distributed, in whole or in part, without restriction of any
2759 kind, provided that the above copyright notice and this paragraph are
2760 included on all such copies and derivative works. However, this
2761 document itself may not be modified in any way, such as by removing
2762 the copyright notice or references to the Internet Society or other
2763 Internet organizations, except as needed for the purpose of
2764 developing Internet standards in which case the procedures for
2765 copyrights defined in the Internet Standards process must be
2766 followed, or as required to translate it into languages other than
2769 The limited permissions granted above are perpetual and will not be
2770 revoked by the Internet Society or its successors or assigns.
2772 This document and the information contained herein is provided on an
2773 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
2774 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
2775 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
2776 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
2777 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
2781 Funding for the RFC Editor function is currently provided by the
2802 Waldbusser & Grillo Standards Track [Page 50]