idnits 2.17.1 draft-krupczak-hostmibv2-01.txt: 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. Found some kind of copyright notice around line 34 but it does not match any copyright boilerplate known by this tool. Expected boilerplate is as follows today (2024-04-25) 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 -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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. ** Missing revision: the document name given in the document, 'draft-krupczak-hostmibv2-01-txt', does not give the document revision number ~~ Missing draftname component: the document name given in the document, 'draft-krupczak-hostmibv2-01-txt', does not seem to contain all the document name components required ('draft' prefix, document source, document name, and revision) -- see https://www.ietf.org/id-info/guidelines#naming for more information. == Mismatching filename: the document gives the document name as 'draft-krupczak-hostmibv2-01-txt', but the file name used is 'draft-krupczak-hostmibv2-01' ** The document is more than 15 pages and seems to lack a Table of Contents. == 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 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 separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 2 instances of too long lines in the document, the longest one being 2 characters in excess of 72. ** There are 15 instances of lines with control characters in the document. ** The abstract seems to contain references ([1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 2 instances of lines with non-RFC2606-compliant FQDNs in the document. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 259: '...agement software MUST be able to displ...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 62 has weird spacing: '...mputers are i...' == Line 237 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 (1 October 1998) is 9338 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 1514 (ref. '1') (Obsoleted by RFC 2790) -- Possible downref: Non-RFC (?) normative reference: ref. '2' -- Possible downref: Non-RFC (?) normative reference: ref. '4' ** Obsolete normative reference: RFC 1902 (ref. '5') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1904 (ref. '6') (Obsoleted by RFC 2580) Summary: 18 errors (**), 1 flaw (~~), 7 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Host Resources MIB V2 4 1 October 1998 6 draft-krupczak-hostmibv2-01-txt 8 Bobby Krupczak 9 Empire Technologies, Inc. 10 rdk@empiretech.com 12 Expires 25 March, 1999 14 Status of this Memo 16 This document is an Internet-Draft. Internet-Drafts are working 17 documents of the Internet Engineering Task Force (IETF), its areas, 18 and its working groups. Note that other groups may also distribute 19 working documents as Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet- Drafts as reference 24 material or to cite them other than as ``work in progress.'' 26 To learn the current status of any Internet-Draft, please check the 27 ``1id-abstracts.txt'' listing contained in the Internet- Drafts 28 Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 29 munnari.oz.au (Pacific Rim), ftp.ietf.org (US East Coast), or 30 ftp.isi.edu (US West Coast). 32 Copyright Notice 34 Copyright (C) The Internet Society (1998). All Rights Reserved. 36 Abstract 38 This memo modifies the original Host Resources MIB (RFC 1514) by 39 converting it to the SNMPv2 SMI. Further, this memo adds 40 clarifying text, based on implementation and deployment experience, 41 to ambiguous MIB object specifications. It does not add nor remove 42 managed objects from the original specification nor change their 43 fundamental semantics. 45 The original memo defines a MIB for use with managing host systems. 46 This memo does not modify the original RFC's definitions or 47 assumptions. Included from the original RFC [1]: 49 The term "host" is construed to mean any computer that 50 communicates with other similar computers attached to the 51 internet and that is directly used by one or more human 52 beings. Although this MIB does not necessarily apply to devices 53 whose primary function is communications services (e.g., 54 terminal servers, routers, bridges, monitoring equipment), such 55 relevance is not explicitly precluded. This MIB instruments 56 attributes common to all internet hosts including, for example, 57 both personal computers and systems that run variants of Unix. 59 1. Overview 61 The Host Resources MIB defines a uniform set of objects useful for 62 the management of host computers. Host computers are independent of 63 the operating system, network services, or any software application. 65 The Host Resources MIB defines objects which are common across many 66 computer system architectures. 68 In addition, there are objects in MIB-II [3] which also provide host 69 management functionality. Implementation of the System and Interfaces 70 groups is mandatory for implementors of the Host Resources MIB. 72 2. Modifications to the original Host Resources MIB (RFC 1514) 74 This memo does not alter the original Host Resources MIB (RFC 75 1514) by adding or removing MIB objects. Rather, it converts the 76 original MIB specification to the SMIv2 [5] and adds clarifying 77 text to several MIB objects based on implementation experience and 78 feedback from real users of the MIB. 80 Additional storage, filesystem, and device types are clearly 81 warranted but should be specified in a separate document rather 82 than in this MIB specification itself. The original storage, 83 filesystem, and device types are preserved here in this memo for 84 compatibility's sake. 86 2.1 Conversion to SMIv2 88 The conversion from SMIv1 to SMIv2 occurred using the algorithm 89 provided in [2] as a rough guideline. More specifically, the 90 following actions were taken: 92 + Addition of MODULE-IDENTIFY clause from SMIv2 RFC 1902. 94 + All objects specifications were converted to use the SMIv2 95 OBJECT-TYPE macro defined in RFC 1902. 97 + Type changes 98 - Counter to Counter32 99 - Gauge to Gauge32 100 - INTEGER to Integer32 where appropriate 102 + hrPrinterDetectedErrorState syntax changed to BITS to better 103 document its syntax and semantics. Further, at the request of 104 the printer-working group (PWG), additional bit definitions 105 have been added. These changes are backwards compatible with 106 the original RFC 1514 specification. 108 + Compliance branch and statements have been added as per the 109 MODULE-COMPLIANCE macro from RFC 1904 [6]. This macro formalizes 110 the notion of mandatory and optional MIB groupings which have 111 previously been specified in natural language text 112 accompanying a MIB document. The branch hrConformance has 113 been added as branch 7 under the main MIB branch. 115 2.2 Managed Object Clarifications 117 The specification for hrNetworkIfIndex states that the value of a 118 network device's ifIndex value be returned. However, not all network 119 devices contained in a host system may have a corresponding ifIndex 120 value. In this case, the value of 0 should be returned for 121 hrNetworkIfIndex. 123 The definition of the hrSWInstalledTable and accompanying MIB 124 objects is somewhat ambiguous when it comes to discerning between 125 applications and software packages installed on the underlying 126 system. Further, implementation and deployment experience have led 127 the author to acknowledge the usefulness of information pertaining 128 to installed packages, the definition of the hrSWInstalledTable 129 should be expanded to include software packages installed on the 130 underlying system. Included in this expanded definition of 131 "software" are system and application patches. This expansion of 132 the definition of installed software is consistent with many users 133 and with the original MIB's interpretation in [4] which was 134 reviewed by one of the editors of the original specification. 136 3. Definitions 138 HOST-RESOURCES-V2-MIB DEFINITIONS ::= BEGIN 140 IMPORTS 141 Counter32, Gauge32, Integer32, TimeTicks, mib-2, OBJECT-TYPE, 142 MODULE-IDENTITY, BITS 143 FROM SNMPv2-SMI 144 MODULE-COMPLIANCE, OBJECT-GROUP 146 FROM SNMPv2-CONF 147 DisplayString 148 FROM SNMPv2-TC; 150 hostResourcesMibModule MODULE-IDENTITY 151 LAST-UPDATED "9803071600Z" 152 ORGANIZATION "IETF Host Resources MIB Working Group" 153 CONTACT-INFO 154 "Bobby Krupczak 155 Postal: Empire Technologies, Inc. 156 541 Tenth St, NW 157 Suite 169 158 Atlanta, GA 30318-5713 159 USA 160 Phone: 770.384.0184 161 Fax: 770.384.0183 162 Email: rdk@empiretech.com" 163 DESCRIPTION 164 "The Host Resourcers MIB defines a uniform set of 165 objects useful for the management of host computers. Host 166 computers are independent of the operating system, network 167 services, or any software application. 169 The Host Resources MIB defines objects which are common 170 across many computer system architectures. 172 In addition, there are objects in MIB-II which also 173 provide host management functionality. Implementation of 174 the System and Interface groups is mandatory for 175 implementors of the Host Resources MIB." 176 REVISION "9803071600Z" 177 DESCRIPTION 178 "$Id: hostmib-v2.txt,v 1.1 1998/09/23 13:39:27 rdk Exp rdk $ 179 $Log: hostmib-v2.txt,v $ 180 Revision 1.1 1998/09/23 13:39:27 rdk 181 Initial revision 182 Revision 1.1 1998/03/08 03:12:48 rdk 183 Initial revision" 184 ::= { mib-2 25 } 186 -- for SMIv1 compatibility 187 host OBJECT IDENTIFIER ::= { mib-2 25 } 189 hrSystem OBJECT IDENTIFIER ::= { host 1 } 190 hrStorage OBJECT IDENTIFIER ::= { host 2 } 191 hrDevice OBJECT IDENTIFIER ::= { host 3 } 192 hrSWRun OBJECT IDENTIFIER ::= { host 4 } 193 hrSWRunPerf OBJECT IDENTIFIER ::= { host 5 } 194 hrSWInstalled OBJECT IDENTIFIER ::= { host 6 } 195 hrConformance OBJECT IDENTIFIER ::= { host 7 } 197 -- textual conventions (SNMPv1 style) 199 -- a truth value 200 Boolean ::= INTEGER { true(1), false(2) } 202 -- memory size, expressed in units of 1024bytes 203 KBytes ::= Integer32 (0..2147483647) 205 -- This textual convention is intended to identify the manufacturer, 206 -- model, and version of a specific hardware or software product. 207 -- It is suggested that these OBJECT IDENTIFIERs are allocated such 208 -- that all products from a particular manufacturer are registered 209 -- under a subtree distinct to that manufacturer. In addition, all 210 -- versions of a product should be registered under a subtree 211 -- distinct to that product. With this strategy, a management 212 -- station may uniquely determine the manufacturer and/or model of a 213 -- product whose productID is unknown to the management station. 214 -- Objects of this type may be useful for inventory purposes or for 215 -- automatically detecting incompatibilities or version mismatches 216 -- between various hardware and software components on a system. 218 ProductID ::= OBJECT IDENTIFIER 220 -- unknownProduct will be used for any unknown ProductID 221 -- unknownProduct OBJECT IDENTIFIER ::= { 0 0 } 223 -- For example, the product ID for the ACME 4860 66MHz clock doubled 224 -- processor might be: 225 -- enterprises.acme.acmeProcessors.a4860DX2.MHz66 226 -- A software product might be registered as: 227 -- enterprises.acme.acmeOperatingSystems.acmeDOS.six(6).one(1) 229 -- DateAndTime ::= OCTET STRING (SIZE (8)) 231 DateAndTime ::= OCTET STRING (SIZE (8 | 11)) 233 -- A date-time specification for the local time of day. 234 -- This data type is intended to provide a consistent 235 -- method of reporting date information. 236 -- 237 -- field octets contents range 238 -- _____ ______ ________ _____ 239 -- 1 1-2 year 0..65536 240 -- (in network byte order) 241 -- 2 3 month 1..12 242 -- 3 4 day 1..31 243 -- 4 5 hour 0..23 244 -- 5 6 minutes 0..59 245 -- 6 7 seconds 0..60 246 -- (use 60 for leap-second) 247 -- 7 8 deci-seconds 0..9 248 -- 8 9 direction from UTC "+" / "-" 249 -- (in ascii notation) 250 -- 9 10 hours from UTC 0..11 251 -- 10 11 minutes from UTC 0..59 252 -- 253 -- Note that if only local time is known, then 254 -- timezone information (fields 8-10) is not present. 256 InternationalDisplayString ::= OCTET STRING 258 -- This data type is used to model textual information. 259 -- Management software MUST be able to display this field 260 -- as if its content was UTF-8, in accordance with RFC 2077. 261 -- For compliance with older management software, a local 262 -- algorithm, such as preconfiguration, may be used to determine 263 -- which character set is in use and how it should be displayed. 265 -- The Host Resources System Group 266 -- 267 -- Implementation of this group is mandatory for all host systems. 269 hrSystemUptime OBJECT-TYPE 270 SYNTAX TimeTicks 271 MAX-ACCESS read-only 272 STATUS current 273 DESCRIPTION 274 "The amount of time since this host was last 275 initialized. Note that this is different from 276 sysUpTime in MIB-II [3] because sysUpTime is the 277 uptime of the network management portion of the 278 system." 279 ::= { hrSystem 1 } 281 hrSystemDate OBJECT-TYPE 282 SYNTAX DateAndTime 283 MAX-ACCESS read-write 284 STATUS current 285 DESCRIPTION 286 "The host's notion of the local date and time of 287 day." 288 ::= { hrSystem 2 } 290 hrSystemInitialLoadDevice OBJECT-TYPE 291 SYNTAX Integer32 (1..2147483647) 292 MAX-ACCESS read-write 293 STATUS current 294 DESCRIPTION 295 "The index of the hrDeviceEntry for the device from 296 which this host is configured to load its initial 297 operating system configuration." 298 ::= { hrSystem 3 } 300 hrSystemInitialLoadParameters OBJECT-TYPE 301 SYNTAX InternationalDisplayString (SIZE (0..128)) 302 MAX-ACCESS read-write 303 STATUS current 304 DESCRIPTION 305 "This object contains the parameters (e.g. a 306 pathname and parameter) supplied to the load device 307 when requesting the initial operating system 308 configuration from that device." 309 ::= { hrSystem 4 } 311 hrSystemNumUsers OBJECT-TYPE 312 SYNTAX Gauge32 313 MAX-ACCESS read-only 314 STATUS current 315 DESCRIPTION 316 "The number of user sessions for which this host is 317 storing state information. A session is a 318 collection of processes requiring a single act of 319 user authentication and possibly subject to 320 collective job control." 321 ::= { hrSystem 5 } 323 hrSystemProcesses OBJECT-TYPE 324 SYNTAX Gauge32 325 MAX-ACCESS read-only 326 STATUS current 327 DESCRIPTION 328 "The number of process contexts currently loaded or 329 running on this system." 330 ::= { hrSystem 6 } 332 hrSystemMaxProcesses OBJECT-TYPE 333 SYNTAX Integer32 (0..2147483647) 334 MAX-ACCESS read-only 335 STATUS current 336 DESCRIPTION 337 "The maximum number of process contexts this system 338 can support. If there is no fixed maximum, the 339 value should be zero. On systems that have a fixed 340 maximum, this object can help diagnose failures 341 that occur when this maximum is reached." 342 ::= { hrSystem 7 } 344 -- The Host Resources Storage Group 345 -- 346 -- Implementation of this group is mandatory for all host systems. 348 -- Registration for some storage types, for use with hrStorageType 349 hrStorageTypes OBJECT IDENTIFIER ::= { hrStorage 1 } 350 hrStorageOther OBJECT IDENTIFIER ::= { hrStorageTypes 1 } 351 hrStorageRam OBJECT IDENTIFIER ::= { hrStorageTypes 2 } 352 -- hrStorageVirtualMemory is temporary storage of swapped 353 -- or paged memory 354 hrStorageVirtualMemory OBJECT IDENTIFIER ::= { hrStorageTypes 3 } 355 hrStorageFixedDisk OBJECT IDENTIFIER ::= { hrStorageTypes 4 } 356 hrStorageRemovableDisk OBJECT IDENTIFIER ::= { hrStorageTypes 5 } 357 hrStorageFloppyDisk OBJECT IDENTIFIER ::= { hrStorageTypes 6 } 358 hrStorageCompactDisc OBJECT IDENTIFIER ::= { hrStorageTypes 7 } 359 hrStorageRamDisk OBJECT IDENTIFIER ::= { hrStorageTypes 8 } 361 hrMemorySize OBJECT-TYPE 362 SYNTAX KBytes 363 MAX-ACCESS read-only 364 STATUS current 365 DESCRIPTION 366 "The amount of physical main memory contained by 367 the host." 368 ::= { hrStorage 2 } 370 hrStorageTable OBJECT-TYPE 371 SYNTAX SEQUENCE OF HrStorageEntry 372 MAX-ACCESS not-accessible 373 STATUS current 374 DESCRIPTION 375 "The (conceptual) table of logical storage areas on 376 the host. 378 An entry shall be placed in the storage table for 379 each logical area of storage that is allocated and 380 has fixed resource limits. The amount of storage 381 represented in an entity is the amount actually 382 usable by the requesting entity, and excludes loss 383 due to formatting or file system reference 384 information. 386 These entries are associated with logical storage 387 areas, as might be seen by an application, rather 388 than physical storage entities which are typically 389 seen by an operating system. Storage such as tapes 390 and floppies without file systems on them are 391 typically not allocated in chunks by the operating 392 system to requesting applications, and therefore 393 shouldn't appear in this table. Examples of valid 394 storage for this table include disk partitions, 395 file systems, ram (for some architectures this is 396 further segmented into regular memory, extended 397 memory, and so on), backing store for virtual 398 memory (`swap space'). 400 This table is intended to be a useful diagnostic 401 for `out of memory' and `out of buffers' types of 402 failures. In addition, it can be a useful 403 performance monitoring tool for tracking memory, 404 disk, or buffer usage." 405 ::= { hrStorage 3 } 407 hrStorageEntry OBJECT-TYPE 408 SYNTAX HrStorageEntry 409 MAX-ACCESS not-accessible 410 STATUS current 411 DESCRIPTION 412 "A (conceptual) entry for one logical storage area 413 on the host. As an example, an instance of the 414 hrStorageType object might be named 415 hrStorageType.3" 416 INDEX { hrStorageIndex } 417 ::= { hrStorageTable 1 } 419 HrStorageEntry ::= SEQUENCE { 420 hrStorageIndex Integer32, 421 hrStorageType OBJECT IDENTIFIER, 422 hrStorageDescr DisplayString, 423 hrStorageAllocationUnits Integer32, 424 hrStorageSize Integer32, 425 hrStorageUsed Integer32, 426 hrStorageAllocationFailures Counter32 427 } 429 hrStorageIndex OBJECT-TYPE 430 SYNTAX Integer32 (1..2147483647) 431 MAX-ACCESS read-only 432 STATUS current 433 DESCRIPTION 434 "A unique value for each logical storage area 435 contained by the host." 436 ::= { hrStorageEntry 1 } 438 hrStorageType OBJECT-TYPE 439 SYNTAX OBJECT IDENTIFIER 440 MAX-ACCESS read-only 441 STATUS current 442 DESCRIPTION 443 "The type of storage represented by this entry." 444 ::= { hrStorageEntry 2 } 446 hrStorageDescr OBJECT-TYPE 447 SYNTAX DisplayString 448 MAX-ACCESS read-only 449 STATUS current 450 DESCRIPTION 451 "A description of the type and instance of the 452 storage described by this entry." 453 ::= { hrStorageEntry 3 } 455 hrStorageAllocationUnits OBJECT-TYPE 456 SYNTAX Integer32 (1..2147483647) 457 MAX-ACCESS read-only 458 STATUS current 459 DESCRIPTION 460 "The size, in bytes, of the data objects allocated 461 from this pool. If this entry is monitoring 462 sectors, blocks, buffers, or packets, for example, 463 this number will commonly be greater than one. 464 Otherwise this number will typically be one." 465 ::= { hrStorageEntry 4 } 467 hrStorageSize OBJECT-TYPE 468 SYNTAX Integer32 (0..2147483647) 469 MAX-ACCESS read-write 470 STATUS current 471 DESCRIPTION 472 "The size of the storage represented by this entry, 473 in units of hrStorageAllocationUnits." 474 ::= { hrStorageEntry 5 } 476 hrStorageUsed OBJECT-TYPE 477 SYNTAX Integer32 (0..2147483647) 478 MAX-ACCESS read-only 479 STATUS current 480 DESCRIPTION 481 "The amount of the storage represented by this 482 entry that is allocated, in units of 483 hrStorageAllocationUnits." 484 ::= { hrStorageEntry 6 } 486 hrStorageAllocationFailures OBJECT-TYPE 487 SYNTAX Counter32 488 MAX-ACCESS read-only 489 STATUS current 490 DESCRIPTION 491 "The number of requests for storage represented by 492 this entry that could not be honored due to not 493 enough storage. It should be noted that as this 494 object has a SYNTAX of Counter32, that it does not 495 have a defined initial value. However, it is 496 recommended that this object be initialized to 497 zero." 498 ::= { hrStorageEntry 7 } 500 -- The Host Resources Device Group 501 -- 502 -- Implementation of this group is mandatory for all host systems. 503 -- 504 -- The device group is useful for identifying and diagnosing the 505 -- devices on a system. The hrDeviceTable contains common 506 -- information for any type of device. In addition, some devices 507 -- have device-specific tables for more detailed information. More 508 -- such tables may be defined in the future for other device types. 510 -- Registration for some device types, for use with hrDeviceType 511 hrDeviceTypes OBJECT IDENTIFIER ::= { hrDevice 1 } 513 hrDeviceOther OBJECT IDENTIFIER ::= { hrDeviceTypes 1 } 514 hrDeviceUnknown OBJECT IDENTIFIER ::= { hrDeviceTypes 2 } 515 hrDeviceProcessor OBJECT IDENTIFIER ::= { hrDeviceTypes 3 } 516 hrDeviceNetwork OBJECT IDENTIFIER ::= { hrDeviceTypes 4 } 517 hrDevicePrinter OBJECT IDENTIFIER ::= { hrDeviceTypes 5 } 518 hrDeviceDiskStorage OBJECT IDENTIFIER ::= { hrDeviceTypes 6 } 519 hrDeviceVideo OBJECT IDENTIFIER ::= { hrDeviceTypes 10 } 520 hrDeviceAudio OBJECT IDENTIFIER ::= { hrDeviceTypes 11 } 521 hrDeviceCoprocessor OBJECT IDENTIFIER ::= { hrDeviceTypes 12 } 522 hrDeviceKeyboard OBJECT IDENTIFIER ::= { hrDeviceTypes 13 } 523 hrDeviceModem OBJECT IDENTIFIER ::= { hrDeviceTypes 14 } 524 hrDeviceParallelPort OBJECT IDENTIFIER ::= { hrDeviceTypes 15 } 525 hrDevicePointing OBJECT IDENTIFIER ::= { hrDeviceTypes 16 } 526 hrDeviceSerialPort OBJECT IDENTIFIER ::= { hrDeviceTypes 17 } 527 hrDeviceTape OBJECT IDENTIFIER ::= { hrDeviceTypes 18 } 528 hrDeviceClock OBJECT IDENTIFIER ::= { hrDeviceTypes 19 } 529 hrDeviceVolatileMemory OBJECT IDENTIFIER ::= { hrDeviceTypes 20 } 530 hrDeviceNonVolatileMemory OBJECT IDENTIFIER ::= { hrDeviceTypes 21 } 532 hrDeviceTable OBJECT-TYPE 533 SYNTAX SEQUENCE OF HrDeviceEntry 534 MAX-ACCESS not-accessible 535 STATUS current 536 DESCRIPTION 537 "The (conceptual) table of devices contained by the 538 host." 539 ::= { hrDevice 2 } 541 hrDeviceEntry OBJECT-TYPE 542 SYNTAX HrDeviceEntry 543 MAX-ACCESS not-accessible 544 STATUS current 545 DESCRIPTION 546 "A (conceptual) entry for one device contained by 547 the host. As an example, an instance of the 548 hrDeviceType object might be named hrDeviceType.3" 549 INDEX { hrDeviceIndex } 550 ::= { hrDeviceTable 1 } 552 HrDeviceEntry ::= SEQUENCE { 553 hrDeviceIndex Integer32, 554 hrDeviceType OBJECT IDENTIFIER, 555 hrDeviceDescr DisplayString, 556 hrDeviceID ProductID, 557 hrDeviceStatus INTEGER, 558 hrDeviceErrors Counter32 559 } 561 hrDeviceIndex OBJECT-TYPE 562 SYNTAX Integer32 (1..2147483647) 563 MAX-ACCESS read-only 564 STATUS current 565 DESCRIPTION 566 "A unique value for each device contained by the 567 host. The value for each device must remain 568 constant at least from one re-initialization of the 569 agent to the next re-initialization." 570 ::= { hrDeviceEntry 1 } 572 hrDeviceType OBJECT-TYPE 573 SYNTAX OBJECT IDENTIFIER 574 MAX-ACCESS read-only 575 STATUS current 576 DESCRIPTION 577 "An indication of the type of device. 579 If this value is `hrDeviceProcessor { hrDeviceTypes 580 3 }' then an entry exists in the hrProcessorTable 581 which corresponds to this device. 583 If this value is `hrDeviceNetwork { hrDeviceTypes 4 584 }', then an entry exists in the hrNetworkTable 585 which corresponds to this device. 587 If this value is `hrDevicePrinter { hrDeviceTypes 5 588 }', then an entry exists in the hrPrinterTable 589 which corresponds to this device. 591 If this value is `hrDeviceDiskStorage { 592 hrDeviceTypes 6 }', then an entry exists in the 593 hrDiskStorageTable which corresponds to this 594 device." 595 ::= { hrDeviceEntry 2 } 597 hrDeviceDescr OBJECT-TYPE 598 SYNTAX DisplayString (SIZE (0..64)) 599 MAX-ACCESS read-only 600 STATUS current 601 DESCRIPTION 602 "A textual description of this device, including 603 the device's manufacturer and revision, and 604 optionally, its serial number." 605 ::= { hrDeviceEntry 3 } 607 hrDeviceID OBJECT-TYPE 608 SYNTAX ProductID 609 MAX-ACCESS read-only 610 STATUS current 611 DESCRIPTION 612 "The product ID for this device." 613 ::= { hrDeviceEntry 4 } 615 hrDeviceStatus OBJECT-TYPE 616 SYNTAX INTEGER { 617 unknown(1), 618 running(2), 619 warning(3), 620 testing(4), 621 down(5) 622 } 623 MAX-ACCESS read-only 624 STATUS current 625 DESCRIPTION 626 "The current operational state of the device 627 described by this row of the table. A value 628 unknown(1) indicates that the current state of the 629 device is unknown. running(2) indicates that the 630 device is up and running and that no unusual error 631 conditions are known. The warning(3) state 632 indicates that agent has been informed of an 633 unusual error condition by the operational software 634 (e.g., a disk device driver) but that the device is 635 still 'operational'. An example would be high 636 number of soft errors on a disk. A value of 637 testing(4), indicates that the device is not 638 available for use because it is in the testing 639 state. The state of down(5) is used only when the 640 agent has been informed that the device is not 641 available for any use." 642 ::= { hrDeviceEntry 5 } 644 hrDeviceErrors OBJECT-TYPE 645 SYNTAX Counter32 646 MAX-ACCESS read-only 647 STATUS current 648 DESCRIPTION 649 "The number of errors detected on this device. It 650 should be noted that as this object has a SYNTAX 651 of Counter32, that it does not have a defined 652 initial value. However, it is recommended that 653 this object be initialized to zero." 654 ::= { hrDeviceEntry 6 } 656 hrProcessorTable OBJECT-TYPE 657 SYNTAX SEQUENCE OF HrProcessorEntry 658 MAX-ACCESS not-accessible 659 STATUS current 660 DESCRIPTION 661 "The (conceptual) table of processors contained by 662 the host. 664 Note that this table is potentially sparse: a 665 (conceptual) entry exists only if the correspondent 666 value of the hrDeviceType object is 667 `hrDeviceProcessor'." 668 ::= { hrDevice 3 } 670 hrProcessorEntry OBJECT-TYPE 671 SYNTAX HrProcessorEntry 672 MAX-ACCESS not-accessible 673 STATUS current 674 DESCRIPTION 675 "A (conceptual) entry for one processor contained 676 by the host. The hrDeviceIndex in the index 677 represents the entry in the hrDeviceTable that 678 corresponds to the hrProcessorEntry. 680 As an example of how objects in this table are 681 named, an instance of the hrProcessorFrwID object 682 might be named hrProcessorFrwID.3" 683 INDEX { hrDeviceIndex } 684 ::= { hrProcessorTable 1 } 686 HrProcessorEntry ::= SEQUENCE { 687 hrProcessorFrwID ProductID, 688 hrProcessorLoad Integer32 689 } 691 hrProcessorFrwID OBJECT-TYPE 692 SYNTAX ProductID 693 MAX-ACCESS read-only 694 STATUS current 695 DESCRIPTION 696 "The product ID of the firmware associated with the 697 processor." 698 ::= { hrProcessorEntry 1 } 700 hrProcessorLoad OBJECT-TYPE 701 SYNTAX Integer32 (0..100) 702 MAX-ACCESS read-only 703 STATUS current 704 DESCRIPTION 705 "The average, over the last minute, of the 706 percentage of time that this processor was not 707 idle." 708 ::= { hrProcessorEntry 2 } 710 hrNetworkTable OBJECT-TYPE 711 SYNTAX SEQUENCE OF HrNetworkEntry 712 MAX-ACCESS not-accessible 713 STATUS current 714 DESCRIPTION 715 "The (conceptual) table of network devices 716 contained by the host. 718 Note that this table is potentially sparse: a 719 (conceptual) entry exists only if the correspondent 720 value of the hrDeviceType object is 721 `hrDeviceNetwork'." 722 ::= { hrDevice 4 } 724 hrNetworkEntry OBJECT-TYPE 725 SYNTAX HrNetworkEntry 726 MAX-ACCESS not-accessible 727 STATUS current 728 DESCRIPTION 729 "A (conceptual) entry for one network device 730 contained by the host. The hrDeviceIndex in the 731 index represents the entry in the hrDeviceTable 732 that corresponds to the hrNetworkEntry. 734 As an example of how objects in this table are 735 named, an instance of the hrNetworkIfIndex object 736 might be named hrNetworkIfIndex.3" 737 INDEX { hrDeviceIndex } 738 ::= { hrNetworkTable 1 } 740 HrNetworkEntry ::= SEQUENCE { 741 hrNetworkIfIndex Integer32 742 } 744 hrNetworkIfIndex OBJECT-TYPE 745 SYNTAX Integer32 746 MAX-ACCESS read-only 747 STATUS current 748 DESCRIPTION 749 "The value of ifIndex which corresponds to this 750 network device. If this network device is not contained 751 in the mib2.ifTable, then 0 shall be returned for this 752 variable." 753 ::= { hrNetworkEntry 1 } 755 hrPrinterTable OBJECT-TYPE 756 SYNTAX SEQUENCE OF HrPrinterEntry 757 MAX-ACCESS not-accessible 758 STATUS current 759 DESCRIPTION 760 "The (conceptual) table of printers local to the 761 host. 763 Note that this table is potentially sparse: a 764 (conceptual) entry exists only if the correspondent 765 value of the hrDeviceType object is 766 `hrDevicePrinter'." 767 ::= { hrDevice 5 } 769 hrPrinterEntry OBJECT-TYPE 770 SYNTAX HrPrinterEntry 771 MAX-ACCESS not-accessible 772 STATUS current 773 DESCRIPTION 774 "A (conceptual) entry for one printer local to the 775 host. The hrDeviceIndex in the index represents 776 the entry in the hrDeviceTable that corresponds to 777 the hrPrinterEntry. 779 As an example of how objects in this table are 780 named, an instance of the hrPrinterStatus object 781 might be named hrPrinterStatus.3" 782 INDEX { hrDeviceIndex } 783 ::= { hrPrinterTable 1 } 785 HrPrinterEntry ::= SEQUENCE { 786 hrPrinterStatus INTEGER, 787 hrPrinterDetectedErrorState BITS 788 } 790 hrPrinterStatus OBJECT-TYPE 791 SYNTAX INTEGER { 792 other(1), 793 unknown(2), 794 idle(3), 795 printing(4), 796 warmup(5) 797 } 798 MAX-ACCESS read-only 799 STATUS current 800 DESCRIPTION 801 "The current status of this printer device. When 802 in the idle(3), printing(4), or warmup(5) state, 803 the corresponding hrDeviceStatus should be 804 running(2) or warning(3). When in the unknown(2) 805 state, the corresponding hrDeviceStatus should be 806 unknown(1)." 807 ::= { hrPrinterEntry 1 } 809 hrPrinterDetectedErrorState OBJECT-TYPE 810 -- SYNTAX BITS (0..128) { 811 SYNTAX BITS { 812 lowPaper(0), 813 noPaper(1), 814 lowToner(2), 815 noToner(3), 816 doorOpen(4), 817 jammed(5), 818 offline(6), 819 serviceRequested(7), 821 inputTrayMissing(8), 822 outputTrayMissing(9), 823 markerSupplyMissing(10), 824 outputNearFull(11), 825 outputFull(12), 826 inputTrayEmpty(13), 827 overduePreventMaint(14) 828 } 829 MAX-ACCESS read-only 830 STATUS current 831 DESCRIPTION 832 "This object represents any error conditions 833 detected by the printer. The error conditions are 834 encoded as bits in an octet string, with the 835 following definitions: 837 Condition Bit # hrDeviceStatus 839 lowPaper 0 warning(3) or down(5) 840 noPaper 1 warning(3) or down(5) 841 lowToner 2 warning(3) or down(5) 842 noToner 3 warning(3) or down(5) 843 doorOpen 4 warning(3) or down(5) 844 jammed 5 warning(3) or down(5) 845 offline 6 warning(3) or down(5) 846 serviceRequested 7 warning(3) or down(5) 848 inputTrayMissing 8 warning(3) or down(5) 849 outputTrayMissing 9 warning(3) or down(5) 850 markerSupplyMissing 10 warning(3) or down(5) 851 outputNearFull 11 warning(3) or down(5) 852 outputFull 12 warning(3) or down(5) 853 inputTrayEmpty 13 warning(3) or down(5) 854 overduePreventMaint 14 warning(3) or down(5) 856 If multiple conditions are currently detected and 857 the hrDeviceStatus would not otherwise be 858 unknown(1) or testing(4), the hrDeviceStatus shall 859 correspond to the worst state of those indicated, 860 where down(5) is worse than warning(3) which is 861 worse than running(2). 863 Bits are numbered starting with the most 864 significant bit of the first byte being bit 0, the 865 least significant bit of the first byte being bit 866 7, the most significant bit of the second byte 867 being bit 8, and so on. A one bit encodes that 868 the condition was detected, while a zero bit 869 encodes that the condition was not detected. 871 This object is useful for alerting an operator to 872 specific warning or error conditions that may 873 occur, especially those requiring human 874 intervention. 876 Because error bits 8 through 14 can indicate a printer 877 that is still functioning, the corresponding 878 (recommended) printer hrDeviceStatus can be either 879 warning(3) or down(5). 881 New bits may be defined by standards-track MIB modules 882 but the maximum size of instances of this variable 883 should be 128 octets." 884 ::= { hrPrinterEntry 2 } 886 hrDiskStorageTable OBJECT-TYPE 887 SYNTAX SEQUENCE OF HrDiskStorageEntry 888 MAX-ACCESS not-accessible 889 STATUS current 890 DESCRIPTION 891 "The (conceptual) table of long-term storage 892 devices contained by the host. In particular, disk 893 devices accessed remotely over a network are not 894 included here. 896 Note that this table is potentially sparse: a 897 (conceptual) entry exists only if the correspondent 898 value of the hrDeviceType object is 899 `hrDeviceDiskStorage'." 900 ::= { hrDevice 6 } 902 hrDiskStorageEntry OBJECT-TYPE 903 SYNTAX HrDiskStorageEntry 904 MAX-ACCESS not-accessible 905 STATUS current 906 DESCRIPTION 907 "A (conceptual) entry for one long-term storage 908 device contained by the host. The hrDeviceIndex in 909 the index represents the entry in the hrDeviceTable 910 that corresponds to the hrDiskStorageEntry. As an 911 example, an instance of the hrDiskStorageCapacity 912 object might be named hrDiskStorageCapacity.3" 913 INDEX { hrDeviceIndex } 914 ::= { hrDiskStorageTable 1 } 916 HrDiskStorageEntry ::= SEQUENCE { 917 hrDiskStorageAccess INTEGER, 918 hrDiskStorageMedia INTEGER, 919 hrDiskStorageRemoveble Boolean, 920 hrDiskStorageCapacity KBytes 921 } 923 hrDiskStorageAccess OBJECT-TYPE 924 SYNTAX INTEGER { 925 readWrite(1), 926 readOnly(2) 927 } 928 MAX-ACCESS read-only 929 STATUS current 930 DESCRIPTION 931 "An indication if this long-term storage device is 932 readable and writable or only readable. This 933 should reflect the media type, any write-protect 934 mechanism, and any device configuration that 935 affects the entire device." 936 ::= { hrDiskStorageEntry 1 } 938 hrDiskStorageMedia OBJECT-TYPE 939 SYNTAX INTEGER { 940 other(1), 941 unknown(2), 942 hardDisk(3), 943 floppyDisk(4), 944 opticalDiskROM(5), 945 opticalDiskWORM(6), -- Write Once Read Many 946 opticalDiskRW(7), 947 ramDisk(8) 948 } 949 MAX-ACCESS read-only 950 STATUS current 951 DESCRIPTION 952 "An indication of the type of media used in this 953 long-term storage device." 954 ::= { hrDiskStorageEntry 2 } 956 hrDiskStorageRemoveble OBJECT-TYPE 957 SYNTAX Boolean 958 MAX-ACCESS read-only 959 STATUS current 960 DESCRIPTION 961 "Denotes whether or not the disk media may be 962 removed from the drive." 963 ::= { hrDiskStorageEntry 3 } 965 hrDiskStorageCapacity OBJECT-TYPE 966 SYNTAX KBytes 967 MAX-ACCESS read-only 968 STATUS current 969 DESCRIPTION 970 "The total size for this long-term storage device." 971 ::= { hrDiskStorageEntry 4 } 973 hrPartitionTable OBJECT-TYPE 974 SYNTAX SEQUENCE OF HrPartitionEntry 975 MAX-ACCESS not-accessible 976 STATUS current 977 DESCRIPTION 978 "The (conceptual) table of partitions for long-term 979 storage devices contained by the host. In 980 particular, partitions accessed remotely over a 981 network are not included here." 982 ::= { hrDevice 7 } 984 hrPartitionEntry OBJECT-TYPE 985 SYNTAX HrPartitionEntry 986 MAX-ACCESS not-accessible 987 STATUS current 988 DESCRIPTION 989 "A (conceptual) entry for one partition. The 990 hrDeviceIndex in the index represents the entry in 991 the hrDeviceTable that corresponds to the 992 hrPartitionEntry. 994 As an example of how objects in this table are 995 named, an instance of the hrPartitionSize object 996 might be named hrPartitionSize.3.1" 997 INDEX { hrDeviceIndex, hrPartitionIndex } 998 ::= { hrPartitionTable 1 } 1000 HrPartitionEntry ::= SEQUENCE { 1001 hrPartitionIndex Integer32, 1002 hrPartitionLabel InternationalDisplayString, 1003 hrPartitionID OCTET STRING, 1004 hrPartitionSize KBytes, 1005 hrPartitionFSIndex Integer32 1006 } 1008 hrPartitionIndex OBJECT-TYPE 1009 SYNTAX Integer32 (1..2147483647) 1010 MAX-ACCESS read-only 1011 STATUS current 1012 DESCRIPTION 1013 "A unique value for each partition on this long- 1014 term storage device. The value for each long-term 1015 storage device must remain constant at least from 1016 one re-initialization of the agent to the next re- 1018 initialization." 1019 ::= { hrPartitionEntry 1 } 1021 hrPartitionLabel OBJECT-TYPE 1022 SYNTAX InternationalDisplayString (SIZE (0..128)) 1023 MAX-ACCESS read-only 1024 STATUS current 1025 DESCRIPTION 1026 "A textual description of this partition." 1027 ::= { hrPartitionEntry 2 } 1029 hrPartitionID OBJECT-TYPE 1030 SYNTAX OCTET STRING 1031 MAX-ACCESS read-only 1032 STATUS current 1033 DESCRIPTION 1034 "A descriptor which uniquely represents this 1035 partition to the responsible operating system. On 1036 some systems, this might take on a binary 1037 representation." 1038 ::= { hrPartitionEntry 3 } 1040 hrPartitionSize OBJECT-TYPE 1041 SYNTAX KBytes 1042 MAX-ACCESS read-only 1043 STATUS current 1044 DESCRIPTION 1045 "The size of this partition." 1046 ::= { hrPartitionEntry 4 } 1048 hrPartitionFSIndex OBJECT-TYPE 1049 SYNTAX Integer32 (0..2147483647) 1050 MAX-ACCESS read-only 1051 STATUS current 1052 DESCRIPTION 1053 "The index of the file system mounted on this 1054 partition. If no file system is mounted on this 1055 partition, then this value shall be zero. Note 1056 that multiple partitions may point to one file 1057 system, denoting that that file system resides on 1058 those partitions. Multiple file systems may not 1059 reside on one partition." 1060 ::= { hrPartitionEntry 5 } 1062 -- The File System Table 1063 hrFSTable OBJECT-TYPE 1064 SYNTAX SEQUENCE OF HrFSEntry 1066 MAX-ACCESS not-accessible 1067 STATUS current 1068 DESCRIPTION 1069 "The (conceptual) table of file systems local to 1070 this host or remotely mounted from a file server. 1071 File systems that are in only one user's 1072 environment on a multi-user system will not be 1073 included in this table." 1074 ::= { hrDevice 8 } 1076 hrFSEntry OBJECT-TYPE 1077 SYNTAX HrFSEntry 1078 MAX-ACCESS not-accessible 1079 STATUS current 1080 DESCRIPTION 1081 "A (conceptual) entry for one file system local to 1082 this host or remotely mounted from a file server. 1083 File systems that are in only one user's 1084 environment on a multi-user system will not be 1085 included in this table. 1087 As an example of how objects in this table are 1088 named, an instance of the hrFSMountPoint object 1089 might be named hrFSMountPoint.3" 1090 INDEX { hrFSIndex } 1091 ::= { hrFSTable 1 } 1093 -- Registration for some popular File System types, 1094 -- for use with hrFSType. 1096 hrFSTypes OBJECT IDENTIFIER ::= { hrDevice 9 } 1098 hrFSOther OBJECT IDENTIFIER ::= { hrFSTypes 1 } 1099 hrFSUnknown OBJECT IDENTIFIER ::= { hrFSTypes 2 } 1100 hrFSBerkeleyFFS OBJECT IDENTIFIER ::= { hrFSTypes 3 } 1101 hrFSSys5FS OBJECT IDENTIFIER ::= { hrFSTypes 4 } 1102 -- DOS 1103 hrFSFat OBJECT IDENTIFIER ::= { hrFSTypes 5 } 1104 -- OS/2 High Performance File System 1105 hrFSHPFS OBJECT IDENTIFIER ::= { hrFSTypes 6 } 1106 -- Macintosh Hierarchical File System 1107 hrFSHFS OBJECT IDENTIFIER ::= { hrFSTypes 7 } 1109 -- Macintosh File System 1110 hrFSMFS OBJECT IDENTIFIER ::= { hrFSTypes 8 } 1111 -- Windows NT 1112 hrFSNTFS OBJECT IDENTIFIER ::= { hrFSTypes 9 } 1114 hrFSVNode OBJECT IDENTIFIER ::= { hrFSTypes 10 } 1115 hrFSJournaled OBJECT IDENTIFIER ::= { hrFSTypes 11 } 1116 -- CD File systems 1117 hrFSiso9660 OBJECT IDENTIFIER ::= { hrFSTypes 12 } 1118 hrFSRockRidge OBJECT IDENTIFIER ::= { hrFSTypes 13 } 1120 hrFSNFS OBJECT IDENTIFIER ::= { hrFSTypes 14 } 1121 hrFSNetware OBJECT IDENTIFIER ::= { hrFSTypes 15 } 1122 -- Andrew File System 1123 hrFSAFS OBJECT IDENTIFIER ::= { hrFSTypes 16 } 1124 -- OSF DCE Distributed File System 1125 hrFSDFS OBJECT IDENTIFIER ::= { hrFSTypes 17 } 1126 hrFSAppleshare OBJECT IDENTIFIER ::= { hrFSTypes 18 } 1127 hrFSRFS OBJECT IDENTIFIER ::= { hrFSTypes 19 } 1128 -- Data General 1129 hrFSDGCFS OBJECT IDENTIFIER ::= { hrFSTypes 20 } 1130 -- SVR4 Boot File System 1131 hrFSBFS OBJECT IDENTIFIER ::= { hrFSTypes 21 } 1133 HrFSEntry ::= SEQUENCE { 1134 hrFSIndex Integer32, 1135 hrFSMountPoint InternationalDisplayString, 1136 hrFSRemoteMountPoint InternationalDisplayString, 1137 hrFSType OBJECT IDENTIFIER, 1138 hrFSAccess INTEGER, 1139 hrFSBootable Boolean, 1140 hrFSStorageIndex Integer32, 1141 hrFSLastFullBackupDate DateAndTime, 1142 hrFSLastPartialBackupDate DateAndTime 1143 } 1145 hrFSIndex OBJECT-TYPE 1146 SYNTAX Integer32 (1..2147483647) 1147 MAX-ACCESS read-only 1148 STATUS current 1149 DESCRIPTION 1150 "A unique value for each file system local to this 1151 host. The value for each file system must remain 1152 constant at least from one re-initialization of 1153 the agent to the next re-initialization." 1154 ::= { hrFSEntry 1 } 1156 hrFSMountPoint OBJECT-TYPE 1157 SYNTAX InternationalDisplayString (SIZE(0..128)) 1158 MAX-ACCESS read-only 1159 STATUS current 1161 DESCRIPTION 1162 "The path name of the root of this file system." 1163 ::= { hrFSEntry 2 } 1165 hrFSRemoteMountPoint OBJECT-TYPE 1166 SYNTAX InternationalDisplayString (SIZE(0..128)) 1167 MAX-ACCESS read-only 1168 STATUS current 1169 DESCRIPTION 1170 "A description of the name and/or address of the 1171 server that this file system is mounted from. 1172 This may also include parameters such as the mount 1173 point on the remote file system. If this is not a 1174 remote file system, this string should have a 1175 length of zero." 1176 ::= { hrFSEntry 3 } 1178 hrFSType OBJECT-TYPE 1179 SYNTAX OBJECT IDENTIFIER 1180 MAX-ACCESS read-only 1181 STATUS current 1182 DESCRIPTION 1183 "The value of this object identifies the type of 1184 this file system." 1185 ::= { hrFSEntry 4 } 1187 hrFSAccess OBJECT-TYPE 1188 SYNTAX INTEGER { 1189 readWrite(1), 1190 readOnly(2) 1191 } 1192 MAX-ACCESS read-only 1193 STATUS current 1194 DESCRIPTION 1195 "An indication if this file system is logically 1196 configured by the operating system to be readable 1197 and writable or only readable. This does not 1198 represent any local access-control policy, except 1199 one that is applied to the file system as a whole." 1200 ::= { hrFSEntry 5 } 1202 hrFSBootable OBJECT-TYPE 1203 SYNTAX Boolean 1204 MAX-ACCESS read-only 1205 STATUS current 1206 DESCRIPTION 1207 "A flag indicating whether this file system is 1208 bootable." 1210 ::= { hrFSEntry 6 } 1212 hrFSStorageIndex OBJECT-TYPE 1213 SYNTAX Integer32 (0..2147483647) 1214 MAX-ACCESS read-only 1215 STATUS current 1216 DESCRIPTION 1217 "The index of the hrStorageEntry that represents 1218 information about this file system. If there is 1219 no such information available, then this value 1220 shall be zero. The relevant storage entry will be 1221 useful in tracking the percent usage of this file 1222 system and diagnosing errors that may occur when 1223 it runs out of space." 1224 ::= { hrFSEntry 7 } 1226 hrFSLastFullBackupDate OBJECT-TYPE 1227 SYNTAX DateAndTime 1228 MAX-ACCESS read-write 1229 STATUS current 1230 DESCRIPTION 1231 "The last date at which this complete file system 1232 was copied to another storage device for backup. 1233 This information is useful for ensuring that 1234 backups are being performed regularly. 1236 If this information is not known, then this 1237 variable shall have the value corresponding to 1238 January 1, year 0000, 00:00:00.0, which is encoded 1239 as (hex)'00 00 01 01 00 00 00 00'." 1241 ::= { hrFSEntry 8 } 1243 hrFSLastPartialBackupDate OBJECT-TYPE 1244 SYNTAX DateAndTime 1245 MAX-ACCESS read-write 1246 STATUS current 1247 DESCRIPTION 1248 "The last date at which a portion of this file 1249 system was copied to another storage device for 1250 backup. This information is useful for ensuring 1251 that backups are being performed regularly. 1253 If this information is not known, then this 1254 variable shall have the value corresponding to 1255 January 1, year 0000, 00:00:00.0, which is encoded 1256 as (hex)'00 00 01 01 00 00 00 00'." 1257 ::= { hrFSEntry 9 } 1259 -- The Host Resources Running Software Group 1260 -- 1261 -- Implementation of this group is optional. 1262 -- 1263 -- The hrSWRunTable contains an entry for each distinct piece of 1264 -- software that is running or loaded into physical or virtual 1265 -- memory in preparation for running. This includes the host's 1266 -- operating system, device drivers, and applications. 1268 hrSWOSIndex OBJECT-TYPE 1269 SYNTAX Integer32 (1..2147483647) 1270 MAX-ACCESS read-only 1271 STATUS current 1272 DESCRIPTION 1273 "The value of the hrSWRunIndex for the 1274 hrSWRunEntry that represents the primary operating 1275 system running on this host. This object is 1276 useful for quickly and uniquely identifying that 1277 primary operating system." 1278 ::= { hrSWRun 1 } 1280 hrSWRunTable OBJECT-TYPE 1281 SYNTAX SEQUENCE OF HrSWRunEntry 1282 MAX-ACCESS not-accessible 1283 STATUS current 1284 DESCRIPTION 1285 "The (conceptual) table of software running on the 1286 host." 1287 ::= { hrSWRun 2 } 1289 hrSWRunEntry OBJECT-TYPE 1290 SYNTAX HrSWRunEntry 1291 MAX-ACCESS not-accessible 1292 STATUS current 1293 DESCRIPTION 1294 "A (conceptual) entry for one piece of software 1295 running on the host Note that because the installed 1296 software table only contains information for 1297 software stored locally on this host, not every 1298 piece of running software will be found in the 1299 installed software table. This is true of software 1300 that was loaded and run from a non-local source, 1301 such as a network-mounted file system. 1303 As an example of how objects in this table are 1304 named, an instance of the hrSWRunName object might 1305 be named hrSWRunName.1287" 1306 INDEX { hrSWRunIndex } 1307 ::= { hrSWRunTable 1 } 1309 HrSWRunEntry ::= SEQUENCE { 1310 hrSWRunIndex Integer32, 1311 hrSWRunName InternationalDisplayString, 1312 hrSWRunID ProductID, 1313 hrSWRunPath InternationalDisplayString, 1314 hrSWRunParameters InternationalDisplayString, 1315 hrSWRunType INTEGER, 1316 hrSWRunStatus INTEGER 1317 } 1319 hrSWRunIndex OBJECT-TYPE 1320 SYNTAX Integer32 (1..2147483647) 1321 MAX-ACCESS read-only 1322 STATUS current 1323 DESCRIPTION 1324 "A unique value for each piece of software running 1325 on the host. Wherever possible, this should be the 1326 system's native, unique identification number." 1327 ::= { hrSWRunEntry 1 } 1329 hrSWRunName OBJECT-TYPE 1330 SYNTAX InternationalDisplayString (SIZE (0..64)) 1331 MAX-ACCESS read-only 1332 STATUS current 1333 DESCRIPTION 1334 "A textual description of this running piece of 1335 software, including the manufacturer, revision, 1336 and the name by which it is commonly known. If 1337 this software was installed locally, this should be 1338 the same string as used in the corresponding 1339 hrSWInstalledName." 1340 ::= { hrSWRunEntry 2 } 1342 hrSWRunID OBJECT-TYPE 1343 SYNTAX ProductID 1344 MAX-ACCESS read-only 1345 STATUS current 1346 DESCRIPTION 1347 "The product ID of this running piece of software." 1348 ::= { hrSWRunEntry 3 } 1350 hrSWRunPath OBJECT-TYPE 1351 SYNTAX InternationalDisplayString (SIZE(0..128)) 1352 MAX-ACCESS read-only 1353 STATUS current 1354 DESCRIPTION 1356 "A description of the location on long-term storage 1357 (e.g. a disk drive) from which this software was 1358 loaded." 1359 ::= { hrSWRunEntry 4 } 1361 hrSWRunParameters OBJECT-TYPE 1362 SYNTAX InternationalDisplayString (SIZE(0..128)) 1363 MAX-ACCESS read-only 1364 STATUS current 1365 DESCRIPTION 1366 "A description of the parameters supplied to this 1367 software when it was initially loaded." 1368 ::= { hrSWRunEntry 5 } 1370 hrSWRunType OBJECT-TYPE 1371 SYNTAX INTEGER { 1372 unknown(1), 1373 operatingSystem(2), 1374 deviceDriver(3), 1375 application(4) 1376 } 1377 MAX-ACCESS read-only 1378 STATUS current 1379 DESCRIPTION 1380 "The type of this software." 1381 ::= { hrSWRunEntry 6 } 1383 hrSWRunStatus OBJECT-TYPE 1384 SYNTAX INTEGER { 1385 running(1), 1386 runnable(2), -- waiting for resource (CPU, memory, IO) 1387 notRunnable(3), -- loaded but waiting for event 1388 invalid(4) -- not loaded 1389 } 1390 MAX-ACCESS read-write 1391 STATUS current 1392 DESCRIPTION 1393 "The status of this running piece of software. 1394 Setting this value to invalid(4) shall cause this 1395 software to stop running and to be unloaded." 1396 ::= { hrSWRunEntry 7 } 1398 -- The Host Resources Running Software Performance Group 1399 -- Implementation of this group is optional. 1400 -- 1401 -- The hrSWRunPerfTable contains an entry corresponding to 1402 -- each entry in the hrSWRunTable. 1404 hrSWRunPerfTable OBJECT-TYPE 1405 SYNTAX SEQUENCE OF HrSWRunPerfEntry 1406 MAX-ACCESS not-accessible 1407 STATUS current 1408 DESCRIPTION 1409 "The (conceptual) table of running software 1410 performance metrics." 1411 ::= { hrSWRunPerf 1 } 1413 hrSWRunPerfEntry OBJECT-TYPE 1414 SYNTAX HrSWRunPerfEntry 1415 MAX-ACCESS not-accessible 1416 STATUS current 1417 DESCRIPTION 1418 "A (conceptual) entry containing software 1419 performance metrics. As an example, an instance 1420 of the hrSWRunPerfCPU object might be named 1421 hrSWRunPerfCPU.1287" 1422 INDEX { hrSWRunIndex } -- This table augments information in 1423 -- the hrSWRunTable. 1424 ::= { hrSWRunPerfTable 1 } 1426 HrSWRunPerfEntry ::= SEQUENCE { 1427 hrSWRunPerfCPU Integer32, 1428 hrSWRunPerfMem KBytes 1429 } 1430 hrSWRunPerfCPU OBJECT-TYPE 1431 SYNTAX Integer32 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "The number of centi-seconds of the total system's 1436 CPU resources consumed by this process. Note that 1437 on a multi-processor system, this value may 1438 increment by more than one centi-second in one 1439 centi-second of real (wall clock) time." 1440 ::= { hrSWRunPerfEntry 1 } 1442 hrSWRunPerfMem OBJECT-TYPE 1443 SYNTAX KBytes 1444 MAX-ACCESS read-only 1445 STATUS current 1446 DESCRIPTION 1447 "The total amount of real system memory allocated 1448 to this process." 1449 ::= { hrSWRunPerfEntry 2 } 1451 -- The Host Resources Installed Software Group 1452 -- 1453 -- Implementation of this group is optional. 1454 -- 1455 -- The hrSWInstalledTable contains an entry for each piece 1456 -- of software installed in long-term storage (e.g. a disk 1457 -- drive) locally on this host. Note that this does not 1458 -- include software loadable remotely from a network 1459 -- server. 1460 -- 1461 -- This table is useful for identifying and inventorying 1462 -- software on a host and for diagnosing incompatibility 1463 -- and version mismatch problems between various pieces 1464 -- of hardware and software. 1465 -- 1466 -- Included in the definition of "software" are patches and 1467 -- software packages. Operating systems which provide a unified 1468 -- set of utilities for adding and removing software components, 1469 -- or a unified administrative location for their specification, 1470 -- usually provide the necessary information for the implementation 1471 -- of the hrSWInstalledTable. 1473 hrSWInstalledLastChange OBJECT-TYPE 1474 SYNTAX TimeTicks 1475 MAX-ACCESS read-only 1476 STATUS current 1477 DESCRIPTION 1478 "The value of sysUpTime when an entry in the 1479 hrSWInstalledTable was last added, renamed, or 1480 deleted. Because this table is likely to contain 1481 many entries, polling of this object allows a 1482 management station to determine when re-downloading 1483 of the table might be useful." 1484 ::= { hrSWInstalled 1 } 1486 hrSWInstalledLastUpdateTime OBJECT-TYPE 1487 SYNTAX TimeTicks 1488 MAX-ACCESS read-only 1489 STATUS current 1490 DESCRIPTION 1491 "The value of sysUpTime when the hrSWInstalledTable 1492 was last completely updated. Because caching of 1493 this data will be a popular implementation 1494 strategy, retrieval of this object allows a 1495 management station to obtain a guarantee that no 1496 data in this table is older than the indicated 1497 time." 1498 ::= { hrSWInstalled 2 } 1500 hrSWInstalledTable OBJECT-TYPE 1501 SYNTAX SEQUENCE OF HrSWInstalledEntry 1502 MAX-ACCESS not-accessible 1503 STATUS current 1504 DESCRIPTION 1505 "The (conceptual) table of software installed on 1506 this host." 1507 ::= { hrSWInstalled 3 } 1509 hrSWInstalledEntry OBJECT-TYPE 1510 SYNTAX HrSWInstalledEntry 1511 MAX-ACCESS not-accessible 1512 STATUS current 1513 DESCRIPTION 1514 "A (conceptual) entry for a piece of software 1515 installed on this host. 1517 As an example of how objects in this table are 1518 named, an instance of the hrSWInstalledName object 1519 might be named hrSWInstalledName.96" 1520 INDEX { hrSWInstalledIndex } 1521 ::= { hrSWInstalledTable 1 } 1523 HrSWInstalledEntry ::= SEQUENCE { 1524 hrSWInstalledIndex Integer32, 1525 hrSWInstalledName InternationalDisplayString, 1526 hrSWInstalledID ProductID, 1527 hrSWInstalledType INTEGER, 1528 hrSWInstalledDate DateAndTime 1529 } 1531 hrSWInstalledIndex OBJECT-TYPE 1532 SYNTAX Integer32 (1..2147483647) 1533 MAX-ACCESS read-only 1534 STATUS current 1535 DESCRIPTION 1536 "A unique value for each piece of software 1537 installed on the host. This value shall be in the 1538 range from 1 to the number of pieces of software 1539 installed on the host." 1540 ::= { hrSWInstalledEntry 1 } 1542 hrSWInstalledName OBJECT-TYPE 1543 SYNTAX InternationalDisplayString (SIZE (0..64)) 1544 MAX-ACCESS read-only 1545 STATUS current 1546 DESCRIPTION 1547 "A textual description of this installed piece of 1548 software, including the manufacturer, revision, the 1549 name by which it is commonly known, and optionally, 1550 its serial number." 1551 ::= { hrSWInstalledEntry 2 } 1553 hrSWInstalledID OBJECT-TYPE 1555 SYNTAX ProductID 1556 MAX-ACCESS read-only 1557 STATUS current 1558 DESCRIPTION 1559 "The product ID of this installed piece of 1560 software." 1561 ::= { hrSWInstalledEntry 3 } 1563 hrSWInstalledType OBJECT-TYPE 1564 SYNTAX INTEGER { 1565 unknown(1), 1566 operatingSystem(2), 1567 deviceDriver(3), 1568 application(4) 1569 } 1570 MAX-ACCESS read-only 1571 STATUS current 1572 DESCRIPTION 1573 "The type of this software." 1574 ::= { hrSWInstalledEntry 4 } 1576 hrSWInstalledDate OBJECT-TYPE 1577 SYNTAX DateAndTime 1578 MAX-ACCESS read-only 1579 STATUS current 1580 DESCRIPTION 1581 "The last-modification date of this application as 1582 it would appear in a directory listing. If the 1583 underlying system supports this variable, but the date 1584 of a particular entry is indeterminable, then January 1, 1585 year 0000, 00:00:00.0, which is encoded 1586 (hex)'00 00 01 01 00 00 00 00, shall be returned." 1587 ::= { hrSWInstalledEntry 5 } 1589 -- Conformance Macros 1591 hrMIBCompliances OBJECT IDENTIFIER ::= { hrConformance 1 } 1592 hrMIBGroups OBJECT IDENTIFIER ::= { hrConformance 2 } 1594 hrMIBCompliance MODULE-COMPLIANCE 1595 STATUS current 1596 DESCRIPTION 1597 "Describes the requirements for conformance to the Host 1598 Resources MIB" 1599 MODULE 1600 MANDATORY-GROUPS { hrSystemGroup, hrStorageGroup, hrDeviceGroup } 1601 GROUP hrSWRunGroup 1602 DESCRIPTION 1603 "Optional running software group" 1604 GROUP hrSWInstalledGroup 1605 DESCRIPTION 1606 "Optional installed software group" 1607 ::= { hrMIBCompliances 1 } 1609 hrSystemGroup OBJECT-GROUP 1610 OBJECTS { 1611 hrSystemUptime, 1612 hrSystemDate, 1613 hrSystemInitialLoadDevice, 1614 hrSystemInitialLoadParameters, 1615 hrSystemNumUsers, 1616 hrSystemProcesses, 1617 hrSystemMaxProcesses 1618 } 1619 STATUS current 1620 DESCRIPTION 1621 "The System Group" 1622 ::= { hrMIBGroups 1 } 1624 hrStorageGroup OBJECT-GROUP 1625 OBJECTS { 1626 hrMemorySize, 1627 hrStorageIndex, 1628 hrStorageType, 1629 hrStorageDescr, 1630 hrStorageAllocationUnits, 1631 hrStorageSize, 1632 hrStorageUsed, 1633 hrStorageAllocationFailures 1634 } 1635 STATUS current 1636 DESCRIPTION 1637 "The Storage Group" 1638 ::= { hrMIBGroups 2 } 1640 hrDeviceGroup OBJECT-GROUP 1641 OBJECTS { 1642 hrDeviceIndex, 1643 hrDeviceType, 1644 hrDeviceDescr, 1645 hrDeviceID, 1646 hrDeviceStatus, 1647 hrDeviceErrors, 1648 hrProcessorFrwID, 1649 hrProcessorLoad, 1650 hrNetworkIfIndex, 1651 hrPrinterStatus, 1652 hrPrinterDetectedErrorState, 1653 hrDiskStorageAccess, 1654 hrDiskStorageMedia, 1655 hrDiskStorageRemoveble, 1656 hrDiskStorageCapacity, 1657 hrPartitionIndex, 1658 hrPartitionLabel, 1659 hrPartitionID, 1660 hrPartitionSize, 1661 hrPartitionFSIndex, 1662 hrFSIndex, 1663 hrFSMountPoint, 1664 hrFSRemoteMountPoint, 1665 hrFSType, 1666 hrFSAccess, 1667 hrFSBootable, 1668 hrFSStorageIndex, 1669 hrFSLastFullBackupDate, 1670 hrFSLastPartialBackupDate 1671 } 1672 STATUS current 1673 DESCRIPTION 1674 "The Device Group" 1675 ::= { hrMIBGroups 3 } 1677 hrSWRunGroup OBJECT-GROUP 1678 OBJECTS { 1679 hrSWOSIndex, 1680 hrSWRunIndex, 1681 hrSWRunName, 1682 hrSWRunID, 1683 hrSWRunPath, 1684 hrSWRunParameters, 1685 hrSWRunType, 1686 hrSWRunStatus, 1687 hrSWRunPerfCPU, 1688 hrSWRunPerfMem 1689 } 1690 STATUS current 1691 DESCRIPTION 1692 "The optional Running Software Group" 1693 ::= { hrMIBGroups 4 } 1695 hrSWInstalledGroup OBJECT-GROUP 1696 OBJECTS { 1697 hrSWInstalledLastChange, 1698 hrSWInstalledLastUpdateTime, 1699 hrSWInstalledIndex, 1700 hrSWInstalledName, 1701 hrSWInstalledID, 1702 hrSWInstalledType, 1703 hrSWInstalledDate 1704 } 1705 STATUS current 1706 DESCRIPTION 1707 "The optional Installed Software Group" 1708 ::= { hrMIBGroups 5 } 1710 END 1712 4. References 1714 [1] Grillo, P. and Waldbusser, S. "Host Resources MIB", RFC 1514, 1715 September 1993. 1717 [2] Perkins, D. and McGinnis, E. "Understanding SNMP MIBs", 1718 Prentice-Hall, 1st edition, 1997. 1720 [3] McCloghrie K., and M. Rose, Editors, "Management Information 1721 Base for Network Management of TCP/IP-based internets", STD 17, 1722 RFC 1213, Performance Systems International, March 1991. 1724 [4] Rose, M. T. and McCloghrie, Keith, "How to Manage Your Network 1725 Using SNMP", Prentice-Hall, 1st edition, 1995. 1727 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 1728 of Management Information for Version 2 of the Simple Network 1729 Management Protocol (SNMPv2)", RFC 1902, January 1996. 1731 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1732 "Conformance Statements for Version 2 of the Simple Network 1733 Management Protocol (SNMPv2)", RFC 1904, January 1996. 1735 5. Acknowledgements 1737 This document was based on the original RFC 1514 edited P. Grillo 1738 and S. Waldbusser and produced by the original Host Resources MIB 1739 working group. 1741 6. Security Considerations 1743 Security issues are not discussed in this memo. 1745 7. Author's Address 1747 Robert Krupczak 1748 Empire Technologies, Inc. 1749 541 Tenth St, NW 1750 Suite 169 1751 Atlanta, GA 30318-5713 1752 +1.770.384.0184 1753 rdk@empiretech.com