1 -- *****************************************************************
2 -- RFC1213-MIB.my: MIB-II MIB file
4 -- April 1994, Jeffrey T. Johnson
6 -- Copyright (c) 1994-1996 by cisco Systems, Inc.
7 -- All rights reserved.
9 -- *****************************************************************
11 -- This mib was extracted from RFC 1213
12 -- The following changes have been applied:
13 -- The enumerations unknown(4) and dormant(5) have been added to
14 -- ifOperStatus to reflect a change to the ifTable introduced in
17 -- The SYNTAX of ifType has been changed to IANAifType, to reflect the
18 -- change to the ifTable introduced in RFC1573.
20 RFC1213-MIB DEFINITIONS ::= BEGIN
23 mgmt, NetworkAddress, IpAddress, Counter, Gauge,
33 -- This MIB module uses the extended OBJECT-TYPE macro as
37 -- MIB-II (same prefix as MIB-I)
39 mib-2 OBJECT IDENTIFIER ::= { mgmt 1 }
41 -- textual conventions
45 -- This data type is used to model textual information taken
46 -- from the NVT ASCII character set. By convention, objects
47 -- with this syntax are declared as having
53 -- This data type is used to model media addresses. For many
54 -- types of media, this will be in a binary representation.
55 -- For example, an ethernet address would be represented as
56 -- a string of 6 octets.
61 system OBJECT IDENTIFIER ::= { mib-2 1 }
63 interfaces OBJECT IDENTIFIER ::= { mib-2 2 }
65 at OBJECT IDENTIFIER ::= { mib-2 3 }
67 ip OBJECT IDENTIFIER ::= { mib-2 4 }
69 icmp OBJECT IDENTIFIER ::= { mib-2 5 }
71 tcp OBJECT IDENTIFIER ::= { mib-2 6 }
73 udp OBJECT IDENTIFIER ::= { mib-2 7 }
75 egp OBJECT IDENTIFIER ::= { mib-2 8 }
77 -- historical (some say hysterical)
78 -- cmot OBJECT IDENTIFIER ::= { mib-2 9 }
80 transmission OBJECT IDENTIFIER ::= { mib-2 10 }
82 snmp OBJECT IDENTIFIER ::= { mib-2 11 }
87 -- Implementation of the System group is mandatory for all
88 -- systems. If an agent is not configured to have a value
89 -- for any of these variables, a string of length 0 is
93 SYNTAX DisplayString (SIZE (0..255))
97 "A textual description of the entity. This value
98 should include the full name and version
99 identification of the system's hardware type,
100 software operating-system, and networking
101 software. It is mandatory that this only contain
102 printable ASCII characters."
105 sysObjectID OBJECT-TYPE
106 SYNTAX OBJECT IDENTIFIER
110 "The vendor's authoritative identification of the
111 network management subsystem contained in the
112 entity. This value is allocated within the SMI
113 enterprises subtree (1.3.6.1.4.1) and provides an
114 easy and unambiguous means for determining `what
115 kind of box' is being managed. For example, if
116 vendor `Flintstones, Inc.' was assigned the
117 subtree 1.3.6.1.4.1.4242, it could assign the
118 identifier 1.3.6.1.4.1.4242.1.1 to its `Fred
122 sysUpTime OBJECT-TYPE
127 "The time (in hundredths of a second) since the
128 network management portion of the system was last
132 sysContact OBJECT-TYPE
133 SYNTAX DisplayString (SIZE (0..255))
137 "The textual identification of the contact person
138 for this managed node, together with information
139 on how to contact this person."
143 SYNTAX DisplayString (SIZE (0..255))
147 "An administratively-assigned name for this
148 managed node. By convention, this is the node's
149 fully-qualified domain name."
152 sysLocation OBJECT-TYPE
153 SYNTAX DisplayString (SIZE (0..255))
157 "The physical location of this node (e.g.,
158 `telephone closet, 3rd floor')."
161 sysServices OBJECT-TYPE
162 SYNTAX INTEGER (0..127)
166 "A value which indicates the set of services that
167 this entity primarily offers.
169 The value is a sum. This sum initially takes the
170 value zero, Then, for each layer, L, in the range
171 1 through 7, that this node performs transactions
172 for, 2 raised to (L - 1) is added to the sum. For
173 example, a node which performs primarily routing
174 functions would have a value of 4 (2^(3-1)). In
175 contrast, a node which is a host offering
176 application services would have a value of 72
177 (2^(4-1) + 2^(7-1)). Note that in the context of
178 the Internet suite of protocols, values should be
179 calculated accordingly:
182 1 physical (e.g., repeaters)
183 2 datalink/subnetwork (e.g., bridges)
184 3 internet (e.g., IP gateways)
185 4 end-to-end (e.g., IP hosts)
186 7 applications (e.g., mail relays)
188 For systems including OSI protocols, layers 5 and
189 6 may also be counted."
192 -- the Interfaces group
194 -- Implementation of the Interfaces group is mandatory for
202 "The number of network interfaces (regardless of
203 their current state) present on this system."
207 -- the Interfaces table
209 -- The Interfaces table contains information on the entity's
210 -- interfaces. Each interface is thought of as being
211 -- attached to a `subnetwork'. Note that this term should
212 -- not be confused with `subnet' which refers to an
213 -- addressing partitioning scheme used in the Internet suite
217 SYNTAX SEQUENCE OF IfEntry
218 ACCESS not-accessible
221 "A list of interface entries. The number of
222 entries is given by the value of ifNumber."
227 ACCESS not-accessible
230 "An interface entry containing objects at the
231 subnetwork layer and below for a particular
289 "A unique value for each interface. Its value
290 ranges between 1 and the value of ifNumber. The
291 value for each interface must remain constant at
292 least from one re-initialization of the entity's
293 network management system to the next re-
298 SYNTAX DisplayString (SIZE (0..255))
302 "A textual string containing information about the
303 interface. This string should include the name of
304 the manufacturer, the product name and the version
305 of the hardware interface."
313 "The type of interface. Additional values for ifType
314 are assigned by the Internet Assigned Numbers
315 Authority (IANA), through updating the syntax of the
316 IANAifType textual convention."
325 "The size of the largest datagram which can be
326 sent/received on the interface, specified in
327 octets. For interfaces that are used for
328 transmitting network datagrams, this is the size
329 of the largest network datagram that can be sent
338 "An estimate of the interface's current bandwidth
339 in bits per second. For interfaces which do not
340 vary in bandwidth or for those where no accurate
341 estimation can be made, this object should contain
342 the nominal bandwidth."
345 ifPhysAddress OBJECT-TYPE
350 "The interface's address at the protocol layer
351 immediately `below' the network layer in the
352 protocol stack. For interfaces which do not have
353 such an address (e.g., a serial line), this object
354 should contain an octet string of zero length."
357 ifAdminStatus OBJECT-TYPE
359 up(1), -- ready to pass packets
361 testing(3) -- in some test mode
366 "The desired state of the interface. The
367 testing(3) state indicates that no operational
368 packets can be passed."
371 ifOperStatus OBJECT-TYPE
373 up(1), -- ready to pass packets
375 testing(3), -- in some test mode
382 "The current operational state of the interface.
383 The testing(3) state indicates that no operational
384 packets can be passed."
387 ifLastChange OBJECT-TYPE
392 "The value of sysUpTime at the time the interface
393 entered its current operational state. If the
394 current state was entered prior to the last re-
395 initialization of the local network management
396 subsystem, then this object contains a zero
400 ifInOctets OBJECT-TYPE
405 "The total number of octets received on the
406 interface, including framing characters."
409 ifInUcastPkts OBJECT-TYPE
414 "The number of subnetwork-unicast packets
415 delivered to a higher-layer protocol."
418 ifInNUcastPkts OBJECT-TYPE
423 "The number of non-unicast (i.e., subnetwork-
424 broadcast or subnetwork-multicast) packets
425 delivered to a higher-layer protocol."
428 ifInDiscards OBJECT-TYPE
433 "The number of inbound packets which were chosen
434 to be discarded even though no errors had been
435 detected to prevent their being deliverable to a
436 higher-layer protocol. One possible reason for
437 discarding such a packet could be to free up
441 ifInErrors OBJECT-TYPE
446 "The number of inbound packets that contained
447 errors preventing them from being deliverable to a
448 higher-layer protocol."
451 ifInUnknownProtos OBJECT-TYPE
456 "The number of packets received via the interface
457 which were discarded because of an unknown or
458 unsupported protocol."
461 ifOutOctets OBJECT-TYPE
466 "The total number of octets transmitted out of the
467 interface, including framing characters."
470 ifOutUcastPkts OBJECT-TYPE
475 "The total number of packets that higher-level
476 protocols requested be transmitted to a
477 subnetwork-unicast address, including those that
478 were discarded or not sent."
481 ifOutNUcastPkts OBJECT-TYPE
486 "The total number of packets that higher-level
487 protocols requested be transmitted to a non-
488 unicast (i.e., a subnetwork-broadcast or
489 subnetwork-multicast) address, including those
490 that were discarded or not sent."
493 ifOutDiscards OBJECT-TYPE
498 "The number of outbound packets which were chosen
499 to be discarded even though no errors had been
500 detected to prevent their being transmitted. One
501 possible reason for discarding such a packet could
502 be to free up buffer space."
505 ifOutErrors OBJECT-TYPE
510 "The number of outbound packets that could not be
511 transmitted because of errors."
514 ifOutQLen OBJECT-TYPE
519 "The length of the output packet queue (in
523 ifSpecific OBJECT-TYPE
524 SYNTAX OBJECT IDENTIFIER
528 "A reference to MIB definitions specific to the
529 particular media being used to realize the
530 interface. For example, if the interface is
531 realized by an ethernet, then the value of this
532 object refers to a document defining objects
533 specific to ethernet. If this information is not
534 present, its value should be set to the OBJECT
535 IDENTIFIER { 0 0 }, which is a syntactically valid
536 object identifier, and any conformant
537 implementation of ASN.1 and BER must be able to
538 generate and recognize this value."
542 -- the Address Translation group
544 -- Implementation of the Address Translation group is
545 -- mandatory for all systems. Note however that this group
546 -- is deprecated by MIB-II. That is, it is being included
547 -- solely for compatibility with MIB-I nodes, and will most
548 -- likely be excluded from MIB-III nodes. From MIB-II and
549 -- onwards, each network protocol group contains its own
550 -- address translation tables.
552 -- The Address Translation group contains one table which is
553 -- the union across all interfaces of the translation tables
554 -- for converting a NetworkAddress (e.g., an IP address) into
555 -- a subnetwork-specific address. For lack of a better term,
556 -- this document refers to such a subnetwork-specific address
557 -- as a `physical' address.
559 -- Examples of such translation tables are: for broadcast
560 -- media where ARP is in use, the translation table is
561 -- equivalent to the ARP cache; or, on an X.25 network where
562 -- non-algorithmic translation to X.121 addresses is
563 -- required, the translation table contains the
564 -- NetworkAddress to X.121 address equivalences.
567 SYNTAX SEQUENCE OF AtEntry
568 ACCESS not-accessible
571 "The Address Translation tables contain the
572 NetworkAddress to `physical' address equivalences.
573 Some interfaces do not use translation tables for
574 determining address equivalences (e.g., DDN-X.25
575 has an algorithmic method); if all interfaces are
576 of this type, then the Address Translation table
577 is empty, i.e., has zero entries."
582 ACCESS not-accessible
585 "Each entry contains one NetworkAddress to
586 `physical' address equivalence."
601 atIfIndex OBJECT-TYPE
606 "The interface on which this entry's equivalence
607 is effective. The interface identified by a
608 particular value of this index is the same
609 interface as identified by the same value of
613 atPhysAddress OBJECT-TYPE
618 "The media-dependent `physical' address.
620 Setting this object to a null string (one of zero
621 length) has the effect of invaliding the
622 corresponding entry in the atTable object. That
623 is, it effectively disassociates the interface
624 identified with said entry from the mapping
625 identified with said entry. It is an
626 implementation-specific matter as to whether the
627 agent removes an invalidated entry from the table.
628 Accordingly, management stations must be prepared
629 to receive tabular information from agents that
630 corresponds to entries not currently in use.
631 Proper interpretation of such entries requires
632 examination of the relevant atPhysAddress object."
635 atNetAddress OBJECT-TYPE
636 SYNTAX NetworkAddress
640 "The NetworkAddress (e.g., the IP address)
641 corresponding to the media-dependent `physical'
648 -- Implementation of the IP group is mandatory for all
651 ipForwarding OBJECT-TYPE
653 forwarding(1), -- acting as a gateway
654 not-forwarding(2) -- NOT acting as a gateway
659 "The indication of whether this entity is acting
660 as an IP gateway in respect to the forwarding of
661 datagrams received by, but not addressed to, this
662 entity. IP gateways forward datagrams. IP hosts
663 do not (except those source-routed via the host).
665 Note that for some managed nodes, this object may
666 take on only a subset of the values possible.
667 Accordingly, it is appropriate for an agent to
668 return a `badValue' response if a management
669 station attempts to change this object to an
670 inappropriate value."
673 ipDefaultTTL OBJECT-TYPE
678 "The default value inserted into the Time-To-Live
679 field of the IP header of datagrams originated at
680 this entity, whenever a TTL value is not supplied
681 by the transport layer protocol."
684 ipInReceives OBJECT-TYPE
689 "The total number of input datagrams received from
690 interfaces, including those received in error."
693 ipInHdrErrors OBJECT-TYPE
698 "The number of input datagrams discarded due to
699 errors in their IP headers, including bad
700 checksums, version number mismatch, other format
701 errors, time-to-live exceeded, errors discovered
702 in processing their IP options, etc."
705 ipInAddrErrors OBJECT-TYPE
710 "The number of input datagrams discarded because
711 the IP address in their IP header's destination
712 field was not a valid address to be received at
713 this entity. This count includes invalid
714 addresses (e.g., 0.0.0.0) and addresses of
715 unsupported Classes (e.g., Class E). For entities
716 which are not IP Gateways and therefore do not
717 forward datagrams, this counter includes datagrams
718 discarded because the destination address was not
722 ipForwDatagrams OBJECT-TYPE
727 "The number of input datagrams for which this
728 entity was not their final IP destination, as a
729 result of which an attempt was made to find a
730 route to forward them to that final destination.
731 In entities which do not act as IP Gateways, this
732 counter will include only those packets which were
733 Source-Routed via this entity, and the Source-
734 Route option processing was successful."
737 ipInUnknownProtos OBJECT-TYPE
742 "The number of locally-addressed datagrams
743 received successfully but discarded because of an
744 unknown or unsupported protocol."
747 ipInDiscards OBJECT-TYPE
752 "The number of input IP datagrams for which no
753 problems were encountered to prevent their
754 continued processing, but which were discarded
755 (e.g., for lack of buffer space). Note that this
756 counter does not include any datagrams discarded
757 while awaiting re-assembly."
760 ipInDelivers OBJECT-TYPE
765 "The total number of input datagrams successfully
766 delivered to IP user-protocols (including ICMP)."
769 ipOutRequests OBJECT-TYPE
774 "The total number of IP datagrams which local IP
775 user-protocols (including ICMP) supplied to IP in
776 requests for transmission. Note that this counter
777 does not include any datagrams counted in
781 ipOutDiscards OBJECT-TYPE
786 "The number of output IP datagrams for which no
787 problem was encountered to prevent their
788 transmission to their destination, but which were
789 discarded (e.g., for lack of buffer space). Note
790 that this counter would include datagrams counted
791 in ipForwDatagrams if any such packets met this
792 (discretionary) discard criterion."
795 ipOutNoRoutes OBJECT-TYPE
800 "The number of IP datagrams discarded because no
801 route could be found to transmit them to their
802 destination. Note that this counter includes any
803 packets counted in ipForwDatagrams which meet this
804 `no-route' criterion. Note that this includes any
805 datagrams which a host cannot route because all of
806 its default gateways are down."
809 ipReasmTimeout OBJECT-TYPE
814 "The maximum number of seconds which received
815 fragments are held while they are awaiting
816 reassembly at this entity."
819 ipReasmReqds OBJECT-TYPE
824 "The number of IP fragments received which needed
825 to be reassembled at this entity."
828 ipReasmOKs OBJECT-TYPE
833 "The number of IP datagrams successfully re-
837 ipReasmFails OBJECT-TYPE
842 "The number of failures detected by the IP re-
843 assembly algorithm (for whatever reason: timed
844 out, errors, etc). Note that this is not
845 necessarily a count of discarded IP fragments
846 since some algorithms (notably the algorithm in
847 RFC 815) can lose track of the number of fragments
848 by combining them as they are received."
851 ipFragOKs OBJECT-TYPE
856 "The number of IP datagrams that have been
857 successfully fragmented at this entity."
860 ipFragFails OBJECT-TYPE
865 "The number of IP datagrams that have been
866 discarded because they needed to be fragmented at
867 this entity but could not be, e.g., because their
868 Don't Fragment flag was set."
871 ipFragCreates OBJECT-TYPE
876 "The number of IP datagram fragments that have
877 been generated as a result of fragmentation at
883 -- the IP address table
885 -- The IP address table contains this entity's IP addressing
888 ipAddrTable OBJECT-TYPE
889 SYNTAX SEQUENCE OF IpAddrEntry
890 ACCESS not-accessible
893 "The table of addressing information relevant to
894 this entity's IP addresses."
897 ipAddrEntry OBJECT-TYPE
899 ACCESS not-accessible
902 "The addressing information for one of this
903 entity's IP addresses."
904 INDEX { ipAdEntAddr }
905 ::= { ipAddrTable 1 }
921 ipAdEntAddr OBJECT-TYPE
926 "The IP address to which this entry's addressing
927 information pertains."
928 ::= { ipAddrEntry 1 }
931 ipAdEntIfIndex OBJECT-TYPE
936 "The index value which uniquely identifies the
937 interface to which this entry is applicable. The
938 interface identified by a particular value of this
939 index is the same interface as identified by the
940 same value of ifIndex."
941 ::= { ipAddrEntry 2 }
943 ipAdEntNetMask OBJECT-TYPE
948 "The subnet mask associated with the IP address of
949 this entry. The value of the mask is an IP
950 address with all the network bits set to 1 and all
951 the hosts bits set to 0."
952 ::= { ipAddrEntry 3 }
954 ipAdEntBcastAddr OBJECT-TYPE
959 "The value of the least-significant bit in the IP
960 broadcast address used for sending datagrams on
961 the (logical) interface associated with the IP
962 address of this entry. For example, when the
963 Internet standard all-ones broadcast address is
964 used, the value will be 1. This value applies to
965 both the subnet and network broadcasts addresses
966 used by the entity on this (logical) interface."
967 ::= { ipAddrEntry 4 }
969 ipAdEntReasmMaxSize OBJECT-TYPE
970 SYNTAX INTEGER (0..65535)
974 "The size of the largest IP datagram which this
975 entity can re-assemble from incoming IP fragmented
976 datagrams received on this interface."
977 ::= { ipAddrEntry 5 }
979 -- the IP routing table
981 -- The IP routing table contains an entry for each route
982 -- presently known to this entity.
984 ipRouteTable OBJECT-TYPE
985 SYNTAX SEQUENCE OF IpRouteEntry
986 ACCESS not-accessible
989 "This entity's IP Routing table."
992 ipRouteEntry OBJECT-TYPE
994 ACCESS not-accessible
997 "A route to a particular destination."
998 INDEX { ipRouteDest }
999 ::= { ipRouteTable 1 }
1031 ipRouteDest OBJECT-TYPE
1036 "The destination IP address of this route. An
1037 entry with a value of 0.0.0.0 is considered a
1038 default route. Multiple routes to a single
1039 destination can appear in the table, but access to
1040 such multiple entries is dependent on the table-
1041 access mechanisms defined by the network
1042 management protocol in use."
1043 ::= { ipRouteEntry 1 }
1045 ipRouteIfIndex OBJECT-TYPE
1050 "The index value which uniquely identifies the
1051 local interface through which the next hop of this
1052 route should be reached. The interface identified
1053 by a particular value of this index is the same
1054 interface as identified by the same value of
1056 ::= { ipRouteEntry 2 }
1058 ipRouteMetric1 OBJECT-TYPE
1063 "The primary routing metric for this route. The
1064 semantics of this metric are determined by the
1065 routing-protocol specified in the route's
1066 ipRouteProto value. If this metric is not used,
1067 its value should be set to -1."
1068 ::= { ipRouteEntry 3 }
1070 ipRouteMetric2 OBJECT-TYPE
1075 "An alternate routing metric for this route. The
1076 semantics of this metric are determined by the
1077 routing-protocol specified in the route's
1078 ipRouteProto value. If this metric is not used,
1079 its value should be set to -1."
1080 ::= { ipRouteEntry 4 }
1082 ipRouteMetric3 OBJECT-TYPE
1087 "An alternate routing metric for this route. The
1088 semantics of this metric are determined by the
1089 routing-protocol specified in the route's
1090 ipRouteProto value. If this metric is not used,
1091 its value should be set to -1."
1092 ::= { ipRouteEntry 5 }
1094 ipRouteMetric4 OBJECT-TYPE
1099 "An alternate routing metric for this route. The
1100 semantics of this metric are determined by the
1101 routing-protocol specified in the route's
1102 ipRouteProto value. If this metric is not used,
1103 its value should be set to -1."
1104 ::= { ipRouteEntry 6 }
1106 ipRouteNextHop OBJECT-TYPE
1111 "The IP address of the next hop of this route.
1112 (In the case of a route bound to an interface
1113 which is realized via a broadcast media, the value
1114 of this field is the agent's IP address on that
1116 ::= { ipRouteEntry 7 }
1118 ipRouteType OBJECT-TYPE
1120 other(1), -- none of the following
1122 invalid(2), -- an invalidated route
1123 -- route to directly
1124 direct(3), -- connected (sub-)network
1126 -- route to a non-local
1127 indirect(4) -- host/network/sub-network
1132 "The type of route. Note that the values
1133 direct(3) and indirect(4) refer to the notion of
1134 direct and indirect routing in the IP
1137 Setting this object to the value invalid(2) has
1138 the effect of invalidating the corresponding entry
1139 in the ipRouteTable object. That is, it
1140 effectively disassociates the destination
1141 identified with said entry from the route
1142 identified with said entry. It is an
1143 implementation-specific matter as to whether the
1144 agent removes an invalidated entry from the table.
1145 Accordingly, management stations must be prepared
1146 to receive tabular information from agents that
1147 corresponds to entries not currently in use.
1148 Proper interpretation of such entries requires
1149 examination of the relevant ipRouteType object."
1150 ::= { ipRouteEntry 8 }
1152 ipRouteProto OBJECT-TYPE
1154 other(1), -- none of the following
1156 -- non-protocol information,
1157 -- e.g., manually configured
1158 local(2), -- entries
1160 -- set via a network
1161 netmgmt(3), -- management protocol
1163 -- obtained via ICMP,
1164 icmp(4), -- e.g., Redirect
1166 -- the remaining values are
1167 -- all gateway routing
1183 "The routing mechanism via which this route was
1184 learned. Inclusion of values for gateway routing
1185 protocols is not intended to imply that hosts
1186 should support those protocols."
1187 ::= { ipRouteEntry 9 }
1189 ipRouteAge OBJECT-TYPE
1194 "The number of seconds since this route was last
1195 updated or otherwise determined to be correct.
1196 Note that no semantics of `too old' can be implied
1197 except through knowledge of the routing protocol
1198 by which the route was learned."
1199 ::= { ipRouteEntry 10 }
1201 ipRouteMask OBJECT-TYPE
1206 "Indicate the mask to be logical-ANDed with the
1207 destination address before being compared to the
1208 value in the ipRouteDest field. For those systems
1209 that do not support arbitrary subnet masks, an
1210 agent constructs the value of the ipRouteMask by
1211 determining whether the value of the correspondent
1212 ipRouteDest field belong to a class-A, B, or C
1213 network, and then using one of:
1218 255.255.255.0 class-C
1220 If the value of the ipRouteDest is 0.0.0.0 (a
1221 default route), then the mask value is also
1222 0.0.0.0. It should be noted that all IP routing
1223 subsystems implicitly use this mechanism."
1224 ::= { ipRouteEntry 11 }
1226 ipRouteMetric5 OBJECT-TYPE
1231 "An alternate routing metric for this route. The
1232 semantics of this metric are determined by the
1233 routing-protocol specified in the route's
1234 ipRouteProto value. If this metric is not used,
1235 its value should be set to -1."
1236 ::= { ipRouteEntry 12 }
1238 ipRouteInfo OBJECT-TYPE
1239 SYNTAX OBJECT IDENTIFIER
1243 "A reference to MIB definitions specific to the
1244 particular routing protocol which is responsible
1245 for this route, as determined by the value
1246 specified in the route's ipRouteProto value. If
1247 this information is not present, its value should
1248 be set to the OBJECT IDENTIFIER { 0 0 }, which is
1249 a syntactically valid object identifier, and any
1250 conformant implementation of ASN.1 and BER must be
1251 able to generate and recognize this value."
1252 ::= { ipRouteEntry 13 }
1255 -- the IP Address Translation table
1257 -- The IP address translation table contain the IpAddress to
1258 -- `physical' address equivalences. Some interfaces do not
1259 -- use translation tables for determining address
1260 -- equivalences (e.g., DDN-X.25 has an algorithmic method);
1261 -- if all interfaces are of this type, then the Address
1262 -- Translation table is empty, i.e., has zero entries.
1264 ipNetToMediaTable OBJECT-TYPE
1265 SYNTAX SEQUENCE OF IpNetToMediaEntry
1266 ACCESS not-accessible
1269 "The IP Address Translation table used for mapping
1270 from IP addresses to physical addresses."
1273 ipNetToMediaEntry OBJECT-TYPE
1274 SYNTAX IpNetToMediaEntry
1275 ACCESS not-accessible
1278 "Each entry contains one IpAddress to `physical'
1279 address equivalence."
1280 INDEX { ipNetToMediaIfIndex,
1281 ipNetToMediaNetAddress }
1282 ::= { ipNetToMediaTable 1 }
1284 IpNetToMediaEntry ::=
1288 ipNetToMediaPhysAddress
1290 ipNetToMediaNetAddress
1296 ipNetToMediaIfIndex OBJECT-TYPE
1301 "The interface on which this entry's equivalence
1302 is effective. The interface identified by a
1303 particular value of this index is the same
1304 interface as identified by the same value of
1306 ::= { ipNetToMediaEntry 1 }
1308 ipNetToMediaPhysAddress OBJECT-TYPE
1313 "The media-dependent `physical' address."
1314 ::= { ipNetToMediaEntry 2 }
1316 ipNetToMediaNetAddress OBJECT-TYPE
1321 "The IpAddress corresponding to the media-
1322 dependent `physical' address."
1323 ::= { ipNetToMediaEntry 3 }
1325 ipNetToMediaType OBJECT-TYPE
1327 other(1), -- none of the following
1328 invalid(2), -- an invalidated mapping
1335 "The type of mapping.
1337 Setting this object to the value invalid(2) has
1338 the effect of invalidating the corresponding entry
1339 in the ipNetToMediaTable. That is, it effectively
1340 disassociates the interface identified with said
1341 entry from the mapping identified with said entry.
1342 It is an implementation-specific matter as to
1343 whether the agent removes an invalidated entry
1344 from the table. Accordingly, management stations
1345 must be prepared to receive tabular information
1346 from agents that corresponds to entries not
1347 currently in use. Proper interpretation of such
1348 entries requires examination of the relevant
1349 ipNetToMediaType object."
1350 ::= { ipNetToMediaEntry 4 }
1353 -- additional IP objects
1355 ipRoutingDiscards OBJECT-TYPE
1360 "The number of routing entries which were chosen
1361 to be discarded even though they are valid. One
1362 possible reason for discarding such an entry could
1363 be to free-up buffer space for other routing
1370 -- Implementation of the ICMP group is mandatory for all
1373 icmpInMsgs OBJECT-TYPE
1378 "The total number of ICMP messages which the
1379 entity received. Note that this counter includes
1380 all those counted by icmpInErrors."
1383 icmpInErrors OBJECT-TYPE
1388 "The number of ICMP messages which the entity
1389 received but determined as having ICMP-specific
1390 errors (bad ICMP checksums, bad length, etc.)."
1393 icmpInDestUnreachs OBJECT-TYPE
1398 "The number of ICMP Destination Unreachable
1402 icmpInTimeExcds OBJECT-TYPE
1407 "The number of ICMP Time Exceeded messages
1412 icmpInParmProbs OBJECT-TYPE
1417 "The number of ICMP Parameter Problem messages
1421 icmpInSrcQuenchs OBJECT-TYPE
1426 "The number of ICMP Source Quench messages
1430 icmpInRedirects OBJECT-TYPE
1435 "The number of ICMP Redirect messages received."
1438 icmpInEchos OBJECT-TYPE
1443 "The number of ICMP Echo (request) messages
1447 icmpInEchoReps OBJECT-TYPE
1452 "The number of ICMP Echo Reply messages received."
1455 icmpInTimestamps OBJECT-TYPE
1460 "The number of ICMP Timestamp (request) messages
1464 icmpInTimestampReps OBJECT-TYPE
1469 "The number of ICMP Timestamp Reply messages
1473 icmpInAddrMasks OBJECT-TYPE
1478 "The number of ICMP Address Mask Request messages
1482 icmpInAddrMaskReps OBJECT-TYPE
1487 "The number of ICMP Address Mask Reply messages
1491 icmpOutMsgs OBJECT-TYPE
1496 "The total number of ICMP messages which this
1497 entity attempted to send. Note that this counter
1498 includes all those counted by icmpOutErrors."
1501 icmpOutErrors OBJECT-TYPE
1506 "The number of ICMP messages which this entity did
1507 not send due to problems discovered within ICMP
1508 such as a lack of buffers. This value should not
1509 include errors discovered outside the ICMP layer
1510 such as the inability of IP to route the resultant
1511 datagram. In some implementations there may be no
1512 types of error which contribute to this counter's
1516 icmpOutDestUnreachs OBJECT-TYPE
1521 "The number of ICMP Destination Unreachable
1525 icmpOutTimeExcds OBJECT-TYPE
1530 "The number of ICMP Time Exceeded messages sent."
1533 icmpOutParmProbs OBJECT-TYPE
1538 "The number of ICMP Parameter Problem messages
1542 icmpOutSrcQuenchs OBJECT-TYPE
1547 "The number of ICMP Source Quench messages sent."
1550 icmpOutRedirects OBJECT-TYPE
1555 "The number of ICMP Redirect messages sent. For a
1556 host, this object will always be zero, since hosts
1557 do not send redirects."
1560 icmpOutEchos OBJECT-TYPE
1565 "The number of ICMP Echo (request) messages sent."
1568 icmpOutEchoReps OBJECT-TYPE
1573 "The number of ICMP Echo Reply messages sent."
1576 icmpOutTimestamps OBJECT-TYPE
1581 "The number of ICMP Timestamp (request) messages
1585 icmpOutTimestampReps OBJECT-TYPE
1590 "The number of ICMP Timestamp Reply messages
1594 icmpOutAddrMasks OBJECT-TYPE
1599 "The number of ICMP Address Mask Request messages
1604 icmpOutAddrMaskReps OBJECT-TYPE
1609 "The number of ICMP Address Mask Reply messages
1616 -- Implementation of the TCP group is mandatory for all
1617 -- systems that implement the TCP.
1619 -- Note that instances of object types that represent
1620 -- information about a particular TCP connection are
1621 -- transient; they persist only as long as the connection
1624 tcpRtoAlgorithm OBJECT-TYPE
1626 other(1), -- none of the following
1628 constant(2), -- a constant rto
1629 rsre(3), -- MIL-STD-1778, Appendix B
1630 vanj(4) -- Van Jacobson's algorithm [10]
1635 "The algorithm used to determine the timeout value
1636 used for retransmitting unacknowledged octets."
1639 tcpRtoMin OBJECT-TYPE
1644 "The minimum value permitted by a TCP
1645 implementation for the retransmission timeout,
1646 measured in milliseconds. More refined semantics
1647 for objects of this type depend upon the algorithm
1648 used to determine the retransmission timeout. In
1649 particular, when the timeout algorithm is rsre(3),
1650 an object of this type has the semantics of the
1651 LBOUND quantity described in RFC 793."
1655 tcpRtoMax OBJECT-TYPE
1660 "The maximum value permitted by a TCP
1661 implementation for the retransmission timeout,
1662 measured in milliseconds. More refined semantics
1663 for objects of this type depend upon the algorithm
1664 used to determine the retransmission timeout. In
1665 particular, when the timeout algorithm is rsre(3),
1666 an object of this type has the semantics of the
1667 UBOUND quantity described in RFC 793."
1670 tcpMaxConn OBJECT-TYPE
1675 "The limit on the total number of TCP connections
1676 the entity can support. In entities where the
1677 maximum number of connections is dynamic, this
1678 object should contain the value -1."
1681 tcpActiveOpens OBJECT-TYPE
1686 "The number of times TCP connections have made a
1687 direct transition to the SYN-SENT state from the
1691 tcpPassiveOpens OBJECT-TYPE
1696 "The number of times TCP connections have made a
1697 direct transition to the SYN-RCVD state from the
1701 tcpAttemptFails OBJECT-TYPE
1706 "The number of times TCP connections have made a
1707 direct transition to the CLOSED state from either
1708 the SYN-SENT state or the SYN-RCVD state, plus the
1709 number of times TCP connections have made a direct
1710 transition to the LISTEN state from the SYN-RCVD
1714 tcpEstabResets OBJECT-TYPE
1719 "The number of times TCP connections have made a
1720 direct transition to the CLOSED state from either
1721 the ESTABLISHED state or the CLOSE-WAIT state."
1724 tcpCurrEstab OBJECT-TYPE
1729 "The number of TCP connections for which the
1730 current state is either ESTABLISHED or CLOSE-
1734 tcpInSegs OBJECT-TYPE
1739 "The total number of segments received, including
1740 those received in error. This count includes
1741 segments received on currently established
1745 tcpOutSegs OBJECT-TYPE
1750 "The total number of segments sent, including
1751 those on current connections but excluding those
1752 containing only retransmitted octets."
1755 tcpRetransSegs OBJECT-TYPE
1760 "The total number of segments retransmitted - that
1761 is, the number of TCP segments transmitted
1762 containing one or more previously transmitted
1767 -- the TCP Connection table
1769 -- The TCP connection table contains information about this
1770 -- entity's existing TCP connections.
1772 tcpConnTable OBJECT-TYPE
1773 SYNTAX SEQUENCE OF TcpConnEntry
1774 ACCESS not-accessible
1777 "A table containing TCP connection-specific
1781 tcpConnEntry OBJECT-TYPE
1783 ACCESS not-accessible
1786 "Information about a particular current TCP
1787 connection. An object of this type is transient,
1788 in that it ceases to exist when (or soon after)
1789 the connection makes the transition to the CLOSED
1791 INDEX { tcpConnLocalAddress,
1795 ::= { tcpConnTable 1 }
1811 tcpConnState OBJECT-TYPE
1829 "The state of this TCP connection.
1831 The only value which may be set by a management
1832 station is deleteTCB(12). Accordingly, it is
1833 appropriate for an agent to return a `badValue'
1834 response if a management station attempts to set
1835 this object to any other value.
1837 If a management station sets this object to the
1838 value deleteTCB(12), then this has the effect of
1839 deleting the TCB (as defined in RFC 793) of the
1840 corresponding connection on the managed node,
1841 resulting in immediate termination of the
1844 As an implementation-specific option, a RST
1845 segment may be sent from the managed node to the
1846 other TCP endpoint (note however that RST segments
1847 are not sent reliably)."
1848 ::= { tcpConnEntry 1 }
1850 tcpConnLocalAddress OBJECT-TYPE
1855 "The local IP address for this TCP connection. In
1856 the case of a connection in the listen state which
1857 is willing to accept connections for any IP
1858 interface associated with the node, the value
1860 ::= { tcpConnEntry 2 }
1862 tcpConnLocalPort OBJECT-TYPE
1863 SYNTAX INTEGER (0..65535)
1867 "The local port number for this TCP connection."
1868 ::= { tcpConnEntry 3 }
1870 tcpConnRemAddress OBJECT-TYPE
1875 "The remote IP address for this TCP connection."
1876 ::= { tcpConnEntry 4 }
1878 tcpConnRemPort OBJECT-TYPE
1879 SYNTAX INTEGER (0..65535)
1883 "The remote port number for this TCP connection."
1884 ::= { tcpConnEntry 5 }
1887 -- additional TCP objects
1889 tcpInErrs OBJECT-TYPE
1894 "The total number of segments received in error
1895 (e.g., bad TCP checksums)."
1898 tcpOutRsts OBJECT-TYPE
1903 "The number of TCP segments sent containing the
1910 -- Implementation of the UDP group is mandatory for all
1911 -- systems which implement the UDP.
1913 udpInDatagrams OBJECT-TYPE
1918 "The total number of UDP datagrams delivered to
1922 udpNoPorts OBJECT-TYPE
1927 "The total number of received UDP datagrams for
1928 which there was no application at the destination
1932 udpInErrors OBJECT-TYPE
1937 "The number of received UDP datagrams that could
1938 not be delivered for reasons other than the lack
1939 of an application at the destination port."
1942 udpOutDatagrams OBJECT-TYPE
1947 "The total number of UDP datagrams sent from this
1952 -- the UDP Listener table
1954 -- The UDP listener table contains information about this
1955 -- entity's UDP end-points on which a local application is
1956 -- currently accepting datagrams.
1958 udpTable OBJECT-TYPE
1959 SYNTAX SEQUENCE OF UdpEntry
1960 ACCESS not-accessible
1963 "A table containing UDP listener information."
1966 udpEntry OBJECT-TYPE
1968 ACCESS not-accessible
1971 "Information about a particular current UDP
1973 INDEX { udpLocalAddress, udpLocalPort }
1984 udpLocalAddress OBJECT-TYPE
1989 "The local IP address for this UDP listener. In
1990 the case of a UDP listener which is willing to
1991 accept datagrams for any IP interface associated
1992 with the node, the value 0.0.0.0 is used."
1995 udpLocalPort OBJECT-TYPE
1996 SYNTAX INTEGER (0..65535)
2000 "The local port number for this UDP listener."
2006 -- Implementation of the EGP group is mandatory for all
2007 -- systems which implement the EGP.
2009 egpInMsgs OBJECT-TYPE
2014 "The number of EGP messages received without
2018 egpInErrors OBJECT-TYPE
2023 "The number of EGP messages received that proved
2027 egpOutMsgs OBJECT-TYPE
2032 "The total number of locally generated EGP
2036 egpOutErrors OBJECT-TYPE
2041 "The number of locally generated EGP messages not
2042 sent due to resource limitations within an EGP
2047 -- the EGP Neighbor table
2049 -- The EGP neighbor table contains information about this
2050 -- entity's EGP neighbors.
2052 egpNeighTable OBJECT-TYPE
2053 SYNTAX SEQUENCE OF EgpNeighEntry
2054 ACCESS not-accessible
2057 "The EGP neighbor table."
2060 egpNeighEntry OBJECT-TYPE
2061 SYNTAX EgpNeighEntry
2062 ACCESS not-accessible
2065 "Information about this entity's relationship with
2066 a particular EGP neighbor."
2067 INDEX { egpNeighAddr }
2068 ::= { egpNeighTable 1 }
2094 egpNeighIntervalHello
2096 egpNeighIntervalPoll
2100 egpNeighEventTrigger
2104 egpNeighState OBJECT-TYPE
2115 "The EGP state of the local system with respect to
2116 this entry's EGP neighbor. Each EGP state is
2117 represented by a value that is one greater than
2118 the numerical value associated with said state in
2120 ::= { egpNeighEntry 1 }
2122 egpNeighAddr OBJECT-TYPE
2127 "The IP address of this entry's EGP neighbor."
2128 ::= { egpNeighEntry 2 }
2130 egpNeighAs OBJECT-TYPE
2135 "The autonomous system of this EGP peer. Zero
2136 should be specified if the autonomous system
2137 number of the neighbor is not yet known."
2138 ::= { egpNeighEntry 3 }
2140 egpNeighInMsgs OBJECT-TYPE
2145 "The number of EGP messages received without error
2146 from this EGP peer."
2147 ::= { egpNeighEntry 4 }
2149 egpNeighInErrs OBJECT-TYPE
2154 "The number of EGP messages received from this EGP
2155 peer that proved to be in error (e.g., bad EGP
2157 ::= { egpNeighEntry 5 }
2159 egpNeighOutMsgs OBJECT-TYPE
2164 "The number of locally generated EGP messages to
2166 ::= { egpNeighEntry 6 }
2168 egpNeighOutErrs OBJECT-TYPE
2173 "The number of locally generated EGP messages not
2174 sent to this EGP peer due to resource limitations
2175 within an EGP entity."
2176 ::= { egpNeighEntry 7 }
2178 egpNeighInErrMsgs OBJECT-TYPE
2183 "The number of EGP-defined error messages received
2184 from this EGP peer."
2185 ::= { egpNeighEntry 8 }
2187 egpNeighOutErrMsgs OBJECT-TYPE
2192 "The number of EGP-defined error messages sent to
2194 ::= { egpNeighEntry 9 }
2196 egpNeighStateUps OBJECT-TYPE
2201 "The number of EGP state transitions to the UP
2202 state with this EGP peer."
2203 ::= { egpNeighEntry 10 }
2205 egpNeighStateDowns OBJECT-TYPE
2210 "The number of EGP state transitions from the UP
2211 state to any other state with this EGP peer."
2212 ::= { egpNeighEntry 11 }
2214 egpNeighIntervalHello OBJECT-TYPE
2219 "The interval between EGP Hello command
2220 retransmissions (in hundredths of a second). This
2221 represents the t1 timer as defined in RFC 904."
2222 ::= { egpNeighEntry 12 }
2224 egpNeighIntervalPoll OBJECT-TYPE
2229 "The interval between EGP poll command
2230 retransmissions (in hundredths of a second). This
2231 represents the t3 timer as defined in RFC 904."
2232 ::= { egpNeighEntry 13 }
2234 egpNeighMode OBJECT-TYPE
2235 SYNTAX INTEGER { active(1), passive(2) }
2239 "The polling mode of this EGP entity, either
2241 ::= { egpNeighEntry 14 }
2243 egpNeighEventTrigger OBJECT-TYPE
2244 SYNTAX INTEGER { start(1), stop(2) }
2248 "A control variable used to trigger operator-
2249 initiated Start and Stop events. When read, this
2250 variable always returns the most recent value that
2251 egpNeighEventTrigger was set to. If it has not
2252 been set since the last initialization of the
2253 network management subsystem on the node, it
2254 returns a value of `stop'.
2256 When set, this variable causes a Start or Stop
2257 event on the specified neighbor, as specified on
2258 pages 8-10 of RFC 904. Briefly, a Start event
2259 causes an Idle peer to begin neighbor acquisition
2260 and a non-Idle peer to reinitiate neighbor
2261 acquisition. A stop event causes a non-Idle peer
2262 to return to the Idle state until a Start event
2263 occurs, either via egpNeighEventTrigger or
2265 ::= { egpNeighEntry 15 }
2268 -- additional EGP objects
2275 "The autonomous system number of this EGP entity."
2278 -- the Transmission group
2280 -- Based on the transmission media underlying each interface
2281 -- on a system, the corresponding portion of the Transmission
2282 -- group is mandatory for that system.
2284 -- When Internet-standard definitions for managing
2285 -- transmission media are defined, the transmission group is
2286 -- used to provide a prefix for the names of those objects.
2288 -- Typically, such definitions reside in the experimental
2289 -- portion of the MIB until they are "proven", then as a
2290 -- part of the Internet standardization process, the
2291 -- definitions are accordingly elevated and a new object
2292 -- identifier, under the transmission group is defined. By
2293 -- convention, the name assigned is:
2295 -- type OBJECT IDENTIFIER ::= { transmission number }
2297 -- where "type" is the symbolic value used for the media in
2298 -- the ifType column of the ifTable object, and "number" is
2299 -- the actual integer value corresponding to the symbol.
2304 -- Implementation of the SNMP group is mandatory for all
2305 -- systems which support an SNMP protocol entity. Some of
2306 -- the objects defined below will be zero-valued in those
2307 -- SNMP implementations that are optimized to support only
2308 -- those functions specific to either a management agent or
2309 -- a management station. In particular, it should be
2310 -- observed that the objects below refer to an SNMP entity,
2311 -- and there may be several SNMP entities residing on a
2312 -- managed node (e.g., if the node is hosting acting as
2313 -- a management station).
2315 snmpInPkts OBJECT-TYPE
2320 "The total number of Messages delivered to the
2321 SNMP entity from the transport service."
2324 snmpOutPkts OBJECT-TYPE
2329 "The total number of SNMP Messages which were
2330 passed from the SNMP protocol entity to the
2334 snmpInBadVersions OBJECT-TYPE
2339 "The total number of SNMP Messages which were
2340 delivered to the SNMP protocol entity and were for
2341 an unsupported SNMP version."
2344 snmpInBadCommunityNames OBJECT-TYPE
2349 "The total number of SNMP Messages delivered to
2350 the SNMP protocol entity which used a SNMP
2351 community name not known to said entity."
2354 snmpInBadCommunityUses OBJECT-TYPE
2359 "The total number of SNMP Messages delivered to
2360 the SNMP protocol entity which represented an SNMP
2361 operation which was not allowed by the SNMP
2362 community named in the Message."
2365 snmpInASNParseErrs OBJECT-TYPE
2370 "The total number of ASN.1 or BER errors
2371 encountered by the SNMP protocol entity when
2372 decoding received SNMP Messages."
2375 -- { snmp 7 } is not used
2377 snmpInTooBigs OBJECT-TYPE
2382 "The total number of SNMP PDUs which were
2383 delivered to the SNMP protocol entity and for
2384 which the value of the error-status field is
2388 snmpInNoSuchNames OBJECT-TYPE
2393 "The total number of SNMP PDUs which were
2394 delivered to the SNMP protocol entity and for
2395 which the value of the error-status field is
2399 snmpInBadValues OBJECT-TYPE
2404 "The total number of SNMP PDUs which were
2405 delivered to the SNMP protocol entity and for
2406 which the value of the error-status field is
2410 snmpInReadOnlys OBJECT-TYPE
2415 "The total number valid SNMP PDUs which were
2416 delivered to the SNMP protocol entity and for
2417 which the value of the error-status field is
2418 `readOnly'. It should be noted that it is a
2419 protocol error to generate an SNMP PDU which
2420 contains the value `readOnly' in the error-status
2421 field, as such this object is provided as a means
2422 of detecting incorrect implementations of the
2426 snmpInGenErrs OBJECT-TYPE
2431 "The total number of SNMP PDUs which were
2432 delivered to the SNMP protocol entity and for
2433 which the value of the error-status field is
2437 snmpInTotalReqVars OBJECT-TYPE
2442 "The total number of MIB objects which have been
2443 retrieved successfully by the SNMP protocol entity
2444 as the result of receiving valid SNMP Get-Request
2448 snmpInTotalSetVars OBJECT-TYPE
2453 "The total number of MIB objects which have been
2454 altered successfully by the SNMP protocol entity
2455 as the result of receiving valid SNMP Set-Request
2459 snmpInGetRequests OBJECT-TYPE
2464 "The total number of SNMP Get-Request PDUs which
2465 have been accepted and processed by the SNMP
2469 snmpInGetNexts OBJECT-TYPE
2474 "The total number of SNMP Get-Next PDUs which have
2475 been accepted and processed by the SNMP protocol
2479 snmpInSetRequests OBJECT-TYPE
2484 "The total number of SNMP Set-Request PDUs which
2485 have been accepted and processed by the SNMP
2489 snmpInGetResponses OBJECT-TYPE
2494 "The total number of SNMP Get-Response PDUs which
2495 have been accepted and processed by the SNMP
2499 snmpInTraps OBJECT-TYPE
2504 "The total number of SNMP Trap PDUs which have
2505 been accepted and processed by the SNMP protocol
2509 snmpOutTooBigs OBJECT-TYPE
2514 "The total number of SNMP PDUs which were
2515 generated by the SNMP protocol entity and for
2516 which the value of the error-status field is
2520 snmpOutNoSuchNames OBJECT-TYPE
2525 "The total number of SNMP PDUs which were
2526 generated by the SNMP protocol entity and for
2527 which the value of the error-status is
2531 snmpOutBadValues OBJECT-TYPE
2536 "The total number of SNMP PDUs which were
2537 generated by the SNMP protocol entity and for
2538 which the value of the error-status field is
2542 -- { snmp 23 } is not used
2544 snmpOutGenErrs OBJECT-TYPE
2549 "The total number of SNMP PDUs which were
2550 generated by the SNMP protocol entity and for
2551 which the value of the error-status field is
2555 snmpOutGetRequests OBJECT-TYPE
2560 "The total number of SNMP Get-Request PDUs which
2561 have been generated by the SNMP protocol entity."
2564 snmpOutGetNexts OBJECT-TYPE
2569 "The total number of SNMP Get-Next PDUs which have
2570 been generated by the SNMP protocol entity."
2573 snmpOutSetRequests OBJECT-TYPE
2578 "The total number of SNMP Set-Request PDUs which
2579 have been generated by the SNMP protocol entity."
2582 snmpOutGetResponses OBJECT-TYPE
2587 "The total number of SNMP Get-Response PDUs which
2588 have been generated by the SNMP protocol entity."
2591 snmpOutTraps OBJECT-TYPE
2596 "The total number of SNMP Trap PDUs which have
2597 been generated by the SNMP protocol entity."
2600 snmpEnableAuthenTraps OBJECT-TYPE
2601 SYNTAX INTEGER { enabled(1), disabled(2) }
2605 "Indicates whether the SNMP agent process is
2606 permitted to generate authentication-failure
2607 traps. The value of this object overrides any
2608 configuration information; as such, it provides a
2609 means whereby all authentication-failure traps may
2612 Note that it is strongly recommended that this
2613 object be stored in non-volatile memory so that it
2614 remains constant between re-initializations of the
2615 network management system."