idnits 2.17.1 draft-ops-hostmib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Expected the document's filename to be given on the first page, but didn't find any == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. -- The abstract seems to indicate that this document obsoletes RFC1514, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 126 has weird spacing: '...mputers are...' == The document doesn't use any RFC 2119 keywords, yet has text resembling RFC 2119 boilerplate text. == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date () is 739384 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 1907 (Obsoleted by RFC 3418) ** Obsolete normative reference: RFC 2233 (Obsoleted by RFC 2863) Summary: 17 errors (**), 0 flaws (~~), 5 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET DRAFT Host Resources MIB July 99 4 Host Resources MIB 6 Saturday July 31 22:00:00 PDT 1999 8 Steven Waldbusser 9 International Network Services (INS) 10 waldbusser@ins.com 12 Pete Grillo 13 PlusFactor Software Inc. 14 pete@plusfactor.com 16 Status of this Memo 18 This document is an Internet-Draft and is in full conformance 19 with all provisions of Section 10 of RFC2026. 21 Internet-Drafts are working documents of the Internet 22 Engineering Task Force (IETF), its areas, and its working 23 groups. Note that other groups may also distribute working 24 documents as Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six 27 months and may be updated, replaced, or obsoleted by other 28 documents at any time. It is inappropriate to use Internet- 29 Drafts as reference material or to cite them other than as 30 "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt 35 The list of Internet-Draft Shadow Directories can be accessed 36 at http://www.ietf.org/shadow.html. 38 Copyright Notice 40 Copyright (C) The Internet Society (1999). All Rights Reserved. 42 Abstract 44 This memo defines a portion of the Management Information Base 45 (MIB) for use with network management protocols in the 46 Internet community. This memo obsoletes RFC 1514, the "Host 47 Resources MIB". This memo extends that specification by 48 clarifying changes based on implementation and deployment 49 experience and documenting the Host Resources MIB in SMIv2 50 format while remaining semantically identical to the existing 51 SMIv1-based MIB. 53 This memo defines a MIB for use with managing host systems. 54 The term "host" is construed to mean any computer that 55 communicates with other similar computers attached to the 56 internet and that is directly used by one or more human 57 beings. Although this MIB does not necessarily apply to 58 devices whose primary function is communications services 59 (e.g., terminal servers, routers, bridges, monitoring 60 equipment), such relevance is not explicitly precluded. This 61 MIB instruments attributes common to all internet hosts 62 including, for example, both personal computers and systems 63 that run variants of Unix. 65 1. The SNMP Management Framework 67 The SNMP Management Framework presently consists of five 68 major components: 70 o An overall architecture, described in RFC 2571 71 [RFC2571]. 73 o Mechanisms for describing and naming objects and 74 events for the purpose of management. The first 75 version of this Structure of Management Information 76 (SMI) is called SMIv1 and described in STD 16, RFC 77 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 78 1215 [RFC1215]. The second version, called SMIv2, is 79 described in STD 58, RFC 2578 [RFC2578], RFC 2579 80 [RFC2579] and RFC 2580 [RFC2580]. 82 o Message protocols for transferring management 83 information. The first version of the SNMP message 84 protocol is called SNMPv1 and described in STD 15, RFC 85 1157 [RFC1157]. A second version of the SNMP message 86 protocol, which is not an Internet standards track 87 protocol, is called SNMPv2c and described in RFC 1901 88 [RFC1901] and RFC 1906 [RFC1906]. The third version of 89 the message protocol is called SNMPv3 and described in 90 RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 91 [RFC2574]. 93 o Protocol operations for accessing management 94 information. The first set of protocol operations and 95 associated PDU formats is described in STD 15, RFC 96 1157 [RFC1157]. A second set of protocol operations 97 and associated PDU formats is described in RFC 1905 98 [RFC1905]. 100 o A set of fundamental applications described in RFC 101 2573 [RFC2573] and the view-based access control 102 mechanism described in RFC 2575 [RFC2575]. 104 A more detailed introduction to the current SNMP Management 105 Framework can be found in RFC 2570 [RFC2570]. 107 Managed objects are accessed via a virtual information 108 store, termed the Management Information Base or MIB. 109 Objects in the MIB are defined using the mechanisms defined 110 in the SMI. 112 This memo specifies a MIB module that is compliant to the 113 SMIv2. A MIB conforming to the SMIv1 can be produced 114 through the appropriate translations. The resulting 115 translated MIB must be semantically equivalent, except 116 where objects or events are omitted because no translation 117 is possible (use of Counter64). Some machine readable 118 information in SMIv2 will be converted into textual 119 descriptions in SMIv1 during the translation process. 120 However, this loss of machine readable information is not 121 considered to change the semantics of the MIB. 123 2. Host Resources MIB 125 The Host Resources MIB defines a uniform set of objects useful 126 for the management of host computers. Host computers are 127 independent of the operating system, network services, or any 128 software application. 130 The Host Resources MIB defines objects which are common across 131 many computer system architectures. 133 In addition, there are objects in the SNMPv2-MIB [RFC1907] and 134 IF-MIB [RFC2233] which also provide host management 135 functionality. Implementation of the System and Interfaces 136 groups is mandatory for implementors of the Host Resources 137 MIB. 139 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 140 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED","MAY", and 141 "OPTIONAL" in this document are to be interpreted as described 142 in [RFC2119]. 144 3. IANA Considerations 146 This MIB contains type definitions for storage types, device 147 types, and file system types for use as values for the 148 hrStorageType, hrDeviceType, and hrFSType objects, 149 respectively. As new computing technologies are developed, new 150 types need to be registered for these technologies. The IANA 151 (Internet Assigned Numbers Authority) is designated as the 152 registration authority for new registrations beyond those 153 published in this document. 155 Given the large number of such technologies and potential 156 confusion in naming of these technologies (such as a 157 technology known by two names or a name and an acronym), there 158 is a real danger that more than one registration might be 159 created for what is essentially the same technology. In order 160 to ensure that future type registrations are performed 161 correctly, applications for new types will be reviewed by a 162 Designated Expert appointed by the IESG. 164 4. Definitions 166 HOST-RESOURCES-MIB DEFINITIONS ::= BEGIN 168 IMPORTS 169 MODULE-IDENTITY, OBJECT-TYPE, mib-2, 170 Integer32, Counter32, Gauge32, TimeTicks FROM SNMPv2-SMI 172 TEXTUAL-CONVENTION, DisplayString, 173 TruthValue, DateAndTime, AutonomousType FROM SNMPv2-TC 175 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 177 InterfaceIndexOrZero FROM IF-MIB; 179 hostResourcesMibModule MODULE-IDENTITY 180 LAST-UPDATED "9907312200Z" -- 31 July, 1999 181 ORGANIZATION "IETF Host Resources MIB Working Group" 182 CONTACT-INFO 183 "Steve Waldbusser 184 Postal: International Network Services (INS) 185 1213 Innsbruck Dr. 186 Sunnyvale, CA 94089 187 USA 188 Phone: 650-318-1251 189 Fax: 650-318-1633 190 Email: waldbusser@ins.com 192 In addition, the Host Resources MIB mailing list is dedicated to 193 discussion of this MIB. To join the mailing list, send a request 194 message to hostmib-request@andrew.cmu.edu. The mailing list 195 address is hostmib@andrew.cmu.edu." 196 DESCRIPTION 197 "This MIB is for use in managing host systems. The 198 term `host' is construed to mean any computer that 199 communicates with other similar computers attached to 200 the internet and that is directly used by one or more 201 human beings. Although this MIB does not necessarily 202 apply to devices whose primary function is 203 communications services (e.g., terminal servers, 204 routers, bridges, monitoring equipment), such 205 relevance is not explicitly precluded. This MIB 206 instruments attributes common to all internet hosts 207 including, for example, both personal computers and 208 systems that run variants of Unix." 209 REVISION "9907312200Z" -- 31 July, 1999 210 DESCRIPTION 211 "Clarifications and bug fixes based on implementation 212 experience. This revision was also reformatted in the 213 SMIv2 format. The revisions made were: 215 New RFC document standards: 216 Added Copyright notice, updated introduction to SNMP 217 Framework, updated references section, added reference to 218 RFC 2119, and added a meaningful Security Considerations 219 section. 221 New IANA considerations section for registration of new types 223 Conversion to new SMIv2 syntax for the following types and 224 macros: 225 Counter32, Integer32, Gauge32, MODULE-IDENTITY, 226 OBJECT-TYPE, TEXTUAL-CONVENTION, OBJECT-IDENTITY, 227 MODULE-COMPLIANCE, OBJECT-GROUP 229 Used new Textual Conventions: 230 TruthValue, DateAndTime, AutonomousType, 231 InterfaceIndexOrZero 233 Fixed typo in hrPrinterStatus. 235 Added missing error bits to hrPrinterDetectedErrorState and 236 clarified how to handle situations when two errors are active 237 at once. 239 Clarified that size of objects of type 240 InternationalDisplayString is number of octets, not number of 241 encoded symbols. 243 Clarified the use of the following objects based on 244 implementation experience: 245 hrSystemInitialLoadDevice, hrSystemInitialLoadParameters, 246 hrMemorySize, hrStorageSize, hrStorageAllocationFailures, 247 hrDeviceErrors, hrProcessorLoad, hrNetworkIfIndex, 248 hrDiskStorageCapacity, hrSWRunStatus, hrSWRunPerfCPU, 249 and hrSWInstalledDate. 251 Clarified implementation technique for hrSWInstalledTable. 253 Used new AUGMENTS clause for hrSWRunPerfTable 254 This revision published as RFCXXXX." 255 REVISION "9309011200Z" -- 1 Sep, 1993 256 DESCRIPTION 257 "The original version of this MIB, published as 258 RFC1514." 259 ::= { hrMIBAdminInfo 1 } 261 host OBJECT IDENTIFIER ::= { mib-2 25 } 263 hrSystem OBJECT IDENTIFIER ::= { host 1 } 264 hrStorage OBJECT IDENTIFIER ::= { host 2 } 265 hrDevice OBJECT IDENTIFIER ::= { host 3 } 266 hrSWRun OBJECT IDENTIFIER ::= { host 4 } 267 hrSWRunPerf OBJECT IDENTIFIER ::= { host 5 } 268 hrSWInstalled OBJECT IDENTIFIER ::= { host 6 } 269 hrMIBAdminInfo OBJECT IDENTIFIER ::= { host 7 } 270 -- textual conventions 272 KBytes ::= TEXTUAL-CONVENTION 273 STATUS current 274 DESCRIPTION 275 "Storage size, expressed in units of 1024 bytes." 276 SYNTAX Integer32 (0..2147483647) 278 ProductID ::= TEXTUAL-CONVENTION 279 STATUS current 280 DESCRIPTION 281 "This textual convention is intended to identify the 282 manufacturer, model, and version of a specific 283 hardware or software product. It is suggested that 284 these OBJECT IDENTIFIERs are allocated such that all 285 products from a particular manufacturer are registered 286 under a subtree distinct to that manufacturer. In 287 addition, all versions of a product should be 288 registered under a subtree distinct to that product. 289 With this strategy, a management station may uniquely 290 determine the manufacturer and/or model of a product 291 whose productID is unknown to the management station. 292 Objects of this type may be useful for inventory 293 purposes or for automatically detecting 294 incompatibilities or version mismatches between 295 various hardware and software components on a system. 297 For example, the product ID for the ACME 4860 66MHz 298 clock doubled processor might be: 299 enterprises.acme.acmeProcessors.a4860DX2.MHz66 301 A software product might be registered as: 302 enterprises.acme.acmeOperatingSystems.acmeDOS.six(6).one(1) 303 " 304 SYNTAX OBJECT IDENTIFIER 306 -- unknownProduct will be used for any unknown ProductID 307 -- unknownProduct OBJECT IDENTIFIER ::= { 0 0 } 308 InternationalDisplayString ::= TEXTUAL-CONVENTION 309 STATUS current 310 DESCRIPTION 311 "This data type is used to model textual information 312 in some character set. A network management station 313 should use a local algorithm to determine which 314 character set is in use and how it should be 315 displayed. Note that this character set may be 316 encoded with more than one octet per symbol, but will 317 most often be NVT ASCII. When a size clause is 318 specified for an object of this type, the size refers 319 to the length in octets, not the number of symbols." 320 SYNTAX OCTET STRING 322 -- The Host Resources System Group 324 hrSystemUptime OBJECT-TYPE 325 SYNTAX TimeTicks 326 MAX-ACCESS read-only 327 STATUS current 328 DESCRIPTION 329 "The amount of time since this host was last 330 initialized. Note that this is different from 331 sysUpTime in the SNMPv2-MIB [RFC1907] because 332 sysUpTime is the uptime of the network management 333 portion of the system." 334 ::= { hrSystem 1 } 336 hrSystemDate OBJECT-TYPE 337 SYNTAX DateAndTime 338 MAX-ACCESS read-write 339 STATUS current 340 DESCRIPTION 341 "The host's notion of the local date and time of day." 342 ::= { hrSystem 2 } 344 hrSystemInitialLoadDevice OBJECT-TYPE 345 SYNTAX Integer32 (1..2147483647) 346 MAX-ACCESS read-write 347 STATUS current 348 DESCRIPTION 349 "The index of the hrDeviceEntry for the device from 350 which this host is configured to load its initial 351 operating system configuration (i.e., which operating 352 system code and/or boot parameters). 354 Note that writing to this object just changes the 355 configuration that will be used the next time the 356 operating system is loaded and does not actually cause 357 the reload to occur." 358 ::= { hrSystem 3 } 360 hrSystemInitialLoadParameters OBJECT-TYPE 361 SYNTAX InternationalDisplayString (SIZE (0..128)) 362 MAX-ACCESS read-write 363 STATUS current 364 DESCRIPTION 365 "This object contains the parameters (e.g. a pathname 366 and parameter) supplied to the load device when 367 requesting the initial operating system configuration 368 from that device. 370 Note that writing to this object just changes the 371 configuration that will be used the next time the 372 operating system is loaded and does not actually cause 373 the reload to occur." 374 ::= { hrSystem 4 } 376 hrSystemNumUsers OBJECT-TYPE 377 SYNTAX Gauge32 378 MAX-ACCESS read-only 379 STATUS current 380 DESCRIPTION 381 "The number of user sessions for which this host is 382 storing state information. A session is a collection 383 of processes requiring a single act of user 384 authentication and possibly subject to collective job 385 control." 386 ::= { hrSystem 5 } 388 hrSystemProcesses OBJECT-TYPE 389 SYNTAX Gauge32 390 MAX-ACCESS read-only 391 STATUS current 392 DESCRIPTION 393 "The number of process contexts currently loaded or 394 running on this system." 395 ::= { hrSystem 6 } 397 hrSystemMaxProcesses OBJECT-TYPE 398 SYNTAX Integer32 (0..2147483647) 399 MAX-ACCESS read-only 400 STATUS current 401 DESCRIPTION 402 "The maximum number of process contexts this system 403 can support. If there is no fixed maximum, the value 404 should be zero. On systems that have a fixed maximum, 405 this object can help diagnose failures that occur when 406 this maximum is reached." 407 ::= { hrSystem 7 } 409 -- The Host Resources Storage Group 411 -- Registration point for storage types, for use with hrStorageType. 412 -- These are defined in the HOST-RESOURCES-TYPES module. 413 hrStorageTypes OBJECT IDENTIFIER ::= { hrStorage 1 } 415 hrMemorySize OBJECT-TYPE 416 SYNTAX KBytes 417 MAX-ACCESS read-only 418 STATUS current 419 DESCRIPTION 420 "The amount of physical read-write main memory, 421 typically RAM, contained by the host." 422 ::= { hrStorage 2 } 424 hrStorageTable OBJECT-TYPE 425 SYNTAX SEQUENCE OF HrStorageEntry 426 MAX-ACCESS not-accessible 427 STATUS current 428 DESCRIPTION 429 "The (conceptual) table of logical storage areas on 430 the host. 432 An entry shall be placed in the storage table for each 433 logical area of storage that is allocated and has 434 fixed resource limits. The amount of storage 435 represented in an entity is the amount actually usable 436 by the requesting entity, and excludes loss due to 437 formatting or file system reference information. 439 These entries are associated with logical storage 440 areas, as might be seen by an application, rather than 441 physical storage entities which are typically seen by 442 an operating system. Storage such as tapes and 443 floppies without file systems on them are typically 444 not allocated in chunks by the operating system to 445 requesting applications, and therefore shouldn't 446 appear in this table. Examples of valid storage for 447 this table include disk partitions, file systems, ram 448 (for some architectures this is further segmented into 449 regular memory, extended memory, and so on), backing 450 store for virtual memory (`swap space'). 452 This table is intended to be a useful diagnostic for 453 `out of memory' and `out of buffers' types of 454 failures. In addition, it can be a useful performance 455 monitoring tool for tracking memory, disk, or buffer 456 usage." 457 ::= { hrStorage 3 } 459 hrStorageEntry OBJECT-TYPE 460 SYNTAX HrStorageEntry 461 MAX-ACCESS not-accessible 462 STATUS current 463 DESCRIPTION 464 "A (conceptual) entry for one logical storage area on 465 the host. As an example, an instance of the 466 hrStorageType object might be named hrStorageType.3" 467 INDEX { hrStorageIndex } 468 ::= { hrStorageTable 1 } 470 HrStorageEntry ::= SEQUENCE { 471 hrStorageIndex Integer32, 472 hrStorageType AutonomousType, 473 hrStorageDescr DisplayString, 474 hrStorageAllocationUnits Integer32, 475 hrStorageSize Integer32, 476 hrStorageUsed Integer32, 477 hrStorageAllocationFailures Counter32 478 } 480 hrStorageIndex OBJECT-TYPE 481 SYNTAX Integer32 (1..2147483647) 482 MAX-ACCESS read-only 483 STATUS current 484 DESCRIPTION 485 "A unique value for each logical storage area 486 contained by the host." 487 ::= { hrStorageEntry 1 } 489 hrStorageType OBJECT-TYPE 490 SYNTAX AutonomousType 491 MAX-ACCESS read-only 492 STATUS current 493 DESCRIPTION 494 "The type of storage represented by this entry." 495 ::= { hrStorageEntry 2 } 497 hrStorageDescr OBJECT-TYPE 498 SYNTAX DisplayString 499 MAX-ACCESS read-only 500 STATUS current 501 DESCRIPTION 502 "A description of the type and instance of the storage 503 described by this entry." 504 ::= { hrStorageEntry 3 } 506 hrStorageAllocationUnits OBJECT-TYPE 507 SYNTAX Integer32 (1..2147483647) 508 MAX-ACCESS read-only 509 STATUS current 510 DESCRIPTION 511 "The size, in bytes, of the data objects allocated 512 from this pool. If this entry is monitoring sectors, 513 blocks, buffers, or packets, for example, this number 514 will commonly be greater than one. Otherwise this 515 number will typically be one." 516 ::= { hrStorageEntry 4 } 518 hrStorageSize OBJECT-TYPE 519 SYNTAX Integer32 (0..2147483647) 520 MAX-ACCESS read-write 521 STATUS current 522 DESCRIPTION 523 "The size of the storage represented by this entry, in 524 units of hrStorageAllocationUnits. This object is 525 writable to allow remote configuration of the size of 526 the storage area in those cases where such an 527 operation makes sense and is possible on the 528 underlying system. For example, the amount of main 529 memory allocated to a buffer pool might be modified or 530 the amount of disk space allocated to virtual memory 531 might be modified." 532 ::= { hrStorageEntry 5 } 534 hrStorageUsed OBJECT-TYPE 535 SYNTAX Integer32 (0..2147483647) 536 MAX-ACCESS read-only 537 STATUS current 538 DESCRIPTION 539 "The amount of the storage represented by this entry 540 that is allocated, in units of 541 hrStorageAllocationUnits." 542 ::= { hrStorageEntry 6 } 544 hrStorageAllocationFailures OBJECT-TYPE 545 SYNTAX Counter32 546 MAX-ACCESS read-only 547 STATUS current 548 DESCRIPTION 549 "The number of requests for storage represented by 550 this entry that could not be honored due to not enough 551 storage. It should be noted that as this object has a 552 SYNTAX of Counter32, that it does not have a defined 553 initial value. However, it is recommended that this 554 object be initialized to zero, even though management 555 stations must not depend on such an initialization." 556 ::= { hrStorageEntry 7 } 558 -- The Host Resources Device Group 559 -- 560 -- The device group is useful for identifying and diagnosing the 561 -- devices on a system. The hrDeviceTable contains common 562 -- information for any type of device. In addition, some devices 563 -- have device-specific tables for more detailed information. More 564 -- such tables may be defined in the future for other device types. 566 -- Registration point for device types, for use with hrDeviceType. 567 -- These are defined in the HOST-RESOURCES-TYPES module. 568 hrDeviceTypes OBJECT IDENTIFIER ::= { hrDevice 1 } 569 hrDeviceTable OBJECT-TYPE 570 SYNTAX SEQUENCE OF HrDeviceEntry 571 MAX-ACCESS not-accessible 572 STATUS current 573 DESCRIPTION 574 "The (conceptual) table of devices contained by the 575 host." 576 ::= { hrDevice 2 } 578 hrDeviceEntry OBJECT-TYPE 579 SYNTAX HrDeviceEntry 580 MAX-ACCESS not-accessible 581 STATUS current 582 DESCRIPTION 583 "A (conceptual) entry for one device contained by the 584 host. As an example, an instance of the hrDeviceType 585 object might be named hrDeviceType.3" 586 INDEX { hrDeviceIndex } 587 ::= { hrDeviceTable 1 } 589 HrDeviceEntry ::= SEQUENCE { 590 hrDeviceIndex Integer32, 591 hrDeviceType AutonomousType, 592 hrDeviceDescr DisplayString, 593 hrDeviceID ProductID, 594 hrDeviceStatus INTEGER, 595 hrDeviceErrors Counter32 596 } 598 hrDeviceIndex OBJECT-TYPE 599 SYNTAX Integer32 (1..2147483647) 600 MAX-ACCESS read-only 601 STATUS current 602 DESCRIPTION 603 "A unique value for each device contained by the host. 604 The value for each device must remain constant at 605 least from one re-initialization of the agent to the 606 next re-initialization." 607 ::= { hrDeviceEntry 1 } 609 hrDeviceType OBJECT-TYPE 610 SYNTAX AutonomousType 611 MAX-ACCESS read-only 612 STATUS current 613 DESCRIPTION 614 "An indication of the type of device. 616 If this value is 617 `hrDeviceProcessor { hrDeviceTypes 3 }' then an entry 618 exists in the hrProcessorTable which corresponds to 619 this device. 621 If this value is 622 `hrDeviceNetwork { hrDeviceTypes 4 }', then an entry 623 exists in the hrNetworkTable which corresponds to this 624 device. 626 If this value is 627 `hrDevicePrinter { hrDeviceTypes 5 }', then an entry 628 exists in the hrPrinterTable which corresponds to this 629 device. 631 If this value is 632 `hrDeviceDiskStorage { hrDeviceTypes 6 }', then an 633 entry exists in the hrDiskStorageTable which 634 corresponds to this device." 635 ::= { hrDeviceEntry 2 } 637 hrDeviceDescr OBJECT-TYPE 638 SYNTAX DisplayString (SIZE (0..64)) 639 MAX-ACCESS read-only 640 STATUS current 641 DESCRIPTION 642 "A textual description of this device, including the 643 device's manufacturer and revision, and optionally, 644 its serial number." 645 ::= { hrDeviceEntry 3 } 647 hrDeviceID OBJECT-TYPE 648 SYNTAX ProductID 649 MAX-ACCESS read-only 650 STATUS current 651 DESCRIPTION 652 "The product ID for this device." 653 ::= { hrDeviceEntry 4 } 655 hrDeviceStatus OBJECT-TYPE 656 SYNTAX INTEGER { 657 unknown(1), 658 running(2), 659 warning(3), 660 testing(4), 661 down(5) 662 } 663 MAX-ACCESS read-only 664 STATUS current 665 DESCRIPTION 666 "The current operational state of the device described 667 by this row of the table. A value unknown(1) 668 indicates that the current state of the device is 669 unknown. running(2) indicates that the device is up 670 and running and that no unusual error conditions are 671 known. The warning(3) state indicates that agent has 672 been informed of an unusual error condition by the 673 operational software (e.g., a disk device driver) but 674 that the device is still 'operational'. An example 675 would be a high number of soft errors on a disk. A 676 value of testing(4), indicates that the device is not 677 available for use because it is in the testing state. 678 The state of down(5) is used only when the agent has 679 been informed that the device is not available for any 680 use." 681 ::= { hrDeviceEntry 5 } 683 hrDeviceErrors OBJECT-TYPE 684 SYNTAX Counter32 685 MAX-ACCESS read-only 686 STATUS current 687 DESCRIPTION 688 "The number of errors detected on this device. It 689 should be noted that as this object has a SYNTAX of 690 Counter32, that it does not have a defined initial 691 value. However, it is recommended that this object be 692 initialized to zero, even though management stations 693 must not depend on such an initialization." 694 ::= { hrDeviceEntry 6 } 696 hrProcessorTable OBJECT-TYPE 697 SYNTAX SEQUENCE OF HrProcessorEntry 698 MAX-ACCESS not-accessible 699 STATUS current 700 DESCRIPTION 701 "The (conceptual) table of processors contained by the 702 host. 704 Note that this table is potentially sparse: a 705 (conceptual) entry exists only if the correspondent 706 value of the hrDeviceType object is 707 `hrDeviceProcessor'." 708 ::= { hrDevice 3 } 710 hrProcessorEntry OBJECT-TYPE 711 SYNTAX HrProcessorEntry 712 MAX-ACCESS not-accessible 713 STATUS current 714 DESCRIPTION 715 "A (conceptual) entry for one processor contained by 716 the host. The hrDeviceIndex in the index represents 717 the entry in the hrDeviceTable that corresponds to the 718 hrProcessorEntry. 720 As an example of how objects in this table are named, 721 an instance of the hrProcessorFrwID object might be 722 named hrProcessorFrwID.3" 723 INDEX { hrDeviceIndex } 724 ::= { hrProcessorTable 1 } 726 HrProcessorEntry ::= SEQUENCE { 727 hrProcessorFrwID ProductID, 728 hrProcessorLoad Integer32 729 } 731 hrProcessorFrwID OBJECT-TYPE 732 SYNTAX ProductID 733 MAX-ACCESS read-only 734 STATUS current 735 DESCRIPTION 736 "The product ID of the firmware associated with the 737 processor." 738 ::= { hrProcessorEntry 1 } 740 hrProcessorLoad OBJECT-TYPE 741 SYNTAX Integer32 (0..100) 742 MAX-ACCESS read-only 743 STATUS current 744 DESCRIPTION 745 "The average, over the last minute, of the percentage 746 of time that this processor was not idle. 747 Implementations may approximate this one minute 748 smoothing period if necessary." 749 ::= { hrProcessorEntry 2 } 751 hrNetworkTable OBJECT-TYPE 752 SYNTAX SEQUENCE OF HrNetworkEntry 753 MAX-ACCESS not-accessible 754 STATUS current 755 DESCRIPTION 756 "The (conceptual) table of network devices contained 757 by the host. 759 Note that this table is potentially sparse: a 760 (conceptual) entry exists only if the correspondent 761 value of the hrDeviceType object is 762 `hrDeviceNetwork'." 763 ::= { hrDevice 4 } 765 hrNetworkEntry OBJECT-TYPE 766 SYNTAX HrNetworkEntry 767 MAX-ACCESS not-accessible 768 STATUS current 769 DESCRIPTION 770 "A (conceptual) entry for one network device contained 771 by the host. The hrDeviceIndex in the index 772 represents the entry in the hrDeviceTable that 773 corresponds to the hrNetworkEntry. 775 As an example of how objects in this table are named, 776 an instance of the hrNetworkIfIndex object might be 777 named hrNetworkIfIndex.3" 778 INDEX { hrDeviceIndex } 779 ::= { hrNetworkTable 1 } 781 HrNetworkEntry ::= SEQUENCE { 782 hrNetworkIfIndex InterfaceIndexOrZero 783 } 785 hrNetworkIfIndex OBJECT-TYPE 786 SYNTAX InterfaceIndexOrZero 787 MAX-ACCESS read-only 788 STATUS current 789 DESCRIPTION 790 "The value of ifIndex which corresponds to this 791 network device. If this device is not represented in 792 the ifTable, then this value shall be zero." 793 ::= { hrNetworkEntry 1 } 795 hrPrinterTable OBJECT-TYPE 796 SYNTAX SEQUENCE OF HrPrinterEntry 797 MAX-ACCESS not-accessible 798 STATUS current 799 DESCRIPTION 800 "The (conceptual) table of printers local to the host. 802 Note that this table is potentially sparse: a 803 (conceptual) entry exists only if the correspondent 804 value of the hrDeviceType object is 805 `hrDevicePrinter'." 806 ::= { hrDevice 5 } 808 hrPrinterEntry OBJECT-TYPE 809 SYNTAX HrPrinterEntry 810 MAX-ACCESS not-accessible 811 STATUS current 812 DESCRIPTION 813 "A (conceptual) entry for one printer local to the 814 host. The hrDeviceIndex in the index represents the 815 entry in the hrDeviceTable that corresponds to the 816 hrPrinterEntry. 818 As an example of how objects in this table are named, 819 an instance of the hrPrinterStatus object might be 820 named hrPrinterStatus.3" 821 INDEX { hrDeviceIndex } 822 ::= { hrPrinterTable 1 } 824 HrPrinterEntry ::= SEQUENCE { 825 hrPrinterStatus INTEGER, 826 hrPrinterDetectedErrorState OCTET STRING 827 } 829 hrPrinterStatus OBJECT-TYPE 830 SYNTAX INTEGER { 831 other(1), 832 unknown(2), 833 idle(3), 834 printing(4), 835 warmup(5) 836 } 837 MAX-ACCESS read-only 838 STATUS current 839 DESCRIPTION 840 "The current status of this printer device. When in 841 the idle(3), printing(4), or warmup(5) state, the 842 corresponding hrDeviceStatus should be running(2) or 843 warning(3). When in the unknown(2) state, the 844 corresponding hrDeviceStatus should be unknown(1)." 845 ::= { hrPrinterEntry 1 } 847 hrPrinterDetectedErrorState OBJECT-TYPE 848 SYNTAX OCTET STRING 849 MAX-ACCESS read-only 850 STATUS current 851 DESCRIPTION 852 "This object represents any error conditions detected 853 by the printer. The error conditions are encoded as 854 bits in an octet string, with the following 855 definitions: 857 Condition Bit # hrDeviceStatus 859 lowPaper 0 warning(3) 860 noPaper 1 down(5) 861 lowToner 2 warning(3) 862 noToner 3 down(5) 863 doorOpen 4 down(5) 864 jammed 5 down(5) 865 offline 6 down(5) 866 serviceRequested 7 warning(3) 867 inputTrayMissing 8 warning(3) 868 outputTrayMissing 9 warning(3) 869 markerSupplyMissing 10 warning(3) 870 outputNearFull 11 warning(3) 871 outputFull 12 warning(3) 872 inputTrayEmpty 13 warning(3) 873 overduePreventMaint 14 warning(3) 875 The hrDeviceStatus column shows the hrDeviceStatus 876 which is typically appropriate when such an error 877 condition exists. If multiple conditions are 878 simultaneously detected and the hrDeviceStatus would 879 not otherwise be unknown(1) or testing(4), the 880 hrDeviceStatus shall correspond to the worst state of 881 those indicated, where down(5) is worse than 882 warning(3) which is worse than running(2). 884 Bits are numbered starting with the most significant 885 bit of the first byte being bit 0, the least 886 significant bit of the first byte being bit 7, the 887 most significant bit of the second byte being bit 8, 888 and so on. A one bit encodes that the condition was 889 detected, while a zero bit encodes that the condition 890 was not detected. 892 This object is useful for alerting an operator to 893 specific warning or error conditions that may occur, 894 especially those requiring human intervention." 895 ::= { hrPrinterEntry 2 } 897 hrDiskStorageTable OBJECT-TYPE 898 SYNTAX SEQUENCE OF HrDiskStorageEntry 899 MAX-ACCESS not-accessible 900 STATUS current 901 DESCRIPTION 902 "The (conceptual) table of long-term storage devices 903 contained by the host. In particular, disk devices 904 accessed remotely over a network are not included 905 here. 907 Note that this table is potentially sparse: a 908 (conceptual) entry exists only if the correspondent 909 value of the hrDeviceType object is 910 `hrDeviceDiskStorage'." 911 ::= { hrDevice 6 } 913 hrDiskStorageEntry OBJECT-TYPE 914 SYNTAX HrDiskStorageEntry 915 MAX-ACCESS not-accessible 916 STATUS current 917 DESCRIPTION 918 "A (conceptual) entry for one long-term storage device 919 contained by the host. The hrDeviceIndex in the index 920 represents the entry in the hrDeviceTable that 921 corresponds to the hrDiskStorageEntry. As an example, 922 an instance of the hrDiskStorageCapacity object might 923 be named hrDiskStorageCapacity.3" 924 INDEX { hrDeviceIndex } 925 ::= { hrDiskStorageTable 1 } 927 HrDiskStorageEntry ::= SEQUENCE { 928 hrDiskStorageAccess INTEGER, 929 hrDiskStorageMedia INTEGER, 930 hrDiskStorageRemoveble TruthValue, 931 hrDiskStorageCapacity KBytes 932 } 934 hrDiskStorageAccess OBJECT-TYPE 935 SYNTAX INTEGER { 936 readWrite(1), 937 readOnly(2) 938 } 939 MAX-ACCESS read-only 940 STATUS current 941 DESCRIPTION 942 "An indication if this long-term storage device is 943 readable and writable or only readable. This should 944 reflect the media type, any write-protect mechanism, 945 and any device configuration that affects the entire 946 device." 947 ::= { hrDiskStorageEntry 1 } 949 hrDiskStorageMedia OBJECT-TYPE 950 SYNTAX INTEGER { 951 other(1), 952 unknown(2), 953 hardDisk(3), 954 floppyDisk(4), 955 opticalDiskROM(5), 956 opticalDiskWORM(6), -- Write Once Read Many 957 opticalDiskRW(7), 958 ramDisk(8) 959 } 960 MAX-ACCESS read-only 961 STATUS current 962 DESCRIPTION 963 "An indication of the type of media used in this long- 964 term storage device." 965 ::= { hrDiskStorageEntry 2 } 967 hrDiskStorageRemoveble OBJECT-TYPE 968 SYNTAX TruthValue 969 MAX-ACCESS read-only 970 STATUS current 971 DESCRIPTION 972 "Denotes whether or not the disk media may be removed 973 from the drive." 974 ::= { hrDiskStorageEntry 3 } 976 hrDiskStorageCapacity OBJECT-TYPE 977 SYNTAX KBytes 978 MAX-ACCESS read-only 979 STATUS current 980 DESCRIPTION 981 "The total size for this long-term storage device. If 982 the media is removable and is currently removed, this 983 value should be zero." 984 ::= { hrDiskStorageEntry 4 } 986 hrPartitionTable OBJECT-TYPE 987 SYNTAX SEQUENCE OF HrPartitionEntry 988 MAX-ACCESS not-accessible 989 STATUS current 990 DESCRIPTION 991 "The (conceptual) table of partitions for long-term 992 storage devices contained by the host. In particular, 993 partitions accessed remotely over a network are not 994 included here." 995 ::= { hrDevice 7 } 997 hrPartitionEntry OBJECT-TYPE 998 SYNTAX HrPartitionEntry 999 MAX-ACCESS not-accessible 1000 STATUS current 1001 DESCRIPTION 1002 "A (conceptual) entry for one partition. The 1003 hrDeviceIndex in the index represents the entry in the 1004 hrDeviceTable that corresponds to the 1005 hrPartitionEntry. 1007 As an example of how objects in this table are named, 1008 an instance of the hrPartitionSize object might be 1009 named hrPartitionSize.3.1" 1010 INDEX { hrDeviceIndex, hrPartitionIndex } 1011 ::= { hrPartitionTable 1 } 1013 HrPartitionEntry ::= SEQUENCE { 1014 hrPartitionIndex Integer32, 1015 hrPartitionLabel InternationalDisplayString, 1016 hrPartitionID OCTET STRING, 1017 hrPartitionSize KBytes, 1018 hrPartitionFSIndex Integer32 1019 } 1021 hrPartitionIndex OBJECT-TYPE 1022 SYNTAX Integer32 (1..2147483647) 1023 MAX-ACCESS read-only 1024 STATUS current 1025 DESCRIPTION 1026 "A unique value for each partition on this long-term 1027 storage device. The value for each long-term storage 1028 device must remain constant at least from one re- 1029 initialization of the agent to the next re- 1030 initialization." 1032 ::= { hrPartitionEntry 1 } 1034 hrPartitionLabel OBJECT-TYPE 1035 SYNTAX InternationalDisplayString (SIZE (0..128)) 1036 MAX-ACCESS read-only 1037 STATUS current 1038 DESCRIPTION 1039 "A textual description of this partition." 1040 ::= { hrPartitionEntry 2 } 1042 hrPartitionID OBJECT-TYPE 1043 SYNTAX OCTET STRING 1044 MAX-ACCESS read-only 1045 STATUS current 1046 DESCRIPTION 1047 "A descriptor which uniquely represents this partition 1048 to the responsible operating system. On some systems, 1049 this might take on a binary representation." 1050 ::= { hrPartitionEntry 3 } 1052 hrPartitionSize OBJECT-TYPE 1053 SYNTAX KBytes 1054 MAX-ACCESS read-only 1055 STATUS current 1056 DESCRIPTION 1057 "The size of this partition." 1058 ::= { hrPartitionEntry 4 } 1060 hrPartitionFSIndex OBJECT-TYPE 1061 SYNTAX Integer32 (0..2147483647) 1062 MAX-ACCESS read-only 1063 STATUS current 1064 DESCRIPTION 1065 "The index of the file system mounted on this 1066 partition. If no file system is mounted on this 1067 partition, then this value shall be zero. Note that 1068 multiple partitions may point to one file system, 1069 denoting that that file system resides on those 1070 partitions. Multiple file systems may not reside on 1071 one partition." 1072 ::= { hrPartitionEntry 5 } 1074 -- The File System Table 1076 -- Registration point for popular File System types, 1077 -- for use with hrFSType. These are defined in the 1078 -- HOST-RESOURCES-TYPES module. 1079 hrFSTypes OBJECT IDENTIFIER ::= { hrDevice 9 } 1081 hrFSTable OBJECT-TYPE 1082 SYNTAX SEQUENCE OF HrFSEntry 1083 MAX-ACCESS not-accessible 1084 STATUS current 1085 DESCRIPTION 1086 "The (conceptual) table of file systems local to this 1087 host or remotely mounted from a file server. File 1088 systems that are in only one user's environment on a 1089 multi-user system will not be included in this table." 1090 ::= { hrDevice 8 } 1092 hrFSEntry OBJECT-TYPE 1093 SYNTAX HrFSEntry 1094 MAX-ACCESS not-accessible 1095 STATUS current 1096 DESCRIPTION 1097 "A (conceptual) entry for one file system local to 1098 this host or remotely mounted from a file server. 1099 File systems that are in only one user's environment 1100 on a multi-user system will not be included in this 1101 table. 1103 As an example of how objects in this table are named, 1104 an instance of the hrFSMountPoint object might be 1105 named hrFSMountPoint.3" 1106 INDEX { hrFSIndex } 1107 ::= { hrFSTable 1 } 1109 HrFSEntry ::= SEQUENCE { 1110 hrFSIndex Integer32, 1111 hrFSMountPoint InternationalDisplayString, 1112 hrFSRemoteMountPoint InternationalDisplayString, 1113 hrFSType AutonomousType, 1114 hrFSAccess INTEGER, 1115 hrFSBootable TruthValue, 1116 hrFSStorageIndex Integer32, 1117 hrFSLastFullBackupDate DateAndTime, 1118 hrFSLastPartialBackupDate DateAndTime 1120 } 1122 hrFSIndex OBJECT-TYPE 1123 SYNTAX Integer32 (1..2147483647) 1124 MAX-ACCESS read-only 1125 STATUS current 1126 DESCRIPTION 1127 "A unique value for each file system local to this 1128 host. The value for each file system must remain 1129 constant at least from one re-initialization of the 1130 agent to the next re-initialization." 1131 ::= { hrFSEntry 1 } 1133 hrFSMountPoint OBJECT-TYPE 1134 SYNTAX InternationalDisplayString (SIZE(0..128)) 1135 MAX-ACCESS read-only 1136 STATUS current 1137 DESCRIPTION 1138 "The path name of the root of this file system." 1139 ::= { hrFSEntry 2 } 1141 hrFSRemoteMountPoint OBJECT-TYPE 1142 SYNTAX InternationalDisplayString (SIZE(0..128)) 1143 MAX-ACCESS read-only 1144 STATUS current 1145 DESCRIPTION 1146 "A description of the name and/or address of the 1147 server that this file system is mounted from. This 1148 may also include parameters such as the mount point on 1149 the remote file system. If this is not a remote file 1150 system, this string should have a length of zero." 1151 ::= { hrFSEntry 3 } 1153 hrFSType OBJECT-TYPE 1154 SYNTAX AutonomousType 1155 MAX-ACCESS read-only 1156 STATUS current 1157 DESCRIPTION 1158 "The value of this object identifies the type of this 1159 file system." 1160 ::= { hrFSEntry 4 } 1162 hrFSAccess OBJECT-TYPE 1163 SYNTAX INTEGER { 1164 readWrite(1), 1165 readOnly(2) 1166 } 1167 MAX-ACCESS read-only 1168 STATUS current 1169 DESCRIPTION 1170 "An indication if this file system is logically 1171 configured by the operating system to be readable and 1172 writable or only readable. This does not represent 1173 any local access-control policy, except one that is 1174 applied to the file system as a whole." 1175 ::= { hrFSEntry 5 } 1177 hrFSBootable OBJECT-TYPE 1178 SYNTAX TruthValue 1179 MAX-ACCESS read-only 1180 STATUS current 1181 DESCRIPTION 1182 "A flag indicating whether this file system is 1183 bootable." 1184 ::= { hrFSEntry 6 } 1186 hrFSStorageIndex OBJECT-TYPE 1187 SYNTAX Integer32 (0..2147483647) 1188 MAX-ACCESS read-only 1189 STATUS current 1190 DESCRIPTION 1191 "The index of the hrStorageEntry that represents 1192 information about this file system. If there is no 1193 such information available, then this value shall be 1194 zero. The relevant storage entry will be useful in 1195 tracking the percent usage of this file system and 1196 diagnosing errors that may occur when it runs out of 1197 space." 1198 ::= { hrFSEntry 7 } 1200 hrFSLastFullBackupDate OBJECT-TYPE 1201 SYNTAX DateAndTime 1202 MAX-ACCESS read-write 1203 STATUS current 1204 DESCRIPTION 1205 "The last date at which this complete file system was 1206 copied to another storage device for backup. This 1207 information is useful for ensuring that backups are 1208 being performed regularly. 1210 If this information is not known, then this variable 1211 shall have the value corresponding to January 1, year 1212 0000, 00:00:00.0, which is encoded as 1213 (hex)'00 00 01 01 00 00 00 00'." 1214 ::= { hrFSEntry 8 } 1216 hrFSLastPartialBackupDate OBJECT-TYPE 1217 SYNTAX DateAndTime 1218 MAX-ACCESS read-write 1219 STATUS current 1220 DESCRIPTION 1221 "The last date at which a portion of this file system 1222 was copied to another storage device for backup. This 1223 information is useful for ensuring that backups are 1224 being performed regularly. 1226 If this information is not known, then this variable 1227 shall have the value corresponding to January 1, year 1228 0000, 00:00:00.0, which is encoded as 1229 (hex)'00 00 01 01 00 00 00 00'." 1230 ::= { hrFSEntry 9 } 1232 -- The Host Resources Running Software Group 1233 -- 1234 -- The hrSWRunTable contains an entry for each distinct piece of 1235 -- software that is running or loaded into physical or virtual 1236 -- memory in preparation for running. This includes the host's 1237 -- operating system, device drivers, and applications. 1239 hrSWOSIndex OBJECT-TYPE 1240 SYNTAX Integer32 (1..2147483647) 1241 MAX-ACCESS read-only 1242 STATUS current 1243 DESCRIPTION 1244 "The value of the hrSWRunIndex for the hrSWRunEntry 1245 that represents the primary operating system running 1246 on this host. This object is useful for quickly and 1247 uniquely identifying that primary operating system." 1248 ::= { hrSWRun 1 } 1250 hrSWRunTable OBJECT-TYPE 1251 SYNTAX SEQUENCE OF HrSWRunEntry 1252 MAX-ACCESS not-accessible 1253 STATUS current 1254 DESCRIPTION 1255 "The (conceptual) table of software running on the 1256 host." 1257 ::= { hrSWRun 2 } 1259 hrSWRunEntry OBJECT-TYPE 1260 SYNTAX HrSWRunEntry 1261 MAX-ACCESS not-accessible 1262 STATUS current 1263 DESCRIPTION 1264 "A (conceptual) entry for one piece of software 1265 running on the host Note that because the installed 1266 software table only contains information for software 1267 stored locally on this host, not every piece of 1268 running software will be found in the installed 1269 software table. This is true of software that was 1270 loaded and run from a non-local source, such as a 1271 network-mounted file system. 1273 As an example of how objects in this table are named, 1274 an instance of the hrSWRunName object might be named 1275 hrSWRunName.1287" 1276 INDEX { hrSWRunIndex } 1277 ::= { hrSWRunTable 1 } 1279 HrSWRunEntry ::= SEQUENCE { 1280 hrSWRunIndex Integer32, 1281 hrSWRunName InternationalDisplayString, 1282 hrSWRunID ProductID, 1283 hrSWRunPath InternationalDisplayString, 1284 hrSWRunParameters InternationalDisplayString, 1285 hrSWRunType INTEGER, 1286 hrSWRunStatus INTEGER 1287 } 1289 hrSWRunIndex OBJECT-TYPE 1290 SYNTAX Integer32 (1..2147483647) 1291 MAX-ACCESS read-only 1292 STATUS current 1293 DESCRIPTION 1294 "A unique value for each piece of software running on 1295 the host. Wherever possible, this should be the 1296 system's native, unique identification number." 1297 ::= { hrSWRunEntry 1 } 1299 hrSWRunName OBJECT-TYPE 1300 SYNTAX InternationalDisplayString (SIZE (0..64)) 1301 MAX-ACCESS read-only 1302 STATUS current 1303 DESCRIPTION 1304 "A textual description of this running piece of 1305 software, including the manufacturer, revision, and 1306 the name by which it is commonly known. If this 1307 software was installed locally, this should be the 1308 same string as used in the corresponding 1309 hrSWInstalledName." 1310 ::= { hrSWRunEntry 2 } 1312 hrSWRunID OBJECT-TYPE 1313 SYNTAX ProductID 1314 MAX-ACCESS read-only 1315 STATUS current 1316 DESCRIPTION 1317 "The product ID of this running piece of software." 1318 ::= { hrSWRunEntry 3 } 1320 hrSWRunPath OBJECT-TYPE 1321 SYNTAX InternationalDisplayString (SIZE(0..128)) 1322 MAX-ACCESS read-only 1323 STATUS current 1324 DESCRIPTION 1325 "A description of the location on long-term storage 1326 (e.g. a disk drive) from which this software was 1327 loaded." 1328 ::= { hrSWRunEntry 4 } 1330 hrSWRunParameters OBJECT-TYPE 1331 SYNTAX InternationalDisplayString (SIZE(0..128)) 1332 MAX-ACCESS read-only 1333 STATUS current 1334 DESCRIPTION 1335 "A description of the parameters supplied to this 1336 software when it was initially loaded." 1337 ::= { hrSWRunEntry 5 } 1339 hrSWRunType OBJECT-TYPE 1340 SYNTAX INTEGER { 1341 unknown(1), 1342 operatingSystem(2), 1343 deviceDriver(3), 1344 application(4) 1345 } 1346 MAX-ACCESS read-only 1347 STATUS current 1348 DESCRIPTION 1349 "The type of this software." 1350 ::= { hrSWRunEntry 6 } 1352 hrSWRunStatus OBJECT-TYPE 1353 SYNTAX INTEGER { 1354 running(1), 1355 runnable(2), -- waiting for resource 1356 -- (i.e., CPU, memory, IO) 1357 notRunnable(3), -- loaded but waiting for event 1358 invalid(4) -- not loaded 1359 } 1360 MAX-ACCESS read-write 1361 STATUS current 1362 DESCRIPTION 1363 "The status of this running piece of software. 1364 Setting this value to invalid(4) shall cause this 1365 software to stop running and to be unloaded. Sets to 1366 other values are not valid." 1368 ::= { hrSWRunEntry 7 } 1370 -- The Host Resources Running Software Performance Group 1371 -- 1372 -- The hrSWRunPerfTable contains an entry corresponding to 1373 -- each entry in the hrSWRunTable. 1375 hrSWRunPerfTable OBJECT-TYPE 1376 SYNTAX SEQUENCE OF HrSWRunPerfEntry 1377 MAX-ACCESS not-accessible 1378 STATUS current 1379 DESCRIPTION 1380 "The (conceptual) table of running software 1381 performance metrics." 1382 ::= { hrSWRunPerf 1 } 1384 hrSWRunPerfEntry OBJECT-TYPE 1385 SYNTAX HrSWRunPerfEntry 1386 MAX-ACCESS not-accessible 1387 STATUS current 1388 DESCRIPTION 1389 "A (conceptual) entry containing software performance 1390 metrics. As an example, an instance of the 1391 hrSWRunPerfCPU object might be named 1392 hrSWRunPerfCPU.1287" 1393 AUGMENTS { hrSWRunEntry } -- This table augments information in 1394 -- the hrSWRunTable. 1395 ::= { hrSWRunPerfTable 1 } 1397 HrSWRunPerfEntry ::= SEQUENCE { 1398 hrSWRunPerfCPU Integer32, 1399 hrSWRunPerfMem KBytes 1400 } 1402 hrSWRunPerfCPU OBJECT-TYPE 1403 SYNTAX Integer32 (0..2147483647) 1404 MAX-ACCESS read-only 1405 STATUS current 1406 DESCRIPTION 1407 "The number of centi-seconds of the total system's CPU 1408 resources consumed by this process. Note that on a 1409 multi-processor system, this value may increment by 1410 more than one centi-second in one centi-second of real 1411 (wall clock) time." 1412 ::= { hrSWRunPerfEntry 1 } 1414 hrSWRunPerfMem OBJECT-TYPE 1415 SYNTAX KBytes 1416 MAX-ACCESS read-only 1417 STATUS current 1418 DESCRIPTION 1419 "The total amount of real system memory allocated to 1420 this process." 1421 ::= { hrSWRunPerfEntry 2 } 1423 -- The Host Resources Installed Software Group 1424 -- 1425 -- The hrSWInstalledTable contains an entry for each piece 1426 -- of software installed in long-term storage (e.g. a disk 1427 -- drive) locally on this host. Note that this does not 1428 -- include software loadable remotely from a network 1429 -- server. 1430 -- 1431 -- Different implementations may track software in varying 1432 -- ways. For example, while some implementations may track 1433 -- executable files as distinct pieces of software, other 1434 -- implementations may use other strategies such as keeping 1435 -- track of software "packages" (e.g., related groups of files) 1436 -- or keeping track of system or application "patches". 1437 -- 1438 -- This table is useful for identifying and inventorying 1439 -- software on a host and for diagnosing incompatibility 1440 -- and version mismatch problems between various pieces 1441 -- of hardware and software. 1443 hrSWInstalledLastChange OBJECT-TYPE 1444 SYNTAX TimeTicks 1445 MAX-ACCESS read-only 1446 STATUS current 1447 DESCRIPTION 1448 "The value of sysUpTime when an entry in the 1449 hrSWInstalledTable was last added, renamed, or 1450 deleted. Because this table is likely to contain many 1451 entries, polling of this object allows a management 1452 station to determine when re-downloading of the table 1453 might be useful." 1454 ::= { hrSWInstalled 1 } 1456 hrSWInstalledLastUpdateTime OBJECT-TYPE 1457 SYNTAX TimeTicks 1458 MAX-ACCESS read-only 1459 STATUS current 1460 DESCRIPTION 1461 "The value of sysUpTime when the hrSWInstalledTable 1462 was last completely updated. Because caching of this 1463 data will be a popular implementation strategy, 1464 retrieval of this object allows a management station 1465 to obtain a guarantee that no data in this table is 1466 older than the indicated time." 1467 ::= { hrSWInstalled 2 } 1469 hrSWInstalledTable OBJECT-TYPE 1470 SYNTAX SEQUENCE OF HrSWInstalledEntry 1471 MAX-ACCESS not-accessible 1472 STATUS current 1473 DESCRIPTION 1474 "The (conceptual) table of software installed on this 1475 host." 1476 ::= { hrSWInstalled 3 } 1478 hrSWInstalledEntry OBJECT-TYPE 1479 SYNTAX HrSWInstalledEntry 1480 MAX-ACCESS not-accessible 1481 STATUS current 1482 DESCRIPTION 1483 "A (conceptual) entry for a piece of software 1484 installed on this host. 1486 As an example of how objects in this table are named, 1487 an instance of the hrSWInstalledName object might be 1488 named hrSWInstalledName.96" 1489 INDEX { hrSWInstalledIndex } 1490 ::= { hrSWInstalledTable 1 } 1492 HrSWInstalledEntry ::= SEQUENCE { 1493 hrSWInstalledIndex Integer32, 1494 hrSWInstalledName InternationalDisplayString, 1495 hrSWInstalledID ProductID, 1496 hrSWInstalledType INTEGER, 1497 hrSWInstalledDate DateAndTime 1498 } 1500 hrSWInstalledIndex OBJECT-TYPE 1501 SYNTAX Integer32 (1..2147483647) 1502 MAX-ACCESS read-only 1503 STATUS current 1504 DESCRIPTION 1505 "A unique value for each piece of software installed 1506 on the host. This value shall be in the range from 1 1507 to the number of pieces of software installed on the 1508 host." 1509 ::= { hrSWInstalledEntry 1 } 1511 hrSWInstalledName OBJECT-TYPE 1512 SYNTAX InternationalDisplayString (SIZE (0..64)) 1513 MAX-ACCESS read-only 1514 STATUS current 1515 DESCRIPTION 1516 "A textual description of this installed piece of 1517 software, including the manufacturer, revision, the 1518 name by which it is commonly known, and optionally, 1519 its serial number." 1520 ::= { hrSWInstalledEntry 2 } 1522 hrSWInstalledID OBJECT-TYPE 1523 SYNTAX ProductID 1524 MAX-ACCESS read-only 1525 STATUS current 1526 DESCRIPTION 1527 "The product ID of this installed piece of software." 1528 ::= { hrSWInstalledEntry 3 } 1530 hrSWInstalledType OBJECT-TYPE 1531 SYNTAX INTEGER { 1532 unknown(1), 1533 operatingSystem(2), 1534 deviceDriver(3), 1535 application(4) 1536 } 1537 MAX-ACCESS read-only 1538 STATUS current 1539 DESCRIPTION 1540 "The type of this software." 1541 ::= { hrSWInstalledEntry 4 } 1543 hrSWInstalledDate OBJECT-TYPE 1544 SYNTAX DateAndTime 1545 MAX-ACCESS read-only 1546 STATUS current 1547 DESCRIPTION 1548 "The last-modification date of this application as it 1549 would appear in a directory listing. 1551 If this information is not known, then this variable 1552 shall have the value corresponding to January 1, year 1553 0000, 00:00:00.0, which is encoded as 1554 (hex)'00 00 01 01 00 00 00 00'." 1555 ::= { hrSWInstalledEntry 5 } 1557 -- Conformance information 1559 hrMIBCompliances OBJECT IDENTIFIER ::= { hrMIBAdminInfo 2 } 1560 hrMIBGroups OBJECT IDENTIFIER ::= { hrMIBAdminInfo 3 } 1562 -- Compliance Statements 1563 hrMIBCompliance MODULE-COMPLIANCE 1564 STATUS current 1565 DESCRIPTION 1566 "The requirements for conformance to the Host Resources MIB." 1567 MODULE -- this module 1568 MANDATORY-GROUPS { hrSystemGroup, hrStorageGroup, hrDeviceGroup } 1570 OBJECT hrSystemDate 1571 MIN-ACCESS read-only 1572 DESCRIPTION 1573 "Write access is not required." 1575 OBJECT hrSystemInitialLoadDevice 1576 MIN-ACCESS read-only 1577 DESCRIPTION 1578 "Write access is not required." 1580 OBJECT hrSystemInitialLoadParameters 1581 MIN-ACCESS read-only 1582 DESCRIPTION 1583 "Write access is not required." 1585 OBJECT hrStorageSize 1586 MIN-ACCESS read-only 1587 DESCRIPTION 1588 "Write access is not required." 1590 OBJECT hrFSLastFullBackupDate 1591 MIN-ACCESS read-only 1592 DESCRIPTION 1593 "Write access is not required." 1595 OBJECT hrFSLastPartialBackupDate 1596 MIN-ACCESS read-only 1597 DESCRIPTION 1598 "Write access is not required." 1600 GROUP hrSWRunGroup 1601 DESCRIPTION 1602 "The Running Software Group. Implementation 1603 of this group is mandatory only when the 1604 hrSWRunPerfGroup is implemented." 1606 OBJECT hrSWRunStatus 1607 MIN-ACCESS read-only 1608 DESCRIPTION 1609 "Write access is not required." 1611 GROUP hrSWRunPerfGroup 1612 DESCRIPTION 1613 "The Running Software Performance Group. 1614 Implementation of this group is at the discretion 1615 of the implementor." 1617 GROUP hrSWInstalledGroup 1618 DESCRIPTION 1619 "The Installed Software Group. 1620 Implementation of this group is at the discretion 1621 of the implementor." 1623 ::= { hrMIBCompliances 1 } 1625 hrSystemGroup OBJECT-GROUP 1626 OBJECTS { 1627 hrSystemUptime, hrSystemDate, 1628 hrSystemInitialLoadDevice, 1629 hrSystemInitialLoadParameters, 1630 hrSystemNumUsers, hrSystemProcesses, 1631 hrSystemMaxProcesses 1632 } 1633 STATUS current 1634 DESCRIPTION 1635 "The Host Resources System Group." 1636 ::= { hrMIBGroups 1 } 1638 hrStorageGroup OBJECT-GROUP 1639 OBJECTS { 1640 hrMemorySize, hrStorageIndex, hrStorageType, 1641 hrStorageDescr, hrStorageAllocationUnits, 1642 hrStorageSize, hrStorageUsed, 1643 hrStorageAllocationFailures 1644 } 1645 STATUS current 1646 DESCRIPTION 1647 "The Host Resources Storage Group." 1648 ::= { hrMIBGroups 2 } 1650 hrDeviceGroup OBJECT-GROUP 1651 OBJECTS { 1652 hrDeviceIndex, hrDeviceType, hrDeviceDescr, 1653 hrDeviceID, hrDeviceStatus, hrDeviceErrors, 1654 hrProcessorFrwID, hrProcessorLoad, 1655 hrNetworkIfIndex, hrPrinterStatus, 1656 hrPrinterDetectedErrorState, 1657 hrDiskStorageAccess, hrDiskStorageMedia, 1658 hrDiskStorageRemoveble, hrDiskStorageCapacity, 1659 hrPartitionIndex, hrPartitionLabel, 1660 hrPartitionID, hrPartitionSize, 1661 hrPartitionFSIndex, hrFSIndex, hrFSMountPoint, 1662 hrFSRemoteMountPoint, hrFSType, hrFSAccess, 1663 hrFSBootable, hrFSStorageIndex, 1664 hrFSLastFullBackupDate, 1665 hrFSLastPartialBackupDate 1666 } 1667 STATUS current 1668 DESCRIPTION 1669 "The Host Resources Device Group." 1670 ::= { hrMIBGroups 3 } 1672 hrSWRunGroup OBJECT-GROUP 1673 OBJECTS { 1674 hrSWOSIndex, hrSWRunIndex, hrSWRunName, 1675 hrSWRunID, hrSWRunPath, hrSWRunParameters, 1676 hrSWRunType, hrSWRunStatus 1677 } 1678 STATUS current 1679 DESCRIPTION 1680 "The Host Resources Running Software Group." 1681 ::= { hrMIBGroups 4 } 1683 hrSWRunPerfGroup OBJECT-GROUP 1684 OBJECTS { hrSWRunPerfCPU, hrSWRunPerfMem } 1685 STATUS current 1686 DESCRIPTION 1687 "The Host Resources Running Software 1688 Performance Group." 1689 ::= { hrMIBGroups 5 } 1691 hrSWInstalledGroup OBJECT-GROUP 1692 OBJECTS { 1693 hrSWInstalledLastChange, 1694 hrSWInstalledLastUpdateTime, 1695 hrSWInstalledIndex, hrSWInstalledName, 1696 hrSWInstalledID, hrSWInstalledType, 1697 hrSWInstalledDate 1698 } 1699 STATUS current 1700 DESCRIPTION 1701 "The Host Resources Installed Software Group." 1702 ::= { hrMIBGroups 6 } 1704 END 1705 5. Type Definitions 1707 HOST-RESOURCES-TYPES DEFINITIONS ::= BEGIN 1709 IMPORTS 1710 MODULE-IDENTITY, OBJECT-IDENTITY FROM SNMPv2-SMI 1711 hrMIBAdminInfo, hrStorage, hrDevice FROM HOST-RESOURCES-MIB; 1713 hostResourcesTypesModule MODULE-IDENTITY 1714 LAST-UPDATED "9907312200Z" -- 31 July, 1999 1715 ORGANIZATION "IETF Host Resources MIB Working Group" 1716 CONTACT-INFO 1717 "Steve Waldbusser 1718 Postal: International Network Services (INS) 1719 1213 Innsbruck Dr. 1720 Sunnyvale, CA 94089 1721 USA 1722 Phone: 650-318-1251 1723 Fax: 650-318-1633 1724 Email: waldbusser@ins.com 1726 In addition, the Host Resources MIB mailing list is dedicated to 1727 discussion of this MIB. To join the mailing list, send a request 1728 message to hostmib-request@andrew.cmu.edu. The mailing list 1729 address is hostmib@andrew.cmu.edu." 1730 DESCRIPTION 1731 "This MIB module registers type definitions for 1732 storage types, device types, and file system types." 1733 REVISION "9907302200Z" -- 30 July, 1999 1734 DESCRIPTION 1735 "The original version of this module." 1736 ::= { hrMIBAdminInfo 4 } 1738 -- Registrations for some storage types, for use with hrStorageType 1739 hrStorageTypes OBJECT IDENTIFIER ::= { hrStorage 1 } 1741 hrStorageOther OBJECT-IDENTITY 1742 STATUS current 1743 DESCRIPTION 1744 "The storage type identifier used when no other defined 1745 type is appropriate." 1746 ::= { hrStorageTypes 1 } 1748 hrStorageRam OBJECT-IDENTITY 1749 STATUS current 1750 DESCRIPTION 1751 "The storage type identifier used for RAM." 1752 ::= { hrStorageTypes 2 } 1754 hrStorageVirtualMemory OBJECT-IDENTITY 1755 STATUS current 1756 DESCRIPTION 1757 "The storage type identifier used for virtual memory, 1758 temporary storage of swapped or paged memory." 1759 ::= { hrStorageTypes 3 } 1761 hrStorageFixedDisk OBJECT-IDENTITY 1762 STATUS current 1763 DESCRIPTION 1764 "The storage type identifier used for non-removable 1765 rigid rotating magnetic storage devices." 1766 ::= { hrStorageTypes 4 } 1768 hrStorageRemovableDisk OBJECT-IDENTITY 1769 STATUS current 1770 DESCRIPTION 1771 "The storage type identifier used for removable rigid 1772 rotating magnetic storage devices." 1773 ::= { hrStorageTypes 5 } 1775 hrStorageFloppyDisk OBJECT-IDENTITY 1776 STATUS current 1777 DESCRIPTION 1778 "The storage type identifier used for non-rigid rotating 1779 magnetic storage devices." 1780 ::= { hrStorageTypes 6 } 1782 hrStorageCompactDisc OBJECT-IDENTITY 1783 STATUS current 1784 DESCRIPTION 1785 "The storage type identifier used for read-only rotating 1786 optical storage devices." 1787 ::= { hrStorageTypes 7 } 1789 hrStorageRamDisk OBJECT-IDENTITY 1790 STATUS current 1791 DESCRIPTION 1792 "The storage type identifier used for a file system that 1793 is stored in RAM." 1794 ::= { hrStorageTypes 8 } 1796 hrStorageFlashMemory OBJECT-IDENTITY 1797 STATUS current 1798 DESCRIPTION 1799 "The storage type identifier used for flash memory." 1800 ::= { hrStorageTypes 9 } 1802 hrStorageNetworkDisk OBJECT-IDENTITY 1803 STATUS current 1804 DESCRIPTION 1805 "The storage type identifier used for a 1806 networked file system." 1807 ::= { hrStorageTypes 10 } 1809 -- Registrations for some device types, for use with hrDeviceType 1810 hrDeviceTypes OBJECT IDENTIFIER ::= { hrDevice 1 } 1812 hrDeviceOther OBJECT-IDENTITY 1813 STATUS current 1814 DESCRIPTION 1815 "The device type identifier used when no other defined 1816 type is appropriate." 1817 ::= { hrDeviceTypes 1 } 1819 hrDeviceUnknown OBJECT-IDENTITY 1820 STATUS current 1821 DESCRIPTION 1822 "The device type identifier used when the device type is 1823 unknown." 1824 ::= { hrDeviceTypes 2 } 1826 hrDeviceProcessor OBJECT-IDENTITY 1827 STATUS current 1828 DESCRIPTION 1829 "The device type identifier used for a CPU." 1830 ::= { hrDeviceTypes 3 } 1832 hrDeviceNetwork OBJECT-IDENTITY 1833 STATUS current 1834 DESCRIPTION 1835 "The device type identifier used for a network interface." 1836 ::= { hrDeviceTypes 4 } 1838 hrDevicePrinter OBJECT-IDENTITY 1839 STATUS current 1840 DESCRIPTION 1841 "The device type identifier used for a printer." 1842 ::= { hrDeviceTypes 5 } 1844 hrDeviceDiskStorage OBJECT-IDENTITY 1845 STATUS current 1846 DESCRIPTION 1847 "The device type identifier used for a disk drive." 1848 ::= { hrDeviceTypes 6 } 1850 hrDeviceVideo OBJECT-IDENTITY 1851 STATUS current 1852 DESCRIPTION 1853 "The device type identifier used for a video device." 1854 ::= { hrDeviceTypes 10 } 1856 hrDeviceAudio OBJECT-IDENTITY 1857 STATUS current 1858 DESCRIPTION 1859 "The device type identifier used for an audio device." 1860 ::= { hrDeviceTypes 11 } 1862 hrDeviceCoprocessor OBJECT-IDENTITY 1863 STATUS current 1864 DESCRIPTION 1865 "The device type identifier used for a co-processor." 1866 ::= { hrDeviceTypes 12 } 1868 hrDeviceKeyboard OBJECT-IDENTITY 1869 STATUS current 1870 DESCRIPTION 1871 "The device type identifier used for a keyboard device." 1872 ::= { hrDeviceTypes 13 } 1874 hrDeviceModem OBJECT-IDENTITY 1875 STATUS current 1876 DESCRIPTION 1877 "The device type identifier used for a modem." 1878 ::= { hrDeviceTypes 14 } 1880 hrDeviceParallelPort OBJECT-IDENTITY 1881 STATUS current 1882 DESCRIPTION 1883 "The device type identifier used for a parallel port." 1884 ::= { hrDeviceTypes 15 } 1886 hrDevicePointing OBJECT-IDENTITY 1887 STATUS current 1888 DESCRIPTION 1889 "The device type identifier used for a pointing device 1890 (e.g., a mouse)." 1891 ::= { hrDeviceTypes 16 } 1893 hrDeviceSerialPort OBJECT-IDENTITY 1894 STATUS current 1895 DESCRIPTION 1896 "The device type identifier used for a serial port." 1897 ::= { hrDeviceTypes 17 } 1899 hrDeviceTape OBJECT-IDENTITY 1900 STATUS current 1901 DESCRIPTION 1902 "The device type identifier used for a tape storage device." 1903 ::= { hrDeviceTypes 18 } 1905 hrDeviceClock OBJECT-IDENTITY 1906 STATUS current 1907 DESCRIPTION 1908 "The device type identifier used for a clock device." 1909 ::= { hrDeviceTypes 19 } 1911 hrDeviceVolatileMemory OBJECT-IDENTITY 1912 STATUS current 1913 DESCRIPTION 1914 "The device type identifier used for a volatile memory 1915 storage device." 1916 ::= { hrDeviceTypes 20 } 1918 hrDeviceNonVolatileMemory OBJECT-IDENTITY 1919 STATUS current 1920 DESCRIPTION 1921 "The device type identifier used for a non-volatile memory 1922 storage device." 1923 ::= { hrDeviceTypes 21 } 1925 -- Registrations for some popular File System types, 1926 -- for use with hrFSType. 1927 hrFSTypes OBJECT IDENTIFIER ::= { hrDevice 9 } 1929 hrFSOther OBJECT-IDENTITY 1930 STATUS current 1931 DESCRIPTION 1932 "The file system type identifier used when no other 1933 defined type is appropriate." 1934 ::= { hrFSTypes 1 } 1936 hrFSUnknown OBJECT-IDENTITY 1937 STATUS current 1938 DESCRIPTION 1939 "The file system type identifier used when the type of 1940 file system is unknown." 1941 ::= { hrFSTypes 2 } 1943 hrFSBerkeleyFFS OBJECT-IDENTITY 1944 STATUS current 1945 DESCRIPTION 1946 "The file system type identifier used for the 1947 Berkeley Fast File System." 1948 ::= { hrFSTypes 3 } 1950 hrFSSys5FS OBJECT-IDENTITY 1951 STATUS current 1952 DESCRIPTION 1953 "The file system type identifier used for the 1954 System V File System." 1955 ::= { hrFSTypes 4 } 1957 hrFSFat OBJECT-IDENTITY 1958 STATUS current 1959 DESCRIPTION 1960 "The file system type identifier used for 1961 DOS's FAT file system." 1962 ::= { hrFSTypes 5 } 1964 hrFSHPFS OBJECT-IDENTITY 1965 STATUS current 1966 DESCRIPTION 1967 "The file system type identifier used for OS/2's 1968 High Performance File System." 1969 ::= { hrFSTypes 6 } 1971 hrFSHFS OBJECT-IDENTITY 1972 STATUS current 1973 DESCRIPTION 1974 "The file system type identifier used for the 1975 Macintosh Hierarchical File System." 1977 ::= { hrFSTypes 7 } 1979 hrFSMFS OBJECT-IDENTITY 1980 STATUS current 1981 DESCRIPTION 1982 "The file system type identifier used for the 1983 Macintosh File System." 1984 ::= { hrFSTypes 8 } 1986 hrFSNTFS OBJECT-IDENTITY 1987 STATUS current 1988 DESCRIPTION 1989 "The file system type identifier used for the 1990 Windows NT File System." 1991 ::= { hrFSTypes 9 } 1993 hrFSVNode OBJECT-IDENTITY 1994 STATUS current 1995 DESCRIPTION 1996 "The file system type identifier used for the 1997 VNode File System." 1998 ::= { hrFSTypes 10 } 2000 hrFSJournaled OBJECT-IDENTITY 2001 STATUS current 2002 DESCRIPTION 2003 "The file system type identifier used for the 2004 Journaled File System." 2005 ::= { hrFSTypes 11 } 2007 hrFSiso9660 OBJECT-IDENTITY 2008 STATUS current 2009 DESCRIPTION 2010 "The file system type identifier used for the 2011 ISO 9660 File System for CD's." 2012 ::= { hrFSTypes 12 } 2014 hrFSRockRidge OBJECT-IDENTITY 2015 STATUS current 2016 DESCRIPTION 2017 "The file system type identifier used for the 2018 RockRidge File System for CD's." 2019 ::= { hrFSTypes 13 } 2021 hrFSNFS OBJECT-IDENTITY 2022 STATUS current 2023 DESCRIPTION 2024 "The file system type identifier used for the 2025 NFS File System." 2026 ::= { hrFSTypes 14 } 2028 hrFSNetware OBJECT-IDENTITY 2029 STATUS current 2030 DESCRIPTION 2031 "The file system type identifier used for the 2032 Netware File System." 2033 ::= { hrFSTypes 15 } 2035 hrFSAFS OBJECT-IDENTITY 2036 STATUS current 2037 DESCRIPTION 2038 "The file system type identifier used for the 2039 Andrew File System." 2040 ::= { hrFSTypes 16 } 2042 hrFSDFS OBJECT-IDENTITY 2043 STATUS current 2044 DESCRIPTION 2045 "The file system type identifier used for the 2046 OSF DCE Distributed File System." 2047 ::= { hrFSTypes 17 } 2049 hrFSAppleshare OBJECT-IDENTITY 2050 STATUS current 2051 DESCRIPTION 2052 "The file system type identifier used for the 2053 AppleShare File System." 2054 ::= { hrFSTypes 18 } 2056 hrFSRFS OBJECT-IDENTITY 2057 STATUS current 2058 DESCRIPTION 2059 "The file system type identifier used for the 2060 RFS File System." 2061 ::= { hrFSTypes 19 } 2063 hrFSDGCFS OBJECT-IDENTITY 2064 STATUS current 2065 DESCRIPTION 2066 "The file system type identifier used for the 2067 Data General DGCFS." 2068 ::= { hrFSTypes 20 } 2070 hrFSBFS OBJECT-IDENTITY 2071 STATUS current 2072 DESCRIPTION 2073 "The file system type identifier used for the 2074 SVR4 Boot File System." 2075 ::= { hrFSTypes 21 } 2077 hrFSFAT32 OBJECT-IDENTITY 2078 STATUS current 2079 DESCRIPTION 2080 "The file system type identifier used for the 2081 Windows FAT32 File System." 2082 ::= { hrFSTypes 22 } 2084 hrFSLinuxExt2 OBJECT-IDENTITY 2085 STATUS current 2086 DESCRIPTION 2087 "The file system type identifier used for the 2088 Linux EXT2 File System." 2089 ::= { hrFSTypes 23 } 2091 END 2092 6. Security Considerations 2094 There are a number of management objects defined in this MIB 2095 that have a MAX-ACCESS clause of read-write. Such objects may 2096 be considered sensitive or vulnerable in some network 2097 environments. The support for SET operations in a non-secure 2098 environment without proper protection can have a negative 2099 effect on system operations. 2101 There are a number of managed objects in this MIB that may 2102 contain sensitive information. The objects in the Running 2103 Software Group list information about running software on the 2104 system (including the operating system software and version). 2105 Some may wish not to disclose to others what software they are 2106 running. Further, an inventory of the running software and 2107 versions may be helpful to an attacker who hopes to exploit 2108 software bugs in certain applications. The same issues exist 2109 for the objects in the Installed Software Group. 2111 It is thus important to control even GET access to these 2112 objects and possibly to even encrypt the values of these 2113 object when sending them over the network via SNMP. Not all 2114 versions of SNMP provide features for such a secure 2115 environment. 2117 SNMPv1 by itself is not a secure environment. Even if the 2118 network itself is secure (for example by using IPSec), even 2119 then, there is no control as to who on the secure network is 2120 allowed to access and GET/SET (read/change/create/delete) the 2121 objects in this MIB. 2123 It is recommended that the implementers consider the security 2124 features as provided by the SNMPv3 framework. Specifically, 2125 the use of the User-based Security Model RFC 2574 [RFC2574] 2126 and the View-based Access Control Model RFC 2575 [RFC2575] is 2127 recommended. 2129 It is then a customer/user responsibility to ensure that the 2130 SNMP entity giving access to an instance of this MIB, is 2131 properly configured to give access to the objects only to 2132 those principals (users) that have legitimate rights to indeed 2133 GET or SET (change/create/delete) them. 2135 7. References 2137 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 2138 Architecture for Describing SNMP Management 2139 Frameworks", RFC 2571, April 1999 2141 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 2142 Identification of Management Information for 2143 TCP/IP-based Internets", STD 16, RFC 1155, May 2144 1990 2146 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB 2147 Definitions", STD 16, RFC 1212, March 1991 2149 [RFC1215] M. Rose, "A Convention for Defining Traps for use 2150 with the SNMP", RFC 1215, March 1991 2152 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2153 Case, J., Rose, M., and S. Waldbusser, "Structure 2154 of Management Information Version 2 (SMIv2)", STD 2155 58, RFC 2578, April 1999 2157 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2158 Case, J., Rose, M., and S. Waldbusser, "Textual 2159 Conventions for SMIv2", STD 58, RFC 2579, April 2160 1999 2162 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2163 Case, J., Rose, M., and S. Waldbusser, 2164 "Conformance Statements for SMIv2", STD 58, RFC 2165 2580, April 1999 2167 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. 2168 Davin, "Simple Network Management Protocol", STD 2169 15, RFC 1157, May 1990. 2171 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. 2172 Waldbusser, "Introduction to Community-based 2173 SNMPv2", RFC 1901, January 1996. 2175 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. 2176 Waldbusser, "Transport Mappings for Version 2 of 2177 the Simple Network Management Protocol (SNMPv2)", 2178 RFC 1906, January 1996. 2180 [RFC2572] Case, J., Harrington D., Presuhn R., and B. 2181 Wijnen, "Message Processing and Dispatching for 2182 the Simple Network Management Protocol (SNMP)", 2183 RFC 2572, April 1999 2185 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based 2186 Security Model (USM) for version 3 of the Simple 2187 Network Management Protocol (SNMPv3)", RFC 2574, 2188 April 1999 2190 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 2191 Waldbusser, "Protocol Operations for Version 2 of 2192 the Simple Network Management Protocol (SNMPv2)", 2193 RFC 1905, January 1996. 2195 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2196 Applications", RFC 2573, April 1999 2198 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 2199 based Access Control Model (VACM) for the Simple 2200 Network Management Protocol (SNMP)", RFC 2575, 2201 April 1999 2203 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2204 "Introduction to Version 3 of the Internet- 2205 standard Network Management Framework", RFC 2570, 2206 April 1999 2208 [RFC1907] Case, J., McCloghrie, K., Rose, M., and S. 2209 Waldbusser, "Management Information Base for 2210 Version 2 of the Simple Network Management 2211 Protocol (SNMPv2)", RFC 1907, SNMP Research, Inc., 2212 Cisco Systems, Inc., Dover Beach Consulting, Inc., 2213 International Network Services, January 1996. 2215 [RFC2233] McCloghrie, K. and F. Kastenholz, "The Interfaces 2216 Group MIB", RFC 2233, November 1997. 2218 [RFC2119] Bradner, S., "Key words for use in RFCs to 2219 Indicate Requirement Levels", BCP 14, RFC 2119, 2220 March 1997. 2222 8. Acknowledgments 2224 This document was produced by the Host Resources MIB working 2225 group. 2227 Bobby Krupczak's efforts were particularly helpful in the 2228 creation of the draft standard version of this document. 2230 In addition, the authors gratefully acknowledge the comments 2231 of the following individuals: 2233 Amatzia Ben-Artzi NetManage 2234 Steve Bostock Novell 2235 Stephen Bush GE Information Systems 2236 Jeff Case SNMP Research 2237 Chuck Davin Bellcore 2238 Ray Edgarton Bell Atlantic 2239 Mike Erlinger Aerospace Corporation 2240 Tim Farley Magee Enterprises 2241 Mark Kepke Hewlett Packard 2242 Bobby Krupczak Georgia Tech 2243 Cheryl Krupczak Georgia Tech 2244 Keith McCloghrie Hughes Lan Systems 2245 Greg Minshall Novell 2246 Steve Moulton SNMP Research 2247 Dave Perkins Synoptics 2248 Ed Reeder Objective Systems Integrators 2249 Mike Ritter Apple Computer 2250 Marshall Rose Dover Beach Consulting 2251 Jon Saperia DEC 2252 Rodney Thayer Sable Technology 2253 Kaj Tesink Bellcore 2254 Dean Throop Data General 2255 Bert Wijnen IBM 2257 9. Authors' Address 2259 Pete Grillo 2260 Phone: +1 503 827 6717 2261 Email: pete@plusfactor.com 2263 Steven Waldbusser 2264 International Network Services (INS) 2265 1213 Innsbruck Dr. 2267 Sunnyvale CA 94089 2269 Phone: +1 650 318 1251 2270 Fax: +1 650 318 1633 2272 Email: waldbusser@ins.como 2274 10. Intellectual Property 2276 The IETF takes no position regarding the validity or scope of 2277 any intellectual property or other rights that might be 2278 claimed to pertain to the implementation or use of the 2279 technology described in this document or the extent to which 2280 any license under such rights might or might not be available; 2281 neither does it represent that it has made any effort to 2282 identify any such rights. Information on the IETF's 2283 procedures with respect to rights in standards-track and 2284 standards-related documentation can be found in BCP-11. 2285 Copies of claims of rights made available for publication and 2286 any assurances of licenses to be made available, or the result 2287 of an attempt made to obtain a general license or permission 2288 for the use of such proprietary rights by implementors or 2289 users of this specification can be obtained from the IETF 2290 Secretariat. 2292 The IETF invites any interested party to bring to its 2293 attention any copyrights, patents or patent applications, or 2294 other proprietary rights which may cover technology that may 2295 be required to practice this standard. Please address the 2296 information to the IETF Executive Director. 2298 11. Copyright Statement 2300 Copyright (C) The Internet Society (1999). All Rights 2301 Reserved. 2303 This document and translations of it may be copied and 2304 furnished to others, and derivative works that comment on or 2305 otherwise explain it or assist in its implementation may be 2306 prepared, copied, published and distributed, in whole or in 2307 part, without restriction of any kind, provided that the above 2308 copyright notice and this paragraph are included on all such 2309 copies and derivative works. However, this document itself 2310 may not be modified in any way, such as by removing the 2311 copyright notice or references to the Internet Society or 2312 other Internet organizations, except as needed for the purpose 2313 of developing Internet standards in which case the procedures 2314 for copyrights defined in the Internet Standards process must 2315 be followed, or as required to translate it into languages 2316 other than English. 2318 The limited permissions granted above are perpetual and will 2319 not be revoked by the Internet Society or its successors or 2320 assigns. 2322 This document and the information contained herein is provided 2323 on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 2324 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 2325 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE 2326 USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 2327 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 2328 PARTICULAR PURPOSE. 2330 Table of Contents 2332 1 The SNMP Management Framework ......................... 3 2333 2 Host Resources MIB .................................... 5 2334 3 IANA Considerations ................................... 5 2335 4 Definitions ........................................... 6 2336 5.1 Textual Conventions ................................. 9 2337 5.2 The Host Resources System Group ..................... 11 2338 5.3 The Host Resources Storage Group .................... 13 2339 5.4 The Host Resources Device Group ..................... 18 2340 5.5 The Host Resources Running Software Group ........... 37 2341 5.6 The Host Resources Running Software Performance 2342 Group .............................................. 41 2343 5.7 The Host Resources Installed Software Group ......... 43 2344 5.8 Conformance Definitions ............................. 46 2345 5 Type Definitions ...................................... 50 2346 6 Security Considerations ............................... 59 2347 7 References ............................................ 60 2348 8 Acknowledgments ....................................... 62 2349 9 Authors' Address ...................................... 62 2350 10 Intellectual Property ................................ 63 2351 11 Copyright Statement .................................. 63