smi-ffi 0.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,2621 @@
1
+ RFC1213-MIB DEFINITIONS ::= BEGIN
2
+
3
+ IMPORTS
4
+ mgmt, NetworkAddress, IpAddress, Counter, Gauge,
5
+ TimeTicks
6
+ FROM RFC1155-SMI
7
+ OBJECT-TYPE
8
+ FROM RFC-1212;
9
+
10
+ -- This MIB module uses the extended OBJECT-TYPE macro as
11
+ -- defined in [14];
12
+
13
+
14
+ -- MIB-II (same prefix as MIB-I)
15
+
16
+ mib-2 OBJECT IDENTIFIER ::= { mgmt 1 }
17
+
18
+ -- textual conventions
19
+
20
+ DisplayString ::=
21
+ OCTET STRING
22
+ -- This data type is used to model textual information taken
23
+ -- from the NVT ASCII character set. By convention, objects
24
+ -- with this syntax are declared as having
25
+
26
+ --
27
+ -- SIZE (0..255)
28
+
29
+ PhysAddress ::=
30
+ OCTET STRING
31
+ -- This data type is used to model media addresses. For many
32
+ -- types of media, this will be in a binary representation.
33
+ -- For example, an ethernet address would be represented as
34
+ -- a string of 6 octets.
35
+
36
+
37
+ -- groups in MIB-II
38
+
39
+ system OBJECT IDENTIFIER ::= { mib-2 1 }
40
+
41
+ interfaces OBJECT IDENTIFIER ::= { mib-2 2 }
42
+
43
+ at OBJECT IDENTIFIER ::= { mib-2 3 }
44
+
45
+ ip OBJECT IDENTIFIER ::= { mib-2 4 }
46
+
47
+ icmp OBJECT IDENTIFIER ::= { mib-2 5 }
48
+
49
+ tcp OBJECT IDENTIFIER ::= { mib-2 6 }
50
+
51
+ udp OBJECT IDENTIFIER ::= { mib-2 7 }
52
+
53
+ egp OBJECT IDENTIFIER ::= { mib-2 8 }
54
+
55
+ -- historical (some say hysterical)
56
+ -- cmot OBJECT IDENTIFIER ::= { mib-2 9 }
57
+
58
+ transmission OBJECT IDENTIFIER ::= { mib-2 10 }
59
+
60
+ snmp OBJECT IDENTIFIER ::= { mib-2 11 }
61
+
62
+
63
+ -- the System group
64
+
65
+ -- Implementation of the System group is mandatory for all
66
+ -- systems. If an agent is not configured to have a value
67
+ -- for any of these variables, a string of length 0 is
68
+ -- returned.
69
+
70
+ sysDescr OBJECT-TYPE
71
+ SYNTAX DisplayString (SIZE (0..255))
72
+ ACCESS read-only
73
+ STATUS mandatory
74
+ DESCRIPTION
75
+ "A textual description of the entity. This value
76
+ should include the full name and version
77
+ identification of the system's hardware type,
78
+ software operating-system, and networking
79
+ software. It is mandatory that this only contain
80
+ printable ASCII characters."
81
+ ::= { system 1 }
82
+
83
+ sysObjectID OBJECT-TYPE
84
+ SYNTAX OBJECT IDENTIFIER
85
+ ACCESS read-only
86
+ STATUS mandatory
87
+ DESCRIPTION
88
+ "The vendor's authoritative identification of the
89
+ network management subsystem contained in the
90
+ entity. This value is allocated within the SMI
91
+ enterprises subtree (1.3.6.1.4.1) and provides an
92
+ easy and unambiguous means for determining `what
93
+ kind of box' is being managed. For example, if
94
+ vendor `Flintstones, Inc.' was assigned the
95
+ subtree 1.3.6.1.4.1.4242, it could assign the
96
+ identifier 1.3.6.1.4.1.4242.1.1 to its `Fred
97
+ Router'."
98
+ ::= { system 2 }
99
+
100
+ sysUpTime OBJECT-TYPE
101
+ SYNTAX TimeTicks
102
+ ACCESS read-only
103
+ STATUS mandatory
104
+ DESCRIPTION
105
+ "The time (in hundredths of a second) since the
106
+ network management portion of the system was last
107
+ re-initialized."
108
+ ::= { system 3 }
109
+
110
+ sysContact OBJECT-TYPE
111
+ SYNTAX DisplayString (SIZE (0..255))
112
+ ACCESS read-write
113
+ STATUS mandatory
114
+ DESCRIPTION
115
+ "The textual identification of the contact person
116
+ for this managed node, together with information
117
+ on how to contact this person."
118
+ ::= { system 4 }
119
+
120
+ sysName OBJECT-TYPE
121
+ SYNTAX DisplayString (SIZE (0..255))
122
+ ACCESS read-write
123
+ STATUS mandatory
124
+ DESCRIPTION
125
+ "An administratively-assigned name for this
126
+ managed node. By convention, this is the node's
127
+ fully-qualified domain name."
128
+ ::= { system 5 }
129
+
130
+ sysLocation OBJECT-TYPE
131
+ SYNTAX DisplayString (SIZE (0..255))
132
+ ACCESS read-write
133
+ STATUS mandatory
134
+ DESCRIPTION
135
+ "The physical location of this node (e.g.,
136
+ `telephone closet, 3rd floor')."
137
+ ::= { system 6 }
138
+
139
+ sysServices OBJECT-TYPE
140
+ SYNTAX INTEGER (0..127)
141
+ ACCESS read-only
142
+ STATUS mandatory
143
+ DESCRIPTION
144
+ "A value which indicates the set of services that
145
+ this entity primarily offers.
146
+
147
+ The value is a sum. This sum initially takes the
148
+ value zero, Then, for each layer, L, in the range
149
+ 1 through 7, that this node performs transactions
150
+ for, 2 raised to (L - 1) is added to the sum. For
151
+ example, a node which performs primarily routing
152
+ functions would have a value of 4 (2^(3-1)). In
153
+ contrast, a node which is a host offering
154
+ application services would have a value of 72
155
+ (2^(4-1) + 2^(7-1)). Note that in the context of
156
+ the Internet suite of protocols, values should be
157
+ calculated accordingly:
158
+
159
+ layer functionality
160
+ 1 physical (e.g., repeaters)
161
+ 2 datalink/subnetwork (e.g., bridges)
162
+ 3 internet (e.g., IP gateways)
163
+ 4 end-to-end (e.g., IP hosts)
164
+ 7 applications (e.g., mail relays)
165
+
166
+ For systems including OSI protocols, layers 5 and
167
+ 6 may also be counted."
168
+ ::= { system 7 }
169
+
170
+ -- the Interfaces group
171
+
172
+ -- Implementation of the Interfaces group is mandatory for
173
+ -- all systems.
174
+
175
+ ifNumber OBJECT-TYPE
176
+ SYNTAX INTEGER
177
+ ACCESS read-only
178
+ STATUS mandatory
179
+ DESCRIPTION
180
+ "The number of network interfaces (regardless of
181
+ their current state) present on this system."
182
+ ::= { interfaces 1 }
183
+
184
+
185
+ -- the Interfaces table
186
+
187
+ -- The Interfaces table contains information on the entity's
188
+ -- interfaces. Each interface is thought of as being
189
+ -- attached to a `subnetwork'. Note that this term should
190
+ -- not be confused with `subnet' which refers to an
191
+ -- addressing partitioning scheme used in the Internet suite
192
+ -- of protocols.
193
+
194
+ ifTable OBJECT-TYPE
195
+ SYNTAX SEQUENCE OF IfEntry
196
+ ACCESS not-accessible
197
+ STATUS mandatory
198
+ DESCRIPTION
199
+ "A list of interface entries. The number of
200
+ entries is given by the value of ifNumber."
201
+ ::= { interfaces 2 }
202
+
203
+ ifEntry OBJECT-TYPE
204
+ SYNTAX IfEntry
205
+ ACCESS not-accessible
206
+ STATUS mandatory
207
+ DESCRIPTION
208
+ "An interface entry containing objects at the
209
+ subnetwork layer and below for a particular
210
+ interface."
211
+ INDEX { ifIndex }
212
+ ::= { ifTable 1 }
213
+
214
+ IfEntry ::=
215
+ SEQUENCE {
216
+ ifIndex
217
+ INTEGER,
218
+ ifDescr
219
+ DisplayString,
220
+ ifType
221
+ INTEGER,
222
+ ifMtu
223
+ INTEGER,
224
+ ifSpeed
225
+ Gauge,
226
+ ifPhysAddress
227
+ PhysAddress,
228
+ ifAdminStatus
229
+ INTEGER,
230
+ ifOperStatus
231
+ INTEGER,
232
+ ifLastChange
233
+ TimeTicks,
234
+ ifInOctets
235
+ Counter,
236
+ ifInUcastPkts
237
+ Counter,
238
+ ifInNUcastPkts
239
+ Counter,
240
+ ifInDiscards
241
+ Counter,
242
+ ifInErrors
243
+ Counter,
244
+ ifInUnknownProtos
245
+ Counter,
246
+ ifOutOctets
247
+ Counter,
248
+ ifOutUcastPkts
249
+ Counter,
250
+ ifOutNUcastPkts
251
+ Counter,
252
+ ifOutDiscards
253
+ Counter,
254
+ ifOutErrors
255
+ Counter,
256
+ ifOutQLen
257
+ Gauge,
258
+ ifSpecific
259
+ OBJECT IDENTIFIER
260
+ }
261
+
262
+ ifIndex OBJECT-TYPE
263
+ SYNTAX INTEGER
264
+ ACCESS read-only
265
+ STATUS mandatory
266
+ DESCRIPTION
267
+ "A unique value for each interface. Its value
268
+ ranges between 1 and the value of ifNumber. The
269
+ value for each interface must remain constant at
270
+ least from one re-initialization of the entity's
271
+ network management system to the next re-
272
+ initialization."
273
+ ::= { ifEntry 1 }
274
+
275
+ ifDescr OBJECT-TYPE
276
+ SYNTAX DisplayString (SIZE (0..255))
277
+ ACCESS read-only
278
+ STATUS mandatory
279
+ DESCRIPTION
280
+ "A textual string containing information about the
281
+ interface. This string should include the name of
282
+ the manufacturer, the product name and the version
283
+ of the hardware interface."
284
+ ::= { ifEntry 2 }
285
+
286
+ ifType OBJECT-TYPE
287
+ SYNTAX INTEGER {
288
+ other(1), -- none of the following
289
+ regular1822(2),
290
+ hdh1822(3),
291
+ ddn-x25(4),
292
+ rfc877-x25(5),
293
+ ethernet-csmacd(6),
294
+ iso88023-csmacd(7),
295
+ iso88024-tokenBus(8),
296
+ iso88025-tokenRing(9),
297
+ iso88026-man(10),
298
+ starLan(11),
299
+ proteon-10Mbit(12),
300
+ proteon-80Mbit(13),
301
+ hyperchannel(14),
302
+ fddi(15),
303
+ lapb(16),
304
+ sdlc(17),
305
+ ds1(18), -- T-1
306
+ e1(19), -- european equiv. of T-1
307
+ basicISDN(20),
308
+ primaryISDN(21), -- proprietary serial
309
+ propPointToPointSerial(22),
310
+ ppp(23),
311
+ softwareLoopback(24),
312
+ eon(25), -- CLNP over IP [11]
313
+ ethernet-3Mbit(26),
314
+ nsip(27), -- XNS over IP
315
+ slip(28), -- generic SLIP
316
+ ultra(29), -- ULTRA technologies
317
+ ds3(30), -- T-3
318
+ sip(31), -- SMDS
319
+ frame-relay(32)
320
+ }
321
+ ACCESS read-only
322
+ STATUS mandatory
323
+ DESCRIPTION
324
+ "The type of interface, distinguished according to
325
+ the physical/link protocol(s) immediately `below'
326
+ the network layer in the protocol stack."
327
+ ::= { ifEntry 3 }
328
+
329
+ ifMtu OBJECT-TYPE
330
+ SYNTAX INTEGER
331
+ ACCESS read-only
332
+ STATUS mandatory
333
+ DESCRIPTION
334
+ "The size of the largest datagram which can be
335
+ sent/received on the interface, specified in
336
+ octets. For interfaces that are used for
337
+ transmitting network datagrams, this is the size
338
+ of the largest network datagram that can be sent
339
+ on the interface."
340
+ ::= { ifEntry 4 }
341
+
342
+ ifSpeed OBJECT-TYPE
343
+ SYNTAX Gauge
344
+ ACCESS read-only
345
+ STATUS mandatory
346
+ DESCRIPTION
347
+ "An estimate of the interface's current bandwidth
348
+ in bits per second. For interfaces which do not
349
+ vary in bandwidth or for those where no accurate
350
+ estimation can be made, this object should contain
351
+ the nominal bandwidth."
352
+ ::= { ifEntry 5 }
353
+
354
+ ifPhysAddress OBJECT-TYPE
355
+ SYNTAX PhysAddress
356
+ ACCESS read-only
357
+ STATUS mandatory
358
+ DESCRIPTION
359
+ "The interface's address at the protocol layer
360
+ immediately `below' the network layer in the
361
+ protocol stack. For interfaces which do not have
362
+ such an address (e.g., a serial line), this object
363
+ should contain an octet string of zero length."
364
+ ::= { ifEntry 6 }
365
+
366
+ ifAdminStatus OBJECT-TYPE
367
+ SYNTAX INTEGER {
368
+ up(1), -- ready to pass packets
369
+ down(2),
370
+ testing(3) -- in some test mode
371
+ }
372
+ ACCESS read-write
373
+ STATUS mandatory
374
+ DESCRIPTION
375
+ "The desired state of the interface. The
376
+ testing(3) state indicates that no operational
377
+ packets can be passed."
378
+ ::= { ifEntry 7 }
379
+
380
+ ifOperStatus OBJECT-TYPE
381
+ SYNTAX INTEGER {
382
+ up(1), -- ready to pass packets
383
+ down(2),
384
+ testing(3) -- in some test mode
385
+ }
386
+ ACCESS read-only
387
+ STATUS mandatory
388
+ DESCRIPTION
389
+ "The current operational state of the interface.
390
+ The testing(3) state indicates that no operational
391
+ packets can be passed."
392
+ ::= { ifEntry 8 }
393
+
394
+ ifLastChange OBJECT-TYPE
395
+ SYNTAX TimeTicks
396
+ ACCESS read-only
397
+ STATUS mandatory
398
+ DESCRIPTION
399
+ "The value of sysUpTime at the time the interface
400
+ entered its current operational state. If the
401
+ current state was entered prior to the last re-
402
+ initialization of the local network management
403
+ subsystem, then this object contains a zero
404
+ value."
405
+ ::= { ifEntry 9 }
406
+
407
+ ifInOctets OBJECT-TYPE
408
+ SYNTAX Counter
409
+ ACCESS read-only
410
+ STATUS mandatory
411
+ DESCRIPTION
412
+ "The total number of octets received on the
413
+ interface, including framing characters."
414
+ ::= { ifEntry 10 }
415
+
416
+ ifInUcastPkts OBJECT-TYPE
417
+ SYNTAX Counter
418
+ ACCESS read-only
419
+ STATUS mandatory
420
+ DESCRIPTION
421
+ "The number of subnetwork-unicast packets
422
+ delivered to a higher-layer protocol."
423
+ ::= { ifEntry 11 }
424
+
425
+ ifInNUcastPkts OBJECT-TYPE
426
+ SYNTAX Counter
427
+ ACCESS read-only
428
+ STATUS mandatory
429
+ DESCRIPTION
430
+ "The number of non-unicast (i.e., subnetwork-
431
+ broadcast or subnetwork-multicast) packets
432
+ delivered to a higher-layer protocol."
433
+ ::= { ifEntry 12 }
434
+
435
+ ifInDiscards OBJECT-TYPE
436
+ SYNTAX Counter
437
+ ACCESS read-only
438
+ STATUS mandatory
439
+ DESCRIPTION
440
+ "The number of inbound packets which were chosen
441
+ to be discarded even though no errors had been
442
+ detected to prevent their being deliverable to a
443
+ higher-layer protocol. One possible reason for
444
+ discarding such a packet could be to free up
445
+ buffer space."
446
+ ::= { ifEntry 13 }
447
+
448
+ ifInErrors OBJECT-TYPE
449
+ SYNTAX Counter
450
+ ACCESS read-only
451
+ STATUS mandatory
452
+ DESCRIPTION
453
+ "The number of inbound packets that contained
454
+ errors preventing them from being deliverable to a
455
+ higher-layer protocol."
456
+ ::= { ifEntry 14 }
457
+
458
+ ifInUnknownProtos OBJECT-TYPE
459
+ SYNTAX Counter
460
+ ACCESS read-only
461
+ STATUS mandatory
462
+ DESCRIPTION
463
+ "The number of packets received via the interface
464
+ which were discarded because of an unknown or
465
+ unsupported protocol."
466
+ ::= { ifEntry 15 }
467
+
468
+ ifOutOctets OBJECT-TYPE
469
+ SYNTAX Counter
470
+ ACCESS read-only
471
+ STATUS mandatory
472
+ DESCRIPTION
473
+ "The total number of octets transmitted out of the
474
+ interface, including framing characters."
475
+ ::= { ifEntry 16 }
476
+
477
+ ifOutUcastPkts OBJECT-TYPE
478
+ SYNTAX Counter
479
+ ACCESS read-only
480
+ STATUS mandatory
481
+ DESCRIPTION
482
+ "The total number of packets that higher-level
483
+ protocols requested be transmitted to a
484
+ subnetwork-unicast address, including those that
485
+ were discarded or not sent."
486
+ ::= { ifEntry 17 }
487
+
488
+ ifOutNUcastPkts OBJECT-TYPE
489
+ SYNTAX Counter
490
+ ACCESS read-only
491
+ STATUS mandatory
492
+ DESCRIPTION
493
+ "The total number of packets that higher-level
494
+ protocols requested be transmitted to a non-
495
+ unicast (i.e., a subnetwork-broadcast or
496
+ subnetwork-multicast) address, including those
497
+ that were discarded or not sent."
498
+ ::= { ifEntry 18 }
499
+
500
+ ifOutDiscards OBJECT-TYPE
501
+ SYNTAX Counter
502
+ ACCESS read-only
503
+ STATUS mandatory
504
+ DESCRIPTION
505
+ "The number of outbound packets which were chosen
506
+ to be discarded even though no errors had been
507
+ detected to prevent their being transmitted. One
508
+ possible reason for discarding such a packet could
509
+ be to free up buffer space."
510
+ ::= { ifEntry 19 }
511
+
512
+ ifOutErrors OBJECT-TYPE
513
+ SYNTAX Counter
514
+ ACCESS read-only
515
+ STATUS mandatory
516
+ DESCRIPTION
517
+ "The number of outbound packets that could not be
518
+ transmitted because of errors."
519
+ ::= { ifEntry 20 }
520
+
521
+ ifOutQLen OBJECT-TYPE
522
+ SYNTAX Gauge
523
+ ACCESS read-only
524
+ STATUS mandatory
525
+ DESCRIPTION
526
+ "The length of the output packet queue (in
527
+ packets)."
528
+ ::= { ifEntry 21 }
529
+
530
+ ifSpecific OBJECT-TYPE
531
+ SYNTAX OBJECT IDENTIFIER
532
+ ACCESS read-only
533
+ STATUS mandatory
534
+ DESCRIPTION
535
+ "A reference to MIB definitions specific to the
536
+ particular media being used to realize the
537
+ interface. For example, if the interface is
538
+ realized by an ethernet, then the value of this
539
+ object refers to a document defining objects
540
+ specific to ethernet. If this information is not
541
+ present, its value should be set to the OBJECT
542
+ IDENTIFIER { 0 0 }, which is a syntatically valid
543
+ object identifier, and any conformant
544
+ implementation of ASN.1 and BER must be able to
545
+ generate and recognize this value."
546
+ ::= { ifEntry 22 }
547
+
548
+
549
+ -- the Address Translation group
550
+
551
+ -- Implementation of the Address Translation group is
552
+ -- mandatory for all systems. Note however that this group
553
+ -- is deprecated by MIB-II. That is, it is being included
554
+
555
+ -- solely for compatibility with MIB-I nodes, and will most
556
+ -- likely be excluded from MIB-III nodes. From MIB-II and
557
+ -- onwards, each network protocol group contains its own
558
+ -- address translation tables.
559
+
560
+ -- The Address Translation group contains one table which is
561
+ -- the union across all interfaces of the translation tables
562
+ -- for converting a NetworkAddress (e.g., an IP address) into
563
+ -- a subnetwork-specific address. For lack of a better term,
564
+ -- this document refers to such a subnetwork-specific address
565
+ -- as a `physical' address.
566
+
567
+ -- Examples of such translation tables are: for broadcast
568
+ -- media where ARP is in use, the translation table is
569
+ -- equivalent to the ARP cache; or, on an X.25 network where
570
+ -- non-algorithmic translation to X.121 addresses is
571
+ -- required, the translation table contains the
572
+ -- NetworkAddress to X.121 address equivalences.
573
+
574
+ atTable OBJECT-TYPE
575
+ SYNTAX SEQUENCE OF AtEntry
576
+ ACCESS not-accessible
577
+ STATUS deprecated
578
+ DESCRIPTION
579
+ "The Address Translation tables contain the
580
+ NetworkAddress to `physical' address equivalences.
581
+ Some interfaces do not use translation tables for
582
+ determining address equivalences (e.g., DDN-X.25
583
+ has an algorithmic method); if all interfaces are
584
+ of this type, then the Address Translation table
585
+ is empty, i.e., has zero entries."
586
+ ::= { at 1 }
587
+
588
+ atEntry OBJECT-TYPE
589
+ SYNTAX AtEntry
590
+ ACCESS not-accessible
591
+ STATUS deprecated
592
+ DESCRIPTION
593
+ "Each entry contains one NetworkAddress to
594
+ `physical' address equivalence."
595
+ INDEX { atIfIndex,
596
+ atNetAddress }
597
+ ::= { atTable 1 }
598
+
599
+ AtEntry ::=
600
+ SEQUENCE {
601
+ atIfIndex
602
+ INTEGER,
603
+ atPhysAddress
604
+ PhysAddress,
605
+ atNetAddress
606
+ NetworkAddress
607
+ }
608
+
609
+ atIfIndex OBJECT-TYPE
610
+ SYNTAX INTEGER
611
+ ACCESS read-write
612
+ STATUS deprecated
613
+ DESCRIPTION
614
+ "The interface on which this entry's equivalence
615
+ is effective. The interface identified by a
616
+ particular value of this index is the same
617
+ interface as identified by the same value of
618
+ ifIndex."
619
+ ::= { atEntry 1 }
620
+
621
+ atPhysAddress OBJECT-TYPE
622
+ SYNTAX PhysAddress
623
+ ACCESS read-write
624
+ STATUS deprecated
625
+ DESCRIPTION
626
+ "The media-dependent `physical' address.
627
+
628
+ Setting this object to a null string (one of zero
629
+ length) has the effect of invaliding the
630
+ corresponding entry in the atTable object. That
631
+ is, it effectively dissasociates the interface
632
+ identified with said entry from the mapping
633
+ identified with said entry. It is an
634
+ implementation-specific matter as to whether the
635
+ agent removes an invalidated entry from the table.
636
+ Accordingly, management stations must be prepared
637
+ to receive tabular information from agents that
638
+ corresponds to entries not currently in use.
639
+ Proper interpretation of such entries requires
640
+ examination of the relevant atPhysAddress object."
641
+ ::= { atEntry 2 }
642
+
643
+ atNetAddress OBJECT-TYPE
644
+ SYNTAX NetworkAddress
645
+ ACCESS read-write
646
+ STATUS deprecated
647
+ DESCRIPTION
648
+ "The NetworkAddress (e.g., the IP address)
649
+ corresponding to the media-dependent `physical'
650
+ address."
651
+ ::= { atEntry 3 }
652
+
653
+
654
+ -- the IP group
655
+
656
+ -- Implementation of the IP group is mandatory for all
657
+ -- systems.
658
+
659
+ ipForwarding OBJECT-TYPE
660
+ SYNTAX INTEGER {
661
+ forwarding(1), -- acting as a gateway
662
+ not-forwarding(2) -- NOT acting as a gateway
663
+ }
664
+ ACCESS read-write
665
+ STATUS mandatory
666
+ DESCRIPTION
667
+ "The indication of whether this entity is acting
668
+ as an IP gateway in respect to the forwarding of
669
+ datagrams received by, but not addressed to, this
670
+ entity. IP gateways forward datagrams. IP hosts
671
+ do not (except those source-routed via the host).
672
+
673
+ Note that for some managed nodes, this object may
674
+ take on only a subset of the values possible.
675
+ Accordingly, it is appropriate for an agent to
676
+ return a `badValue' response if a management
677
+ station attempts to change this object to an
678
+ inappropriate value."
679
+ ::= { ip 1 }
680
+
681
+ ipDefaultTTL OBJECT-TYPE
682
+ SYNTAX INTEGER
683
+ ACCESS read-write
684
+ STATUS mandatory
685
+ DESCRIPTION
686
+ "The default value inserted into the Time-To-Live
687
+ field of the IP header of datagrams originated at
688
+ this entity, whenever a TTL value is not supplied
689
+ by the transport layer protocol."
690
+ ::= { ip 2 }
691
+
692
+ ipInReceives OBJECT-TYPE
693
+ SYNTAX Counter
694
+ ACCESS read-only
695
+ STATUS mandatory
696
+ DESCRIPTION
697
+ "The total number of input datagrams received from
698
+ interfaces, including those received in error."
699
+ ::= { ip 3 }
700
+
701
+ ipInHdrErrors OBJECT-TYPE
702
+ SYNTAX Counter
703
+ ACCESS read-only
704
+ STATUS mandatory
705
+ DESCRIPTION
706
+ "The number of input datagrams discarded due to
707
+ errors in their IP headers, including bad
708
+ checksums, version number mismatch, other format
709
+ errors, time-to-live exceeded, errors discovered
710
+ in processing their IP options, etc."
711
+ ::= { ip 4 }
712
+
713
+ ipInAddrErrors OBJECT-TYPE
714
+ SYNTAX Counter
715
+ ACCESS read-only
716
+ STATUS mandatory
717
+ DESCRIPTION
718
+ "The number of input datagrams discarded because
719
+ the IP address in their IP header's destination
720
+ field was not a valid address to be received at
721
+ this entity. This count includes invalid
722
+ addresses (e.g., 0.0.0.0) and addresses of
723
+ unsupported Classes (e.g., Class E). For entities
724
+ which are not IP Gateways and therefore do not
725
+ forward datagrams, this counter includes datagrams
726
+ discarded because the destination address was not
727
+ a local address."
728
+ ::= { ip 5 }
729
+
730
+ ipForwDatagrams OBJECT-TYPE
731
+ SYNTAX Counter
732
+ ACCESS read-only
733
+ STATUS mandatory
734
+ DESCRIPTION
735
+ "The number of input datagrams for which this
736
+ entity was not their final IP destination, as a
737
+ result of which an attempt was made to find a
738
+ route to forward them to that final destination.
739
+ In entities which do not act as IP Gateways, this
740
+ counter will include only those packets which were
741
+ Source-Routed via this entity, and the Source-
742
+ Route option processing was successful."
743
+ ::= { ip 6 }
744
+
745
+ ipInUnknownProtos OBJECT-TYPE
746
+ SYNTAX Counter
747
+ ACCESS read-only
748
+ STATUS mandatory
749
+ DESCRIPTION
750
+ "The number of locally-addressed datagrams
751
+ received successfully but discarded because of an
752
+ unknown or unsupported protocol."
753
+ ::= { ip 7 }
754
+
755
+ ipInDiscards OBJECT-TYPE
756
+ SYNTAX Counter
757
+ ACCESS read-only
758
+ STATUS mandatory
759
+ DESCRIPTION
760
+ "The number of input IP datagrams for which no
761
+ problems were encountered to prevent their
762
+ continued processing, but which were discarded
763
+ (e.g., for lack of buffer space). Note that this
764
+ counter does not include any datagrams discarded
765
+ while awaiting re-assembly."
766
+ ::= { ip 8 }
767
+
768
+ ipInDelivers OBJECT-TYPE
769
+ SYNTAX Counter
770
+ ACCESS read-only
771
+ STATUS mandatory
772
+ DESCRIPTION
773
+ "The total number of input datagrams successfully
774
+ delivered to IP user-protocols (including ICMP)."
775
+ ::= { ip 9 }
776
+
777
+ ipOutRequests OBJECT-TYPE
778
+ SYNTAX Counter
779
+ ACCESS read-only
780
+ STATUS mandatory
781
+ DESCRIPTION
782
+ "The total number of IP datagrams which local IP
783
+ user-protocols (including ICMP) supplied to IP in
784
+ requests for transmission. Note that this counter
785
+ does not include any datagrams counted in
786
+ ipForwDatagrams."
787
+ ::= { ip 10 }
788
+
789
+ ipOutDiscards OBJECT-TYPE
790
+ SYNTAX Counter
791
+ ACCESS read-only
792
+ STATUS mandatory
793
+ DESCRIPTION
794
+ "The number of output IP datagrams for which no
795
+ problem was encountered to prevent their
796
+ transmission to their destination, but which were
797
+ discarded (e.g., for lack of buffer space). Note
798
+ that this counter would include datagrams counted
799
+ in ipForwDatagrams if any such packets met this
800
+ (discretionary) discard criterion."
801
+ ::= { ip 11 }
802
+
803
+ ipOutNoRoutes OBJECT-TYPE
804
+ SYNTAX Counter
805
+ ACCESS read-only
806
+ STATUS mandatory
807
+ DESCRIPTION
808
+ "The number of IP datagrams discarded because no
809
+ route could be found to transmit them to their
810
+ destination. Note that this counter includes any
811
+ packets counted in ipForwDatagrams which meet this
812
+ `no-route' criterion. Note that this includes any
813
+ datagarms which a host cannot route because all of
814
+ its default gateways are down."
815
+ ::= { ip 12 }
816
+
817
+ ipReasmTimeout OBJECT-TYPE
818
+ SYNTAX INTEGER
819
+ ACCESS read-only
820
+ STATUS mandatory
821
+ DESCRIPTION
822
+ "The maximum number of seconds which received
823
+ fragments are held while they are awaiting
824
+ reassembly at this entity."
825
+ ::= { ip 13 }
826
+
827
+ ipReasmReqds OBJECT-TYPE
828
+ SYNTAX Counter
829
+ ACCESS read-only
830
+ STATUS mandatory
831
+ DESCRIPTION
832
+ "The number of IP fragments received which needed
833
+ to be reassembled at this entity."
834
+ ::= { ip 14 }
835
+
836
+ ipReasmOKs OBJECT-TYPE
837
+ SYNTAX Counter
838
+ ACCESS read-only
839
+ STATUS mandatory
840
+ DESCRIPTION
841
+ "The number of IP datagrams successfully re-
842
+ assembled."
843
+ ::= { ip 15 }
844
+
845
+ ipReasmFails OBJECT-TYPE
846
+ SYNTAX Counter
847
+ ACCESS read-only
848
+ STATUS mandatory
849
+ DESCRIPTION
850
+ "The number of failures detected by the IP re-
851
+ assembly algorithm (for whatever reason: timed
852
+ out, errors, etc). Note that this is not
853
+ necessarily a count of discarded IP fragments
854
+ since some algorithms (notably the algorithm in
855
+ RFC 815) can lose track of the number of fragments
856
+ by combining them as they are received."
857
+ ::= { ip 16 }
858
+
859
+ ipFragOKs OBJECT-TYPE
860
+ SYNTAX Counter
861
+ ACCESS read-only
862
+ STATUS mandatory
863
+ DESCRIPTION
864
+ "The number of IP datagrams that have been
865
+ successfully fragmented at this entity."
866
+ ::= { ip 17 }
867
+
868
+ ipFragFails OBJECT-TYPE
869
+ SYNTAX Counter
870
+ ACCESS read-only
871
+ STATUS mandatory
872
+ DESCRIPTION
873
+ "The number of IP datagrams that have been
874
+ discarded because they needed to be fragmented at
875
+ this entity but could not be, e.g., because their
876
+ Don't Fragment flag was set."
877
+ ::= { ip 18 }
878
+
879
+ ipFragCreates OBJECT-TYPE
880
+ SYNTAX Counter
881
+ ACCESS read-only
882
+ STATUS mandatory
883
+ DESCRIPTION
884
+ "The number of IP datagram fragments that have
885
+ been generated as a result of fragmentation at
886
+ this entity."
887
+ ::= { ip 19 }
888
+
889
+ -- the IP address table
890
+
891
+ -- The IP address table contains this entity's IP addressing
892
+ -- information.
893
+
894
+ ipAddrTable OBJECT-TYPE
895
+ SYNTAX SEQUENCE OF IpAddrEntry
896
+ ACCESS not-accessible
897
+ STATUS mandatory
898
+ DESCRIPTION
899
+ "The table of addressing information relevant to
900
+ this entity's IP addresses."
901
+ ::= { ip 20 }
902
+
903
+ ipAddrEntry OBJECT-TYPE
904
+ SYNTAX IpAddrEntry
905
+ ACCESS not-accessible
906
+ STATUS mandatory
907
+ DESCRIPTION
908
+ "The addressing information for one of this
909
+ entity's IP addresses."
910
+ INDEX { ipAdEntAddr }
911
+ ::= { ipAddrTable 1 }
912
+
913
+ IpAddrEntry ::=
914
+ SEQUENCE {
915
+ ipAdEntAddr
916
+ IpAddress,
917
+ ipAdEntIfIndex
918
+ INTEGER,
919
+ ipAdEntNetMask
920
+ IpAddress,
921
+ ipAdEntBcastAddr
922
+ INTEGER,
923
+ ipAdEntReasmMaxSize
924
+ INTEGER (0..65535)
925
+ }
926
+
927
+ ipAdEntAddr OBJECT-TYPE
928
+ SYNTAX IpAddress
929
+ ACCESS read-only
930
+ STATUS mandatory
931
+ DESCRIPTION
932
+ "The IP address to which this entry's addressing
933
+ information pertains."
934
+ ::= { ipAddrEntry 1 }
935
+
936
+ ipAdEntIfIndex OBJECT-TYPE
937
+ SYNTAX INTEGER
938
+ ACCESS read-only
939
+ STATUS mandatory
940
+ DESCRIPTION
941
+ "The index value which uniquely identifies the
942
+ interface to which this entry is applicable. The
943
+ interface identified by a particular value of this
944
+ index is the same interface as identified by the
945
+ same value of ifIndex."
946
+ ::= { ipAddrEntry 2 }
947
+
948
+ ipAdEntNetMask OBJECT-TYPE
949
+ SYNTAX IpAddress
950
+ ACCESS read-only
951
+ STATUS mandatory
952
+ DESCRIPTION
953
+ "The subnet mask associated with the IP address of
954
+ this entry. The value of the mask is an IP
955
+ address with all the network bits set to 1 and all
956
+ the hosts bits set to 0."
957
+ ::= { ipAddrEntry 3 }
958
+
959
+ ipAdEntBcastAddr OBJECT-TYPE
960
+ SYNTAX INTEGER
961
+ ACCESS read-only
962
+ STATUS mandatory
963
+ DESCRIPTION
964
+ "The value of the least-significant bit in the IP
965
+ broadcast address used for sending datagrams on
966
+ the (logical) interface associated with the IP
967
+ address of this entry. For example, when the
968
+ Internet standard all-ones broadcast address is
969
+ used, the value will be 1. This value applies to
970
+ both the subnet and network broadcasts addresses
971
+ used by the entity on this (logical) interface."
972
+ ::= { ipAddrEntry 4 }
973
+
974
+ ipAdEntReasmMaxSize OBJECT-TYPE
975
+ SYNTAX INTEGER (0..65535)
976
+ ACCESS read-only
977
+ STATUS mandatory
978
+ DESCRIPTION
979
+ "The size of the largest IP datagram which this
980
+ entity can re-assemble from incoming IP fragmented
981
+ datagrams received on this interface."
982
+ ::= { ipAddrEntry 5 }
983
+
984
+ -- the IP routing table
985
+
986
+ -- The IP routing table contains an entry for each route
987
+ -- presently known to this entity.
988
+
989
+ ipRouteTable OBJECT-TYPE
990
+ SYNTAX SEQUENCE OF IpRouteEntry
991
+ ACCESS not-accessible
992
+ STATUS mandatory
993
+ DESCRIPTION
994
+ "This entity's IP Routing table."
995
+ ::= { ip 21 }
996
+
997
+ ipRouteEntry OBJECT-TYPE
998
+ SYNTAX IpRouteEntry
999
+ ACCESS not-accessible
1000
+ STATUS mandatory
1001
+ DESCRIPTION
1002
+ "A route to a particular destination."
1003
+ INDEX { ipRouteDest }
1004
+ ::= { ipRouteTable 1 }
1005
+
1006
+ IpRouteEntry ::=
1007
+ SEQUENCE {
1008
+ ipRouteDest
1009
+ IpAddress,
1010
+ ipRouteIfIndex
1011
+ INTEGER,
1012
+ ipRouteMetric1
1013
+ INTEGER,
1014
+ ipRouteMetric2
1015
+ INTEGER,
1016
+ ipRouteMetric3
1017
+ INTEGER,
1018
+ ipRouteMetric4
1019
+ INTEGER,
1020
+ ipRouteNextHop
1021
+ IpAddress,
1022
+ ipRouteType
1023
+ INTEGER,
1024
+ ipRouteProto
1025
+ INTEGER,
1026
+ ipRouteAge
1027
+ INTEGER,
1028
+ ipRouteMask
1029
+ IpAddress,
1030
+ ipRouteMetric5
1031
+ INTEGER,
1032
+ ipRouteInfo
1033
+ OBJECT IDENTIFIER
1034
+ }
1035
+
1036
+ ipRouteDest OBJECT-TYPE
1037
+ SYNTAX IpAddress
1038
+ ACCESS read-write
1039
+ STATUS mandatory
1040
+ DESCRIPTION
1041
+ "The destination IP address of this route. An
1042
+ entry with a value of 0.0.0.0 is considered a
1043
+ default route. Multiple routes to a single
1044
+ destination can appear in the table, but access to
1045
+ such multiple entries is dependent on the table-
1046
+ access mechanisms defined by the network
1047
+ management protocol in use."
1048
+ ::= { ipRouteEntry 1 }
1049
+
1050
+ ipRouteIfIndex OBJECT-TYPE
1051
+ SYNTAX INTEGER
1052
+ ACCESS read-write
1053
+ STATUS mandatory
1054
+ DESCRIPTION
1055
+ "The index value which uniquely identifies the
1056
+ local interface through which the next hop of this
1057
+ route should be reached. The interface identified
1058
+ by a particular value of this index is the same
1059
+ interface as identified by the same value of
1060
+ ifIndex."
1061
+ ::= { ipRouteEntry 2 }
1062
+
1063
+ ipRouteMetric1 OBJECT-TYPE
1064
+ SYNTAX INTEGER
1065
+ ACCESS read-write
1066
+ STATUS mandatory
1067
+ DESCRIPTION
1068
+ "The primary routing metric for this route. The
1069
+ semantics of this metric are determined by the
1070
+ routing-protocol specified in the route's
1071
+ ipRouteProto value. If this metric is not used,
1072
+ its value should be set to -1."
1073
+ ::= { ipRouteEntry 3 }
1074
+
1075
+ ipRouteMetric2 OBJECT-TYPE
1076
+ SYNTAX INTEGER
1077
+ ACCESS read-write
1078
+ STATUS mandatory
1079
+ DESCRIPTION
1080
+ "An alternate routing metric for this route. The
1081
+ semantics of this metric are determined by the
1082
+ routing-protocol specified in the route's
1083
+ ipRouteProto value. If this metric is not used,
1084
+ its value should be set to -1."
1085
+ ::= { ipRouteEntry 4 }
1086
+
1087
+ ipRouteMetric3 OBJECT-TYPE
1088
+ SYNTAX INTEGER
1089
+ ACCESS read-write
1090
+ STATUS mandatory
1091
+ DESCRIPTION
1092
+ "An alternate routing metric for this route. The
1093
+ semantics of this metric are determined by the
1094
+ routing-protocol specified in the route's
1095
+ ipRouteProto value. If this metric is not used,
1096
+ its value should be set to -1."
1097
+ ::= { ipRouteEntry 5 }
1098
+
1099
+ ipRouteMetric4 OBJECT-TYPE
1100
+ SYNTAX INTEGER
1101
+ ACCESS read-write
1102
+ STATUS mandatory
1103
+ DESCRIPTION
1104
+ "An alternate routing metric for this route. The
1105
+ semantics of this metric are determined by the
1106
+ routing-protocol specified in the route's
1107
+ ipRouteProto value. If this metric is not used,
1108
+ its value should be set to -1."
1109
+ ::= { ipRouteEntry 6 }
1110
+
1111
+ ipRouteNextHop OBJECT-TYPE
1112
+ SYNTAX IpAddress
1113
+ ACCESS read-write
1114
+ STATUS mandatory
1115
+ DESCRIPTION
1116
+ "The IP address of the next hop of this route.
1117
+ (In the case of a route bound to an interface
1118
+ which is realized via a broadcast media, the value
1119
+ of this field is the agent's IP address on that
1120
+ interface.)"
1121
+ ::= { ipRouteEntry 7 }
1122
+
1123
+ ipRouteType OBJECT-TYPE
1124
+ SYNTAX INTEGER {
1125
+ other(1), -- none of the following
1126
+
1127
+ invalid(2), -- an invalidated route
1128
+
1129
+ -- route to directly
1130
+ direct(3), -- connected (sub-)network
1131
+
1132
+ -- route to a non-local
1133
+ indirect(4) -- host/network/sub-network
1134
+ }
1135
+ ACCESS read-write
1136
+ STATUS mandatory
1137
+ DESCRIPTION
1138
+ "The type of route. Note that the values
1139
+ direct(3) and indirect(4) refer to the notion of
1140
+ direct and indirect routing in the IP
1141
+ architecture.
1142
+
1143
+ Setting this object to the value invalid(2) has
1144
+ the effect of invalidating the corresponding entry
1145
+ in the ipRouteTable object. That is, it
1146
+ effectively dissasociates the destination
1147
+ identified with said entry from the route
1148
+ identified with said entry. It is an
1149
+ implementation-specific matter as to whether the
1150
+ agent removes an invalidated entry from the table.
1151
+ Accordingly, management stations must be prepared
1152
+ to receive tabular information from agents that
1153
+ corresponds to entries not currently in use.
1154
+ Proper interpretation of such entries requires
1155
+ examination of the relevant ipRouteType object."
1156
+ ::= { ipRouteEntry 8 }
1157
+
1158
+ ipRouteProto OBJECT-TYPE
1159
+ SYNTAX INTEGER {
1160
+ other(1), -- none of the following
1161
+
1162
+ -- non-protocol information,
1163
+ -- e.g., manually configured
1164
+ local(2), -- entries
1165
+
1166
+ -- set via a network
1167
+ netmgmt(3), -- management protocol
1168
+
1169
+ -- obtained via ICMP,
1170
+ icmp(4), -- e.g., Redirect
1171
+
1172
+ -- the remaining values are
1173
+ -- all gateway routing
1174
+ -- protocols
1175
+ egp(5),
1176
+ ggp(6),
1177
+ hello(7),
1178
+ rip(8),
1179
+ is-is(9),
1180
+ es-is(10),
1181
+ ciscoIgrp(11),
1182
+ bbnSpfIgp(12),
1183
+ ospf(13),
1184
+ bgp(14)
1185
+ }
1186
+ ACCESS read-only
1187
+ STATUS mandatory
1188
+ DESCRIPTION
1189
+ "The routing mechanism via which this route was
1190
+ learned. Inclusion of values for gateway routing
1191
+ protocols is not intended to imply that hosts
1192
+ should support those protocols."
1193
+ ::= { ipRouteEntry 9 }
1194
+
1195
+ ipRouteAge OBJECT-TYPE
1196
+ SYNTAX INTEGER
1197
+ ACCESS read-write
1198
+ STATUS mandatory
1199
+ DESCRIPTION
1200
+ "The number of seconds since this route was last
1201
+ updated or otherwise determined to be correct.
1202
+ Note that no semantics of `too old' can be implied
1203
+ except through knowledge of the routing protocol
1204
+ by which the route was learned."
1205
+ ::= { ipRouteEntry 10 }
1206
+
1207
+ ipRouteMask OBJECT-TYPE
1208
+ SYNTAX IpAddress
1209
+ ACCESS read-write
1210
+ STATUS mandatory
1211
+ DESCRIPTION
1212
+ "Indicate the mask to be logical-ANDed with the
1213
+ destination address before being compared to the
1214
+ value in the ipRouteDest field. For those systems
1215
+ that do not support arbitrary subnet masks, an
1216
+ agent constructs the value of the ipRouteMask by
1217
+ determining whether the value of the correspondent
1218
+ ipRouteDest field belong to a class-A, B, or C
1219
+ network, and then using one of:
1220
+
1221
+ mask network
1222
+ 255.0.0.0 class-A
1223
+ 255.255.0.0 class-B
1224
+ 255.255.255.0 class-C
1225
+ If the value of the ipRouteDest is 0.0.0.0 (a
1226
+ default route), then the mask value is also
1227
+ 0.0.0.0. It should be noted that all IP routing
1228
+ subsystems implicitly use this mechanism."
1229
+ ::= { ipRouteEntry 11 }
1230
+
1231
+ ipRouteMetric5 OBJECT-TYPE
1232
+ SYNTAX INTEGER
1233
+ ACCESS read-write
1234
+ STATUS mandatory
1235
+ DESCRIPTION
1236
+ "An alternate routing metric for this route. The
1237
+ semantics of this metric are determined by the
1238
+ routing-protocol specified in the route's
1239
+ ipRouteProto value. If this metric is not used,
1240
+ its value should be set to -1."
1241
+ ::= { ipRouteEntry 12 }
1242
+
1243
+ ipRouteInfo OBJECT-TYPE
1244
+ SYNTAX OBJECT IDENTIFIER
1245
+ ACCESS read-only
1246
+ STATUS mandatory
1247
+ DESCRIPTION
1248
+ "A reference to MIB definitions specific to the
1249
+ particular routing protocol which is responsible
1250
+ for this route, as determined by the value
1251
+ specified in the route's ipRouteProto value. If
1252
+ this information is not present, its value should
1253
+ be set to the OBJECT IDENTIFIER { 0 0 }, which is
1254
+ a syntatically valid object identifier, and any
1255
+ conformant implementation of ASN.1 and BER must be
1256
+ able to generate and recognize this value."
1257
+ ::= { ipRouteEntry 13 }
1258
+
1259
+
1260
+ -- the IP Address Translation table
1261
+
1262
+ -- The IP address translation table contain the IpAddress to
1263
+ -- `physical' address equivalences. Some interfaces do not
1264
+ -- use translation tables for determining address
1265
+ -- equivalences (e.g., DDN-X.25 has an algorithmic method);
1266
+ -- if all interfaces are of this type, then the Address
1267
+ -- Translation table is empty, i.e., has zero entries.
1268
+
1269
+ ipNetToMediaTable OBJECT-TYPE
1270
+ SYNTAX SEQUENCE OF IpNetToMediaEntry
1271
+ ACCESS not-accessible
1272
+ STATUS mandatory
1273
+ DESCRIPTION
1274
+ "The IP Address Translation table used for mapping
1275
+ from IP addresses to physical addresses."
1276
+ ::= { ip 22 }
1277
+
1278
+ ipNetToMediaEntry OBJECT-TYPE
1279
+ SYNTAX IpNetToMediaEntry
1280
+ ACCESS not-accessible
1281
+ STATUS mandatory
1282
+ DESCRIPTION
1283
+ "Each entry contains one IpAddress to `physical'
1284
+ address equivalence."
1285
+ INDEX { ipNetToMediaIfIndex,
1286
+ ipNetToMediaNetAddress }
1287
+ ::= { ipNetToMediaTable 1 }
1288
+
1289
+ IpNetToMediaEntry ::=
1290
+ SEQUENCE {
1291
+ ipNetToMediaIfIndex
1292
+ INTEGER,
1293
+ ipNetToMediaPhysAddress
1294
+ PhysAddress,
1295
+ ipNetToMediaNetAddress
1296
+ IpAddress,
1297
+ ipNetToMediaType
1298
+ INTEGER
1299
+ }
1300
+
1301
+ ipNetToMediaIfIndex OBJECT-TYPE
1302
+ SYNTAX INTEGER
1303
+ ACCESS read-write
1304
+ STATUS mandatory
1305
+ DESCRIPTION
1306
+ "The interface on which this entry's equivalence
1307
+ is effective. The interface identified by a
1308
+ particular value of this index is the same
1309
+ interface as identified by the same value of
1310
+ ifIndex."
1311
+ ::= { ipNetToMediaEntry 1 }
1312
+
1313
+ ipNetToMediaPhysAddress OBJECT-TYPE
1314
+ SYNTAX PhysAddress
1315
+ ACCESS read-write
1316
+ STATUS mandatory
1317
+ DESCRIPTION
1318
+ "The media-dependent `physical' address."
1319
+ ::= { ipNetToMediaEntry 2 }
1320
+
1321
+ ipNetToMediaNetAddress OBJECT-TYPE
1322
+ SYNTAX IpAddress
1323
+ ACCESS read-write
1324
+ STATUS mandatory
1325
+ DESCRIPTION
1326
+ "The IpAddress corresponding to the media-
1327
+ dependent `physical' address."
1328
+ ::= { ipNetToMediaEntry 3 }
1329
+
1330
+ ipNetToMediaType OBJECT-TYPE
1331
+ SYNTAX INTEGER {
1332
+ other(1), -- none of the following
1333
+ invalid(2), -- an invalidated mapping
1334
+ dynamic(3),
1335
+ static(4)
1336
+ }
1337
+ ACCESS read-write
1338
+ STATUS mandatory
1339
+ DESCRIPTION
1340
+ "The type of mapping.
1341
+
1342
+ Setting this object to the value invalid(2) has
1343
+ the effect of invalidating the corresponding entry
1344
+ in the ipNetToMediaTable. That is, it effectively
1345
+ dissasociates the interface identified with said
1346
+ entry from the mapping identified with said entry.
1347
+ It is an implementation-specific matter as to
1348
+ whether the agent removes an invalidated entry
1349
+ from the table. Accordingly, management stations
1350
+ must be prepared to receive tabular information
1351
+ from agents that corresponds to entries not
1352
+ currently in use. Proper interpretation of such
1353
+ entries requires examination of the relevant
1354
+ ipNetToMediaType object."
1355
+ ::= { ipNetToMediaEntry 4 }
1356
+
1357
+
1358
+ -- additional IP objects
1359
+
1360
+ ipRoutingDiscards OBJECT-TYPE
1361
+ SYNTAX Counter
1362
+ ACCESS read-only
1363
+ STATUS mandatory
1364
+ DESCRIPTION
1365
+ "The number of routing entries which were chosen
1366
+ to be discarded even though they are valid. One
1367
+ possible reason for discarding such an entry could
1368
+ be to free-up buffer space for other routing
1369
+ entries."
1370
+ ::= { ip 23 }
1371
+
1372
+
1373
+ -- the ICMP group
1374
+
1375
+ -- Implementation of the ICMP group is mandatory for all
1376
+ -- systems.
1377
+
1378
+ icmpInMsgs OBJECT-TYPE
1379
+ SYNTAX Counter
1380
+ ACCESS read-only
1381
+ STATUS mandatory
1382
+ DESCRIPTION
1383
+ "The total number of ICMP messages which the
1384
+ entity received. Note that this counter includes
1385
+ all those counted by icmpInErrors."
1386
+ ::= { icmp 1 }
1387
+
1388
+ icmpInErrors OBJECT-TYPE
1389
+ SYNTAX Counter
1390
+ ACCESS read-only
1391
+ STATUS mandatory
1392
+ DESCRIPTION
1393
+ "The number of ICMP messages which the entity
1394
+ received but determined as having ICMP-specific
1395
+ errors (bad ICMP checksums, bad length, etc.)."
1396
+ ::= { icmp 2 }
1397
+
1398
+ icmpInDestUnreachs OBJECT-TYPE
1399
+ SYNTAX Counter
1400
+ ACCESS read-only
1401
+ STATUS mandatory
1402
+ DESCRIPTION
1403
+ "The number of ICMP Destination Unreachable
1404
+ messages received."
1405
+ ::= { icmp 3 }
1406
+
1407
+ icmpInTimeExcds OBJECT-TYPE
1408
+ SYNTAX Counter
1409
+ ACCESS read-only
1410
+ STATUS mandatory
1411
+ DESCRIPTION
1412
+ "The number of ICMP Time Exceeded messages
1413
+ received."
1414
+ ::= { icmp 4 }
1415
+
1416
+ icmpInParmProbs OBJECT-TYPE
1417
+ SYNTAX Counter
1418
+ ACCESS read-only
1419
+ STATUS mandatory
1420
+ DESCRIPTION
1421
+ "The number of ICMP Parameter Problem messages
1422
+ received."
1423
+ ::= { icmp 5 }
1424
+
1425
+ icmpInSrcQuenchs OBJECT-TYPE
1426
+ SYNTAX Counter
1427
+ ACCESS read-only
1428
+ STATUS mandatory
1429
+ DESCRIPTION
1430
+ "The number of ICMP Source Quench messages
1431
+ received."
1432
+ ::= { icmp 6 }
1433
+
1434
+ icmpInRedirects OBJECT-TYPE
1435
+ SYNTAX Counter
1436
+ ACCESS read-only
1437
+ STATUS mandatory
1438
+ DESCRIPTION
1439
+ "The number of ICMP Redirect messages received."
1440
+ ::= { icmp 7 }
1441
+
1442
+ icmpInEchos OBJECT-TYPE
1443
+ SYNTAX Counter
1444
+ ACCESS read-only
1445
+ STATUS mandatory
1446
+ DESCRIPTION
1447
+ "The number of ICMP Echo (request) messages
1448
+ received."
1449
+ ::= { icmp 8 }
1450
+
1451
+ icmpInEchoReps OBJECT-TYPE
1452
+ SYNTAX Counter
1453
+ ACCESS read-only
1454
+ STATUS mandatory
1455
+ DESCRIPTION
1456
+ "The number of ICMP Echo Reply messages received."
1457
+ ::= { icmp 9 }
1458
+
1459
+ icmpInTimestamps OBJECT-TYPE
1460
+ SYNTAX Counter
1461
+ ACCESS read-only
1462
+ STATUS mandatory
1463
+ DESCRIPTION
1464
+ "The number of ICMP Timestamp (request) messages
1465
+ received."
1466
+ ::= { icmp 10 }
1467
+
1468
+ icmpInTimestampReps OBJECT-TYPE
1469
+ SYNTAX Counter
1470
+ ACCESS read-only
1471
+ STATUS mandatory
1472
+ DESCRIPTION
1473
+ "The number of ICMP Timestamp Reply messages
1474
+ received."
1475
+ ::= { icmp 11 }
1476
+
1477
+ icmpInAddrMasks OBJECT-TYPE
1478
+ SYNTAX Counter
1479
+ ACCESS read-only
1480
+ STATUS mandatory
1481
+ DESCRIPTION
1482
+ "The number of ICMP Address Mask Request messages
1483
+ received."
1484
+ ::= { icmp 12 }
1485
+
1486
+ icmpInAddrMaskReps OBJECT-TYPE
1487
+ SYNTAX Counter
1488
+ ACCESS read-only
1489
+ STATUS mandatory
1490
+ DESCRIPTION
1491
+ "The number of ICMP Address Mask Reply messages
1492
+ received."
1493
+ ::= { icmp 13 }
1494
+
1495
+ icmpOutMsgs OBJECT-TYPE
1496
+ SYNTAX Counter
1497
+ ACCESS read-only
1498
+ STATUS mandatory
1499
+ DESCRIPTION
1500
+ "The total number of ICMP messages which this
1501
+ entity attempted to send. Note that this counter
1502
+ includes all those counted by icmpOutErrors."
1503
+ ::= { icmp 14 }
1504
+
1505
+ icmpOutErrors OBJECT-TYPE
1506
+ SYNTAX Counter
1507
+ ACCESS read-only
1508
+ STATUS mandatory
1509
+ DESCRIPTION
1510
+ "The number of ICMP messages which this entity did
1511
+ not send due to problems discovered within ICMP
1512
+ such as a lack of buffers. This value should not
1513
+ include errors discovered outside the ICMP layer
1514
+ such as the inability of IP to route the resultant
1515
+ datagram. In some implementations there may be no
1516
+ types of error which contribute to this counter's
1517
+ value."
1518
+ ::= { icmp 15 }
1519
+
1520
+ icmpOutDestUnreachs OBJECT-TYPE
1521
+ SYNTAX Counter
1522
+ ACCESS read-only
1523
+ STATUS mandatory
1524
+ DESCRIPTION
1525
+ "The number of ICMP Destination Unreachable
1526
+ messages sent."
1527
+ ::= { icmp 16 }
1528
+
1529
+ icmpOutTimeExcds OBJECT-TYPE
1530
+ SYNTAX Counter
1531
+ ACCESS read-only
1532
+ STATUS mandatory
1533
+ DESCRIPTION
1534
+ "The number of ICMP Time Exceeded messages sent."
1535
+ ::= { icmp 17 }
1536
+
1537
+ icmpOutParmProbs OBJECT-TYPE
1538
+ SYNTAX Counter
1539
+ ACCESS read-only
1540
+ STATUS mandatory
1541
+ DESCRIPTION
1542
+ "The number of ICMP Parameter Problem messages
1543
+ sent."
1544
+ ::= { icmp 18 }
1545
+
1546
+ icmpOutSrcQuenchs OBJECT-TYPE
1547
+ SYNTAX Counter
1548
+ ACCESS read-only
1549
+ STATUS mandatory
1550
+ DESCRIPTION
1551
+ "The number of ICMP Source Quench messages sent."
1552
+ ::= { icmp 19 }
1553
+
1554
+ icmpOutRedirects OBJECT-TYPE
1555
+ SYNTAX Counter
1556
+ ACCESS read-only
1557
+ STATUS mandatory
1558
+ DESCRIPTION
1559
+ "The number of ICMP Redirect messages sent. For a
1560
+ host, this object will always be zero, since hosts
1561
+ do not send redirects."
1562
+ ::= { icmp 20 }
1563
+
1564
+ icmpOutEchos OBJECT-TYPE
1565
+ SYNTAX Counter
1566
+ ACCESS read-only
1567
+ STATUS mandatory
1568
+ DESCRIPTION
1569
+ "The number of ICMP Echo (request) messages sent."
1570
+ ::= { icmp 21 }
1571
+
1572
+ icmpOutEchoReps OBJECT-TYPE
1573
+ SYNTAX Counter
1574
+ ACCESS read-only
1575
+ STATUS mandatory
1576
+ DESCRIPTION
1577
+ "The number of ICMP Echo Reply messages sent."
1578
+ ::= { icmp 22 }
1579
+
1580
+ icmpOutTimestamps OBJECT-TYPE
1581
+ SYNTAX Counter
1582
+ ACCESS read-only
1583
+ STATUS mandatory
1584
+ DESCRIPTION
1585
+ "The number of ICMP Timestamp (request) messages
1586
+ sent."
1587
+ ::= { icmp 23 }
1588
+
1589
+ icmpOutTimestampReps OBJECT-TYPE
1590
+ SYNTAX Counter
1591
+ ACCESS read-only
1592
+ STATUS mandatory
1593
+ DESCRIPTION
1594
+ "The number of ICMP Timestamp Reply messages
1595
+ sent."
1596
+ ::= { icmp 24 }
1597
+
1598
+ icmpOutAddrMasks OBJECT-TYPE
1599
+ SYNTAX Counter
1600
+ ACCESS read-only
1601
+ STATUS mandatory
1602
+ DESCRIPTION
1603
+ "The number of ICMP Address Mask Request messages
1604
+ sent."
1605
+ ::= { icmp 25 }
1606
+
1607
+ icmpOutAddrMaskReps OBJECT-TYPE
1608
+ SYNTAX Counter
1609
+ ACCESS read-only
1610
+ STATUS mandatory
1611
+ DESCRIPTION
1612
+ "The number of ICMP Address Mask Reply messages
1613
+ sent."
1614
+ ::= { icmp 26 }
1615
+
1616
+
1617
+ -- the TCP group
1618
+
1619
+ -- Implementation of the TCP group is mandatory for all
1620
+ -- systems that implement the TCP.
1621
+
1622
+ -- Note that instances of object types that represent
1623
+ -- information about a particular TCP connection are
1624
+ -- transient; they persist only as long as the connection
1625
+ -- in question.
1626
+
1627
+ tcpRtoAlgorithm OBJECT-TYPE
1628
+ SYNTAX INTEGER {
1629
+ other(1), -- none of the following
1630
+
1631
+ constant(2), -- a constant rto
1632
+ rsre(3), -- MIL-STD-1778, Appendix B
1633
+ vanj(4) -- Van Jacobson's algorithm [10]
1634
+ }
1635
+ ACCESS read-only
1636
+ STATUS mandatory
1637
+ DESCRIPTION
1638
+ "The algorithm used to determine the timeout value
1639
+ used for retransmitting unacknowledged octets."
1640
+ ::= { tcp 1 }
1641
+
1642
+ tcpRtoMin OBJECT-TYPE
1643
+ SYNTAX INTEGER
1644
+ ACCESS read-only
1645
+ STATUS mandatory
1646
+ DESCRIPTION
1647
+ "The minimum value permitted by a TCP
1648
+ implementation for the retransmission timeout,
1649
+ measured in milliseconds. More refined semantics
1650
+ for objects of this type depend upon the algorithm
1651
+ used to determine the retransmission timeout. In
1652
+ particular, when the timeout algorithm is rsre(3),
1653
+ an object of this type has the semantics of the
1654
+ LBOUND quantity described in RFC 793."
1655
+ ::= { tcp 2 }
1656
+
1657
+
1658
+ tcpRtoMax OBJECT-TYPE
1659
+ SYNTAX INTEGER
1660
+ ACCESS read-only
1661
+ STATUS mandatory
1662
+ DESCRIPTION
1663
+ "The maximum value permitted by a TCP
1664
+ implementation for the retransmission timeout,
1665
+ measured in milliseconds. More refined semantics
1666
+ for objects of this type depend upon the algorithm
1667
+ used to determine the retransmission timeout. In
1668
+ particular, when the timeout algorithm is rsre(3),
1669
+ an object of this type has the semantics of the
1670
+ UBOUND quantity described in RFC 793."
1671
+ ::= { tcp 3 }
1672
+
1673
+ tcpMaxConn OBJECT-TYPE
1674
+ SYNTAX INTEGER
1675
+ ACCESS read-only
1676
+ STATUS mandatory
1677
+ DESCRIPTION
1678
+ "The limit on the total number of TCP connections
1679
+ the entity can support. In entities where the
1680
+ maximum number of connections is dynamic, this
1681
+ object should contain the value -1."
1682
+ ::= { tcp 4 }
1683
+
1684
+ tcpActiveOpens OBJECT-TYPE
1685
+ SYNTAX Counter
1686
+ ACCESS read-only
1687
+ STATUS mandatory
1688
+ DESCRIPTION
1689
+ "The number of times TCP connections have made a
1690
+ direct transition to the SYN-SENT state from the
1691
+ CLOSED state."
1692
+ ::= { tcp 5 }
1693
+
1694
+ tcpPassiveOpens OBJECT-TYPE
1695
+ SYNTAX Counter
1696
+ ACCESS read-only
1697
+ STATUS mandatory
1698
+ DESCRIPTION
1699
+ "The number of times TCP connections have made a
1700
+ direct transition to the SYN-RCVD state from the
1701
+ LISTEN state."
1702
+ ::= { tcp 6 }
1703
+
1704
+ tcpAttemptFails OBJECT-TYPE
1705
+ SYNTAX Counter
1706
+ ACCESS read-only
1707
+ STATUS mandatory
1708
+ DESCRIPTION
1709
+ "The number of times TCP connections have made a
1710
+ direct transition to the CLOSED state from either
1711
+ the SYN-SENT state or the SYN-RCVD state, plus the
1712
+ number of times TCP connections have made a direct
1713
+ transition to the LISTEN state from the SYN-RCVD
1714
+ state."
1715
+ ::= { tcp 7 }
1716
+
1717
+ tcpEstabResets OBJECT-TYPE
1718
+ SYNTAX Counter
1719
+ ACCESS read-only
1720
+ STATUS mandatory
1721
+ DESCRIPTION
1722
+ "The number of times TCP connections have made a
1723
+ direct transition to the CLOSED state from either
1724
+ the ESTABLISHED state or the CLOSE-WAIT state."
1725
+ ::= { tcp 8 }
1726
+
1727
+ tcpCurrEstab OBJECT-TYPE
1728
+ SYNTAX Gauge
1729
+ ACCESS read-only
1730
+ STATUS mandatory
1731
+ DESCRIPTION
1732
+ "The number of TCP connections for which the
1733
+ current state is either ESTABLISHED or CLOSE-
1734
+ WAIT."
1735
+ ::= { tcp 9 }
1736
+
1737
+ tcpInSegs OBJECT-TYPE
1738
+ SYNTAX Counter
1739
+ ACCESS read-only
1740
+ STATUS mandatory
1741
+ DESCRIPTION
1742
+ "The total number of segments received, including
1743
+ those received in error. This count includes
1744
+ segments received on currently established
1745
+ connections."
1746
+ ::= { tcp 10 }
1747
+
1748
+ tcpOutSegs OBJECT-TYPE
1749
+ SYNTAX Counter
1750
+ ACCESS read-only
1751
+ STATUS mandatory
1752
+ DESCRIPTION
1753
+ "The total number of segments sent, including
1754
+ those on current connections but excluding those
1755
+ containing only retransmitted octets."
1756
+ ::= { tcp 11 }
1757
+
1758
+ tcpRetransSegs OBJECT-TYPE
1759
+ SYNTAX Counter
1760
+ ACCESS read-only
1761
+ STATUS mandatory
1762
+ DESCRIPTION
1763
+ "The total number of segments retransmitted - that
1764
+ is, the number of TCP segments transmitted
1765
+ containing one or more previously transmitted
1766
+ octets."
1767
+ ::= { tcp 12 }
1768
+
1769
+
1770
+ -- the TCP Connection table
1771
+
1772
+ -- The TCP connection table contains information about this
1773
+ -- entity's existing TCP connections.
1774
+
1775
+ tcpConnTable OBJECT-TYPE
1776
+ SYNTAX SEQUENCE OF TcpConnEntry
1777
+ ACCESS not-accessible
1778
+ STATUS mandatory
1779
+ DESCRIPTION
1780
+ "A table containing TCP connection-specific
1781
+ information."
1782
+ ::= { tcp 13 }
1783
+
1784
+ tcpConnEntry OBJECT-TYPE
1785
+ SYNTAX TcpConnEntry
1786
+ ACCESS not-accessible
1787
+ STATUS mandatory
1788
+ DESCRIPTION
1789
+ "Information about a particular current TCP
1790
+ connection. An object of this type is transient,
1791
+ in that it ceases to exist when (or soon after)
1792
+ the connection makes the transition to the CLOSED
1793
+ state."
1794
+ INDEX { tcpConnLocalAddress,
1795
+ tcpConnLocalPort,
1796
+ tcpConnRemAddress,
1797
+ tcpConnRemPort }
1798
+ ::= { tcpConnTable 1 }
1799
+
1800
+ TcpConnEntry ::=
1801
+ SEQUENCE {
1802
+ tcpConnState
1803
+ INTEGER,
1804
+ tcpConnLocalAddress
1805
+ IpAddress,
1806
+ tcpConnLocalPort
1807
+ INTEGER (0..65535),
1808
+ tcpConnRemAddress
1809
+ IpAddress,
1810
+ tcpConnRemPort
1811
+ INTEGER (0..65535)
1812
+ }
1813
+
1814
+ tcpConnState OBJECT-TYPE
1815
+ SYNTAX INTEGER {
1816
+ closed(1),
1817
+ listen(2),
1818
+ synSent(3),
1819
+ synReceived(4),
1820
+ established(5),
1821
+ finWait1(6),
1822
+ finWait2(7),
1823
+ closeWait(8),
1824
+ lastAck(9),
1825
+ closing(10),
1826
+ timeWait(11),
1827
+ deleteTCB(12)
1828
+ }
1829
+ ACCESS read-write
1830
+ STATUS mandatory
1831
+ DESCRIPTION
1832
+ "The state of this TCP connection.
1833
+
1834
+ The only value which may be set by a management
1835
+ station is deleteTCB(12). Accordingly, it is
1836
+ appropriate for an agent to return a `badValue'
1837
+ response if a management station attempts to set
1838
+ this object to any other value.
1839
+
1840
+ If a management station sets this object to the
1841
+ value deleteTCB(12), then this has the effect of
1842
+ deleting the TCB (as defined in RFC 793) of the
1843
+ corresponding connection on the managed node,
1844
+ resulting in immediate termination of the
1845
+ connection.
1846
+
1847
+ As an implementation-specific option, a RST
1848
+ segment may be sent from the managed node to the
1849
+ other TCP endpoint (note however that RST segments
1850
+ are not sent reliably)."
1851
+ ::= { tcpConnEntry 1 }
1852
+
1853
+ tcpConnLocalAddress OBJECT-TYPE
1854
+ SYNTAX IpAddress
1855
+ ACCESS read-only
1856
+ STATUS mandatory
1857
+ DESCRIPTION
1858
+ "The local IP address for this TCP connection. In
1859
+ the case of a connection in the listen state which
1860
+ is willing to accept connections for any IP
1861
+ interface associated with the node, the value
1862
+ 0.0.0.0 is used."
1863
+ ::= { tcpConnEntry 2 }
1864
+
1865
+ tcpConnLocalPort OBJECT-TYPE
1866
+ SYNTAX INTEGER (0..65535)
1867
+ ACCESS read-only
1868
+ STATUS mandatory
1869
+ DESCRIPTION
1870
+ "The local port number for this TCP connection."
1871
+ ::= { tcpConnEntry 3 }
1872
+
1873
+ tcpConnRemAddress OBJECT-TYPE
1874
+ SYNTAX IpAddress
1875
+ ACCESS read-only
1876
+ STATUS mandatory
1877
+ DESCRIPTION
1878
+ "The remote IP address for this TCP connection."
1879
+ ::= { tcpConnEntry 4 }
1880
+
1881
+ tcpConnRemPort OBJECT-TYPE
1882
+ SYNTAX INTEGER (0..65535)
1883
+ ACCESS read-only
1884
+ STATUS mandatory
1885
+ DESCRIPTION
1886
+ "The remote port number for this TCP connection."
1887
+ ::= { tcpConnEntry 5 }
1888
+
1889
+
1890
+ -- additional TCP objects
1891
+
1892
+ tcpInErrs OBJECT-TYPE
1893
+ SYNTAX Counter
1894
+ ACCESS read-only
1895
+ STATUS mandatory
1896
+ DESCRIPTION
1897
+ "The total number of segments received in error
1898
+ (e.g., bad TCP checksums)."
1899
+ ::= { tcp 14 }
1900
+
1901
+ tcpOutRsts OBJECT-TYPE
1902
+ SYNTAX Counter
1903
+ ACCESS read-only
1904
+ STATUS mandatory
1905
+ DESCRIPTION
1906
+ "The number of TCP segments sent containing the
1907
+ RST flag."
1908
+ ::= { tcp 15 }
1909
+
1910
+
1911
+ -- the UDP group
1912
+
1913
+ -- Implementation of the UDP group is mandatory for all
1914
+ -- systems which implement the UDP.
1915
+
1916
+ udpInDatagrams OBJECT-TYPE
1917
+ SYNTAX Counter
1918
+ ACCESS read-only
1919
+ STATUS mandatory
1920
+ DESCRIPTION
1921
+ "The total number of UDP datagrams delivered to
1922
+ UDP users."
1923
+ ::= { udp 1 }
1924
+
1925
+ udpNoPorts OBJECT-TYPE
1926
+ SYNTAX Counter
1927
+ ACCESS read-only
1928
+ STATUS mandatory
1929
+ DESCRIPTION
1930
+ "The total number of received UDP datagrams for
1931
+ which there was no application at the destination
1932
+ port."
1933
+ ::= { udp 2 }
1934
+
1935
+ udpInErrors OBJECT-TYPE
1936
+ SYNTAX Counter
1937
+ ACCESS read-only
1938
+ STATUS mandatory
1939
+ DESCRIPTION
1940
+ "The number of received UDP datagrams that could
1941
+ not be delivered for reasons other than the lack
1942
+ of an application at the destination port."
1943
+ ::= { udp 3 }
1944
+
1945
+ udpOutDatagrams OBJECT-TYPE
1946
+ SYNTAX Counter
1947
+ ACCESS read-only
1948
+ STATUS mandatory
1949
+ DESCRIPTION
1950
+ "The total number of UDP datagrams sent from this
1951
+ entity."
1952
+ ::= { udp 4 }
1953
+
1954
+
1955
+ -- the UDP Listener table
1956
+
1957
+ -- The UDP listener table contains information about this
1958
+ -- entity's UDP end-points on which a local application is
1959
+ -- currently accepting datagrams.
1960
+
1961
+ udpTable OBJECT-TYPE
1962
+ SYNTAX SEQUENCE OF UdpEntry
1963
+ ACCESS not-accessible
1964
+ STATUS mandatory
1965
+ DESCRIPTION
1966
+ "A table containing UDP listener information."
1967
+ ::= { udp 5 }
1968
+
1969
+ udpEntry OBJECT-TYPE
1970
+ SYNTAX UdpEntry
1971
+ ACCESS not-accessible
1972
+ STATUS mandatory
1973
+ DESCRIPTION
1974
+ "Information about a particular current UDP
1975
+ listener."
1976
+ INDEX { udpLocalAddress, udpLocalPort }
1977
+ ::= { udpTable 1 }
1978
+
1979
+ UdpEntry ::=
1980
+ SEQUENCE {
1981
+ udpLocalAddress
1982
+ IpAddress,
1983
+ udpLocalPort
1984
+ INTEGER (0..65535)
1985
+ }
1986
+
1987
+ udpLocalAddress OBJECT-TYPE
1988
+ SYNTAX IpAddress
1989
+ ACCESS read-only
1990
+ STATUS mandatory
1991
+ DESCRIPTION
1992
+ "The local IP address for this UDP listener. In
1993
+ the case of a UDP listener which is willing to
1994
+ accept datagrams for any IP interface associated
1995
+ with the node, the value 0.0.0.0 is used."
1996
+ ::= { udpEntry 1 }
1997
+
1998
+ udpLocalPort OBJECT-TYPE
1999
+ SYNTAX INTEGER (0..65535)
2000
+ ACCESS read-only
2001
+ STATUS mandatory
2002
+ DESCRIPTION
2003
+ "The local port number for this UDP listener."
2004
+ ::= { udpEntry 2 }
2005
+
2006
+
2007
+ -- the EGP group
2008
+
2009
+ -- Implementation of the EGP group is mandatory for all
2010
+ -- systems which implement the EGP.
2011
+
2012
+ egpInMsgs OBJECT-TYPE
2013
+ SYNTAX Counter
2014
+ ACCESS read-only
2015
+ STATUS mandatory
2016
+ DESCRIPTION
2017
+ "The number of EGP messages received without
2018
+ error."
2019
+ ::= { egp 1 }
2020
+
2021
+ egpInErrors OBJECT-TYPE
2022
+ SYNTAX Counter
2023
+ ACCESS read-only
2024
+ STATUS mandatory
2025
+ DESCRIPTION
2026
+ "The number of EGP messages received that proved
2027
+ to be in error."
2028
+ ::= { egp 2 }
2029
+
2030
+ egpOutMsgs OBJECT-TYPE
2031
+ SYNTAX Counter
2032
+ ACCESS read-only
2033
+ STATUS mandatory
2034
+ DESCRIPTION
2035
+ "The total number of locally generated EGP
2036
+ messages."
2037
+ ::= { egp 3 }
2038
+
2039
+ egpOutErrors OBJECT-TYPE
2040
+ SYNTAX Counter
2041
+ ACCESS read-only
2042
+ STATUS mandatory
2043
+ DESCRIPTION
2044
+ "The number of locally generated EGP messages not
2045
+ sent due to resource limitations within an EGP
2046
+ entity."
2047
+ ::= { egp 4 }
2048
+
2049
+
2050
+ -- the EGP Neighbor table
2051
+
2052
+ -- The EGP neighbor table contains information about this
2053
+ -- entity's EGP neighbors.
2054
+
2055
+ egpNeighTable OBJECT-TYPE
2056
+ SYNTAX SEQUENCE OF EgpNeighEntry
2057
+ ACCESS not-accessible
2058
+ STATUS mandatory
2059
+ DESCRIPTION
2060
+ "The EGP neighbor table."
2061
+ ::= { egp 5 }
2062
+
2063
+ egpNeighEntry OBJECT-TYPE
2064
+ SYNTAX EgpNeighEntry
2065
+ ACCESS not-accessible
2066
+ STATUS mandatory
2067
+ DESCRIPTION
2068
+ "Information about this entity's relationship with
2069
+ a particular EGP neighbor."
2070
+ INDEX { egpNeighAddr }
2071
+ ::= { egpNeighTable 1 }
2072
+
2073
+ EgpNeighEntry ::=
2074
+ SEQUENCE {
2075
+ egpNeighState
2076
+ INTEGER,
2077
+ egpNeighAddr
2078
+ IpAddress,
2079
+ egpNeighAs
2080
+ INTEGER,
2081
+ egpNeighInMsgs
2082
+ Counter,
2083
+ egpNeighInErrs
2084
+ Counter,
2085
+ egpNeighOutMsgs
2086
+ Counter,
2087
+ egpNeighOutErrs
2088
+ Counter,
2089
+ egpNeighInErrMsgs
2090
+ Counter,
2091
+ egpNeighOutErrMsgs
2092
+ Counter,
2093
+ egpNeighStateUps
2094
+ Counter,
2095
+ egpNeighStateDowns
2096
+ Counter,
2097
+ egpNeighIntervalHello
2098
+ INTEGER,
2099
+ egpNeighIntervalPoll
2100
+ INTEGER,
2101
+ egpNeighMode
2102
+ INTEGER,
2103
+ egpNeighEventTrigger
2104
+ INTEGER
2105
+ }
2106
+
2107
+ egpNeighState OBJECT-TYPE
2108
+ SYNTAX INTEGER {
2109
+ idle(1),
2110
+ acquisition(2),
2111
+ down(3),
2112
+ up(4),
2113
+ cease(5)
2114
+ }
2115
+ ACCESS read-only
2116
+ STATUS mandatory
2117
+ DESCRIPTION
2118
+ "The EGP state of the local system with respect to
2119
+ this entry's EGP neighbor. Each EGP state is
2120
+ represented by a value that is one greater than
2121
+ the numerical value associated with said state in
2122
+ RFC 904."
2123
+ ::= { egpNeighEntry 1 }
2124
+
2125
+ egpNeighAddr OBJECT-TYPE
2126
+ SYNTAX IpAddress
2127
+ ACCESS read-only
2128
+ STATUS mandatory
2129
+ DESCRIPTION
2130
+ "The IP address of this entry's EGP neighbor."
2131
+ ::= { egpNeighEntry 2 }
2132
+
2133
+ egpNeighAs OBJECT-TYPE
2134
+ SYNTAX INTEGER
2135
+ ACCESS read-only
2136
+ STATUS mandatory
2137
+ DESCRIPTION
2138
+ "The autonomous system of this EGP peer. Zero
2139
+ should be specified if the autonomous system
2140
+ number of the neighbor is not yet known."
2141
+ ::= { egpNeighEntry 3 }
2142
+
2143
+ egpNeighInMsgs OBJECT-TYPE
2144
+ SYNTAX Counter
2145
+ ACCESS read-only
2146
+ STATUS mandatory
2147
+ DESCRIPTION
2148
+ "The number of EGP messages received without error
2149
+ from this EGP peer."
2150
+ ::= { egpNeighEntry 4 }
2151
+
2152
+ egpNeighInErrs OBJECT-TYPE
2153
+ SYNTAX Counter
2154
+ ACCESS read-only
2155
+ STATUS mandatory
2156
+ DESCRIPTION
2157
+ "The number of EGP messages received from this EGP
2158
+ peer that proved to be in error (e.g., bad EGP
2159
+ checksum)."
2160
+ ::= { egpNeighEntry 5 }
2161
+
2162
+ egpNeighOutMsgs OBJECT-TYPE
2163
+ SYNTAX Counter
2164
+ ACCESS read-only
2165
+ STATUS mandatory
2166
+ DESCRIPTION
2167
+ "The number of locally generated EGP messages to
2168
+ this EGP peer."
2169
+ ::= { egpNeighEntry 6 }
2170
+
2171
+ egpNeighOutErrs OBJECT-TYPE
2172
+ SYNTAX Counter
2173
+ ACCESS read-only
2174
+ STATUS mandatory
2175
+ DESCRIPTION
2176
+ "The number of locally generated EGP messages not
2177
+ sent to this EGP peer due to resource limitations
2178
+ within an EGP entity."
2179
+ ::= { egpNeighEntry 7 }
2180
+
2181
+ egpNeighInErrMsgs OBJECT-TYPE
2182
+ SYNTAX Counter
2183
+ ACCESS read-only
2184
+ STATUS mandatory
2185
+ DESCRIPTION
2186
+ "The number of EGP-defined error messages received
2187
+ from this EGP peer."
2188
+ ::= { egpNeighEntry 8 }
2189
+
2190
+ egpNeighOutErrMsgs OBJECT-TYPE
2191
+ SYNTAX Counter
2192
+ ACCESS read-only
2193
+ STATUS mandatory
2194
+ DESCRIPTION
2195
+ "The number of EGP-defined error messages sent to
2196
+ this EGP peer."
2197
+ ::= { egpNeighEntry 9 }
2198
+
2199
+ egpNeighStateUps OBJECT-TYPE
2200
+ SYNTAX Counter
2201
+ ACCESS read-only
2202
+ STATUS mandatory
2203
+ DESCRIPTION
2204
+ "The number of EGP state transitions to the UP
2205
+ state with this EGP peer."
2206
+ ::= { egpNeighEntry 10 }
2207
+
2208
+ egpNeighStateDowns OBJECT-TYPE
2209
+ SYNTAX Counter
2210
+ ACCESS read-only
2211
+ STATUS mandatory
2212
+ DESCRIPTION
2213
+ "The number of EGP state transitions from the UP
2214
+ state to any other state with this EGP peer."
2215
+ ::= { egpNeighEntry 11 }
2216
+
2217
+ egpNeighIntervalHello OBJECT-TYPE
2218
+ SYNTAX INTEGER
2219
+ ACCESS read-only
2220
+ STATUS mandatory
2221
+ DESCRIPTION
2222
+ "The interval between EGP Hello command
2223
+ retransmissions (in hundredths of a second). This
2224
+ represents the t1 timer as defined in RFC 904."
2225
+ ::= { egpNeighEntry 12 }
2226
+
2227
+ egpNeighIntervalPoll OBJECT-TYPE
2228
+ SYNTAX INTEGER
2229
+ ACCESS read-only
2230
+ STATUS mandatory
2231
+ DESCRIPTION
2232
+ "The interval between EGP poll command
2233
+ retransmissions (in hundredths of a second). This
2234
+ represents the t3 timer as defined in RFC 904."
2235
+ ::= { egpNeighEntry 13 }
2236
+
2237
+ egpNeighMode OBJECT-TYPE
2238
+ SYNTAX INTEGER { active(1), passive(2) }
2239
+ ACCESS read-only
2240
+ STATUS mandatory
2241
+ DESCRIPTION
2242
+ "The polling mode of this EGP entity, either
2243
+ passive or active."
2244
+ ::= { egpNeighEntry 14 }
2245
+
2246
+ egpNeighEventTrigger OBJECT-TYPE
2247
+ SYNTAX INTEGER { start(1), stop(2) }
2248
+ ACCESS read-write
2249
+ STATUS mandatory
2250
+ DESCRIPTION
2251
+ "A control variable used to trigger operator-
2252
+ initiated Start and Stop events. When read, this
2253
+ variable always returns the most recent value that
2254
+ egpNeighEventTrigger was set to. If it has not
2255
+ been set since the last initialization of the
2256
+ network management subsystem on the node, it
2257
+ returns a value of `stop'.
2258
+
2259
+ When set, this variable causes a Start or Stop
2260
+ event on the specified neighbor, as specified on
2261
+ pages 8-10 of RFC 904. Briefly, a Start event
2262
+ causes an Idle peer to begin neighbor acquisition
2263
+ and a non-Idle peer to reinitiate neighbor
2264
+ acquisition. A stop event causes a non-Idle peer
2265
+ to return to the Idle state until a Start event
2266
+ occurs, either via egpNeighEventTrigger or
2267
+ otherwise."
2268
+ ::= { egpNeighEntry 15 }
2269
+
2270
+
2271
+ -- additional EGP objects
2272
+
2273
+ egpAs OBJECT-TYPE
2274
+ SYNTAX INTEGER
2275
+ ACCESS read-only
2276
+ STATUS mandatory
2277
+ DESCRIPTION
2278
+ "The autonomous system number of this EGP entity."
2279
+ ::= { egp 6 }
2280
+
2281
+ -- the Transmission group
2282
+
2283
+ -- Based on the transmission media underlying each interface
2284
+ -- on a system, the corresponding portion of the Transmission
2285
+ -- group is mandatory for that system.
2286
+
2287
+ -- When Internet-standard definitions for managing
2288
+ -- transmission media are defined, the transmission group is
2289
+ -- used to provide a prefix for the names of those objects.
2290
+
2291
+ -- Typically, such definitions reside in the experimental
2292
+ -- portion of the MIB until they are "proven", then as a
2293
+ -- part of the Internet standardization process, the
2294
+ -- definitions are accordingly elevated and a new object
2295
+ -- identifier, under the transmission group is defined. By
2296
+ -- convention, the name assigned is:
2297
+ --
2298
+ -- type OBJECT IDENTIFIER ::= { transmission number }
2299
+ --
2300
+ -- where "type" is the symbolic value used for the media in
2301
+ -- the ifType column of the ifTable object, and "number" is
2302
+ -- the actual integer value corresponding to the symbol.
2303
+
2304
+
2305
+ -- the SNMP group
2306
+
2307
+ -- Implementation of the SNMP group is mandatory for all
2308
+ -- systems which support an SNMP protocol entity. Some of
2309
+ -- the objects defined below will be zero-valued in those
2310
+ -- SNMP implementations that are optimized to support only
2311
+ -- those functions specific to either a management agent or
2312
+ -- a management station. In particular, it should be
2313
+ -- observed that the objects below refer to an SNMP entity,
2314
+ -- and there may be several SNMP entities residing on a
2315
+ -- managed node (e.g., if the node is hosting acting as
2316
+ -- a management station).
2317
+
2318
+ snmpInPkts OBJECT-TYPE
2319
+ SYNTAX Counter
2320
+ ACCESS read-only
2321
+ STATUS mandatory
2322
+ DESCRIPTION
2323
+ "The total number of Messages delivered to the
2324
+ SNMP entity from the transport service."
2325
+ ::= { snmp 1 }
2326
+
2327
+ snmpOutPkts OBJECT-TYPE
2328
+ SYNTAX Counter
2329
+ ACCESS read-only
2330
+ STATUS mandatory
2331
+ DESCRIPTION
2332
+ "The total number of SNMP Messages which were
2333
+ passed from the SNMP protocol entity to the
2334
+ transport service."
2335
+ ::= { snmp 2 }
2336
+
2337
+ snmpInBadVersions OBJECT-TYPE
2338
+ SYNTAX Counter
2339
+ ACCESS read-only
2340
+ STATUS mandatory
2341
+ DESCRIPTION
2342
+ "The total number of SNMP Messages which were
2343
+ delivered to the SNMP protocol entity and were for
2344
+ an unsupported SNMP version."
2345
+ ::= { snmp 3 }
2346
+
2347
+ snmpInBadCommunityNames OBJECT-TYPE
2348
+ SYNTAX Counter
2349
+ ACCESS read-only
2350
+ STATUS mandatory
2351
+ DESCRIPTION
2352
+ "The total number of SNMP Messages delivered to
2353
+ the SNMP protocol entity which used a SNMP
2354
+ community name not known to said entity."
2355
+ ::= { snmp 4 }
2356
+
2357
+ snmpInBadCommunityUses OBJECT-TYPE
2358
+ SYNTAX Counter
2359
+ ACCESS read-only
2360
+ STATUS mandatory
2361
+ DESCRIPTION
2362
+ "The total number of SNMP Messages delivered to
2363
+ the SNMP protocol entity which represented an SNMP
2364
+ operation which was not allowed by the SNMP
2365
+ community named in the Message."
2366
+ ::= { snmp 5 }
2367
+
2368
+ snmpInASNParseErrs OBJECT-TYPE
2369
+ SYNTAX Counter
2370
+ ACCESS read-only
2371
+ STATUS mandatory
2372
+ DESCRIPTION
2373
+ "The total number of ASN.1 or BER errors
2374
+ encountered by the SNMP protocol entity when
2375
+ decoding received SNMP Messages."
2376
+ ::= { snmp 6 }
2377
+
2378
+ -- { snmp 7 } is not used
2379
+
2380
+ snmpInTooBigs OBJECT-TYPE
2381
+ SYNTAX Counter
2382
+ ACCESS read-only
2383
+ STATUS mandatory
2384
+ DESCRIPTION
2385
+ "The total number of SNMP PDUs which were
2386
+ delivered to the SNMP protocol entity and for
2387
+ which the value of the error-status field is
2388
+ `tooBig'."
2389
+ ::= { snmp 8 }
2390
+
2391
+ snmpInNoSuchNames OBJECT-TYPE
2392
+ SYNTAX Counter
2393
+ ACCESS read-only
2394
+ STATUS mandatory
2395
+ DESCRIPTION
2396
+ "The total number of SNMP PDUs which were
2397
+ delivered to the SNMP protocol entity and for
2398
+ which the value of the error-status field is
2399
+ `noSuchName'."
2400
+ ::= { snmp 9 }
2401
+
2402
+ snmpInBadValues OBJECT-TYPE
2403
+ SYNTAX Counter
2404
+ ACCESS read-only
2405
+ STATUS mandatory
2406
+ DESCRIPTION
2407
+ "The total number of SNMP PDUs which were
2408
+ delivered to the SNMP protocol entity and for
2409
+ which the value of the error-status field is
2410
+ `badValue'."
2411
+ ::= { snmp 10 }
2412
+
2413
+ snmpInReadOnlys OBJECT-TYPE
2414
+ SYNTAX Counter
2415
+ ACCESS read-only
2416
+ STATUS mandatory
2417
+ DESCRIPTION
2418
+ "The total number valid SNMP PDUs which were
2419
+ delivered to the SNMP protocol entity and for
2420
+ which the value of the error-status field is
2421
+ `readOnly'. It should be noted that it is a
2422
+ protocol error to generate an SNMP PDU which
2423
+ contains the value `readOnly' in the error-status
2424
+ field, as such this object is provided as a means
2425
+ of detecting incorrect implementations of the
2426
+ SNMP."
2427
+ ::= { snmp 11 }
2428
+
2429
+ snmpInGenErrs OBJECT-TYPE
2430
+ SYNTAX Counter
2431
+ ACCESS read-only
2432
+ STATUS mandatory
2433
+ DESCRIPTION
2434
+ "The total number of SNMP PDUs which were
2435
+ delivered to the SNMP protocol entity and for
2436
+ which the value of the error-status field is
2437
+ `genErr'."
2438
+ ::= { snmp 12 }
2439
+
2440
+ snmpInTotalReqVars OBJECT-TYPE
2441
+ SYNTAX Counter
2442
+ ACCESS read-only
2443
+ STATUS mandatory
2444
+ DESCRIPTION
2445
+ "The total number of MIB objects which have been
2446
+ retrieved successfully by the SNMP protocol entity
2447
+ as the result of receiving valid SNMP Get-Request
2448
+ and Get-Next PDUs."
2449
+ ::= { snmp 13 }
2450
+
2451
+ snmpInTotalSetVars OBJECT-TYPE
2452
+ SYNTAX Counter
2453
+ ACCESS read-only
2454
+ STATUS mandatory
2455
+ DESCRIPTION
2456
+ "The total number of MIB objects which have been
2457
+ altered successfully by the SNMP protocol entity
2458
+ as the result of receiving valid SNMP Set-Request
2459
+ PDUs."
2460
+ ::= { snmp 14 }
2461
+
2462
+ snmpInGetRequests OBJECT-TYPE
2463
+ SYNTAX Counter
2464
+ ACCESS read-only
2465
+ STATUS mandatory
2466
+ DESCRIPTION
2467
+ "The total number of SNMP Get-Request PDUs which
2468
+ have been accepted and processed by the SNMP
2469
+ protocol entity."
2470
+ ::= { snmp 15 }
2471
+
2472
+ snmpInGetNexts OBJECT-TYPE
2473
+ SYNTAX Counter
2474
+ ACCESS read-only
2475
+ STATUS mandatory
2476
+ DESCRIPTION
2477
+ "The total number of SNMP Get-Next PDUs which have
2478
+ been accepted and processed by the SNMP protocol
2479
+ entity."
2480
+ ::= { snmp 16 }
2481
+
2482
+ snmpInSetRequests OBJECT-TYPE
2483
+ SYNTAX Counter
2484
+ ACCESS read-only
2485
+ STATUS mandatory
2486
+ DESCRIPTION
2487
+ "The total number of SNMP Set-Request PDUs which
2488
+ have been accepted and processed by the SNMP
2489
+ protocol entity."
2490
+ ::= { snmp 17 }
2491
+
2492
+ snmpInGetResponses OBJECT-TYPE
2493
+ SYNTAX Counter
2494
+ ACCESS read-only
2495
+ STATUS mandatory
2496
+ DESCRIPTION
2497
+ "The total number of SNMP Get-Response PDUs which
2498
+ have been accepted and processed by the SNMP
2499
+ protocol entity."
2500
+ ::= { snmp 18 }
2501
+
2502
+ snmpInTraps OBJECT-TYPE
2503
+ SYNTAX Counter
2504
+ ACCESS read-only
2505
+ STATUS mandatory
2506
+ DESCRIPTION
2507
+ "The total number of SNMP Trap PDUs which have
2508
+ been accepted and processed by the SNMP protocol
2509
+ entity."
2510
+ ::= { snmp 19 }
2511
+
2512
+ snmpOutTooBigs OBJECT-TYPE
2513
+ SYNTAX Counter
2514
+ ACCESS read-only
2515
+ STATUS mandatory
2516
+ DESCRIPTION
2517
+ "The total number of SNMP PDUs which were
2518
+ generated by the SNMP protocol entity and for
2519
+ which the value of the error-status field is
2520
+ `tooBig.'"
2521
+ ::= { snmp 20 }
2522
+
2523
+ snmpOutNoSuchNames OBJECT-TYPE
2524
+ SYNTAX Counter
2525
+ ACCESS read-only
2526
+ STATUS mandatory
2527
+ DESCRIPTION
2528
+ "The total number of SNMP PDUs which were
2529
+ generated by the SNMP protocol entity and for
2530
+ which the value of the error-status is
2531
+ `noSuchName'."
2532
+ ::= { snmp 21 }
2533
+
2534
+ snmpOutBadValues OBJECT-TYPE
2535
+ SYNTAX Counter
2536
+ ACCESS read-only
2537
+ STATUS mandatory
2538
+ DESCRIPTION
2539
+ "The total number of SNMP PDUs which were
2540
+ generated by the SNMP protocol entity and for
2541
+ which the value of the error-status field is
2542
+ `badValue'."
2543
+ ::= { snmp 22 }
2544
+
2545
+ -- { snmp 23 } is not used
2546
+
2547
+ snmpOutGenErrs OBJECT-TYPE
2548
+ SYNTAX Counter
2549
+ ACCESS read-only
2550
+ STATUS mandatory
2551
+ DESCRIPTION
2552
+ "The total number of SNMP PDUs which were
2553
+ generated by the SNMP protocol entity and for
2554
+ which the value of the error-status field is
2555
+ `genErr'."
2556
+ ::= { snmp 24 }
2557
+
2558
+ snmpOutGetRequests OBJECT-TYPE
2559
+ SYNTAX Counter
2560
+ ACCESS read-only
2561
+ STATUS mandatory
2562
+ DESCRIPTION
2563
+ "The total number of SNMP Get-Request PDUs which
2564
+ have been generated by the SNMP protocol entity."
2565
+ ::= { snmp 25 }
2566
+
2567
+ snmpOutGetNexts OBJECT-TYPE
2568
+ SYNTAX Counter
2569
+ ACCESS read-only
2570
+ STATUS mandatory
2571
+ DESCRIPTION
2572
+ "The total number of SNMP Get-Next PDUs which have
2573
+ been generated by the SNMP protocol entity."
2574
+ ::= { snmp 26 }
2575
+
2576
+ snmpOutSetRequests OBJECT-TYPE
2577
+ SYNTAX Counter
2578
+ ACCESS read-only
2579
+ STATUS mandatory
2580
+ DESCRIPTION
2581
+ "The total number of SNMP Set-Request PDUs which
2582
+ have been generated by the SNMP protocol entity."
2583
+ ::= { snmp 27 }
2584
+
2585
+ snmpOutGetResponses OBJECT-TYPE
2586
+ SYNTAX Counter
2587
+ ACCESS read-only
2588
+ STATUS mandatory
2589
+ DESCRIPTION
2590
+ "The total number of SNMP Get-Response PDUs which
2591
+ have been generated by the SNMP protocol entity."
2592
+ ::= { snmp 28 }
2593
+
2594
+ snmpOutTraps OBJECT-TYPE
2595
+ SYNTAX Counter
2596
+ ACCESS read-only
2597
+ STATUS mandatory
2598
+ DESCRIPTION
2599
+ "The total number of SNMP Trap PDUs which have
2600
+ been generated by the SNMP protocol entity."
2601
+ ::= { snmp 29 }
2602
+
2603
+ snmpEnableAuthenTraps OBJECT-TYPE
2604
+ SYNTAX INTEGER { enabled(1), disabled(2) }
2605
+ ACCESS read-write
2606
+ STATUS mandatory
2607
+ DESCRIPTION
2608
+ "Indicates whether the SNMP agent process is
2609
+ permitted to generate authentication-failure
2610
+ traps. The value of this object overrides any
2611
+ configuration information; as such, it provides a
2612
+ means whereby all authentication-failure traps may
2613
+ be disabled.
2614
+
2615
+ Note that it is strongly recommended that this
2616
+ object be stored in non-volatile memory so that it
2617
+ remains constant between re-initializations of the
2618
+ network management system."
2619
+ ::= { snmp 30 }
2620
+
2621
+ END