1 -- file: asn1specs/1213_mib2.asn1
3 -- this file is used in ../c{,++}-examples/snmp/
5 -- $Header: /cvs/Darwin/Security/SecuritySNACCRuntime/asn1specs/rfc1213-mib2.asn1,v 1.1.1.1 2001/05/18 23:14:05 mb Exp $
6 -- $Log: rfc1213-mib2.asn1,v $
7 -- Revision 1.1.1.1 2001/05/18 23:14:05 mb
8 -- Move from private repository to open source repository
10 -- Revision 1.1.1.1 1999/03/16 18:05:56 aram
11 -- Originals from SMIME Free Library.
13 -- Revision 1.3 1995/07/27 08:29:19 rj
14 -- rfc1155-smi.asn1, rfc1157-snmp.asn1 and rfc1213-mib2.asn1 renamed from 1155-smi.asn1, 1157-snmp.asn1 and 1213-mib2.asn1 to accomodate to snacc's new file name generation scheme.
16 -- Revision 1.2 1995/07/25 19:53:14 rj
17 -- changed `_' to `-' in file names.
19 -- Revision 1.1 1994/08/31 23:08:28 rj
23 RFC1213-MIB DEFINITIONS ::= BEGIN
26 mgmt, NetworkAddress, IpAddress, Counter, Gauge,
35 -- This MIB module uses the extended OBJECT-TYPE macro as
39 -- MIB-II (same prefix as MIB-I)
41 mib-2 OBJECT IDENTIFIER ::= { mgmt 1 }
43 -- textual conventions
47 -- This data type is used to model textual information taken
48 -- from the NVT ASCII character set. By convention, objects
49 -- with this syntax are declared as having
54 -- This data type is used to model media addresses. For many
55 -- types of media, this will be in a binary representation.
56 -- For example, an ethernet address would be represented as
57 -- a string of 6 octets.
62 system OBJECT IDENTIFIER ::= { mib-2 1 }
64 interfaces OBJECT IDENTIFIER ::= { mib-2 2 }
66 at OBJECT IDENTIFIER ::= { mib-2 3 }
68 ip OBJECT IDENTIFIER ::= { mib-2 4 }
70 icmp OBJECT IDENTIFIER ::= { mib-2 5 }
72 tcp OBJECT IDENTIFIER ::= { mib-2 6 }
74 udp OBJECT IDENTIFIER ::= { mib-2 7 }
76 egp OBJECT IDENTIFIER ::= { mib-2 8 }
78 -- historical (some say hysterical)
79 -- cmot OBJECT IDENTIFIER ::= { mib-2 9 }
81 transmission OBJECT IDENTIFIER ::= { mib-2 10 }
83 snmp OBJECT IDENTIFIER ::= { mib-2 11 }
88 -- Implementation of the System group is mandatory for all
89 -- systems. If an agent is not configured to have a value
90 -- for any of these variables, a string of length 0 is
94 SYNTAX DisplayString (SIZE (0..255))
98 "A textual description of the entity. This value
99 should include the full name and version
100 identification of the system's hardware type,
101 software operating-system, and networking
102 software. It is mandatory that this only contain
103 printable ASCII characters."
106 sysObjectID OBJECT-TYPE
107 SYNTAX OBJECT IDENTIFIER
111 "The vendor's authoritative identification of the
112 network management subsystem contained in the
113 entity. This value is allocated within the SMI
114 enterprises subtree (1.3.6.1.4.1) and provides an
115 easy and unambiguous means for determining `what
116 kind of box' is being managed. For example, if
117 vendor `Flintstones, Inc.' was assigned the
118 subtree 1.3.6.1.4.1.4242, it could assign the
119 identifier 1.3.6.1.4.1.4242.1.1 to its `Fred
123 sysUpTime OBJECT-TYPE
128 "The time (in hundredths of a second) since the
129 network management portion of the system was last
133 sysContact OBJECT-TYPE
134 SYNTAX DisplayString (SIZE (0..255))
138 "The textual identification of the contact person
139 for this managed node, together with information
140 on how to contact this person."
144 SYNTAX DisplayString (SIZE (0..255))
148 "An administratively-assigned name for this
149 managed node. By convention, this is the node's
150 fully-qualified domain name."
153 sysLocation OBJECT-TYPE
154 SYNTAX DisplayString (SIZE (0..255))
158 "The physical location of this node (e.g.,
159 `telephone closet, 3rd floor')."
162 sysServices OBJECT-TYPE
163 SYNTAX INTEGER (0..127)
167 "A value which indicates the set of services that
168 this entity primarily offers.
170 The value is a sum. This sum initially takes the
171 value zero, Then, for each layer, L, in the range
172 1 through 7, that this node performs transactions
173 for, 2 raised to (L - 1) is added to the sum. For
174 example, a node which performs primarily routing
175 functions would have a value of 4 (2^(3-1)). In
176 contrast, a node which is a host offering
177 application services would have a value of 72
178 (2^(4-1) + 2^(7-1)). Note that in the context of
179 the Internet suite of protocols, values should be
180 calculated accordingly:
183 1 physical (e.g., repeaters)
184 2 datalink/subnetwork (e.g., bridges)
185 3 internet (e.g., IP gateways)
186 4 end-to-end (e.g., IP hosts)
187 7 applications (e.g., mail relays)
189 For systems including OSI protocols, layers 5 and
190 6 may also be counted."
195 -- the Interfaces group
197 -- Implementation of the Interfaces group is mandatory for
205 "The number of network interfaces (regardless of
206 their current state) present on this system."
210 -- the Interfaces table
212 -- The Interfaces table contains information on the entity's
213 -- interfaces. Each interface is thought of as being
214 -- attached to a `subnetwork'. Note that this term should
215 -- not be confused with `subnet' which refers to an
216 -- addressing partitioning scheme used in the Internet suite
220 SYNTAX SEQUENCE OF IfEntry
221 ACCESS not-accessible
224 "A list of interface entries. The number of
225 entries is given by the value of ifNumber."
230 ACCESS not-accessible
233 "An interface entry containing objects at the
234 subnetwork layer and below for a particular
292 "A unique value for each interface. Its value
293 ranges between 1 and the value of ifNumber. The
294 value for each interface must remain constant at
295 least from one re-initialization of the entity's
296 network management system to the next re-
301 SYNTAX DisplayString (SIZE (0..255))
305 "A textual string containing information about the
306 interface. This string should include the name of
307 the manufacturer, the product name and the version
308 of the hardware interface."
313 other(1), -- none of the following
320 iso88024-tokenBus(8),
321 iso88025-tokenRing(9),
331 e1(19), -- european equiv. of T-1
333 primaryISDN(21), -- proprietary serial
334 propPointToPointSerial(22),
336 softwareLoopback(24),
337 eon(25), -- CLNP over IP [11]
339 nsip(27), -- XNS over IP
340 slip(28), -- generic SLIP
341 ultra(29), -- ULTRA technologies
349 "The type of interface, distinguished according to
350 the physical/link protocol(s) immediately `below'
351 the network layer in the protocol stack."
359 "The size of the largest datagram which can be
360 sent/received on the interface, specified in
361 octets. For interfaces that are used for
362 transmitting network datagrams, this is the size
363 of the largest network datagram that can be sent
372 "An estimate of the interface's current bandwidth
373 in bits per second. For interfaces which do not
374 vary in bandwidth or for those where no accurate
375 estimation can be made, this object should contain
376 the nominal bandwidth."
379 ifPhysAddress OBJECT-TYPE
384 "The interface's address at the protocol layer
385 immediately `below' the network layer in the
386 protocol stack. For interfaces which do not have
387 such an address (e.g., a serial line), this object
388 should contain an octet string of zero length."
391 ifAdminStatus OBJECT-TYPE
393 up(1), -- ready to pass packets
395 testing(3) -- in some test mode
400 "The desired state of the interface. The
401 testing(3) state indicates that no operational
402 packets can be passed."
405 ifOperStatus OBJECT-TYPE
407 up(1), -- ready to pass packets
409 testing(3) -- in some test mode
414 "The current operational state of the interface.
415 The testing(3) state indicates that no operational
416 packets can be passed."
419 ifLastChange OBJECT-TYPE
424 "The value of sysUpTime at the time the interface
425 entered its current operational state. If the
426 current state was entered prior to the last re-
427 initialization of the local network management
428 subsystem, then this object contains a zero
432 ifInOctets OBJECT-TYPE
437 "The total number of octets received on the
438 interface, including framing characters."
441 ifInUcastPkts OBJECT-TYPE
446 "The number of subnetwork-unicast packets
447 delivered to a higher-layer protocol."
450 ifInNUcastPkts OBJECT-TYPE
455 "The number of non-unicast (i.e., subnetwork-
456 broadcast or subnetwork-multicast) packets
457 delivered to a higher-layer protocol."
460 ifInDiscards OBJECT-TYPE
465 "The number of inbound packets which were chosen
466 to be discarded even though no errors had been
467 detected to prevent their being deliverable to a
468 higher-layer protocol. One possible reason for
469 discarding such a packet could be to free up
473 ifInErrors OBJECT-TYPE
478 "The number of inbound packets that contained
479 errors preventing them from being deliverable to a
480 higher-layer protocol."
484 ifInUnknownProtos OBJECT-TYPE
489 "The number of packets received via the interface
490 which were discarded because of an unknown or
491 unsupported protocol."
494 ifOutOctets OBJECT-TYPE
499 "The total number of octets transmitted out of the
500 interface, including framing characters."
503 ifOutUcastPkts OBJECT-TYPE
508 "The total number of packets that higher-level
509 protocols requested be transmitted to a
510 subnetwork-unicast address, including those that
511 were discarded or not sent."
514 ifOutNUcastPkts OBJECT-TYPE
519 "The total number of packets that higher-level
520 protocols requested be transmitted to a non-
521 unicast (i.e., a subnetwork-broadcast or
522 subnetwork-multicast) address, including those
523 that were discarded or not sent."
526 ifOutDiscards OBJECT-TYPE
531 "The number of outbound packets which were chosen
532 to be discarded even though no errors had been
533 detected to prevent their being transmitted. One
534 possible reason for discarding such a packet could
535 be to free up buffer space."
538 ifOutErrors OBJECT-TYPE
543 "The number of outbound packets that could not be
544 transmitted because of errors."
547 ifOutQLen OBJECT-TYPE
552 "The length of the output packet queue (in
556 ifSpecific OBJECT-TYPE
557 SYNTAX OBJECT IDENTIFIER
561 "A reference to MIB definitions specific to the
562 particular media being used to realize the
563 interface. For example, if the interface is
564 realized by an ethernet, then the value of this
565 object refers to a document defining objects
566 specific to ethernet. If this information is not
567 present, its value should be set to the OBJECT
568 IDENTIFIER { 0 0 }, which is a syntatically valid
569 object identifier, and any conformant
570 implementation of ASN.1 and BER must be able to
571 generate and recognize this value."
575 -- the Address Translation group
577 -- Implementation of the Address Translation group is
578 -- mandatory for all systems. Note however that this group
579 -- is deprecated by MIB-II. That is, it is being included
580 -- solely for compatibility with MIB-I nodes, and will most
581 -- likely be excluded from MIB-III nodes. From MIB-II and
582 -- onwards, each network protocol group contains its own
583 -- address translation tables.
585 -- The Address Translation group contains one table which is
586 -- the union across all interfaces of the translation tables
587 -- for converting a NetworkAddress (e.g., an IP address) into
588 -- a subnetwork-specific address. For lack of a better term,
589 -- this document refers to such a subnetwork-specific address
590 -- as a `physical' address.
592 -- Examples of such translation tables are: for broadcast
593 -- media where ARP is in use, the translation table is
594 -- equivalent to the ARP cache; or, on an X.25 network where
595 -- non-algorithmic translation to X.121 addresses is
596 -- required, the translation table contains the
597 -- NetworkAddress to X.121 address equivalences.
600 SYNTAX SEQUENCE OF AtEntry
601 ACCESS not-accessible
604 "The Address Translation tables contain the
605 NetworkAddress to `physical' address equivalences.
606 Some interfaces do not use translation tables for
607 determining address equivalences (e.g., DDN-X.25
608 has an algorithmic method); if all interfaces are
609 of this type, then the Address Translation table
610 is empty, i.e., has zero entries."
615 ACCESS not-accessible
618 "Each entry contains one NetworkAddress to
619 `physical' address equivalence."
634 atIfIndex OBJECT-TYPE
639 "The interface on which this entry's equivalence
640 is effective. The interface identified by a
641 particular value of this index is the same
642 interface as identified by the same value of
646 atPhysAddress OBJECT-TYPE
651 "The media-dependent `physical' address.
653 Setting this object to a null string (one of zero
654 length) has the effect of invaliding the
655 corresponding entry in the atTable object. That
656 is, it effectively dissasociates the interface
657 identified with said entry from the mapping
658 identified with said entry. It is an
659 implementation-specific matter as to whether the
660 agent removes an invalidated entry from the table.
661 Accordingly, management stations must be prepared
662 to receive tabular information from agents that
663 corresponds to entries not currently in use.
664 Proper interpretation of such entries requires
665 examination of the relevant atPhysAddress object."
668 atNetAddress OBJECT-TYPE
669 SYNTAX NetworkAddress
673 "The NetworkAddress (e.g., the IP address)
674 corresponding to the media-dependent `physical'
681 -- Implementation of the IP group is mandatory for all
684 ipForwarding OBJECT-TYPE
686 forwarding(1), -- acting as a gateway
687 not-forwarding(2) -- NOT acting as a gateway
692 "The indication of whether this entity is acting
693 as an IP gateway in respect to the forwarding of
694 datagrams received by, but not addressed to, this
695 entity. IP gateways forward datagrams. IP hosts
696 do not (except those source-routed via the host).
698 Note that for some managed nodes, this object may
699 take on only a subset of the values possible.
700 Accordingly, it is appropriate for an agent to
701 return a `badValue' response if a management
702 station attempts to change this object to an
703 inappropriate value."
706 ipDefaultTTL OBJECT-TYPE
711 "The default value inserted into the Time-To-Live
712 field of the IP header of datagrams originated at
713 this entity, whenever a TTL value is not supplied
714 by the transport layer protocol."
717 ipInReceives OBJECT-TYPE
722 "The total number of input datagrams received from
723 interfaces, including those received in error."
726 ipInHdrErrors OBJECT-TYPE
731 "The number of input datagrams discarded due to
732 errors in their IP headers, including bad
733 checksums, version number mismatch, other format
734 errors, time-to-live exceeded, errors discovered
735 in processing their IP options, etc."
738 ipInAddrErrors OBJECT-TYPE
743 "The number of input datagrams discarded because
744 the IP address in their IP header's destination
745 field was not a valid address to be received at
746 this entity. This count includes invalid
747 addresses (e.g., 0.0.0.0) and addresses of
748 unsupported Classes (e.g., Class E). For entities
749 which are not IP Gateways and therefore do not
750 forward datagrams, this counter includes datagrams
751 discarded because the destination address was not
755 ipForwDatagrams OBJECT-TYPE
760 "The number of input datagrams for which this
761 entity was not their final IP destination, as a
762 result of which an attempt was made to find a
763 route to forward them to that final destination.
764 In entities which do not act as IP Gateways, this
765 counter will include only those packets which were
766 Source-Routed via this entity, and the Source-
767 Route option processing was successful."
770 ipInUnknownProtos OBJECT-TYPE
775 "The number of locally-addressed datagrams
776 received successfully but discarded because of an
777 unknown or unsupported protocol."
780 ipInDiscards OBJECT-TYPE
785 "The number of input IP datagrams for which no
786 problems were encountered to prevent their
787 continued processing, but which were discarded
788 (e.g., for lack of buffer space). Note that this
789 counter does not include any datagrams discarded
790 while awaiting re-assembly."
793 ipInDelivers OBJECT-TYPE
798 "The total number of input datagrams successfully
799 delivered to IP user-protocols (including ICMP)."
802 ipOutRequests OBJECT-TYPE
807 "The total number of IP datagrams which local IP
808 user-protocols (including ICMP) supplied to IP in
809 requests for transmission. Note that this counter
810 does not include any datagrams counted in
814 ipOutDiscards OBJECT-TYPE
819 "The number of output IP datagrams for which no
820 problem was encountered to prevent their
821 transmission to their destination, but which were
822 discarded (e.g., for lack of buffer space). Note
823 that this counter would include datagrams counted
824 in ipForwDatagrams if any such packets met this
825 (discretionary) discard criterion."
828 ipOutNoRoutes OBJECT-TYPE
833 "The number of IP datagrams discarded because no
834 route could be found to transmit them to their
835 destination. Note that this counter includes any
836 packets counted in ipForwDatagrams which meet this
837 `no-route' criterion. Note that this includes any
838 datagarms which a host cannot route because all of
839 its default gateways are down."
842 ipReasmTimeout OBJECT-TYPE
847 "The maximum number of seconds which received
848 fragments are held while they are awaiting
849 reassembly at this entity."
852 ipReasmReqds OBJECT-TYPE
857 "The number of IP fragments received which needed
858 to be reassembled at this entity."
861 ipReasmOKs OBJECT-TYPE
866 "The number of IP datagrams successfully re-
870 ipReasmFails OBJECT-TYPE
875 "The number of failures detected by the IP re-
876 assembly algorithm (for whatever reason: timed
877 out, errors, etc). Note that this is not
878 necessarily a count of discarded IP fragments
879 since some algorithms (notably the algorithm in
880 RFC 815) can lose track of the number of fragments
881 by combining them as they are received."
884 ipFragOKs OBJECT-TYPE
889 "The number of IP datagrams that have been
890 successfully fragmented at this entity."
893 ipFragFails OBJECT-TYPE
898 "The number of IP datagrams that have been
899 discarded because they needed to be fragmented at
900 this entity but could not be, e.g., because their
901 Don't Fragment flag was set."
904 ipFragCreates OBJECT-TYPE
909 "The number of IP datagram fragments that have
910 been generated as a result of fragmentation at
916 -- the IP address table
918 -- The IP address table contains this entity's IP addressing
921 ipAddrTable OBJECT-TYPE
922 SYNTAX SEQUENCE OF IpAddrEntry
923 ACCESS not-accessible
926 "The table of addressing information relevant to
927 this entity's IP addresses."
930 ipAddrEntry OBJECT-TYPE
932 ACCESS not-accessible
935 "The addressing information for one of this
936 entity's IP addresses."
937 INDEX { ipAdEntAddr }
938 ::= { ipAddrTable 1 }
954 ipAdEntAddr OBJECT-TYPE
959 "The IP address to which this entry's addressing
960 information pertains."
961 ::= { ipAddrEntry 1 }
964 ipAdEntIfIndex OBJECT-TYPE
969 "The index value which uniquely identifies the
970 interface to which this entry is applicable. The
971 interface identified by a particular value of this
972 index is the same interface as identified by the
973 same value of ifIndex."
974 ::= { ipAddrEntry 2 }
976 ipAdEntNetMask OBJECT-TYPE
981 "The subnet mask associated with the IP address of
982 this entry. The value of the mask is an IP
983 address with all the network bits set to 1 and all
984 the hosts bits set to 0."
985 ::= { ipAddrEntry 3 }
987 ipAdEntBcastAddr OBJECT-TYPE
992 "The value of the least-significant bit in the IP
993 broadcast address used for sending datagrams on
994 the (logical) interface associated with the IP
995 address of this entry. For example, when the
996 Internet standard all-ones broadcast address is
997 used, the value will be 1. This value applies to
998 both the subnet and network broadcasts addresses
999 used by the entity on this (logical) interface."
1000 ::= { ipAddrEntry 4 }
1002 ipAdEntReasmMaxSize OBJECT-TYPE
1003 SYNTAX INTEGER (0..65535)
1007 "The size of the largest IP datagram which this
1008 entity can re-assemble from incoming IP fragmented
1009 datagrams received on this interface."
1010 ::= { ipAddrEntry 5 }
1014 -- the IP routing table
1016 -- The IP routing table contains an entry for each route
1017 -- presently known to this entity.
1019 ipRouteTable OBJECT-TYPE
1020 SYNTAX SEQUENCE OF IpRouteEntry
1021 ACCESS not-accessible
1024 "This entity's IP Routing table."
1027 ipRouteEntry OBJECT-TYPE
1029 ACCESS not-accessible
1032 "A route to a particular destination."
1033 INDEX { ipRouteDest }
1034 ::= { ipRouteTable 1 }
1066 ipRouteDest OBJECT-TYPE
1071 "The destination IP address of this route. An
1072 entry with a value of 0.0.0.0 is considered a
1073 default route. Multiple routes to a single
1074 destination can appear in the table, but access to
1075 such multiple entries is dependent on the table-
1076 access mechanisms defined by the network
1077 management protocol in use."
1078 ::= { ipRouteEntry 1 }
1080 ipRouteIfIndex OBJECT-TYPE
1085 "The index value which uniquely identifies the
1086 local interface through which the next hop of this
1087 route should be reached. The interface identified
1088 by a particular value of this index is the same
1089 interface as identified by the same value of
1091 ::= { ipRouteEntry 2 }
1093 ipRouteMetric1 OBJECT-TYPE
1098 "The primary routing metric for this route. The
1099 semantics of this metric are determined by the
1100 routing-protocol specified in the route's
1101 ipRouteProto value. If this metric is not used,
1102 its value should be set to -1."
1103 ::= { ipRouteEntry 3 }
1105 ipRouteMetric2 OBJECT-TYPE
1110 "An alternate routing metric for this route. The
1111 semantics of this metric are determined by the
1112 routing-protocol specified in the route's
1113 ipRouteProto value. If this metric is not used,
1114 its value should be set to -1."
1115 ::= { ipRouteEntry 4 }
1117 ipRouteMetric3 OBJECT-TYPE
1122 "An alternate routing metric for this route. The
1123 semantics of this metric are determined by the
1124 routing-protocol specified in the route's
1125 ipRouteProto value. If this metric is not used,
1126 its value should be set to -1."
1127 ::= { ipRouteEntry 5 }
1129 ipRouteMetric4 OBJECT-TYPE
1134 "An alternate routing metric for this route. The
1135 semantics of this metric are determined by the
1136 routing-protocol specified in the route's
1137 ipRouteProto value. If this metric is not used,
1138 its value should be set to -1."
1139 ::= { ipRouteEntry 6 }
1141 ipRouteNextHop OBJECT-TYPE
1146 "The IP address of the next hop of this route.
1147 (In the case of a route bound to an interface
1148 which is realized via a broadcast media, the value
1149 of this field is the agent's IP address on that
1151 ::= { ipRouteEntry 7 }
1153 ipRouteType OBJECT-TYPE
1155 other(1), -- none of the following
1157 invalid(2), -- an invalidated route
1158 -- route to directly
1159 direct(3), -- connected (sub-)network
1161 -- route to a non-local
1162 indirect(4) -- host/network/sub-network
1167 "The type of route. Note that the values
1168 direct(3) and indirect(4) refer to the notion of
1169 direct and indirect routing in the IP
1172 Setting this object to the value invalid(2) has
1173 the effect of invalidating the corresponding entry
1174 in the ipRouteTable object. That is, it
1175 effectively dissasociates the destination
1176 identified with said entry from the route
1177 identified with said entry. It is an
1178 implementation-specific matter as to whether the
1179 agent removes an invalidated entry from the table.
1180 Accordingly, management stations must be prepared
1181 to receive tabular information from agents that
1182 corresponds to entries not currently in use.
1183 Proper interpretation of such entries requires
1184 examination of the relevant ipRouteType object."
1185 ::= { ipRouteEntry 8 }
1187 ipRouteProto OBJECT-TYPE
1189 other(1), -- none of the following
1191 -- non-protocol information,
1192 -- e.g., manually configured
1193 local(2), -- entries
1195 -- set via a network
1196 netmgmt(3), -- management protocol
1198 -- obtained via ICMP,
1199 icmp(4), -- e.g., Redirect
1201 -- the remaining values are
1202 -- all gateway routing
1218 "The routing mechanism via which this route was
1219 learned. Inclusion of values for gateway routing
1220 protocols is not intended to imply that hosts
1221 should support those protocols."
1222 ::= { ipRouteEntry 9 }
1224 ipRouteAge OBJECT-TYPE
1229 "The number of seconds since this route was last
1230 updated or otherwise determined to be correct.
1231 Note that no semantics of `too old' can be implied
1232 except through knowledge of the routing protocol
1233 by which the route was learned."
1234 ::= { ipRouteEntry 10 }
1236 ipRouteMask OBJECT-TYPE
1241 "Indicate the mask to be logical-ANDed with the
1242 destination address before being compared to the
1243 value in the ipRouteDest field. For those systems
1244 that do not support arbitrary subnet masks, an
1245 agent constructs the value of the ipRouteMask by
1246 determining whether the value of the correspondent
1247 ipRouteDest field belong to a class-A, B, or C
1248 network, and then using one of:
1253 255.255.255.0 class-C
1255 If the value of the ipRouteDest is 0.0.0.0 (a
1256 default route), then the mask value is also
1257 0.0.0.0. It should be noted that all IP routing
1258 subsystems implicitly use this mechanism."
1259 ::= { ipRouteEntry 11 }
1261 ipRouteMetric5 OBJECT-TYPE
1266 "An alternate routing metric for this route. The
1267 semantics of this metric are determined by the
1268 routing-protocol specified in the route's
1269 ipRouteProto value. If this metric is not used,
1270 its value should be set to -1."
1271 ::= { ipRouteEntry 12 }
1273 ipRouteInfo OBJECT-TYPE
1274 SYNTAX OBJECT IDENTIFIER
1278 "A reference to MIB definitions specific to the
1279 particular routing protocol which is responsible
1280 for this route, as determined by the value
1281 specified in the route's ipRouteProto value. If
1282 this information is not present, its value should
1283 be set to the OBJECT IDENTIFIER { 0 0 }, which is
1284 a syntatically valid object identifier, and any
1285 conformant implementation of ASN.1 and BER must be
1286 able to generate and recognize this value."
1287 ::= { ipRouteEntry 13 }
1290 -- the IP Address Translation table
1292 -- The IP address translation table contain the IpAddress to
1293 -- `physical' address equivalences. Some interfaces do not
1294 -- use translation tables for determining address
1295 -- equivalences (e.g., DDN-X.25 has an algorithmic method);
1296 -- if all interfaces are of this type, then the Address
1297 -- Translation table is empty, i.e., has zero entries.
1299 ipNetToMediaTable OBJECT-TYPE
1300 SYNTAX SEQUENCE OF IpNetToMediaEntry
1301 ACCESS not-accessible
1304 "The IP Address Translation table used for mapping
1305 from IP addresses to physical addresses."
1308 ipNetToMediaEntry OBJECT-TYPE
1309 SYNTAX IpNetToMediaEntry
1310 ACCESS not-accessible
1313 "Each entry contains one IpAddress to `physical'
1314 address equivalence."
1315 INDEX { ipNetToMediaIfIndex,
1316 ipNetToMediaNetAddress }
1317 ::= { ipNetToMediaTable 1 }
1319 IpNetToMediaEntry ::=
1323 ipNetToMediaPhysAddress
1325 ipNetToMediaNetAddress
1331 ipNetToMediaIfIndex OBJECT-TYPE
1336 "The interface on which this entry's equivalence
1337 is effective. The interface identified by a
1338 particular value of this index is the same
1339 interface as identified by the same value of
1341 ::= { ipNetToMediaEntry 1 }
1343 ipNetToMediaPhysAddress OBJECT-TYPE
1348 "The media-dependent `physical' address."
1349 ::= { ipNetToMediaEntry 2 }
1353 ipNetToMediaNetAddress OBJECT-TYPE
1358 "The IpAddress corresponding to the media-
1359 dependent `physical' address."
1360 ::= { ipNetToMediaEntry 3 }
1362 ipNetToMediaType OBJECT-TYPE
1364 other(1), -- none of the following
1365 invalid(2), -- an invalidated mapping
1372 "The type of mapping.
1374 Setting this object to the value invalid(2) has
1375 the effect of invalidating the corresponding entry
1376 in the ipNetToMediaTable. That is, it effectively
1377 dissasociates the interface identified with said
1378 entry from the mapping identified with said entry.
1379 It is an implementation-specific matter as to
1380 whether the agent removes an invalidated entry
1381 from the table. Accordingly, management stations
1382 must be prepared to receive tabular information
1383 from agents that corresponds to entries not
1384 currently in use. Proper interpretation of such
1385 entries requires examination of the relevant
1386 ipNetToMediaType object."
1387 ::= { ipNetToMediaEntry 4 }
1390 -- additional IP objects
1392 ipRoutingDiscards OBJECT-TYPE
1397 "The number of routing entries which were chosen
1398 to be discarded even though they are valid. One
1399 possible reason for discarding such an entry could
1400 be to free-up buffer space for other routing
1407 -- Implementation of the ICMP group is mandatory for all
1410 icmpInMsgs OBJECT-TYPE
1415 "The total number of ICMP messages which the
1416 entity received. Note that this counter includes
1417 all those counted by icmpInErrors."
1420 icmpInErrors OBJECT-TYPE
1425 "The number of ICMP messages which the entity
1426 received but determined as having ICMP-specific
1427 errors (bad ICMP checksums, bad length, etc.)."
1430 icmpInDestUnreachs OBJECT-TYPE
1435 "The number of ICMP Destination Unreachable
1439 icmpInTimeExcds OBJECT-TYPE
1444 "The number of ICMP Time Exceeded messages
1449 icmpInParmProbs OBJECT-TYPE
1454 "The number of ICMP Parameter Problem messages
1458 icmpInSrcQuenchs OBJECT-TYPE
1463 "The number of ICMP Source Quench messages
1467 icmpInRedirects OBJECT-TYPE
1472 "The number of ICMP Redirect messages received."
1475 icmpInEchos OBJECT-TYPE
1480 "The number of ICMP Echo (request) messages
1484 icmpInEchoReps OBJECT-TYPE
1489 "The number of ICMP Echo Reply messages received."
1492 icmpInTimestamps OBJECT-TYPE
1497 "The number of ICMP Timestamp (request) messages
1501 icmpInTimestampReps OBJECT-TYPE
1506 "The number of ICMP Timestamp Reply messages
1510 icmpInAddrMasks OBJECT-TYPE
1515 "The number of ICMP Address Mask Request messages
1519 icmpInAddrMaskReps OBJECT-TYPE
1524 "The number of ICMP Address Mask Reply messages
1528 icmpOutMsgs OBJECT-TYPE
1533 "The total number of ICMP messages which this
1534 entity attempted to send. Note that this counter
1535 includes all those counted by icmpOutErrors."
1538 icmpOutErrors OBJECT-TYPE
1543 "The number of ICMP messages which this entity did
1544 not send due to problems discovered within ICMP
1545 such as a lack of buffers. This value should not
1546 include errors discovered outside the ICMP layer
1547 such as the inability of IP to route the resultant
1548 datagram. In some implementations there may be no
1549 types of error which contribute to this counter's
1553 icmpOutDestUnreachs OBJECT-TYPE
1558 "The number of ICMP Destination Unreachable
1562 icmpOutTimeExcds OBJECT-TYPE
1567 "The number of ICMP Time Exceeded messages sent."
1570 icmpOutParmProbs OBJECT-TYPE
1575 "The number of ICMP Parameter Problem messages
1579 icmpOutSrcQuenchs OBJECT-TYPE
1584 "The number of ICMP Source Quench messages sent."
1587 icmpOutRedirects OBJECT-TYPE
1592 "The number of ICMP Redirect messages sent. For a
1593 host, this object will always be zero, since hosts
1594 do not send redirects."
1597 icmpOutEchos OBJECT-TYPE
1602 "The number of ICMP Echo (request) messages sent."
1605 icmpOutEchoReps OBJECT-TYPE
1610 "The number of ICMP Echo Reply messages sent."
1613 icmpOutTimestamps OBJECT-TYPE
1618 "The number of ICMP Timestamp (request) messages
1622 icmpOutTimestampReps OBJECT-TYPE
1627 "The number of ICMP Timestamp Reply messages
1631 icmpOutAddrMasks OBJECT-TYPE
1636 "The number of ICMP Address Mask Request messages
1641 icmpOutAddrMaskReps OBJECT-TYPE
1646 "The number of ICMP Address Mask Reply messages
1653 -- Implementation of the TCP group is mandatory for all
1654 -- systems that implement the TCP.
1656 -- Note that instances of object types that represent
1657 -- information about a particular TCP connection are
1658 -- transient; they persist only as long as the connection
1661 tcpRtoAlgorithm OBJECT-TYPE
1663 other(1), -- none of the following
1665 constant(2), -- a constant rto
1666 rsre(3), -- MIL-STD-1778, Appendix B
1667 vanj(4) -- Van Jacobson's algorithm [10]
1672 "The algorithm used to determine the timeout value
1673 used for retransmitting unacknowledged octets."
1676 tcpRtoMin OBJECT-TYPE
1681 "The minimum value permitted by a TCP
1682 implementation for the retransmission timeout,
1683 measured in milliseconds. More refined semantics
1684 for objects of this type depend upon the algorithm
1685 used to determine the retransmission timeout. In
1686 particular, when the timeout algorithm is rsre(3),
1687 an object of this type has the semantics of the
1688 LBOUND quantity described in RFC 793."
1692 tcpRtoMax OBJECT-TYPE
1697 "The maximum value permitted by a TCP
1698 implementation for the retransmission timeout,
1699 measured in milliseconds. More refined semantics
1700 for objects of this type depend upon the algorithm
1701 used to determine the retransmission timeout. In
1702 particular, when the timeout algorithm is rsre(3),
1703 an object of this type has the semantics of the
1704 UBOUND quantity described in RFC 793."
1707 tcpMaxConn OBJECT-TYPE
1712 "The limit on the total number of TCP connections
1713 the entity can support. In entities where the
1714 maximum number of connections is dynamic, this
1715 object should contain the value -1."
1718 tcpActiveOpens OBJECT-TYPE
1723 "The number of times TCP connections have made a
1724 direct transition to the SYN-SENT state from the
1728 tcpPassiveOpens OBJECT-TYPE
1733 "The number of times TCP connections have made a
1734 direct transition to the SYN-RCVD state from the
1740 tcpAttemptFails OBJECT-TYPE
1745 "The number of times TCP connections have made a
1746 direct transition to the CLOSED state from either
1747 the SYN-SENT state or the SYN-RCVD state, plus the
1748 number of times TCP connections have made a direct
1749 transition to the LISTEN state from the SYN-RCVD
1753 tcpEstabResets OBJECT-TYPE
1758 "The number of times TCP connections have made a
1759 direct transition to the CLOSED state from either
1760 the ESTABLISHED state or the CLOSE-WAIT state."
1763 tcpCurrEstab OBJECT-TYPE
1768 "The number of TCP connections for which the
1769 current state is either ESTABLISHED or CLOSE-
1773 tcpInSegs OBJECT-TYPE
1778 "The total number of segments received, including
1779 those received in error. This count includes
1780 segments received on currently established
1784 tcpOutSegs OBJECT-TYPE
1789 "The total number of segments sent, including
1790 those on current connections but excluding those
1791 containing only retransmitted octets."
1794 tcpRetransSegs OBJECT-TYPE
1799 "The total number of segments retransmitted - that
1800 is, the number of TCP segments transmitted
1801 containing one or more previously transmitted
1806 -- the TCP Connection table
1808 -- The TCP connection table contains information about this
1809 -- entity's existing TCP connections.
1811 tcpConnTable OBJECT-TYPE
1812 SYNTAX SEQUENCE OF TcpConnEntry
1813 ACCESS not-accessible
1816 "A table containing TCP connection-specific
1820 tcpConnEntry OBJECT-TYPE
1822 ACCESS not-accessible
1825 "Information about a particular current TCP
1826 connection. An object of this type is transient,
1827 in that it ceases to exist when (or soon after)
1828 the connection makes the transition to the CLOSED
1830 INDEX { tcpConnLocalAddress,
1834 ::= { tcpConnTable 1 }
1851 tcpConnState OBJECT-TYPE
1869 "The state of this TCP connection.
1871 The only value which may be set by a management
1872 station is deleteTCB(12). Accordingly, it is
1873 appropriate for an agent to return a `badValue'
1874 response if a management station attempts to set
1875 this object to any other value.
1877 If a management station sets this object to the
1878 value deleteTCB(12), then this has the effect of
1879 deleting the TCB (as defined in RFC 793) of the
1880 corresponding connection on the managed node,
1881 resulting in immediate termination of the
1884 As an implementation-specific option, a RST
1885 segment may be sent from the managed node to the
1886 other TCP endpoint (note however that RST segments
1887 are not sent reliably)."
1888 ::= { tcpConnEntry 1 }
1890 tcpConnLocalAddress OBJECT-TYPE
1895 "The local IP address for this TCP connection. In
1896 the case of a connection in the listen state which
1897 is willing to accept connections for any IP
1898 interface associated with the node, the value
1900 ::= { tcpConnEntry 2 }
1902 tcpConnLocalPort OBJECT-TYPE
1903 SYNTAX INTEGER (0..65535)
1907 "The local port number for this TCP connection."
1908 ::= { tcpConnEntry 3 }
1910 tcpConnRemAddress OBJECT-TYPE
1915 "The remote IP address for this TCP connection."
1916 ::= { tcpConnEntry 4 }
1918 tcpConnRemPort OBJECT-TYPE
1919 SYNTAX INTEGER (0..65535)
1923 "The remote port number for this TCP connection."
1924 ::= { tcpConnEntry 5 }
1927 -- additional TCP objects
1929 tcpInErrs OBJECT-TYPE
1934 "The total number of segments received in error
1935 (e.g., bad TCP checksums)."
1938 tcpOutRsts OBJECT-TYPE
1943 "The number of TCP segments sent containing the
1950 -- Implementation of the UDP group is mandatory for all
1951 -- systems which implement the UDP.
1953 udpInDatagrams OBJECT-TYPE
1958 "The total number of UDP datagrams delivered to
1962 udpNoPorts OBJECT-TYPE
1967 "The total number of received UDP datagrams for
1968 which there was no application at the destination
1972 udpInErrors OBJECT-TYPE
1977 "The number of received UDP datagrams that could
1978 not be delivered for reasons other than the lack
1979 of an application at the destination port."
1983 udpOutDatagrams OBJECT-TYPE
1988 "The total number of UDP datagrams sent from this
1993 -- the UDP Listener table
1995 -- The UDP listener table contains information about this
1996 -- entity's UDP end-points on which a local application is
1997 -- currently accepting datagrams.
1999 udpTable OBJECT-TYPE
2000 SYNTAX SEQUENCE OF UdpEntry
2001 ACCESS not-accessible
2004 "A table containing UDP listener information."
2007 udpEntry OBJECT-TYPE
2009 ACCESS not-accessible
2012 "Information about a particular current UDP
2014 INDEX { udpLocalAddress, udpLocalPort }
2025 udpLocalAddress OBJECT-TYPE
2030 "The local IP address for this UDP listener. In
2031 the case of a UDP listener which is willing to
2032 accept datagrams for any IP interface associated
2033 with the node, the value 0.0.0.0 is used."
2036 udpLocalPort OBJECT-TYPE
2037 SYNTAX INTEGER (0..65535)
2041 "The local port number for this UDP listener."
2047 -- Implementation of the EGP group is mandatory for all
2048 -- systems which implement the EGP.
2050 egpInMsgs OBJECT-TYPE
2055 "The number of EGP messages received without
2059 egpInErrors OBJECT-TYPE
2064 "The number of EGP messages received that proved
2068 egpOutMsgs OBJECT-TYPE
2073 "The total number of locally generated EGP
2077 egpOutErrors OBJECT-TYPE
2082 "The number of locally generated EGP messages not
2083 sent due to resource limitations within an EGP
2088 -- the EGP Neighbor table
2090 -- The EGP neighbor table contains information about this
2091 -- entity's EGP neighbors.
2093 egpNeighTable OBJECT-TYPE
2094 SYNTAX SEQUENCE OF EgpNeighEntry
2095 ACCESS not-accessible
2098 "The EGP neighbor table."
2101 egpNeighEntry OBJECT-TYPE
2102 SYNTAX EgpNeighEntry
2103 ACCESS not-accessible
2106 "Information about this entity's relationship with
2107 a particular EGP neighbor."
2108 INDEX { egpNeighAddr }
2109 ::= { egpNeighTable 1 }
2135 egpNeighIntervalHello
2137 egpNeighIntervalPoll
2141 egpNeighEventTrigger
2145 egpNeighState OBJECT-TYPE
2156 "The EGP state of the local system with respect to
2157 this entry's EGP neighbor. Each EGP state is
2158 represented by a value that is one greater than
2159 the numerical value associated with said state in
2161 ::= { egpNeighEntry 1 }
2163 egpNeighAddr OBJECT-TYPE
2168 "The IP address of this entry's EGP neighbor."
2169 ::= { egpNeighEntry 2 }
2171 egpNeighAs OBJECT-TYPE
2176 "The autonomous system of this EGP peer. Zero
2177 should be specified if the autonomous system
2178 number of the neighbor is not yet known."
2179 ::= { egpNeighEntry 3 }
2181 egpNeighInMsgs OBJECT-TYPE
2186 "The number of EGP messages received without error
2187 from this EGP peer."
2188 ::= { egpNeighEntry 4 }
2190 egpNeighInErrs OBJECT-TYPE
2195 "The number of EGP messages received from this EGP
2196 peer that proved to be in error (e.g., bad EGP
2198 ::= { egpNeighEntry 5 }
2200 egpNeighOutMsgs OBJECT-TYPE
2205 "The number of locally generated EGP messages to
2207 ::= { egpNeighEntry 6 }
2209 egpNeighOutErrs OBJECT-TYPE
2214 "The number of locally generated EGP messages not
2215 sent to this EGP peer due to resource limitations
2216 within an EGP entity."
2217 ::= { egpNeighEntry 7 }
2219 egpNeighInErrMsgs OBJECT-TYPE
2224 "The number of EGP-defined error messages received
2225 from this EGP peer."
2226 ::= { egpNeighEntry 8 }
2228 egpNeighOutErrMsgs OBJECT-TYPE
2233 "The number of EGP-defined error messages sent to
2235 ::= { egpNeighEntry 9 }
2237 egpNeighStateUps OBJECT-TYPE
2242 "The number of EGP state transitions to the UP
2243 state with this EGP peer."
2244 ::= { egpNeighEntry 10 }
2246 egpNeighStateDowns OBJECT-TYPE
2251 "The number of EGP state transitions from the UP
2252 state to any other state with this EGP peer."
2253 ::= { egpNeighEntry 11 }
2255 egpNeighIntervalHello OBJECT-TYPE
2260 "The interval between EGP Hello command
2261 retransmissions (in hundredths of a second). This
2262 represents the t1 timer as defined in RFC 904."
2263 ::= { egpNeighEntry 12 }
2265 egpNeighIntervalPoll OBJECT-TYPE
2270 "The interval between EGP poll command
2271 retransmissions (in hundredths of a second). This
2272 represents the t3 timer as defined in RFC 904."
2273 ::= { egpNeighEntry 13 }
2275 egpNeighMode OBJECT-TYPE
2276 SYNTAX INTEGER { active(1), passive(2) }
2280 "The polling mode of this EGP entity, either
2282 ::= { egpNeighEntry 14 }
2284 egpNeighEventTrigger OBJECT-TYPE
2285 SYNTAX INTEGER { start(1), stop(2) }
2289 "A control variable used to trigger operator-
2290 initiated Start and Stop events. When read, this
2291 variable always returns the most recent value that
2292 egpNeighEventTrigger was set to. If it has not
2293 been set since the last initialization of the
2294 network management subsystem on the node, it
2295 returns a value of `stop'.
2297 When set, this variable causes a Start or Stop
2298 event on the specified neighbor, as specified on
2299 pages 8-10 of RFC 904. Briefly, a Start event
2300 causes an Idle peer to begin neighbor acquisition
2301 and a non-Idle peer to reinitiate neighbor
2302 acquisition. A stop event causes a non-Idle peer
2303 to return to the Idle state until a Start event
2304 occurs, either via egpNeighEventTrigger or
2306 ::= { egpNeighEntry 15 }
2309 -- additional EGP objects
2316 "The autonomous system number of this EGP entity."
2321 -- the Transmission group
2323 -- Based on the transmission media underlying each interface
2324 -- on a system, the corresponding portion of the Transmission
2325 -- group is mandatory for that system.
2327 -- When Internet-standard definitions for managing
2328 -- transmission media are defined, the transmission group is
2329 -- used to provide a prefix for the names of those objects.
2331 -- Typically, such definitions reside in the experimental
2332 -- portion of the MIB until they are "proven", then as a
2333 -- part of the Internet standardization process, the
2334 -- definitions are accordingly elevated and a new object
2335 -- identifier, under the transmission group is defined. By
2336 -- convention, the name assigned is:
2338 -- type OBJECT IDENTIFIER ::= { transmission number }
2340 -- where "type" is the symbolic value used for the media in
2341 -- the ifType column of the ifTable object, and "number" is
2342 -- the actual integer value corresponding to the symbol.
2347 -- Implementation of the SNMP group is mandatory for all
2348 -- systems which support an SNMP protocol entity. Some of
2349 -- the objects defined below will be zero-valued in those
2350 -- SNMP implementations that are optimized to support only
2351 -- those functions specific to either a management agent or
2352 -- a management station. In particular, it should be
2353 -- observed that the objects below refer to an SNMP entity,
2354 -- and there may be several SNMP entities residing on a
2355 -- managed node (e.g., if the node is hosting acting as
2356 -- a management station).
2358 snmpInPkts OBJECT-TYPE
2363 "The total number of Messages delivered to the
2364 SNMP entity from the transport service."
2367 snmpOutPkts OBJECT-TYPE
2372 "The total number of SNMP Messages which were
2373 passed from the SNMP protocol entity to the
2377 snmpInBadVersions OBJECT-TYPE
2382 "The total number of SNMP Messages which were
2383 delivered to the SNMP protocol entity and were for
2384 an unsupported SNMP version."
2387 snmpInBadCommunityNames OBJECT-TYPE
2392 "The total number of SNMP Messages delivered to
2393 the SNMP protocol entity which used a SNMP
2394 community name not known to said entity."
2397 snmpInBadCommunityUses OBJECT-TYPE
2402 "The total number of SNMP Messages delivered to
2403 the SNMP protocol entity which represented an SNMP
2404 operation which was not allowed by the SNMP
2405 community named in the Message."
2408 snmpInASNParseErrs OBJECT-TYPE
2413 "The total number of ASN.1 or BER errors
2414 encountered by the SNMP protocol entity when
2415 decoding received SNMP Messages."
2419 -- { snmp 7 } is not used
2421 snmpInTooBigs OBJECT-TYPE
2426 "The total number of SNMP PDUs which were
2427 delivered to the SNMP protocol entity and for
2428 which the value of the error-status field is
2432 snmpInNoSuchNames OBJECT-TYPE
2437 "The total number of SNMP PDUs which were
2438 delivered to the SNMP protocol entity and for
2439 which the value of the error-status field is
2443 snmpInBadValues OBJECT-TYPE
2448 "The total number of SNMP PDUs which were
2449 delivered to the SNMP protocol entity and for
2450 which the value of the error-status field is
2454 snmpInReadOnlys OBJECT-TYPE
2459 "The total number valid SNMP PDUs which were
2460 delivered to the SNMP protocol entity and for
2461 which the value of the error-status field is
2462 `readOnly'. It should be noted that it is a
2463 protocol error to generate an SNMP PDU which
2464 contains the value `readOnly' in the error-status
2465 field, as such this object is provided as a means
2466 of detecting incorrect implementations of the
2470 snmpInGenErrs OBJECT-TYPE
2475 "The total number of SNMP PDUs which were
2476 delivered to the SNMP protocol entity and for
2477 which the value of the error-status field is
2481 snmpInTotalReqVars OBJECT-TYPE
2486 "The total number of MIB objects which have been
2487 retrieved successfully by the SNMP protocol entity
2488 as the result of receiving valid SNMP Get-Request
2492 snmpInTotalSetVars OBJECT-TYPE
2497 "The total number of MIB objects which have been
2498 altered successfully by the SNMP protocol entity
2499 as the result of receiving valid SNMP Set-Request
2503 snmpInGetRequests OBJECT-TYPE
2508 "The total number of SNMP Get-Request PDUs which
2509 have been accepted and processed by the SNMP
2513 snmpInGetNexts OBJECT-TYPE
2518 "The total number of SNMP Get-Next PDUs which have
2519 been accepted and processed by the SNMP protocol
2523 snmpInSetRequests OBJECT-TYPE
2528 "The total number of SNMP Set-Request PDUs which
2529 have been accepted and processed by the SNMP
2533 snmpInGetResponses OBJECT-TYPE
2538 "The total number of SNMP Get-Response PDUs which
2539 have been accepted and processed by the SNMP
2543 snmpInTraps OBJECT-TYPE
2548 "The total number of SNMP Trap PDUs which have
2549 been accepted and processed by the SNMP protocol
2553 snmpOutTooBigs OBJECT-TYPE
2558 "The total number of SNMP PDUs which were
2559 generated by the SNMP protocol entity and for
2560 which the value of the error-status field is
2565 snmpOutNoSuchNames OBJECT-TYPE
2570 "The total number of SNMP PDUs which were
2571 generated by the SNMP protocol entity and for
2572 which the value of the error-status is
2576 snmpOutBadValues OBJECT-TYPE
2581 "The total number of SNMP PDUs which were
2582 generated by the SNMP protocol entity and for
2583 which the value of the error-status field is
2587 -- { snmp 23 } is not used
2589 snmpOutGenErrs OBJECT-TYPE
2594 "The total number of SNMP PDUs which were
2595 generated by the SNMP protocol entity and for
2596 which the value of the error-status field is
2600 snmpOutGetRequests OBJECT-TYPE
2605 "The total number of SNMP Get-Request PDUs which
2606 have been generated by the SNMP protocol entity."
2609 snmpOutGetNexts OBJECT-TYPE
2614 "The total number of SNMP Get-Next PDUs which have
2615 been generated by the SNMP protocol entity."
2618 snmpOutSetRequests OBJECT-TYPE
2623 "The total number of SNMP Set-Request PDUs which
2624 have been generated by the SNMP protocol entity."
2627 snmpOutGetResponses OBJECT-TYPE
2632 "The total number of SNMP Get-Response PDUs which
2633 have been generated by the SNMP protocol entity."
2636 snmpOutTraps OBJECT-TYPE
2641 "The total number of SNMP Trap PDUs which have
2642 been generated by the SNMP protocol entity."
2645 snmpEnableAuthenTraps OBJECT-TYPE
2646 SYNTAX INTEGER { enabled(1), disabled(2) }
2650 "Indicates whether the SNMP agent process is
2651 permitted to generate authentication-failure
2652 traps. The value of this object overrides any
2653 configuration information; as such, it provides a
2654 means whereby all authentication-failure traps may
2657 Note that it is strongly recommended that this
2658 object be stored in non-volatile memory so that it
2659 remains constant between re-initializations of the
2660 network management system."
projects / apple / security.git / blob