1STANDARD-MIB(7)                       MIB                      STANDARD-MIB(7)
2
3
4
5STANDARD-MIB DEFINITIONS ::= BEGIN
6
7     IMPORTS
8          Counter, TimeTicks
9               FROM RFC1155-SMI
10          OBJECT-TYPE
11               FROM RFC-1212
12          DisplayString, mib-2
13               FROM RFC1213-MIB
14          ;
15
16
17-- Standard Datatypes
18
19-- From SNMPv2 (rfc1903)
20TruthValue ::=
21-- Represents a boolean value
22      INTEGER { true(1), false(2) }
23
24-- From SNMPv2 (rfc1903)
25DateAndTime ::=
26--    DESCRIPTION
27--            "A date-time specification.
28--
29--            field  octets  contents                  range
30--              1      1-2   year                      0..65536
31--              2       3    month                     1..12
32--              3       4    day                       1..31
33--              4       5    hour                      0..23
34--              5       6    minutes                   0..59
35--              6       7    seconds                   0..60
36--                           (use 60 for leap-second)
37--              7       8    deci-seconds              0..9
38--              8       9    direction from UTC        '+' / '-'
39--              9      10    hours from UTC            0..11
40--             10      11    minutes from UTC          0..59
41--
42--            For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be
43--            displayed as:
44--
45--                             1992-5-26,13:30:15.0,-4:0
46--
47--            Note that if only local time is known, then timezone
48--            information (fields 8-10) is not present."
49     OCTET STRING (SIZE (8 | 11))
50
51-- From SNMPv2 (rfc1903)
52RowStatus ::=
53     INTEGER {
54          -- the following two values are states:
55          -- these values may be read or written
56          active(1),
57          notInService(2),
58
59          -- the following value is a state:
60          -- this value may be read, but not written
61          notReady(3),
62
63          -- the following three values are
64          -- actions: these values may be written,
65          --   but are never read
66          createAndGo(4),
67          createAndWait(5),
68          destroy(6)
69          }
70
71
72system       OBJECT IDENTIFIER ::= { mib-2 1 }
73snmp         OBJECT IDENTIFIER ::= { mib-2 11 }
74
75
76-- the System group
77
78-- Implementation of the System group is mandatory for all
79-- systems.  If an agent is not configured to have a value
80-- for any of these variables, a string of length 0 is
81-- returned.
82
83sysDescr OBJECT-TYPE
84     SYNTAX  DisplayString (SIZE (0..255))
85     ACCESS  read-only
86     STATUS  mandatory
87     DESCRIPTION
88          "A textual description of the entity.  This value
89          should include the full name and version
90          identification of the system's hardware type,
91          software operating-system, and networking
92          software.  It is mandatory that this only contain
93          printable ASCII characters."
94     ::= { system 1 }
95
96sysObjectID OBJECT-TYPE
97     SYNTAX  OBJECT IDENTIFIER
98     ACCESS  read-only
99     STATUS  mandatory
100     DESCRIPTION
101          "The vendor's authoritative identification of the
102          network management subsystem contained in the
103          entity.  This value is allocated within the SMI
104          enterprises subtree (1.3.6.1.4.1) and provides an
105          easy and unambiguous means for determining `what
106          kind of box' is being managed.  For example, if
107          vendor `Flintstones, Inc.' was assigned the
108          subtree 1.3.6.1.4.1.4242, it could assign the
109          identifier 1.3.6.1.4.1.4242.1.1 to its `Fred
110          Router'."
111     ::= { system 2 }
112
113sysUpTime OBJECT-TYPE
114     SYNTAX  TimeTicks
115     ACCESS  read-only
116     STATUS  mandatory
117     DESCRIPTION
118          "The time (in hundredths of a second) since the
119          network management portion of the system was last
120          re-initialized."
121     ::= { system 3 }
122
123sysContact OBJECT-TYPE
124     SYNTAX  DisplayString (SIZE (0..255))
125     ACCESS  read-write
126     STATUS  mandatory
127     DESCRIPTION
128          "The textual identification of the contact person
129          for this managed node, together with information
130          on how to contact this person."
131     ::= { system 4 }
132
133sysName OBJECT-TYPE
134     SYNTAX  DisplayString (SIZE (0..255))
135     ACCESS  read-write
136     STATUS  mandatory
137     DESCRIPTION
138          "An administratively-assigned name for this
139          managed node.  By convention, this is the node's
140          fully-qualified domain name."
141     ::= { system 5 }
142
143sysLocation OBJECT-TYPE
144     SYNTAX  DisplayString (SIZE (0..255))
145     ACCESS  read-write
146     STATUS  mandatory
147     DESCRIPTION
148          "The physical location of this node (e.g.,
149          `telephone closet, 3rd floor')."
150     ::= { system 6 }
151
152sysServices OBJECT-TYPE
153     SYNTAX  INTEGER (0..127)
154     ACCESS  read-only
155     STATUS  mandatory
156     DESCRIPTION
157          "A value which indicates the set of services that
158          this entity primarily offers.
159
160          The value is a sum.  This sum initially takes the
161          value zero, Then, for each layer, L, in the range
162          1 through 7, that this node performs transactions
163          for, 2 raised to (L - 1) is added to the sum.  For
164          example, a node which performs primarily routing
165          functions would have a value of 4 (2^(3-1)).  In
166          contrast, a node which is a host offering
167          application services would have a value of 72
168          (2^(4-1) + 2^(7-1)).  Note that in the context of
169          the Internet suite of protocols, values should be
170          calculated accordingly:
171
172               layer  functionality
173               1  physical (e.g., repeaters)
174               2  datalink/subnetwork (e.g., bridges)
175               3  internet (e.g., IP gateways)
176               4  end-to-end  (e.g., IP hosts)
177               7  applications (e.g., mail relays)
178
179          For systems including OSI protocols, layers 5 and
180          6 may also be counted."
181     ::= { system 7 }
182
183
184     -- the SNMP group
185
186     -- Implementation of the SNMP group is mandatory for all
187     -- systems which support an SNMP protocol entity.  Some of
188     -- the objects defined below will be zero-valued in those
189     -- SNMP implementations that are optimized to support only
190     -- those functions specific to either a management agent or
191     -- a management station.  In particular, it should be
192     -- observed that the objects below refer to an SNMP entity,
193     -- and there may be several SNMP entities residing on a
194     -- managed node (e.g., if the node is hosting acting as
195     -- a management station).
196
197snmpInPkts OBJECT-TYPE
198     SYNTAX  Counter
199     ACCESS  read-only
200     STATUS  mandatory
201     DESCRIPTION
202          "The total number of Messages delivered to the
203          SNMP entity from the transport service."
204     ::= { snmp 1 }
205
206snmpOutPkts OBJECT-TYPE
207     SYNTAX  Counter
208     ACCESS  read-only
209     STATUS  mandatory
210     DESCRIPTION
211          "The total number of SNMP Messages which were
212          passed from the SNMP protocol entity to the
213          transport service."
214     ::= { snmp 2 }
215
216snmpInBadVersions OBJECT-TYPE
217     SYNTAX  Counter
218     ACCESS  read-only
219     STATUS  mandatory
220     DESCRIPTION
221          "The total number of SNMP Messages which were
222          delivered to the SNMP protocol entity and were for
223          an unsupported SNMP version."
224     ::= { snmp 3 }
225
226snmpInBadCommunityNames OBJECT-TYPE
227     SYNTAX  Counter
228     ACCESS  read-only
229     STATUS  mandatory
230     DESCRIPTION
231          "The total number of SNMP Messages delivered to
232          the SNMP protocol entity which used a SNMP
233          community name not known to said entity."
234     ::= { snmp 4 }
235
236snmpInBadCommunityUses OBJECT-TYPE
237     SYNTAX  Counter
238     ACCESS  read-only
239     STATUS  mandatory
240     DESCRIPTION
241          "The total number of SNMP Messages delivered to
242          the SNMP protocol entity which represented an SNMP
243          operation which was not allowed by the SNMP
244          community named in the Message."
245     ::= { snmp 5 }
246
247snmpInASNParseErrs OBJECT-TYPE
248     SYNTAX  Counter
249     ACCESS  read-only
250     STATUS  mandatory
251     DESCRIPTION
252          "The total number of ASN.1 or BER errors
253          encountered by the SNMP protocol entity when
254          decoding received SNMP Messages."
255     ::= { snmp 6 }
256
257     -- { snmp 7 } is not used
258
259snmpInTooBigs OBJECT-TYPE
260     SYNTAX  Counter
261     ACCESS  read-only
262     STATUS  mandatory
263     DESCRIPTION
264          "The total number of SNMP PDUs which were
265          delivered to the SNMP protocol entity and for
266          which the value of the error-status field is
267          `tooBig'."
268     ::= { snmp 8 }
269
270snmpInNoSuchNames OBJECT-TYPE
271     SYNTAX  Counter
272     ACCESS  read-only
273     STATUS  mandatory
274     DESCRIPTION
275          "The total number of SNMP PDUs which were
276          delivered to the SNMP protocol entity and for
277          which the value of the error-status field is
278          `noSuchName'."
279     ::= { snmp 9 }
280
281snmpInBadValues OBJECT-TYPE
282     SYNTAX  Counter
283     ACCESS  read-only
284     STATUS  mandatory
285     DESCRIPTION
286          "The total number of SNMP PDUs which were
287          delivered to the SNMP protocol entity and for
288          which the value of the error-status field is
289          `badValue'."
290     ::= { snmp 10 }
291
292snmpInReadOnlys OBJECT-TYPE
293     SYNTAX  Counter
294     ACCESS  read-only
295     STATUS  mandatory
296     DESCRIPTION
297          "The total number valid SNMP PDUs which were
298          delivered to the SNMP protocol entity and for
299          which the value of the error-status field is
300          `readOnly'.  It should be noted that it is a
301          protocol error to generate an SNMP PDU which
302          contains the value `readOnly' in the error-status
303          field, as such this object is provided as a means
304          of detecting incorrect implementations of the
305          SNMP."
306     ::= { snmp 11 }
307
308snmpInGenErrs OBJECT-TYPE
309     SYNTAX  Counter
310     ACCESS  read-only
311     STATUS  mandatory
312     DESCRIPTION
313          "The total number of SNMP PDUs which were
314          delivered to the SNMP protocol entity and for
315          which the value of the error-status field is
316          `genErr'."
317     ::= { snmp 12 }
318
319snmpInTotalReqVars OBJECT-TYPE
320     SYNTAX  Counter
321     ACCESS  read-only
322     STATUS  mandatory
323     DESCRIPTION
324          "The total number of MIB objects which have been
325          retrieved successfully by the SNMP protocol entity
326          as the result of receiving valid SNMP Get-Request
327          and Get-Next PDUs."
328     ::= { snmp 13 }
329
330snmpInTotalSetVars OBJECT-TYPE
331     SYNTAX  Counter
332     ACCESS  read-only
333     STATUS  mandatory
334     DESCRIPTION
335          "The total number of MIB objects which have been
336          altered successfully by the SNMP protocol entity
337          as the result of receiving valid SNMP Set-Request
338          PDUs."
339     ::= { snmp 14 }
340
341snmpInGetRequests OBJECT-TYPE
342     SYNTAX  Counter
343     ACCESS  read-only
344     STATUS  mandatory
345     DESCRIPTION
346          "The total number of SNMP Get-Request PDUs which
347          have been accepted and processed by the SNMP
348          protocol entity."
349     ::= { snmp 15 }
350
351snmpInGetNexts OBJECT-TYPE
352     SYNTAX  Counter
353     ACCESS  read-only
354     STATUS  mandatory
355     DESCRIPTION
356          "The total number of SNMP Get-Next PDUs which have
357          been accepted and processed by the SNMP protocol
358          entity."
359     ::= { snmp 16 }
360
361snmpInSetRequests OBJECT-TYPE
362     SYNTAX  Counter
363     ACCESS  read-only
364     STATUS  mandatory
365     DESCRIPTION
366          "The total number of SNMP Set-Request PDUs which
367          have been accepted and processed by the SNMP
368          protocol entity."
369     ::= { snmp 17 }
370
371snmpInGetResponses OBJECT-TYPE
372     SYNTAX  Counter
373     ACCESS  read-only
374     STATUS  mandatory
375     DESCRIPTION
376          "The total number of SNMP Get-Response PDUs which
377          have been accepted and processed by the SNMP
378          protocol entity."
379     ::= { snmp 18 }
380
381snmpInTraps OBJECT-TYPE
382     SYNTAX  Counter
383     ACCESS  read-only
384     STATUS  mandatory
385     DESCRIPTION
386          "The total number of SNMP Trap PDUs which have
387          been accepted and processed by the SNMP protocol
388          entity."
389     ::= { snmp 19 }
390
391snmpOutTooBigs OBJECT-TYPE
392     SYNTAX  Counter
393     ACCESS  read-only
394     STATUS  mandatory
395     DESCRIPTION
396          "The total number of SNMP PDUs which were
397          generated by the SNMP protocol entity and for
398          which the value of the error-status field is
399          `tooBig.'"
400     ::= { snmp 20 }
401
402snmpOutNoSuchNames OBJECT-TYPE
403     SYNTAX  Counter
404     ACCESS  read-only
405     STATUS  mandatory
406     DESCRIPTION
407          "The total number of SNMP PDUs which were
408          generated by the SNMP protocol entity and for
409          which the value of the error-status is
410          `noSuchName'."
411     ::= { snmp 21 }
412
413snmpOutBadValues OBJECT-TYPE
414     SYNTAX  Counter
415     ACCESS  read-only
416     STATUS  mandatory
417     DESCRIPTION
418          "The total number of SNMP PDUs which were
419          generated by the SNMP protocol entity and for
420          which the value of the error-status field is
421          `badValue'."
422     ::= { snmp 22 }
423
424     -- { snmp 23 } is not used
425
426snmpOutGenErrs OBJECT-TYPE
427     SYNTAX  Counter
428     ACCESS  read-only
429     STATUS  mandatory
430     DESCRIPTION
431          "The total number of SNMP PDUs which were
432          generated by the SNMP protocol entity and for
433          which the value of the error-status field is
434          `genErr'."
435     ::= { snmp 24 }
436
437snmpOutGetRequests OBJECT-TYPE
438     SYNTAX  Counter
439     ACCESS  read-only
440     STATUS  mandatory
441     DESCRIPTION
442          "The total number of SNMP Get-Request PDUs which
443          have been generated by the SNMP protocol entity."
444     ::= { snmp 25 }
445
446snmpOutGetNexts OBJECT-TYPE
447     SYNTAX  Counter
448     ACCESS  read-only
449     STATUS  mandatory
450     DESCRIPTION
451          "The total number of SNMP Get-Next PDUs which have
452          been generated by the SNMP protocol entity."
453     ::= { snmp 26 }
454
455snmpOutSetRequests OBJECT-TYPE
456     SYNTAX  Counter
457     ACCESS  read-only
458     STATUS  mandatory
459     DESCRIPTION
460          "The total number of SNMP Set-Request PDUs which
461          have been generated by the SNMP protocol entity."
462     ::= { snmp 27 }
463
464snmpOutGetResponses OBJECT-TYPE
465     SYNTAX  Counter
466     ACCESS  read-only
467     STATUS  mandatory
468     DESCRIPTION
469          "The total number of SNMP Get-Response PDUs which
470          have been generated by the SNMP protocol entity."
471     ::= { snmp 28 }
472
473snmpOutTraps OBJECT-TYPE
474     SYNTAX  Counter
475     ACCESS  read-only
476     STATUS  mandatory
477     DESCRIPTION
478          "The total number of SNMP Trap PDUs which have
479          been generated by the SNMP protocol entity."
480     ::= { snmp 29 }
481
482snmpEnableAuthenTraps OBJECT-TYPE
483     SYNTAX  INTEGER { enabled(1), disabled(2) }
484     ACCESS  read-write
485     STATUS  mandatory
486     DESCRIPTION
487          "Indicates whether the SNMP agent process is
488          permitted to generate authentication-failure
489          traps.  The value of this object overrides any
490          configuration information; as such, it provides a
491          means whereby all authentication-failure traps may
492          be disabled.
493
494          Note that it is strongly recommended that this
495          object be stored in non-volatile memory so that it
496          remains constant between re-initializations of the
497          network management system."
498     ::= { snmp 30 }
499
500coldStart TRAP-TYPE
501     ENTERPRISE  snmp
502     DESCRIPTION
503          "A coldStart trap signifies that the sending
504          protocol entity is reinitializing itself such
505          that the agent's configuration or the rotocol
506          entity implementation may be altered."
507     ::= 0
508
509warmStart TRAP-TYPE
510     ENTERPRISE  snmp
511     DESCRIPTION
512          "A warmStart trap signifies that the sending
513          protocol entity is reinitializing itself such
514          that neither the agent configuration nor the
515          protocol entity implementation is altered."
516     ::= 1
517
518authenticationFailure TRAP-TYPE
519     ENTERPRISE  snmp
520     DESCRIPTION
521          "An authenticationFailure trap signifies that
522          the sending protocol entity is the addressee
523          of a protocol message that is not properly
524          authenticated.  While implementations of the
525          SNMP must be capable of generating this trap,
526          they must also be capable of suppressing the
527          emission of such traps via an implementation-
528          specific mechanism."
529     ::= 4
530
531END
532
533
534
535
536
537Erlang/OTP                           SNMP                      STANDARD-MIB(7)
Impressum