home *** CD-ROM | disk | FTP | other *** search
/ The Best of Windows 95.com 1996 September / WIN95_09962.iso / webmisc / mib1_2a.zip / mib_to_html.txt < prev    next >
Text File  |  1996-05-29  |  5KB  |  106 lines
  1.  
  2.           sysDescr OBJECT-TYPE
  3.               SYNTAX  DisplayString (SIZE (0..255))
  4.               ACCESS  read-only
  5.               STATUS  mandatory
  6.  
  7.  
  8.               DESCRIPTION
  9.                       "A textual description of the entity.  This value
  10.                       should include the full name and version
  11.                       identification of the system's hardware type,
  12.                       software operating-system, and networking
  13.                       software.  It is mandatory that this only contain
  14.                       printable ASCII characters."
  15.               ::= { system 1 }
  16.  
  17.           sysObjectID OBJECT-TYPE
  18.               SYNTAX  OBJECT IDENTIFIER
  19.               ACCESS  read-only
  20.               STATUS  mandatory
  21.               DESCRIPTION
  22.                       "The vendor's authoritative identification of the
  23.                       network management subsystem contained in the
  24.                       entity.  This value is allocated within the SMI
  25.                       enterprises subtree (1.3.6.1.4.1) and provides an
  26.                       easy and unambiguous means for determining `what
  27.                       kind of box' is being managed.  For example, if
  28.                       vendor `Flintstones, Inc.' was assigned the
  29.                       subtree 1.3.6.1.4.1.4242, it could assign the
  30.                       identifier 1.3.6.1.4.1.4242.1.1 to its `Fred
  31.                       Router'."
  32.               ::= { system 2 }
  33.  
  34.           sysUpTime OBJECT-TYPE
  35.               SYNTAX  TimeTicks
  36.               ACCESS  read-only
  37.               STATUS  mandatory
  38.               DESCRIPTION
  39.                       "The time (in hundredths of a second) since the
  40.                       network management portion of the system was last
  41.                       re-initialized."
  42.               ::= { system 3 }
  43.  
  44.           sysContact OBJECT-TYPE
  45.               SYNTAX  DisplayString (SIZE (0..255))
  46.               ACCESS  read-write
  47.               STATUS  mandatory
  48.               DESCRIPTION
  49.                       "The textual identification of the contact person
  50.                       for this managed node, together with information
  51.                       on how to contact this person."
  52.               ::= { system 4 }
  53.  
  54.           sysName OBJECT-TYPE
  55.               SYNTAX  DisplayString (SIZE (0..255))
  56.  
  57.  
  58.               ACCESS  read-write
  59.               STATUS  mandatory
  60.               DESCRIPTION
  61.                       "An administratively-assigned name for this
  62.                       managed node.  By convention, this is the node's
  63.                       fully-qualified domain name."
  64.               ::= { system 5 }
  65.  
  66.           sysLocation OBJECT-TYPE
  67.               SYNTAX  DisplayString (SIZE (0..255))
  68.               ACCESS  read-write
  69.               STATUS  mandatory
  70.               DESCRIPTION
  71.                       "The physical location of this node (e.g.,
  72.                       `telephone closet, 3rd floor')."
  73.               ::= { system 6 }
  74.  
  75.           sysServices OBJECT-TYPE
  76.               SYNTAX  INTEGER (0..127)
  77.               ACCESS  read-only
  78.               STATUS  mandatory
  79.               DESCRIPTION
  80.                       "A value which indicates the set of services that
  81.                       this entity primarily offers.
  82.  
  83.                       The value is a sum.  This sum initially takes the
  84.                       value zero, Then, for each layer, L, in the range
  85.                       1 through 7, that this node performs transactions
  86.                       for, 2 raised to (L - 1) is added to the sum.  For
  87.                       example, a node which performs primarily routing
  88.                       functions would have a value of 4 (2^(3-1)).  In
  89.                       contrast, a node which is a host offering
  90.                       application services would have a value of 72
  91.                       (2^(4-1) + 2^(7-1)).  Note that in the context of
  92.                       the Internet suite of protocols, values should be
  93.                       calculated accordingly:
  94.  
  95.                            layer  functionality
  96.                                1  physical (e.g., repeaters)
  97.                                2  datalink/subnetwork (e.g., bridges)
  98.                                3  internet (e.g., IP gateways)
  99.                                4  end-to-end  (e.g., IP hosts)
  100.                                7  applications (e.g., mail relays)
  101.  
  102.                       For systems including OSI protocols, layers 5 and
  103.                       6 may also be counted."
  104.               ::= { system 7 }
  105.  
  106.