1 RFC1213-MIB DEFINITIONS ::= BEGIN
4 mgmt, NetworkAddress, IpAddress, Counter, Gauge,
10 -- This MIB module uses the extended OBJECT-TYPE macro as
14 -- MIB-II (same prefix as MIB-I)
16 mib-2 OBJECT IDENTIFIER ::= { mgmt 1 }
18 -- textual conventions
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
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.
39 system OBJECT IDENTIFIER ::= { mib-2 1 }
41 interfaces OBJECT IDENTIFIER ::= { mib-2 2 }
43 at OBJECT IDENTIFIER ::= { mib-2 3 }
45 ip OBJECT IDENTIFIER ::= { mib-2 4 }
47 icmp OBJECT IDENTIFIER ::= { mib-2 5 }
49 tcp OBJECT IDENTIFIER ::= { mib-2 6 }
51 udp OBJECT IDENTIFIER ::= { mib-2 7 }
53 egp OBJECT IDENTIFIER ::= { mib-2 8 }
55 -- historical (some say hysterical)
56 -- cmot OBJECT IDENTIFIER ::= { mib-2 9 }
58 transmission OBJECT IDENTIFIER ::= { mib-2 10 }
60 snmp OBJECT IDENTIFIER ::= { mib-2 11 }
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
71 SYNTAX DisplayString (SIZE (0..255))
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."
83 sysObjectID OBJECT-TYPE
84 SYNTAX OBJECT IDENTIFIER
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
100 sysUpTime OBJECT-TYPE
105 "The time (in hundredths of a second) since the
106 network management portion of the system was last
110 sysContact OBJECT-TYPE
111 SYNTAX DisplayString (SIZE (0..255))
115 "The textual identification of the contact person
116 for this managed node, together with information
117 on how to contact this person."
121 SYNTAX DisplayString (SIZE (0..255))
125 "An administratively-assigned name for this
126 managed node. By convention, this is the node's
127 fully-qualified domain name."
130 sysLocation OBJECT-TYPE
131 SYNTAX DisplayString (SIZE (0..255))
135 "The physical location of this node (e.g.,
136 `telephone closet, 3rd floor')."
139 sysServices OBJECT-TYPE
140 SYNTAX INTEGER (0..127)
144 "A value which indicates the set of services that
145 this entity primarily offers.
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:
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)
166 For systems including OSI protocols, layers 5 and
167 6 may also be counted."
170 -- the Interfaces group
172 -- Implementation of the Interfaces group is mandatory for
180 "The number of network interfaces (regardless of
181 their current state) present on this system."
185 -- the Interfaces table
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
195 SYNTAX SEQUENCE OF IfEntry
196 ACCESS not-accessible
199 "A list of interface entries. The number of
200 entries is given by the value of ifNumber."
205 ACCESS not-accessible
208 "An interface entry containing objects at the
209 subnetwork layer and below for a particular
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-
276 SYNTAX DisplayString (SIZE (0..255))
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."
288 other(1), -- none of the following
295 iso88024-tokenBus(8),
296 iso88025-tokenRing(9),
306 e1(19), -- european equiv. of T-1
308 primaryISDN(21), -- proprietary serial
309 propPointToPointSerial(22),
311 softwareLoopback(24),
312 eon(25), -- CLNP over IP [11]
314 nsip(27), -- XNS over IP
315 slip(28), -- generic SLIP
316 ultra(29), -- ULTRA technologies
324 "The type of interface, distinguished according to
325 the physical/link protocol(s) immediately `below'
326 the network layer in the protocol stack."
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
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."
354 ifPhysAddress OBJECT-TYPE
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."
366 ifAdminStatus OBJECT-TYPE
368 up(1), -- ready to pass packets
370 testing(3) -- in some test mode
375 "The desired state of the interface. The
376 testing(3) state indicates that no operational
377 packets can be passed."
380 ifOperStatus OBJECT-TYPE
382 up(1), -- ready to pass packets
384 testing(3) -- in some test mode
389 "The current operational state of the interface.
390 The testing(3) state indicates that no operational
391 packets can be passed."
394 ifLastChange OBJECT-TYPE
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
407 ifInOctets OBJECT-TYPE
412 "The total number of octets received on the
413 interface, including framing characters."
416 ifInUcastPkts OBJECT-TYPE
421 "The number of subnetwork-unicast packets
422 delivered to a higher-layer protocol."
425 ifInNUcastPkts OBJECT-TYPE
430 "The number of non-unicast (i.e., subnetwork-
431 broadcast or subnetwork-multicast) packets
432 delivered to a higher-layer protocol."
435 ifInDiscards OBJECT-TYPE
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
448 ifInErrors OBJECT-TYPE
453 "The number of inbound packets that contained
454 errors preventing them from being deliverable to a
455 higher-layer protocol."
458 ifInUnknownProtos OBJECT-TYPE
463 "The number of packets received via the interface
464 which were discarded because of an unknown or
465 unsupported protocol."
468 ifOutOctets OBJECT-TYPE
473 "The total number of octets transmitted out of the
474 interface, including framing characters."
477 ifOutUcastPkts OBJECT-TYPE
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."
488 ifOutNUcastPkts OBJECT-TYPE
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."
500 ifOutDiscards OBJECT-TYPE
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."
512 ifOutErrors OBJECT-TYPE
517 "The number of outbound packets that could not be
518 transmitted because of errors."
521 ifOutQLen OBJECT-TYPE
526 "The length of the output packet queue (in
530 ifSpecific OBJECT-TYPE
531 SYNTAX OBJECT IDENTIFIER
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."
549 -- the Address Translation group
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
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.
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.
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.
575 SYNTAX SEQUENCE OF AtEntry
576 ACCESS not-accessible
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."
590 ACCESS not-accessible
593 "Each entry contains one NetworkAddress to
594 `physical' address equivalence."
609 atIfIndex OBJECT-TYPE
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
621 atPhysAddress OBJECT-TYPE
626 "The media-dependent `physical' address.
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."
643 atNetAddress OBJECT-TYPE
644 SYNTAX NetworkAddress
648 "The NetworkAddress (e.g., the IP address)
649 corresponding to the media-dependent `physical'
656 -- Implementation of the IP group is mandatory for all
659 ipForwarding OBJECT-TYPE
661 forwarding(1), -- acting as a gateway
662 not-forwarding(2) -- NOT acting as a gateway
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).
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."
681 ipDefaultTTL OBJECT-TYPE
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."
692 ipInReceives OBJECT-TYPE
697 "The total number of input datagrams received from
698 interfaces, including those received in error."
701 ipInHdrErrors OBJECT-TYPE
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."
713 ipInAddrErrors OBJECT-TYPE
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
730 ipForwDatagrams OBJECT-TYPE
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."
745 ipInUnknownProtos OBJECT-TYPE
750 "The number of locally-addressed datagrams
751 received successfully but discarded because of an
752 unknown or unsupported protocol."
755 ipInDiscards OBJECT-TYPE
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."
768 ipInDelivers OBJECT-TYPE
773 "The total number of input datagrams successfully
774 delivered to IP user-protocols (including ICMP)."
777 ipOutRequests OBJECT-TYPE
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
789 ipOutDiscards OBJECT-TYPE
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."
803 ipOutNoRoutes OBJECT-TYPE
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."
817 ipReasmTimeout OBJECT-TYPE
822 "The maximum number of seconds which received
823 fragments are held while they are awaiting
824 reassembly at this entity."
827 ipReasmReqds OBJECT-TYPE
832 "The number of IP fragments received which needed
833 to be reassembled at this entity."
836 ipReasmOKs OBJECT-TYPE
841 "The number of IP datagrams successfully re-
845 ipReasmFails OBJECT-TYPE
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."
859 ipFragOKs OBJECT-TYPE
864 "The number of IP datagrams that have been
865 successfully fragmented at this entity."
868 ipFragFails OBJECT-TYPE
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."
879 ipFragCreates OBJECT-TYPE
884 "The number of IP datagram fragments that have
885 been generated as a result of fragmentation at
889 -- the IP address table
891 -- The IP address table contains this entity's IP addressing
894 ipAddrTable OBJECT-TYPE
895 SYNTAX SEQUENCE OF IpAddrEntry
896 ACCESS not-accessible
899 "The table of addressing information relevant to
900 this entity's IP addresses."
903 ipAddrEntry OBJECT-TYPE
905 ACCESS not-accessible
908 "The addressing information for one of this
909 entity's IP addresses."
910 INDEX { ipAdEntAddr }
911 ::= { ipAddrTable 1 }
927 ipAdEntAddr OBJECT-TYPE
932 "The IP address to which this entry's addressing
933 information pertains."
934 ::= { ipAddrEntry 1 }
936 ipAdEntIfIndex OBJECT-TYPE
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 }
948 ipAdEntNetMask OBJECT-TYPE
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 }
959 ipAdEntBcastAddr OBJECT-TYPE
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 }
974 ipAdEntReasmMaxSize OBJECT-TYPE
975 SYNTAX INTEGER (0..65535)
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 }
984 -- the IP routing table
986 -- The IP routing table contains an entry for each route
987 -- presently known to this entity.
989 ipRouteTable OBJECT-TYPE
990 SYNTAX SEQUENCE OF IpRouteEntry
991 ACCESS not-accessible
994 "This entity's IP Routing table."
997 ipRouteEntry OBJECT-TYPE
999 ACCESS not-accessible
1002 "A route to a particular destination."
1003 INDEX { ipRouteDest }
1004 ::= { ipRouteTable 1 }
1036 ipRouteDest OBJECT-TYPE
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 }
1050 ipRouteIfIndex OBJECT-TYPE
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
1061 ::= { ipRouteEntry 2 }
1063 ipRouteMetric1 OBJECT-TYPE
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 }
1075 ipRouteMetric2 OBJECT-TYPE
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 }
1087 ipRouteMetric3 OBJECT-TYPE
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 }
1099 ipRouteMetric4 OBJECT-TYPE
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 }
1111 ipRouteNextHop OBJECT-TYPE
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
1121 ::= { ipRouteEntry 7 }
1123 ipRouteType OBJECT-TYPE
1125 other(1), -- none of the following
1127 invalid(2), -- an invalidated route
1129 -- route to directly
1130 direct(3), -- connected (sub-)network
1132 -- route to a non-local
1133 indirect(4) -- host/network/sub-network
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
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 }
1158 ipRouteProto OBJECT-TYPE
1160 other(1), -- none of the following
1162 -- non-protocol information,
1163 -- e.g., manually configured
1164 local(2), -- entries
1166 -- set via a network
1167 netmgmt(3), -- management protocol
1169 -- obtained via ICMP,
1170 icmp(4), -- e.g., Redirect
1172 -- the remaining values are
1173 -- all gateway routing
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 }
1195 ipRouteAge OBJECT-TYPE
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 }
1207 ipRouteMask OBJECT-TYPE
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:
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 }
1231 ipRouteMetric5 OBJECT-TYPE
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 }
1243 ipRouteInfo OBJECT-TYPE
1244 SYNTAX OBJECT IDENTIFIER
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 }
1260 -- the IP Address Translation table
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.
1269 ipNetToMediaTable OBJECT-TYPE
1270 SYNTAX SEQUENCE OF IpNetToMediaEntry
1271 ACCESS not-accessible
1274 "The IP Address Translation table used for mapping
1275 from IP addresses to physical addresses."
1278 ipNetToMediaEntry OBJECT-TYPE
1279 SYNTAX IpNetToMediaEntry
1280 ACCESS not-accessible
1283 "Each entry contains one IpAddress to `physical'
1284 address equivalence."
1285 INDEX { ipNetToMediaIfIndex,
1286 ipNetToMediaNetAddress }
1287 ::= { ipNetToMediaTable 1 }
1289 IpNetToMediaEntry ::=
1293 ipNetToMediaPhysAddress
1295 ipNetToMediaNetAddress
1301 ipNetToMediaIfIndex OBJECT-TYPE
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
1311 ::= { ipNetToMediaEntry 1 }
1313 ipNetToMediaPhysAddress OBJECT-TYPE
1318 "The media-dependent `physical' address."
1319 ::= { ipNetToMediaEntry 2 }
1321 ipNetToMediaNetAddress OBJECT-TYPE
1326 "The IpAddress corresponding to the media-
1327 dependent `physical' address."
1328 ::= { ipNetToMediaEntry 3 }
1330 ipNetToMediaType OBJECT-TYPE
1332 other(1), -- none of the following
1333 invalid(2), -- an invalidated mapping
1340 "The type of mapping.
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 }
1358 -- additional IP objects
1360 ipRoutingDiscards OBJECT-TYPE
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
1375 -- Implementation of the ICMP group is mandatory for all
1378 icmpInMsgs OBJECT-TYPE
1383 "The total number of ICMP messages which the
1384 entity received. Note that this counter includes
1385 all those counted by icmpInErrors."
1388 icmpInErrors OBJECT-TYPE
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.)."
1398 icmpInDestUnreachs OBJECT-TYPE
1403 "The number of ICMP Destination Unreachable
1407 icmpInTimeExcds OBJECT-TYPE
1412 "The number of ICMP Time Exceeded messages
1416 icmpInParmProbs OBJECT-TYPE
1421 "The number of ICMP Parameter Problem messages
1425 icmpInSrcQuenchs OBJECT-TYPE
1430 "The number of ICMP Source Quench messages
1434 icmpInRedirects OBJECT-TYPE
1439 "The number of ICMP Redirect messages received."
1442 icmpInEchos OBJECT-TYPE
1447 "The number of ICMP Echo (request) messages
1451 icmpInEchoReps OBJECT-TYPE
1456 "The number of ICMP Echo Reply messages received."
1459 icmpInTimestamps OBJECT-TYPE
1464 "The number of ICMP Timestamp (request) messages
1468 icmpInTimestampReps OBJECT-TYPE
1473 "The number of ICMP Timestamp Reply messages
1477 icmpInAddrMasks OBJECT-TYPE
1482 "The number of ICMP Address Mask Request messages
1486 icmpInAddrMaskReps OBJECT-TYPE
1491 "The number of ICMP Address Mask Reply messages
1495 icmpOutMsgs OBJECT-TYPE
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."
1505 icmpOutErrors OBJECT-TYPE
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
1520 icmpOutDestUnreachs OBJECT-TYPE
1525 "The number of ICMP Destination Unreachable
1529 icmpOutTimeExcds OBJECT-TYPE
1534 "The number of ICMP Time Exceeded messages sent."
1537 icmpOutParmProbs OBJECT-TYPE
1542 "The number of ICMP Parameter Problem messages
1546 icmpOutSrcQuenchs OBJECT-TYPE
1551 "The number of ICMP Source Quench messages sent."
1554 icmpOutRedirects OBJECT-TYPE
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."
1564 icmpOutEchos OBJECT-TYPE
1569 "The number of ICMP Echo (request) messages sent."
1572 icmpOutEchoReps OBJECT-TYPE
1577 "The number of ICMP Echo Reply messages sent."
1580 icmpOutTimestamps OBJECT-TYPE
1585 "The number of ICMP Timestamp (request) messages
1589 icmpOutTimestampReps OBJECT-TYPE
1594 "The number of ICMP Timestamp Reply messages
1598 icmpOutAddrMasks OBJECT-TYPE
1603 "The number of ICMP Address Mask Request messages
1607 icmpOutAddrMaskReps OBJECT-TYPE
1612 "The number of ICMP Address Mask Reply messages
1619 -- Implementation of the TCP group is mandatory for all
1620 -- systems that implement the TCP.
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
1627 tcpRtoAlgorithm OBJECT-TYPE
1629 other(1), -- none of the following
1631 constant(2), -- a constant rto
1632 rsre(3), -- MIL-STD-1778, Appendix B
1633 vanj(4) -- Van Jacobson's algorithm [10]
1638 "The algorithm used to determine the timeout value
1639 used for retransmitting unacknowledged octets."
1642 tcpRtoMin OBJECT-TYPE
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."
1658 tcpRtoMax OBJECT-TYPE
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."
1673 tcpMaxConn OBJECT-TYPE
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."
1684 tcpActiveOpens OBJECT-TYPE
1689 "The number of times TCP connections have made a
1690 direct transition to the SYN-SENT state from the
1694 tcpPassiveOpens OBJECT-TYPE
1699 "The number of times TCP connections have made a
1700 direct transition to the SYN-RCVD state from the
1704 tcpAttemptFails OBJECT-TYPE
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
1717 tcpEstabResets OBJECT-TYPE
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."
1727 tcpCurrEstab OBJECT-TYPE
1732 "The number of TCP connections for which the
1733 current state is either ESTABLISHED or CLOSE-
1737 tcpInSegs OBJECT-TYPE
1742 "The total number of segments received, including
1743 those received in error. This count includes
1744 segments received on currently established
1748 tcpOutSegs OBJECT-TYPE
1753 "The total number of segments sent, including
1754 those on current connections but excluding those
1755 containing only retransmitted octets."
1758 tcpRetransSegs OBJECT-TYPE
1763 "The total number of segments retransmitted - that
1764 is, the number of TCP segments transmitted
1765 containing one or more previously transmitted
1770 -- the TCP Connection table
1772 -- The TCP connection table contains information about this
1773 -- entity's existing TCP connections.
1775 tcpConnTable OBJECT-TYPE
1776 SYNTAX SEQUENCE OF TcpConnEntry
1777 ACCESS not-accessible
1780 "A table containing TCP connection-specific
1784 tcpConnEntry OBJECT-TYPE
1786 ACCESS not-accessible
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
1794 INDEX { tcpConnLocalAddress,
1798 ::= { tcpConnTable 1 }
1814 tcpConnState OBJECT-TYPE
1832 "The state of this TCP connection.
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.
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
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 }
1853 tcpConnLocalAddress OBJECT-TYPE
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
1863 ::= { tcpConnEntry 2 }
1865 tcpConnLocalPort OBJECT-TYPE
1866 SYNTAX INTEGER (0..65535)
1870 "The local port number for this TCP connection."
1871 ::= { tcpConnEntry 3 }
1873 tcpConnRemAddress OBJECT-TYPE
1878 "The remote IP address for this TCP connection."
1879 ::= { tcpConnEntry 4 }
1881 tcpConnRemPort OBJECT-TYPE
1882 SYNTAX INTEGER (0..65535)
1886 "The remote port number for this TCP connection."
1887 ::= { tcpConnEntry 5 }
1890 -- additional TCP objects
1892 tcpInErrs OBJECT-TYPE
1897 "The total number of segments received in error
1898 (e.g., bad TCP checksums)."
1901 tcpOutRsts OBJECT-TYPE
1906 "The number of TCP segments sent containing the
1913 -- Implementation of the UDP group is mandatory for all
1914 -- systems which implement the UDP.
1916 udpInDatagrams OBJECT-TYPE
1921 "The total number of UDP datagrams delivered to
1925 udpNoPorts OBJECT-TYPE
1930 "The total number of received UDP datagrams for
1931 which there was no application at the destination
1935 udpInErrors OBJECT-TYPE
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."
1945 udpOutDatagrams OBJECT-TYPE
1950 "The total number of UDP datagrams sent from this
1955 -- the UDP Listener table
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.
1961 udpTable OBJECT-TYPE
1962 SYNTAX SEQUENCE OF UdpEntry
1963 ACCESS not-accessible
1966 "A table containing UDP listener information."
1969 udpEntry OBJECT-TYPE
1971 ACCESS not-accessible
1974 "Information about a particular current UDP
1976 INDEX { udpLocalAddress, udpLocalPort }
1987 udpLocalAddress OBJECT-TYPE
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."
1998 udpLocalPort OBJECT-TYPE
1999 SYNTAX INTEGER (0..65535)
2003 "The local port number for this UDP listener."
2009 -- Implementation of the EGP group is mandatory for all
2010 -- systems which implement the EGP.
2012 egpInMsgs OBJECT-TYPE
2017 "The number of EGP messages received without
2021 egpInErrors OBJECT-TYPE
2026 "The number of EGP messages received that proved
2030 egpOutMsgs OBJECT-TYPE
2035 "The total number of locally generated EGP
2039 egpOutErrors OBJECT-TYPE
2044 "The number of locally generated EGP messages not
2045 sent due to resource limitations within an EGP
2050 -- the EGP Neighbor table
2052 -- The EGP neighbor table contains information about this
2053 -- entity's EGP neighbors.
2055 egpNeighTable OBJECT-TYPE
2056 SYNTAX SEQUENCE OF EgpNeighEntry
2057 ACCESS not-accessible
2060 "The EGP neighbor table."
2063 egpNeighEntry OBJECT-TYPE
2064 SYNTAX EgpNeighEntry
2065 ACCESS not-accessible
2068 "Information about this entity's relationship with
2069 a particular EGP neighbor."
2070 INDEX { egpNeighAddr }
2071 ::= { egpNeighTable 1 }
2097 egpNeighIntervalHello
2099 egpNeighIntervalPoll
2103 egpNeighEventTrigger
2107 egpNeighState OBJECT-TYPE
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
2123 ::= { egpNeighEntry 1 }
2125 egpNeighAddr OBJECT-TYPE
2130 "The IP address of this entry's EGP neighbor."
2131 ::= { egpNeighEntry 2 }
2133 egpNeighAs OBJECT-TYPE
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 }
2143 egpNeighInMsgs OBJECT-TYPE
2148 "The number of EGP messages received without error
2149 from this EGP peer."
2150 ::= { egpNeighEntry 4 }
2152 egpNeighInErrs OBJECT-TYPE
2157 "The number of EGP messages received from this EGP
2158 peer that proved to be in error (e.g., bad EGP
2160 ::= { egpNeighEntry 5 }
2162 egpNeighOutMsgs OBJECT-TYPE
2167 "The number of locally generated EGP messages to
2169 ::= { egpNeighEntry 6 }
2171 egpNeighOutErrs OBJECT-TYPE
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 }
2181 egpNeighInErrMsgs OBJECT-TYPE
2186 "The number of EGP-defined error messages received
2187 from this EGP peer."
2188 ::= { egpNeighEntry 8 }
2190 egpNeighOutErrMsgs OBJECT-TYPE
2195 "The number of EGP-defined error messages sent to
2197 ::= { egpNeighEntry 9 }
2199 egpNeighStateUps OBJECT-TYPE
2204 "The number of EGP state transitions to the UP
2205 state with this EGP peer."
2206 ::= { egpNeighEntry 10 }
2208 egpNeighStateDowns OBJECT-TYPE
2213 "The number of EGP state transitions from the UP
2214 state to any other state with this EGP peer."
2215 ::= { egpNeighEntry 11 }
2217 egpNeighIntervalHello OBJECT-TYPE
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 }
2227 egpNeighIntervalPoll OBJECT-TYPE
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 }
2237 egpNeighMode OBJECT-TYPE
2238 SYNTAX INTEGER { active(1), passive(2) }
2242 "The polling mode of this EGP entity, either
2244 ::= { egpNeighEntry 14 }
2246 egpNeighEventTrigger OBJECT-TYPE
2247 SYNTAX INTEGER { start(1), stop(2) }
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'.
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
2268 ::= { egpNeighEntry 15 }
2271 -- additional EGP objects
2278 "The autonomous system number of this EGP entity."
2281 -- the Transmission group
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.
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.
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:
2298 -- type OBJECT IDENTIFIER ::= { transmission number }
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.
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).
2318 snmpInPkts OBJECT-TYPE
2323 "The total number of Messages delivered to the
2324 SNMP entity from the transport service."
2327 snmpOutPkts OBJECT-TYPE
2332 "The total number of SNMP Messages which were
2333 passed from the SNMP protocol entity to the
2337 snmpInBadVersions OBJECT-TYPE
2342 "The total number of SNMP Messages which were
2343 delivered to the SNMP protocol entity and were for
2344 an unsupported SNMP version."
2347 snmpInBadCommunityNames OBJECT-TYPE
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."
2357 snmpInBadCommunityUses OBJECT-TYPE
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."
2368 snmpInASNParseErrs OBJECT-TYPE
2373 "The total number of ASN.1 or BER errors
2374 encountered by the SNMP protocol entity when
2375 decoding received SNMP Messages."
2378 -- { snmp 7 } is not used
2380 snmpInTooBigs OBJECT-TYPE
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
2391 snmpInNoSuchNames OBJECT-TYPE
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
2402 snmpInBadValues OBJECT-TYPE
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
2413 snmpInReadOnlys OBJECT-TYPE
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
2429 snmpInGenErrs OBJECT-TYPE
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
2440 snmpInTotalReqVars OBJECT-TYPE
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
2451 snmpInTotalSetVars OBJECT-TYPE
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
2462 snmpInGetRequests OBJECT-TYPE
2467 "The total number of SNMP Get-Request PDUs which
2468 have been accepted and processed by the SNMP
2472 snmpInGetNexts OBJECT-TYPE
2477 "The total number of SNMP Get-Next PDUs which have
2478 been accepted and processed by the SNMP protocol
2482 snmpInSetRequests OBJECT-TYPE
2487 "The total number of SNMP Set-Request PDUs which
2488 have been accepted and processed by the SNMP
2492 snmpInGetResponses OBJECT-TYPE
2497 "The total number of SNMP Get-Response PDUs which
2498 have been accepted and processed by the SNMP
2502 snmpInTraps OBJECT-TYPE
2507 "The total number of SNMP Trap PDUs which have
2508 been accepted and processed by the SNMP protocol
2512 snmpOutTooBigs OBJECT-TYPE
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
2523 snmpOutNoSuchNames OBJECT-TYPE
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
2534 snmpOutBadValues OBJECT-TYPE
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
2545 -- { snmp 23 } is not used
2547 snmpOutGenErrs OBJECT-TYPE
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
2558 snmpOutGetRequests OBJECT-TYPE
2563 "The total number of SNMP Get-Request PDUs which
2564 have been generated by the SNMP protocol entity."
2567 snmpOutGetNexts OBJECT-TYPE
2572 "The total number of SNMP Get-Next PDUs which have
2573 been generated by the SNMP protocol entity."
2576 snmpOutSetRequests OBJECT-TYPE
2581 "The total number of SNMP Set-Request PDUs which
2582 have been generated by the SNMP protocol entity."
2585 snmpOutGetResponses OBJECT-TYPE
2590 "The total number of SNMP Get-Response PDUs which
2591 have been generated by the SNMP protocol entity."
2594 snmpOutTraps OBJECT-TYPE
2599 "The total number of SNMP Trap PDUs which have
2600 been generated by the SNMP protocol entity."
2603 snmpEnableAuthenTraps OBJECT-TYPE
2604 SYNTAX INTEGER { enabled(1), disabled(2) }
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
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."