⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc1514.txt

📁 著名的RFC文档,其中有一些文档是已经翻译成中文的的.
💻 TXT
📖 第 1 页 / 共 5 页
字号:
Network Working Group                                          P. GrilloRequest for Comments: 1514                           Network Innovations                                                       Intel Corporation                                                           S. Waldbusser                                              Carnegie Mellon University                                                          September 1993                           Host Resources MIBStatus of this Memo   This RFC specifies an Internet standards track protocol for the   Internet community, and requests discussion and suggestions for   improvements.  Please refer to the current edition of the "Internet   Official Protocol Standards" for the standardization state and status   of this protocol.  Distribution of this memo is unlimited.Abstract   This memo defines a MIB for use with managing host systems.  The term   "host" is construed to mean any computer that communicates with other   similar computers attached to the internet and that is directly used   by one or more human beings. Although this MIB does not necessarily   apply to devices whose primary function is communications services   (e.g., terminal servers, routers, bridges, monitoring equipment),   such relevance is not explicitly precluded.  This MIB instruments   attributes common to all internet hosts including, for example, both   personal computers and systems that run variants of Unix.Table of Contents   1. The Network Management Framework ......................    2   2. Host Resources MIB ....................................    3   3. Definitions ...........................................    3   4.1 Textual Conventions ..................................    3   4.2 The Host Resources System Group ......................    5   4.3 The Host Resources Storage Group .....................    6   4.4 The Host Resources Device Group ......................   10   4.5 The Host Resources Running Software Group ............   25   4.6 The Host Resources  Running  Software  Performance       Group ................................................   27   4.7 The Host Resources Installed Software Group ..........   29   5. References ............................................   31   6. Acknowledgments .......................................   32   7. Security Considerations ...............................   32   8. Authors' Addresses ....................................   33Grillo & Waldbusser                                             [Page 1]RFC 1514                   Host Resources MIB             September 19931.  The Network Management Framework   The Internet-standard Network Management Framework consists of three   components.  They are:      STD 16, RFC 1155 [1] which defines the SMI, the mechanisms used      for describing and naming objects for the purpose of management.      STD 16, RFC 1212 [2] defines a more concise description mechanism,      which is wholly consistent with the SMI.      STD 17, RFC 1213 [3] which defines MIB-II, the core set of managed      objects for the Internet suite of protocols.      STD 15, RFC 1157 [4] which defines the SNMP, the protocol used for      network access to managed objects.   The Framework permits new objects to be defined for the purpose of   experimentation and evaluation.   Managed objects are accessed via a virtual information store, termed   the Management Information Base or MIB.  Within a given MIB module,   objects are defined using STD 16, RFC 1212's OBJECT-TYPE macro.  At a   minimum, each object has a name, a syntax, an access-level, and an   implementation-status.   The name is an object identifier, an administratively assigned name,   which specifies an object type.  The object type together with an   object instance serves to uniquely identify a specific instantiation   of the object.  For human convenience, we often use a textual string,   termed the object descriptor, to also refer to the object type.   The syntax of an object type defines the abstract data structure   corresponding to that object type.  The ASN.1[5] language is used for   this purpose.  However, RFC 1155 purposely restricts the ASN.1   constructs which may be used.  These restrictions are explicitly made   for simplicity.   The access-level of an object type defines whether it makes "protocol   sense" to read and/or write the value of an instance of the object   type.  (This access-level is independent of any administrative   authorization policy.)   The implementation-status of an object type indicates whether the   object is mandatory, optional, obsolete, or deprecated.Grillo & Waldbusser                                             [Page 2]RFC 1514                   Host Resources MIB             September 19932.  Host Resources MIB   The Host Resources MIB defines a uniform set of objects useful for   the management of host computers.  Host computers  are independent of   the operating system, network services, or any software application.   The Host Resources MIB defines objects which are common across many   computer system architectures.   In addition, there are objects in MIB-II [3] which also provide host   management functionality. Implementation of the System and Interfaces   groups is mandatory for implementors of the Host Resources MIB.3.  Definitions   HOST-RESOURCES-MIB DEFINITIONS ::= BEGIN   IMPORTS       OBJECT-TYPE               FROM RFC-1212       DisplayString             FROM RFC1213-MIB       TimeTicks,       Counter, Gauge            FROM RFC1155-SMI;   host     OBJECT IDENTIFIER ::= { mib-2 25 }   hrSystem        OBJECT IDENTIFIER ::= { host 1 }   hrStorage       OBJECT IDENTIFIER ::= { host 2 }   hrDevice        OBJECT IDENTIFIER ::= { host 3 }   hrSWRun         OBJECT IDENTIFIER ::= { host 4 }   hrSWRunPerf     OBJECT IDENTIFIER ::= { host 5 }   hrSWInstalled   OBJECT IDENTIFIER ::= { host 6 }   -- textual conventions   -- a truth value   Boolean ::=   INTEGER { true(1), false(2) }   -- memory size, expressed in units of 1024bytes   KBytes ::=    INTEGER (0..2147483647)   -- This textual convention is intended to identify the manufacturer,   -- model, and version of a specific hardware or software product.   -- It is suggested that these OBJECT IDENTIFIERs are allocated such   -- that all products from a particular manufacturer are registered   -- under a subtree distinct to that manufacturer.  In addition, allGrillo & Waldbusser                                             [Page 3]RFC 1514                   Host Resources MIB             September 1993   -- versions of a product should be registered under a subtree   -- distinct to that product.  With this strategy, a management   -- station may uniquely determine the manufacturer and/or model of a   -- product whose productID is unknown to the management station.   -- Objects of this type may be useful for inventory purposes or for   -- automatically detecting incompatibilities or version mismatches   -- between various hardware and software components on a system.   ProductID ::= OBJECT IDENTIFIER   -- unknownProduct will be used for any unknown ProductID   -- unknownProduct OBJECT IDENTIFIER ::= { 0 0 }   -- For example, the product ID for the ACME 4860 66MHz clock doubled   -- processor might be:   -- enterprises.acme.acmeProcessors.a4860DX2.MHz66   -- A software product might be registered as:   -- enterprises.acme.acmeOperatingSystems.acmeDOS.six(6).one(1)   DateAndTime ::= OCTET STRING (SIZE (8 | 11))   --        A date-time specification for the local time of day.   --        This data type is intended to provide a consistent   --        method of reporting date information.   --   --            field  octets  contents                  range   --            _____  ______  ________                  _____   --              1      1-2   year                      0..65536   --                           (in network byte order)   --              2       3    month                     1..12   --              3       4    day                       1..31   --              4       5    hour                      0..23   --              5       6    minutes                   0..59   --              6       7    seconds                   0..60   --                           (use 60 for leap-second)   --              7       8    deci-seconds              0..9   --              8       9    direction from UTC        "+" / "-"   --                           (in ascii notation)   --              9      10    hours from UTC            0..11   --             10      11    minutes from UTC          0..59   --   --            Note that if only local time is known, then   --            timezone information (fields 8-10) is not present.   InternationalDisplayString ::= OCTET STRING   --  This data type is used to model textual information in some   --  character set.  A network management station should use a local   --  algorithm to determine which character set is in use and how it   --  should be displayed.  Note that this character set may be encoded   --  with more than one octet per symbol, but will most often be NVTGrillo & Waldbusser                                             [Page 4]RFC 1514                   Host Resources MIB             September 1993   --  ASCII.   -- The Host Resources System Group   --   -- Implementation of this group is mandatory for all host systems.   hrSystemUptime OBJECT-TYPE       SYNTAX TimeTicks       ACCESS read-only       STATUS mandatory       DESCRIPTION              "The amount of time since this host was last              initialized.  Note that this is different from              sysUpTime in MIB-II [3] because sysUpTime is the              uptime of the network management portion of the              system."       ::= { hrSystem 1 }   hrSystemDate OBJECT-TYPE       SYNTAX DateAndTime       ACCESS read-write       STATUS mandatory       DESCRIPTION              "The host's notion of the local date and time of              day."       ::= { hrSystem 2 }   hrSystemInitialLoadDevice OBJECT-TYPE       SYNTAX INTEGER (1..2147483647)       ACCESS read-write       STATUS mandatory       DESCRIPTION              "The index of the hrDeviceEntry for the device from              which this host is configured to load its initial              operating system configuration."       ::= { hrSystem 3 }   hrSystemInitialLoadParameters OBJECT-TYPE       SYNTAX InternationalDisplayString (SIZE (0..128))       ACCESS read-write       STATUS mandatory       DESCRIPTION              "This object contains the parameters (e.g. a              pathname and parameter) supplied to the load device              when requesting the initial operating system              configuration from that device."       ::= { hrSystem 4 }Grillo & Waldbusser                                             [Page 5]RFC 1514                   Host Resources MIB             September 1993   hrSystemNumUsers OBJECT-TYPE       SYNTAX Gauge       ACCESS read-only       STATUS mandatory       DESCRIPTION              "The number of user sessions for which this host is              storing state information.  A session is a              collection of processes requiring a single act of              user authentication and possibly subject to              collective job control."       ::= { hrSystem 5 }   hrSystemProcesses OBJECT-TYPE       SYNTAX Gauge       ACCESS read-only       STATUS mandatory       DESCRIPTION              "The number of process contexts currently loaded or              running on this system."       ::= { hrSystem 6 }   hrSystemMaxProcesses OBJECT-TYPE       SYNTAX INTEGER (0..2147483647)       ACCESS read-only       STATUS mandatory       DESCRIPTION              "The maximum number of process contexts this system              can support.  If there is no fixed maximum, the              value should be zero.  On systems that have a fixed              maximum, this object can help diagnose failures              that occur when this maximum is reached."       ::= { hrSystem 7 }   -- The Host Resources Storage Group   --   -- Implementation of this group is mandatory for all host systems.   -- Registration for some storage types, for use with hrStorageType   hrStorageTypes          OBJECT IDENTIFIER ::= { hrStorage 1 }   hrStorageOther          OBJECT IDENTIFIER ::= { hrStorageTypes 1 }   hrStorageRam            OBJECT IDENTIFIER ::= { hrStorageTypes 2 }   -- hrStorageVirtualMemory is temporary storage of swapped   -- or paged memory   hrStorageVirtualMemory  OBJECT IDENTIFIER ::= { hrStorageTypes 3 }   hrStorageFixedDisk      OBJECT IDENTIFIER ::= { hrStorageTypes 4 }   hrStorageRemovableDisk  OBJECT IDENTIFIER ::= { hrStorageTypes 5 }   hrStorageFloppyDisk     OBJECT IDENTIFIER ::= { hrStorageTypes 6 }Grillo & Waldbusser                                             [Page 6]RFC 1514                   Host Resources MIB             September 1993   hrStorageCompactDisc    OBJECT IDENTIFIER ::= { hrStorageTypes 7 }   hrStorageRamDisk        OBJECT IDENTIFIER ::= { hrStorageTypes 8 }   hrMemorySize OBJECT-TYPE       SYNTAX KBytes       ACCESS read-only       STATUS mandatory       DESCRIPTION              "The amount of physical main memory contained by              the host."       ::= { hrStorage 2 }   hrStorageTable OBJECT-TYPE       SYNTAX SEQUENCE OF HrStorageEntry       ACCESS not-accessible       STATUS mandatory       DESCRIPTION              "The (conceptual) table of logical storage areas on              the host.              An entry shall be placed in the storage table for              each logical area of storage that is allocated and              has fixed resource limits.  The amount of storage              represented in an entity is the amount actually              usable by the requesting entity, and excludes loss              due to formatting or file system reference              information.

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -