idnits 2.17.1 draft-ietf-hostmib-resources-01.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-27) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** 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 Abstract section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2. Abstract' ) ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** There are 55 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** The abstract seems to contain references ([2], [3], [4], [5], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 103 has weird spacing: '...mputers are...' == Line 165 has weird spacing: '... field octet...' == 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 739385 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) -- Missing reference section? '1' on line 1443 looks like a reference -- Missing reference section? '2' on line 1447 looks like a reference -- Missing reference section? '3' on line 1450 looks like a reference -- Missing reference section? '4' on line 1454 looks like a reference -- Missing reference section? '5' on line 1458 looks like a reference Summary: 16 errors (**), 0 flaws (~~), 4 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET DRAFT Host Resources MIB May 93 4 Host Resources MIB 6 Sat May 8 02:07:46 EDT 1993 8 Pete Grillo 9 Network Innovations 10 Intel Corporation 11 pl0143@mail.psi.net 13 Steven Waldbusser 14 Carnegie Mellon University 15 waldbusser@cmu.edu 17 1. Status of this Memo 19 This memo provides information for the Internet community. It 20 does not specify any standard. Distribution of this memo is 21 unlimited. Please send comments to the authors. 23 This document is an Internet Draft. Internet Drafts are 24 working documents of the Internet Engineering Task Force 25 (IETF), its Areas, and its Working Groups. Note that other 26 groups may also distribute working documents as Internet 27 Drafts. 29 Internet Drafts are draft documents valid for a maximum of six 30 months. Internet Drafts may be updated, replaced, or 31 obsoleted by other documents at any time. It is not 32 appropriate to use Internet Drafts as reference material or to 33 cite them other than as a ``working draft'' or ``work in 34 progress.'' Please check the 1id-abstracts.txt listing 35 contained in the internet-drafts Shadow Directories on 36 nic.ddn.mil, nnsc.nsf.net, nic.nordu.net, ftp.nisc.sri.com, or 37 munnari.oz.au to learn the current status of any Internet 38 Draft. 40 2. Abstract 42 This memo defines a MIB for use with managing host systems. 43 The term "host" is construed to mean any computer that 44 communicates with other similar computers attached to the 45 internet and that is directly used by one or more human 46 beings. Although this MIB does not necessarily apply to 47 devices whose primary function is communications services 48 (e.g., terminal servers, routers, bridges, monitoring 49 equipment), such relevance is not explicitly precluded. This 50 MIB instruments attributes common to all internet hosts 51 including, for example, both personal computers and systems 52 that run variants of Unix. 54 3. The Network Management Framework 56 The Internet-standard Network Management Framework consists of 57 three components. They are: 59 RFC 1155[1] which defines the SMI, the mechanisms used for 60 describing and naming objects for the purpose of management. 61 RFC 1212[2] defines a more concise description mechanism, 62 which is wholly consistent with the SMI. 64 RFC 1213[3] which defines MIB-II, the core set of managed 65 objects for the Internet suite of protocols. 67 RFC 1157[4] which defines the SNMP, the protocol used for 68 network access to managed objects. 70 The Framework permits new objects to be defined for the 71 purpose of experimentation and evaluation. 73 Managed objects are accessed via a virtual information store, 74 termed the Management Information Base or MIB. Within a given 75 MIB module, objects are defined using RFC 1212's OBJECT-TYPE 76 macro. At a minimum, each object has a name, a syntax, an 77 access-level, and an implementation-status. 79 The name is an object identifier, an administratively assigned 80 name, which specifies an object type. The object type 81 together with an object instance serves to uniquely identify a 82 specific instantiation of the object. For human convenience, 83 we often use a textual string, termed the object descriptor, 84 to also refer to the object type. 86 The syntax of an object type defines the abstract data 87 structure corresponding to that object type. The ASN.1[5] 88 language is used for this purpose. However, RFC 1155 89 purposely restricts the ASN.1 constructs which may be used. 90 These restrictions are explicitly made for simplicity. 92 The access-level of an object type defines whether it makes 93 "protocol sense" to read and/or write the value of an instance 94 of the object type. (This access-level is independent of any 95 administrative authorization policy.) 97 The implementation-status of an object type indicates whether 98 the object is mandatory, optional, obsolete, or deprecated. 100 4. Host Resources MIB 102 The Host Resources MIB defines a uniform set of objects useful 103 for the management of host computers. Host computers are 104 independent of the operating system, network services, or any 105 software application. 107 The Host Resources MIB defines objects which are common across 108 many computer system architectures. 110 In addition, there are objects in MIB-2 [3] which also provide 111 host management functionality: sysDescr, sysObjectID, 112 sysUpTime, sysContact, sysLocation, and sysServices. 113 Implementation of these objects is mandatory for implementors 114 of the Host Resources MIB. 116 Implementation of the Host Resources MIB also requires 117 implementation of the interfaces group of MIB-2. 119 5. Definitions 121 RFC-Host-Resources-MIB DEFINITIONS ::= BEGIN 123 IMPORTS 124 OBJECT-TYPE FROM RFC-1212 125 DisplayString FROM RFC1213-MIB 126 experimental, TimeTicks, 127 Counter FROM RFC1155-SMI; 129 host OBJECT IDENTIFIER ::= { experimental 36 } 131 hrSystem OBJECT IDENTIFIER ::= { host 1 } 132 hrStorage OBJECT IDENTIFIER ::= { host 2 } 133 hrDevice OBJECT IDENTIFIER ::= { host 3 } 134 hrSWRun OBJECT IDENTIFIER ::= { host 4 } 135 hrSWRunPerf OBJECT IDENTIFIER ::= { host 5 } 136 hrSWInstalled OBJECT IDENTIFIER ::= { host 6 } 137 -- textual conventions 139 -- a truth value 140 Boolean ::= INTEGER { true(1), false(2) } 142 -- memory size, expressed in units of 1024bytes 143 KBytes ::= INTEGER (0..2147483647) 145 -- This textual convention is intended to identify the manufacturer, 146 -- model, and version of a specific hardware or software product. 147 -- It is suggested that these OBJECT IDENTIFIERs are allocated such 148 -- that all products from a particular manufacturer are registered 149 -- under a subtree distinct to that manufacturer. In addition, all 150 -- versions of a product should be registered under a subtree 151 -- distinct to that product. With this strategy, a management 152 -- station may uniquely determine the manufacturer and/or model of a 153 -- product whose productID is unknown to the management station. 154 -- Objects of this type may be useful for inventory purposes or for 155 -- automatically detecting incompatibilities or version mismatches 156 -- between various hardware and software components on a system. 157 ProductID ::= OBJECT IDENTIFIER 158 -- unknownProduct will be used for any unknown ProductID 159 unknownProduct OBJECT IDENTIFIER ::= { 0 0 } 160 DateAndTime ::= OCTET STRING (SIZE (8 | 11)) 161 -- A date-time specification for the local time of day. 162 -- This data type is intended to provide a consistent 163 -- method of reporting date information. 164 -- 165 -- field octets contents range 166 -- _____ ______ ________ _____ 167 -- 1 1-2 year 0..65536 168 -- (in network byte order) 169 -- 2 3 month 1..12 170 -- 3 4 day 1..31 171 -- 4 5 hour 0..23 172 -- 5 6 minutes 0..59 173 -- 6 7 seconds 0..60 174 -- (use 60 for leap-second) 175 -- 7 8 deci-seconds 0..9 176 -- 8 9 direction from UTC "+" / "-" 177 -- (in ascii notation) 178 -- 9 10 hours from UTC 0..11 179 -- 10 11 minutes from UTC 0..59 180 -- 181 -- Note that if only local time is known, then 182 -- timezone information (fields 8-10) is not present. 184 Characters ::= OCTET STRING 185 -- This data type is used to model textual information in some 186 -- character set. A network management station should use a local 187 -- algorithm to determine which character set is in use and how it 188 -- should be displayed. Note that this character set may be encoded 189 -- with more than one octet per symbol, but will most often be NVT 190 -- ASCII. 192 -- The Host Resources System Group 193 -- 194 -- Implementation of this group is mandatory for all host systems. 195 hrSystemUptime OBJECT-TYPE 196 SYNTAX TimeTicks 197 ACCESS read-only 198 STATUS mandatory 199 DESCRIPTION 200 "The amount of time since this host was last 201 initialized. Note that this is different from 202 sysUpTime in MIB-2 [3] because sysUpTime is the 203 uptime of the network management portion of the 204 system." 205 ::= { hrSystem 1 } 207 hrSystemDate OBJECT-TYPE 208 SYNTAX DateAndTime 209 ACCESS read-write 210 STATUS mandatory 211 DESCRIPTION 212 "The host's notion of the local date and time of 213 day." 214 ::= { hrSystem 2 } 216 hrSystemInitialLoadDevice OBJECT-TYPE 217 SYNTAX INTEGER (1..2147483647) 218 ACCESS read-write 219 STATUS mandatory 220 DESCRIPTION 221 "The index of the hrDeviceEntry for the device from 222 which this host is configured to load its initial 223 operating system configuration." 224 ::= { hrSystem 3 } 226 hrSystemInitialLoadParameter OBJECT-TYPE 227 SYNTAX Characters (SIZE (0..128)) 228 ACCESS read-write 229 STATUS mandatory 230 DESCRIPTION 231 "This object contains the parameter (e.g. a 232 pathname and parameter) supplied to the load device 233 when requesting the initial operating system 234 configuration from that device." 235 ::= { hrSystem 4 } 237 hrSystemNumUsers OBJECT-TYPE 238 SYNTAX INTEGER 239 ACCESS read-only 240 STATUS mandatory 241 DESCRIPTION 242 "The number of user sessions for which this host is 243 storing state information." 244 ::= { hrSystem 5 } 246 hrSystemProcesses OBJECT-TYPE 247 SYNTAX INTEGER 248 ACCESS read-only 249 STATUS mandatory 250 DESCRIPTION 251 "The number of process contexts currently loaded or 252 running on this system." 253 ::= { hrSystem 6 } 255 hrSystemMaxProcesses OBJECT-TYPE 256 SYNTAX INTEGER (0..2147483647) 257 ACCESS read-only 258 STATUS mandatory 259 DESCRIPTION 260 "The maximum number of process contexts this system 261 can support. If there is no fixed maximum, the 262 value should be zero. On systems that have a fixed 263 maximum, this object can help diagnose failures 264 that occur when this maximum is reached." 265 ::= { hrSystem 7 } 267 -- The Host Resources Storage Group 268 -- 269 -- Implementation of this group is mandatory for all host systems. 271 -- The following assignments define different storage types. 272 hrStorageTypes OBJECT IDENTIFIER ::= { hrStorage 1 } 273 hrStorageOther OBJECT IDENTIFIER ::= { hrStorageTypes 1 } 274 hrStorageRam OBJECT IDENTIFIER ::= { hrStorageTypes 2 } 275 -- hrStorageVirtualMemory is temporary storage of swapped 276 -- or paged memory 277 hrStorageVirtualMemory OBJECT IDENTIFIER ::= { hrStorageTypes 3 } 278 hrStorageFixedDisk OBJECT IDENTIFIER ::= { hrStorageTypes 4 } 279 hrStorageRemovableDisk OBJECT IDENTIFIER ::= { hrStorageTypes 5 } 280 hrStorageFloppyDisk OBJECT IDENTIFIER ::= { hrStorageTypes 6 } 281 hrStorageCompactDisc OBJECT IDENTIFIER ::= { hrStorageTypes 7 } 282 hrStorageRamDisk OBJECT IDENTIFIER ::= { hrStorageTypes 8 } 284 hrMemorySize OBJECT-TYPE 285 SYNTAX KBytes 286 ACCESS read-only 287 STATUS mandatory 288 DESCRIPTION 289 "The amount of physical main memory contained by 290 the host." 291 ::= { hrStorage 2 } 293 hrStorageTable OBJECT-TYPE 294 SYNTAX SEQUENCE OF HrStorageEntry 295 ACCESS not-accessible 296 STATUS mandatory 297 DESCRIPTION 298 "The (conceptual) table of logical storage areas on 299 the host. 301 An entry shall be placed in the storage table for 302 each logical area of storage that is allocated and 303 has fixed resource limits. The amount of storage 304 represented in an entity is the amount actually 305 usable by the requesting entity, and excludes loss 306 due to formatting or file system reference 307 information. 309 These entries are associated with logical storage 310 areas, as might be seen by an application, rather 311 than physical storage entities which are typically 312 seen by an operating system. Storage such as tapes 313 and floppies without file systems on them are 314 typically not allocated in chunks by the operating 315 system to requesting applications, and therefore 316 shouldn't appear in this table. Examples of valid 317 storage for this table include disk partitions, 318 file systems, ram (for some architectures this is 319 further segmented into regular memory, extended 320 memory, and so on), backing store for virtual 321 memory (`swap space'). 323 This table is intended to be a useful diagnostic 324 for `out of memory' and `out of buffers' types of 325 failures. In addition, it can be a useful 326 performance monitoring tool for tracking memory, 327 disk, or buffer usage." 328 ::= { hrStorage 3 } 330 hrStorageEntry OBJECT-TYPE 331 SYNTAX HrStorageEntry 332 ACCESS not-accessible 333 STATUS mandatory 334 DESCRIPTION 335 "A (conceptual) entry for one logical storage area 336 on the host." 337 INDEX { hrStorageIndex } 338 ::= { hrStorageTable 1 } 340 -- As an example, an instance of the hrStorageType object 341 -- might be named hrStorageType.3 343 HrStorageEntry ::= SEQUENCE { 344 hrStorageIndex INTEGER, 345 hrStorageType OBJECT IDENTIFIER, 346 hrStorageDescr DisplayString, 347 hrStorageAllocationUnits INTEGER, 348 hrStorageSize INTEGER, 349 hrStorageUsed INTEGER, 350 hrStorageAllocationFailures Counter 351 } 353 hrStorageIndex OBJECT-TYPE 354 SYNTAX INTEGER (1..2147483647) 355 ACCESS read-only 356 STATUS mandatory 357 DESCRIPTION 358 "A unique value for each logical storage area 359 contained by the host." 360 ::= { hrStorageEntry 1 } 362 hrStorageType OBJECT-TYPE 363 SYNTAX OBJECT IDENTIFIER 364 ACCESS read-only 365 STATUS mandatory 366 DESCRIPTION 367 "The type of storage represented by this entry." 368 ::= { hrStorageEntry 2 } 370 hrStorageDescr OBJECT-TYPE 371 SYNTAX DisplayString 372 ACCESS read-only 373 STATUS mandatory 374 DESCRIPTION 375 "A description of the type and instance of the 376 storage described by this entry." 377 ::= { hrStorageEntry 3 } 379 hrStorageAllocationUnits OBJECT-TYPE 380 SYNTAX INTEGER (0..2147483647) 381 ACCESS read-only 382 STATUS mandatory 383 DESCRIPTION 384 "The size, in bytes, of the data objects allocated 385 from this pool. If this entry is monitoring 386 sectors, blocks, buffers, or packets, for example, 387 this number will commonly be greater than one. 388 Otherwise this number will typically be one." 389 ::= { hrStorageEntry 4 } 391 hrStorageSize OBJECT-TYPE 392 SYNTAX INTEGER (0..2147483647) 393 ACCESS read-write 394 STATUS mandatory 395 DESCRIPTION 396 "The size of the storage represented by this entry, 397 in units of hrStorageAllocationUnits." 398 ::= { hrStorageEntry 5 } 400 hrStorageUsed OBJECT-TYPE 401 SYNTAX INTEGER (0..2147483647) 402 ACCESS read-only 403 STATUS mandatory 404 DESCRIPTION 405 "The amount of the storage represented by this 406 entry that is allocated, in units of 407 hrStorageAllocationUnits." 408 ::= { hrStorageEntry 6 } 410 hrStorageAllocationFailures OBJECT-TYPE 411 SYNTAX Counter 412 ACCESS read-only 413 STATUS mandatory 414 DESCRIPTION 415 "The number of requests for storage represented by 416 this entry that could not be honored due to not 417 enough storage. It should be noted that as this 418 object has a SYNTAX of Counter, that it does not 419 have a defined initial value. However, it is 420 recommended that this object be initialized to 421 zero." 422 ::= { hrStorageEntry 7 } 424 -- The Host Resources Device Group 425 -- 426 -- Implementation of this group is mandatory for all host systems. 427 -- 428 -- The device group is useful for identifying and diagnosing the 429 -- devices on a system. The hrDeviceTable contains common 430 -- information for any type of device. In addition, some devices 431 -- have device-specific tables for more detailed information. More 432 -- such tables may be defined in the future for other device types. 434 hrDeviceTypes OBJECT IDENTIFIER ::= { hrDevice 1 } 436 hrDeviceOther OBJECT IDENTIFIER ::= { hrDeviceTypes 1 } 437 hrDeviceUnknown OBJECT IDENTIFIER ::= { hrDeviceTypes 2 } 438 hrDeviceProcessor OBJECT IDENTIFIER ::= { hrDeviceTypes 3 } 439 hrDeviceNetwork OBJECT IDENTIFIER ::= { hrDeviceTypes 4 } 440 hrDevicePrinter OBJECT IDENTIFIER ::= { hrDeviceTypes 5 } 441 hrDeviceDiskStorage OBJECT IDENTIFIER ::= { hrDeviceTypes 6 } 442 hrDeviceVideo OBJECT IDENTIFIER ::= { hrDeviceTypes 10 } 443 hrDeviceAudio OBJECT IDENTIFIER ::= { hrDeviceTypes 11 } 444 hrDeviceCoprocessor OBJECT IDENTIFIER ::= { hrDeviceTypes 12 } 445 hrDeviceKeyboard OBJECT IDENTIFIER ::= { hrDeviceTypes 13 } 446 hrDeviceModem OBJECT IDENTIFIER ::= { hrDeviceTypes 14 } 447 hrDeviceParallelPort OBJECT IDENTIFIER ::= { hrDeviceTypes 15 } 448 hrDevicePointing OBJECT IDENTIFIER ::= { hrDeviceTypes 16 } 449 hrDeviceSerialPort OBJECT IDENTIFIER ::= { hrDeviceTypes 17 } 450 hrDeviceTape OBJECT IDENTIFIER ::= { hrDeviceTypes 18 } 451 hrDeviceClock OBJECT IDENTIFIER ::= { hrDeviceTypes 19 } 452 hrDeviceTable OBJECT-TYPE 453 SYNTAX SEQUENCE OF HrDeviceEntry 454 ACCESS not-accessible 455 STATUS mandatory 456 DESCRIPTION 457 "The (conceptual) table of devices contained by the 458 host." 459 ::= { hrDevice 2 } 461 hrDeviceEntry OBJECT-TYPE 462 SYNTAX HrDeviceEntry 463 ACCESS not-accessible 464 STATUS mandatory 465 DESCRIPTION 466 "A (conceptual) entry for one device contained by 467 the host." 468 INDEX { hrDeviceIndex } 469 ::= { hrDeviceTable 1 } 471 -- As an example, an instance of the hrDeviceType object 472 -- might be named hrDeviceType.3 474 HrDeviceEntry ::= SEQUENCE { 475 hrDeviceIndex INTEGER, 476 hrDeviceType OBJECT IDENTIFIER, 477 hrDeviceDescr DisplayString, 478 hrDeviceID ProductID, 479 hrDeviceStatus INTEGER, 480 hrDeviceErrors Counter 481 } 483 hrDeviceIndex OBJECT-TYPE 484 SYNTAX INTEGER (1..2147483647) 485 ACCESS read-only 486 STATUS mandatory 487 DESCRIPTION 488 "A unique value for each device contained by the 489 host. The value for each device must remain 490 constant at least from one re-initialization of the 491 agent to the next re-initialization." 492 ::= { hrDeviceEntry 1 } 494 hrDeviceType OBJECT-TYPE 495 SYNTAX OBJECT IDENTIFIER 496 ACCESS read-only 497 STATUS mandatory 498 DESCRIPTION 499 "An indication of the type of device. 501 If `hrDeviceProcessor { hrDeviceTypes 3 }' then an 502 entry exists in the hrProcessorTable which 503 corresponds to this device. 505 If `hrDeviceNetwork { hrDeviceTypes 4 }', then an 506 entry exists in the hrNetworkTable which 507 corresponds to this device. 509 If `hrDevicePrinter { hrDeviceTypes 5 }', then an 510 entry exists in the hrPrinterTable which 511 corresponds to this device. 513 If `hrDeviceDiskStorage { hrDeviceTypes 6 }', then 514 an entry exists in the hrDiskStorageTable which 515 corresponds to this device." 516 ::= { hrDeviceEntry 2 } 518 hrDeviceDescr OBJECT-TYPE 519 SYNTAX DisplayString (SIZE (0..64)) 520 ACCESS read-only 521 STATUS mandatory 522 DESCRIPTION 523 "A textual description of this device, including 524 the device's manufacturer and revision, and 525 optionally, its serial number." 526 ::= { hrDeviceEntry 3 } 528 hrDeviceID OBJECT-TYPE 529 SYNTAX ProductID 530 ACCESS read-only 531 STATUS mandatory 532 DESCRIPTION 533 "The product ID for this device." 534 ::= { hrDeviceEntry 4 } 536 hrDeviceStatus OBJECT-TYPE 537 SYNTAX INTEGER { 538 unknown(1), 539 running(2), 540 warning(3), 541 testing(4), 542 down(5) 543 } 544 ACCESS read-only 545 STATUS mandatory 546 DESCRIPTION 547 "The current operational state of the device 548 described by this row of the table. A value 1 549 indicates that the current state of the device is 550 unknown. 2 indicates that the device is up and 551 running and that no unusual error conditions are 552 known. A warning state 3, indicates that agent has 553 been informed of an unusual error condition by the 554 operational software (e.g., a disk device driver) 555 but that the device is still 'operational'. An 556 example would be high number of soft errors on a 557 disk. A value of 4, indicates that the device is 558 not available for use because it is in the testing 559 state. The state of 5 is used only when the agent 560 has been informed that the device is not available 561 for any use." 562 ::= { hrDeviceEntry 5 } 564 hrDeviceErrors OBJECT-TYPE 565 SYNTAX Counter 566 ACCESS read-only 567 STATUS mandatory 568 DESCRIPTION 569 "The number of errors detected on this device. It 570 should be noted that as this object has a SYNTAX 571 of Counter, that it does not have a defined 572 initial value. However, it is recommended that 573 this object be initialized to zero." 574 ::= { hrDeviceEntry 6 } 576 hrProcessorTable OBJECT-TYPE 577 SYNTAX SEQUENCE OF HrProcessorEntry 578 ACCESS not-accessible 579 STATUS mandatory 580 DESCRIPTION 581 "The (conceptual) table of processors contained by 582 the host. 584 Note that this table is potentially sparse: a 585 (conceptual) entry exists only if the correspondent 586 value of the hrDeviceType object is 587 `hrDeviceProcessor'." 588 ::= { hrDevice 3 } 590 hrProcessorEntry OBJECT-TYPE 591 SYNTAX HrProcessorEntry 592 ACCESS not-accessible 593 STATUS mandatory 594 DESCRIPTION 595 "A (conceptual) entry for one processor contained 596 by the host. The hrDeviceIndex in the index 597 represents the entry in the hrDeviceTable that 598 corresponds to the hrProcessorEntry." 599 INDEX { hrDeviceIndex } 600 ::= { hrProcessorTable 1 } 602 -- As an example, an instance of the hrProcessorFrwID object 603 -- might be named hrProcessorFrwID.3 604 HrProcessorEntry ::= SEQUENCE { 605 hrProcessorFrwID ProductID, 606 hrProcessorLoad INTEGER 607 } 609 hrProcessorFrwID OBJECT-TYPE 610 SYNTAX ProductID 611 ACCESS read-only 612 STATUS mandatory 613 DESCRIPTION 614 "The product ID of the firmware associated with the 615 processor." 616 ::= { hrProcessorEntry 1 } 618 hrProcessorLoad OBJECT-TYPE 619 SYNTAX INTEGER (0..100) 620 ACCESS read-only 621 STATUS mandatory 622 DESCRIPTION 623 "The average, over the last minute, of the 624 percentage of time that this processor was not 625 idle." 626 ::= { hrProcessorEntry 2 } 628 hrNetworkTable OBJECT-TYPE 629 SYNTAX SEQUENCE OF HrNetworkEntry 630 ACCESS not-accessible 631 STATUS mandatory 632 DESCRIPTION 633 "The (conceptual) table of network devices 634 contained by the host. 636 Note that this table is potentially sparse: a 637 (conceptual) entry exists only if the correspondent 638 value of the hrDeviceType object is 639 `hrDeviceNetwork'." 640 ::= { hrDevice 4 } 642 hrNetworkEntry OBJECT-TYPE 643 SYNTAX HrNetworkEntry 644 ACCESS not-accessible 645 STATUS mandatory 646 DESCRIPTION 647 "A (conceptual) entry for one network device 648 contained by the host. The hrDeviceIndex in the 649 index represents the entry in the hrDeviceTable 650 that corresponds to the hrNetworkEntry." 651 INDEX { hrDeviceIndex } 652 ::= { hrNetworkTable 1 } 654 -- As an example, an instance of the hrNetworkIfIndex object 655 -- might be named hrNetworkIfIndex.3 657 HrNetworkEntry ::= SEQUENCE { 658 hrNetworkIfIndex INTEGER 659 } 661 hrNetworkIfIndex OBJECT-TYPE 662 SYNTAX INTEGER 663 ACCESS read-only 664 STATUS mandatory 665 DESCRIPTION 666 "The value of ifIndex which corresponds to this 667 network device." 668 ::= { hrNetworkEntry 1 } 670 hrPrinterTable OBJECT-TYPE 671 SYNTAX SEQUENCE OF HrPrinterEntry 672 ACCESS not-accessible 673 STATUS mandatory 674 DESCRIPTION 675 "The (conceptual) table of printers local to the 676 host. 678 Note that this table is potentially sparse: a 679 (conceptual) entry exists only if the correspondent 680 value of the hrDeviceType object is 681 `hrDevicePrinter'." 682 ::= { hrDevice 5 } 684 hrPrinterEntry OBJECT-TYPE 685 SYNTAX HrPrinterEntry 686 ACCESS not-accessible 687 STATUS mandatory 688 DESCRIPTION 689 "A (conceptual) entry for one printer local to the 690 host. The hrDeviceIndex in the index represents 691 the entry in the hrDeviceTable that corresponds to 692 the hrPrinterEntry." 693 INDEX { hrDeviceIndex } 694 ::= { hrPrinterTable 1 } 696 -- As an example, an instance of the hrPrinterStatus object 697 -- might be named hrPrinterStatus.3 699 HrPrinterEntry ::= SEQUENCE { 700 hrPrinterStatus INTEGER, 701 hrPrinterDetectedErrorState OCTET STRING 702 } 704 hrPrinterStatus OBJECT-TYPE 705 SYNTAX INTEGER { 706 other(1), 707 unknown(2), 708 idle(3), 709 printing(4), 710 warmup(5) 711 } 712 ACCESS read-only 713 STATUS mandatory 714 DESCRIPTION 715 "The current status of this printer device. When 716 in the idle(1), printing(2), or warmup(3) state, 717 the corresponding hrDeviceStatus should be 718 running(2) or warning(3). When in the unknown 719 state, the corresponding hrDeviceStatus should be 720 unknown(1)." 721 ::= { hrPrinterEntry 1 } 723 hrPrinterDetectedErrorState OBJECT-TYPE 724 SYNTAX OCTET STRING 725 ACCESS read-only 726 STATUS mandatory 727 DESCRIPTION 728 "This object represents any error conditions 729 detected by the printer. The error conditions are 730 encoded as bits in an octet string, with the 731 following definitions: 733 Condition Bit # hrDeviceStatus 735 lowPaper 0 warning(3) 736 noPaper 1 down(5) 737 lowToner 2 warning(3) 738 noToner 3 down(5) 739 doorOpen 4 down(5) 740 jammed 5 down(5) 741 offline 6 down(5) 742 serviceRequested 7 warning(3) 744 If multiple conditions are currently detected and 745 the hrDeviceStatus would not otherwise be 746 unknown(1) or testing(4), the hrDeviceStatus shall 747 correspond to the worst state of those indicated, 748 where down(5) is worse than warning(3) which is 749 worse than running(2). 751 Bits are numbered starting with the most 752 significant bit of the first byte being bit 0, the 753 least significant bit of the first byte being bit 754 7, the most significant bit of the second byte 755 being bit 8, and so on. A one bit encodes that 756 the condition was detected, while a zero bit 757 encodes that the condition was not detected. 759 This object is useful for alerting an operator to 760 specific warning or error conditions that may 761 occur, especially those requiring human 762 intervention." 763 ::= { hrPrinterEntry 2 } 765 hrDiskStorageTable OBJECT-TYPE 766 SYNTAX SEQUENCE OF HrDiskStorageEntry 767 ACCESS not-accessible 768 STATUS mandatory 769 DESCRIPTION 770 "The (conceptual) table of long-term storage 771 devices contained by the host. In particular, disk 772 devices accessed remotely over a network are not 773 included here. 775 Note that this table is potentially sparse: a 776 (conceptual) entry exists only if the correspondent 777 value of the hrDeviceType object is 778 `hrDeviceDiskStorage'." 779 ::= { hrDevice 6 } 781 hrDiskStorageEntry OBJECT-TYPE 782 SYNTAX HrDiskStorageEntry 783 ACCESS not-accessible 784 STATUS mandatory 785 DESCRIPTION 786 "A (conceptual) entry for one long-term storage 787 device contained by the host. The hrDeviceIndex in 788 the index represents the entry in the hrDeviceTable 789 that corresponds to the hrDiskStorageEntry." 790 INDEX { hrDeviceIndex } 791 ::= { hrDiskStorageTable 1 } 793 -- As an example, an instance of the hrDiskStorageCapacity object 794 -- might be named hrDiskStorageCapacity.3 796 HrDiskStorageEntry ::= SEQUENCE { 797 hrDiskStorageAccess INTEGER, 798 hrDiskStorageMedia INTEGER, 799 hrDiskStorageRemoveable Boolean, 800 hrDiskStorageCapacity KBytes 801 } 803 hrDiskStorageAccess OBJECT-TYPE 804 SYNTAX INTEGER { 805 readWrite(1), 806 readOnly(2) 807 } 808 ACCESS read-only 809 STATUS mandatory 810 DESCRIPTION 811 "An indication if this long-term storage device is 812 readable and writable or only readable. This 813 should reflect the media type, any write-protect 814 mechanism, and any device configuration that 815 affects the entire device." 816 ::= { hrDiskStorageEntry 1 } 818 hrDiskStorageMedia OBJECT-TYPE 819 SYNTAX INTEGER { 820 other(1), 821 unknown(2), 822 hardDisk(3), 823 floppyDisk(4), 824 opticalDiskROM(5), 825 opticalDiskWORM(6), -- Write Once Read Many 826 opticalDiskRW(7), 827 ramDisk(8) 828 } 829 ACCESS read-only 830 STATUS mandatory 831 DESCRIPTION 832 "An indication of the type of media used in this 833 long-term storage device." 834 ::= { hrDiskStorageEntry 2 } 836 hrDiskStorageRemoveable OBJECT-TYPE 837 SYNTAX Boolean 838 ACCESS read-only 839 STATUS mandatory 840 DESCRIPTION 841 "Denotes whether or not the disk media may be 842 removed from the drive." 843 ::= { hrDiskStorageEntry 3 } 845 hrDiskStorageCapacity OBJECT-TYPE 846 SYNTAX KBytes 847 ACCESS read-only 848 STATUS mandatory 849 DESCRIPTION 850 "The total size for this long-term storage device." 851 ::= { hrDiskStorageEntry 4 } 853 hrPartitionTable OBJECT-TYPE 854 SYNTAX SEQUENCE OF HrPartitionEntry 855 ACCESS not-accessible 856 STATUS mandatory 857 DESCRIPTION 858 "The (conceptual) table of partitions for long-term 859 storage devices contained by the host. In 860 particular, partitions accessed remotely over a 861 network are not included here." 862 ::= { hrDevice 7 } 864 hrPartitionEntry OBJECT-TYPE 865 SYNTAX HrPartitionEntry 866 ACCESS not-accessible 867 STATUS mandatory 868 DESCRIPTION 869 "A (conceptual) entry for one partition. The 870 hrDeviceIndex in the index represents the entry in 871 the hrDeviceTable that corresponds to the 872 hrPartitionEntry." 873 INDEX { hrDeviceIndex, hrPartitionIndex } 874 ::= { hrPartitionTable 1 } 876 -- As an example, an instance of the hrPartitionSize object 877 -- might be named hrPartitionSize.3.1 879 HrPartitionEntry ::= SEQUENCE { 880 hrPartitionIndex INTEGER, 881 hrPartitionLabel Characters, 882 hrPartitionID OCTET STRING, 883 hrPartitionSize KBytes, 884 hrPartitionFSIndex INTEGER 885 } 887 hrPartitionIndex OBJECT-TYPE 888 SYNTAX INTEGER (1..2147483647) 889 ACCESS read-only 890 STATUS mandatory 891 DESCRIPTION 892 "A unique value for each partition on this long- 893 term storage device. The value for each long-term 894 storage device must remain constant at least from 895 one re-initialization of the agent to the next re- 896 initialization." 897 ::= { hrPartitionEntry 1 } 899 hrPartitionLabel OBJECT-TYPE 900 SYNTAX Characters (SIZE (0..128)) 901 ACCESS read-only 902 STATUS mandatory 903 DESCRIPTION 904 "A textual description of this partition." 905 ::= { hrPartitionEntry 2 } 907 hrPartitionID OBJECT-TYPE 908 SYNTAX OCTET STRING 909 ACCESS read-only 910 STATUS mandatory 911 DESCRIPTION 912 "A descriptor which uniquely represents this 913 partition to the responsible operating system. On 914 some systems, this might take on a binary 915 representation." 916 ::= { hrPartitionEntry 3 } 918 hrPartitionSize OBJECT-TYPE 919 SYNTAX KBytes 920 ACCESS read-only 921 STATUS mandatory 922 DESCRIPTION 923 "The size of this partition." 924 ::= { hrPartitionEntry 4 } 926 hrPartitionFSIndex OBJECT-TYPE 927 SYNTAX INTEGER (0..2147483647) 928 ACCESS read-only 929 STATUS mandatory 930 DESCRIPTION 931 "The index of the file system mounted on this 932 partition. If no file system is mounted on this 933 partition, then this value shall be zero. Note 934 that multiple partitions may point to one file 935 system, denoting that that file system resides on 936 those partitions. Multiple file systems may not 937 reside on one partition." 938 ::= { hrPartitionEntry 5 } 940 -- The File System Table 941 hrFSTable OBJECT-TYPE 942 SYNTAX SEQUENCE OF HrFSEntry 943 ACCESS not-accessible 944 STATUS mandatory 945 DESCRIPTION 946 "The (conceptual) table of file systems local to 947 this host or remotely mounted from a file server. 948 File systems that are in only one user's 949 environment on a multi-user system will not be 950 included in this table." 951 ::= { hrDevice 8 } 953 hrFSEntry OBJECT-TYPE 954 SYNTAX HrFSEntry 955 ACCESS not-accessible 956 STATUS mandatory 957 DESCRIPTION 958 "A (conceptual) entry for one file system local to 959 this host or remotely mounted from a file server. 960 File systems that are in only one user's 961 environment on a multi-user system will not be 962 included in this table." 963 INDEX { hrFSIndex } 964 ::= { hrFSTable 1 } 966 -- As an example, an instance of the hrFSMountPoint object 967 -- might be named hrFSMountPoint.3 969 -- Registration for some popular File System types, 970 -- for use with hrFSType. 972 hrFSTypes OBJECT IDENTIFIER ::= { hrDevice 9 } 974 hrFSOther OBJECT IDENTIFIER ::= { hrFSTypes 1 } 975 hrFSUnknown OBJECT IDENTIFIER ::= { hrFSTypes 2 } 976 hrFSBerkeleyFFS OBJECT IDENTIFIER ::= { hrFSTypes 3 } 977 hrFSSys5FS OBJECT IDENTIFIER ::= { hrFSTypes 4 } 978 -- DOS 979 hrFSFat OBJECT IDENTIFIER ::= { hrFSTypes 5 } 980 -- OS/2 High Performance File System 981 hrFSHPFS OBJECT IDENTIFIER ::= { hrFSTypes 6 } 982 -- Macintosh Hierarchical File System 983 hrFSHFS OBJECT IDENTIFIER ::= { hrFSTypes 7 } 984 -- Macintosh File System 985 hrFSMFS OBJECT IDENTIFIER ::= { hrFSTypes 8 } 986 -- Windows NT 987 hrFSNTFS OBJECT IDENTIFIER ::= { hrFSTypes 9 } 988 hrFSVNode OBJECT IDENTIFIER ::= { hrFSTypes 10 } 989 hrFSJournaled OBJECT IDENTIFIER ::= { hrFSTypes 11 } 990 -- CD File systems 991 hrFSiso9660 OBJECT IDENTIFIER ::= { hrFSTypes 12 } 992 hrFSRockRidge OBJECT IDENTIFIER ::= { hrFSTypes 13 } 994 hrFSNFS OBJECT IDENTIFIER ::= { hrFSTypes 14 } 995 hrFSNetware OBJECT IDENTIFIER ::= { hrFSTypes 15 } 996 -- Andrew File System 997 hrFSAFS OBJECT IDENTIFIER ::= { hrFSTypes 16 } 998 -- OSF DCE Distributed File System 999 hrFSDFS OBJECT IDENTIFIER ::= { hrFSTypes 17 } 1000 hrFSAppleshare OBJECT IDENTIFIER ::= { hrFSTypes 18 } 1001 hrFSRFS OBJECT IDENTIFIER ::= { hrFSTypes 19 } 1002 -- Data General 1003 hrFSDGCFS OBJECT IDENTIFIER ::= { hrFSTypes 20 } 1004 -- SVR4 Boot File System 1005 hrFSBFS OBJECT IDENTIFIER ::= { hrFSTypes 21 } 1007 HrFSEntry ::= SEQUENCE { 1008 hrFSIndex INTEGER, 1009 hrFSMountPoint Characters, 1010 hrFSRemoteMountPoint Characters, 1011 hrFSType OBJECT IDENTIFIER, 1012 hrFSAccess INTEGER, 1013 hrFSBootable Boolean, 1014 hrFSStorageIndex INTEGER, 1015 hrFSLastFullBackupDate DateAndTime, 1016 hrFSLastPartialBackupDate DateAndTime 1017 } 1019 hrFSIndex OBJECT-TYPE 1020 SYNTAX INTEGER (1..2147483647) 1021 ACCESS read-only 1022 STATUS mandatory 1023 DESCRIPTION 1024 "A unique value for each file system local to this 1025 host. The value for each file system must remain 1026 constant at least from one re-initialization of 1027 the agent to the next re-initialization." 1029 ::= { hrFSEntry 1 } 1031 hrFSMountPoint OBJECT-TYPE 1032 SYNTAX Characters (SIZE(0..128)) 1033 ACCESS read-only 1034 STATUS mandatory 1035 DESCRIPTION 1036 "The path name of the root of this file system." 1037 ::= { hrFSEntry 2 } 1039 hrFSRemoteMountPoint OBJECT-TYPE 1040 SYNTAX Characters (SIZE(0..128)) 1041 ACCESS read-only 1042 STATUS mandatory 1043 DESCRIPTION 1044 "A description of the name and/or address of the 1045 server that this file system is mounted from. 1046 This may also include parameters such as the mount 1047 point on the remote file system. If this is not a 1048 remote file system, this string should have a 1049 length of zero." 1050 ::= { hrFSEntry 3 } 1052 hrFSType OBJECT-TYPE 1053 SYNTAX OBJECT IDENTIFIER 1054 ACCESS read-only 1055 STATUS mandatory 1056 DESCRIPTION 1057 "The value of this object identifies the type of 1058 this file system." 1059 ::= { hrFSEntry 4 } 1061 hrFSAccess OBJECT-TYPE 1062 SYNTAX INTEGER { 1063 readWrite(1), 1064 readOnly(2) 1065 } 1066 ACCESS read-only 1067 STATUS mandatory 1068 DESCRIPTION 1069 "An indication if this file system is logically 1070 configured by the operating system to be readable 1071 and writable or only readable. This does not 1072 represent any local access-control policy, except 1073 one that is applied to the file system as a whole." 1075 ::= { hrFSEntry 5 } 1077 hrFSBootable OBJECT-TYPE 1078 SYNTAX Boolean 1079 ACCESS read-only 1080 STATUS mandatory 1081 DESCRIPTION 1082 "A flag indicating whether this file system is 1083 bootable." 1084 ::= { hrFSEntry 6 } 1086 hrFSStorageIndex OBJECT-TYPE 1087 SYNTAX INTEGER (0..2147483647) 1088 ACCESS read-only 1089 STATUS mandatory 1090 DESCRIPTION 1091 "The index of the hrStorageEntry that represents 1092 information about this file system. If there is 1093 no such information available, then this value 1094 shall be zero. The relevant storage entry will be 1095 useful in tracking the percent usage of this file 1096 system and diagnosing errors that may occur when 1097 it runs out of space." 1098 ::= { hrFSEntry 7 } 1100 hrFSLastFullBackupDate OBJECT-TYPE 1101 SYNTAX DateAndTime 1102 ACCESS read-write 1103 STATUS mandatory 1104 DESCRIPTION 1105 "The last date at which this complete file system 1106 was copied to another storage device for backup. 1107 This information is useful for ensuring that 1108 backups are being performed regularly." 1109 ::= { hrFSEntry 8 } 1111 hrFSLastPartialBackupDate OBJECT-TYPE 1112 SYNTAX DateAndTime 1113 ACCESS read-write 1114 STATUS mandatory 1115 DESCRIPTION 1116 "The last date at which a portion of this file 1117 system was copied to another storage device for 1118 backup. This information is useful for ensuring 1119 that backups are being performed regularly." 1121 ::= { hrFSEntry 9 } 1123 -- The Host Resources Running Software Group 1124 -- 1125 -- Implementation of this group is optional. 1126 -- 1127 -- The hrSWRunTable contains an entry for each distinct piece of 1128 -- software that is running or loaded into physical or virtual 1129 -- memory in preparation for running. This includes the host's 1130 -- operating system, device drivers, and applications. 1132 hrSWOSIndex OBJECT-TYPE 1133 SYNTAX INTEGER (1..2147483647) 1134 ACCESS read-only 1135 STATUS mandatory 1136 DESCRIPTION 1137 "The index of the entry in the hrSWRunTable that 1138 represents the primary operating system running on 1139 this host. This object is useful for quickly and 1140 uniquely identifying that primary operating 1141 system." 1142 ::= { hrSWRun 1 } 1144 hrSWRunTable OBJECT-TYPE 1145 SYNTAX SEQUENCE OF HrSWRunEntry 1146 ACCESS not-accessible 1147 STATUS mandatory 1148 DESCRIPTION 1149 "The (conceptual) table of software running on the 1150 host." 1151 ::= { hrSWRun 2 } 1153 hrSWRunEntry OBJECT-TYPE 1154 SYNTAX HrSWRunEntry 1155 ACCESS not-accessible 1156 STATUS mandatory 1157 DESCRIPTION 1158 "A (conceptual) entry for one piece of software 1159 running on the host Note that because the installed 1160 software table only contains information for 1161 software stored locally on this host, not every 1162 piece of running software will be found in the 1163 installed software table. This is true of software 1164 that was loaded and run from a non-local source, 1165 such as a network-mounted file system." 1166 INDEX { hrSWRunIndex } 1167 ::= { hrSWRunTable 1 } 1169 -- As an example, an instance of the hrSWRunName object 1170 -- might be named hrSWRunName.1287 1172 HrSWRunEntry ::= SEQUENCE { 1173 hrSWRunIndex INTEGER, 1174 hrSWRunName Characters, 1175 hrSWRunID ProductID, 1176 hrSWRunPath Characters, 1177 hrSWRunParameters Characters, 1178 hrSWRunType INTEGER, 1179 hrSWRunStatus INTEGER 1180 } 1182 hrSWRunIndex OBJECT-TYPE 1183 SYNTAX INTEGER (1..2147483647) 1184 ACCESS read-only 1185 STATUS mandatory 1186 DESCRIPTION 1187 "A unique value for each piece of software running 1188 on the host. Wherever possible, this should be the 1189 system's native, unique identification number." 1190 ::= { hrSWRunEntry 1 } 1192 hrSWRunName OBJECT-TYPE 1193 SYNTAX Characters (SIZE (0..64)) 1194 ACCESS read-only 1195 STATUS mandatory 1196 DESCRIPTION 1197 "A textual description of this running piece of 1198 software, including the manufacturer, revision, 1199 and the name by which it is commonly known. If 1200 this software was installed locally, this should be 1201 the same string as used in the corresponding 1202 hrSWInstalledName." 1203 ::= { hrSWRunEntry 2 } 1205 hrSWRunID OBJECT-TYPE 1206 SYNTAX ProductID 1207 ACCESS read-only 1208 STATUS mandatory 1209 DESCRIPTION 1210 "The product ID of this running piece of software." 1211 ::= { hrSWRunEntry 3 } 1213 hrSWRunPath OBJECT-TYPE 1214 SYNTAX Characters (SIZE(0..128)) 1215 ACCESS read-only 1216 STATUS mandatory 1217 DESCRIPTION 1218 "A description of the location on long-term storage 1219 (e.g. a disk drive) from which this software was 1220 loaded." 1221 ::= { hrSWRunEntry 4 } 1223 hrSWRunParameters OBJECT-TYPE 1224 SYNTAX Characters (SIZE(0..128)) 1225 ACCESS read-only 1226 STATUS mandatory 1227 DESCRIPTION 1228 "A description of the parameters supplied to this 1229 software when it was initially loaded." 1230 ::= { hrSWRunEntry 5 } 1232 hrSWRunType OBJECT-TYPE 1233 SYNTAX INTEGER { 1234 unknown(1), 1235 operatingSystem(2), 1236 deviceDriver(3), 1237 application(4) 1238 } 1239 ACCESS read-only 1240 STATUS mandatory 1241 DESCRIPTION 1242 "The type of this software." 1243 ::= { hrSWRunEntry 6 } 1245 hrSWRunStatus OBJECT-TYPE 1246 SYNTAX INTEGER { 1247 running(1), 1248 runnable(2), -- waiting for resource (CPU, memory, IO) 1249 notRunnable(3), -- loaded but waiting for event 1250 invalid(4) -- not loaded 1251 } 1252 ACCESS read-write 1253 STATUS mandatory 1254 DESCRIPTION 1255 "The status of this running piece of software. 1256 Setting this value to invalid(4) shall cause this 1257 software to stop running and to be unloaded." 1258 ::= { hrSWRunEntry 7 } 1260 -- The Host Resources Running Software Performance Group 1261 -- Implementation of this group is optional. 1262 -- 1263 -- The hrSWRunPerfTable contains an entry corresponding to 1264 -- each entry in the hrSWRunTable. 1266 hrSWRunPerfTable OBJECT-TYPE 1267 SYNTAX SEQUENCE OF HrSWRunPerfEntry 1268 ACCESS not-accessible 1269 STATUS mandatory 1270 DESCRIPTION 1271 "The (conceptual) table of running software 1272 performance metrics." 1273 ::= { hrSWRunPerf 1 } 1275 hrSWRunPerfEntry OBJECT-TYPE 1276 SYNTAX HrSWRunPerfEntry 1277 ACCESS not-accessible 1278 STATUS mandatory 1279 DESCRIPTION 1280 "A (conceptual) entry containing software 1281 performance metrics." 1282 INDEX { hrSWRunIndex } -- This table augments information in 1283 -- the hrSWRunTable. 1284 ::= { hrSWRunPerfTable 1 } 1286 -- As an example, an instance of the hrSWRunPerfCPU object 1287 -- might be named hrSWRunPerfCPU.1287 1289 HrSWRunPerfEntry ::= SEQUENCE { 1290 hrSWRunPerfCPU INTEGER, 1291 hrSWRunPerfMem KBytes 1292 } 1294 hrSWRunPerfCPU OBJECT-TYPE 1295 SYNTAX INTEGER 1296 ACCESS read-only 1297 STATUS mandatory 1298 DESCRIPTION 1299 "The number of centi-seconds of the total system's 1300 CPU resources consumed by this process. Note that 1301 on a multi-processor system, this value may 1302 increment by more than one centi-second in one 1303 centi-second of real (wall clock) time." 1304 ::= { hrSWRunPerfEntry 1 } 1306 hrSWRunPerfMem OBJECT-TYPE 1307 SYNTAX KBytes 1308 ACCESS read-only 1309 STATUS mandatory 1310 DESCRIPTION 1311 "The total amount of real system memory allocated 1312 to this process." 1313 ::= { hrSWRunPerfEntry 2 } 1315 -- The Host Resources Installed Software Group 1316 -- 1317 -- Implementation of this group is optional. 1318 -- 1319 -- The hrSWInstalledTable contains an entry for each piece 1320 -- of software installed in long-term storage (e.g. a disk 1321 -- drive) locally on this host. Note that this does not 1322 -- include software loadable remotely from a network 1323 -- server. 1324 -- 1325 -- This table is useful for identifying and inventorying 1326 -- software on a host and for diagnosing incompatibility 1327 -- and version mismatch problems between various pieces 1328 -- of hardware and software. 1330 hrSWInstalledLastChange OBJECT-TYPE 1331 SYNTAX TimeTicks 1332 ACCESS read-only 1333 STATUS mandatory 1334 DESCRIPTION 1335 "The value of sysUpTime when an entry in the 1336 hrSWInstalledTable was last added, renamed, or 1337 deleted. Because this table is likely to contain 1338 many entries, polling of this object allows a 1339 management station to determine when re-downloading 1340 of the table might be useful." 1341 ::= { hrSWInstalled 1 } 1343 hrSWInstalledLastUpdateTime OBJECT-TYPE 1344 SYNTAX TimeTicks 1345 ACCESS read-only 1346 STATUS mandatory 1347 DESCRIPTION 1348 "The value of sysUpTime when the hrSWInstalledTable 1349 was last completely updated. Because caching of 1350 this data will be a popular implementation 1351 strategy, retrieval of this object allows a 1352 management station to obtain a guarantee that no 1353 data in this table is older than the indicated 1354 time." 1355 ::= { hrSWInstalled 2 } 1357 hrSWInstalledTable OBJECT-TYPE 1358 SYNTAX SEQUENCE OF HrSWInstalledEntry 1359 ACCESS not-accessible 1360 STATUS mandatory 1361 DESCRIPTION 1362 "The (conceptual) table of software installed on 1363 this host." 1364 ::= { hrSWInstalled 3 } 1366 hrSWInstalledEntry OBJECT-TYPE 1367 SYNTAX HrSWInstalledEntry 1368 ACCESS not-accessible 1369 STATUS mandatory 1370 DESCRIPTION 1371 "A (conceptual) entry for a piece of software 1372 installed on this host." 1373 INDEX { hrSWInstalledIndex } 1374 ::= { hrSWInstalledTable 1 } 1376 -- As an example, an instance of the hrSWInstalledName object 1377 -- might be named hrSWInstalledName.96 1379 HrSWInstalledEntry ::= SEQUENCE { 1380 hrSWInstalledIndex INTEGER, 1381 hrSWInstalledName Characters, 1382 hrSWInstalledID ProductID, 1383 hrSWInstalledType INTEGER, 1384 hrSWInstalledDate DateAndTime 1385 } 1387 hrSWInstalledIndex OBJECT-TYPE 1388 SYNTAX INTEGER (1..2147483647) 1389 ACCESS read-only 1390 STATUS mandatory 1391 DESCRIPTION 1392 "A unique value for each piece of software 1393 installed on the host. This value shall be in the 1394 range from 1 to the number of pieces of software 1395 installed on the host." 1396 ::= { hrSWInstalledEntry 1 } 1398 hrSWInstalledName OBJECT-TYPE 1399 SYNTAX Characters (SIZE (0..64)) 1400 ACCESS read-only 1401 STATUS mandatory 1402 DESCRIPTION 1403 "A textual description of this installed piece of 1404 software, including the manufacturer, revision, the 1405 name by which it is commonly known, and optionally, 1406 its serial number." 1407 ::= { hrSWInstalledEntry 2 } 1409 hrSWInstalledID OBJECT-TYPE 1410 SYNTAX ProductID 1411 ACCESS read-only 1412 STATUS mandatory 1413 DESCRIPTION 1414 "The product ID of this installed piece of 1415 software." 1416 ::= { hrSWInstalledEntry 3 } 1418 hrSWInstalledType OBJECT-TYPE 1419 SYNTAX INTEGER { 1420 unknown(1), 1421 operatingSystem(2), 1422 deviceDriver(3), 1423 application(4) 1424 } 1425 ACCESS read-only 1426 STATUS mandatory 1427 DESCRIPTION 1428 "The type of this software." 1429 ::= { hrSWInstalledEntry 4 } 1431 hrSWInstalledDate OBJECT-TYPE 1432 SYNTAX DateAndTime 1433 ACCESS read-only 1434 STATUS mandatory 1435 DESCRIPTION 1436 "The last-modification date of this application as 1437 it would appear in a directory listing." 1438 ::= { hrSWInstalledEntry 5 } 1440 END 1441 6. References 1443 [1] M.T. Rose and K. McCloghrie, Structure and Identification 1444 of Management Information for TCP/IP-based internets. 1445 Request for Comments 1155, (May, 1990). 1447 [2] M.T. Rose and K. McCloghrie, Concise MIB Definitions. 1448 Request for Comments 1212, (March, 1991). 1450 [3] K. McCloghrie and M.T. Rose, Management Information Base 1451 for Network Management of TCP/IP-based internets: MIB-II. 1452 Request for Comments 1213, (March, 1991). 1454 [4] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin, 1455 Simple Network Management Protocol. Request for Comments 1456 1157, (May, 1990). 1458 [5] Information processing systems - Open Systems 1459 Interconnection - Specification of Abstract Syntax 1460 Notation One (ASN.1), International Organization for 1461 Standardization. International Standard 8824, (December, 1462 1987). 1464 Table of Contents 1466 1 Status of this Memo ................................... 1 1467 2 Abstract .............................................. 2 1468 3 The Network Management Framework ...................... 3 1469 4 Host Resources MIB .................................... 4 1470 5 Definitions ........................................... 5 1471 5.1 Textual Conventions ................................. 6 1472 5.2 The Host Resources System Group ..................... 8 1473 5.3 The Host Resources Storage Group .................... 10 1474 5.4 The Host Resources Device Group ..................... 14 1475 5.5 The Host Resources Running Software Group ........... 33 1476 5.6 The Host Resources Running Software Performance 1477 Group .............................................. 36 1478 5.7 The Host Resources Installed Software Group ......... 38 1479 6 References ............................................ 41