1
RFC1213-MIB DEFINITIONS ::= BEGIN
4
mgmt, NetworkAddress, IpAddress, Counter, Gauge,
10
-- This MIB module uses the extended OBJECT-TYPE macro as
13
-- MIB-II (same prefix as MIB-I)
15
mib-2 OBJECT IDENTIFIER ::= { mgmt 1 }
17
-- textual conventions
21
-- This data type is used to model textual information taken
22
-- from the NVT ASCII character set. By convention, objects
23
-- with this syntax are declared as having
30
-- This data type is used to model media addresses. For many
31
-- types of media, this will be in a binary representation.
32
-- For example, an ethernet address would be represented as
33
-- a string of 6 octets.
37
system OBJECT IDENTIFIER ::= { mib-2 1 }
39
interfaces OBJECT IDENTIFIER ::= { mib-2 2 }
41
at OBJECT IDENTIFIER ::= { mib-2 3 }
43
ip OBJECT IDENTIFIER ::= { mib-2 4 }
45
icmp OBJECT IDENTIFIER ::= { mib-2 5 }
47
tcp OBJECT IDENTIFIER ::= { mib-2 6 }
49
udp OBJECT IDENTIFIER ::= { mib-2 7 }
51
egp OBJECT IDENTIFIER ::= { mib-2 8 }
53
-- historical (some say hysterical)
54
-- cmot OBJECT IDENTIFIER ::= { mib-2 9 }
56
transmission OBJECT IDENTIFIER ::= { mib-2 10 }
58
snmp OBJECT IDENTIFIER ::= { mib-2 11 }
62
-- Implementation of the System group is mandatory for all
63
-- systems. If an agent is not configured to have a value
64
-- for any of these variables, a string of length 0 is
68
SYNTAX DisplayString (SIZE (0..255))
72
"A textual description of the entity. This value
73
should include the full name and version
74
identification of the system's hardware type,
75
software operating-system, and networking
76
software. It is mandatory that this only contain
77
printable ASCII characters."
80
sysObjectID OBJECT-TYPE
81
SYNTAX OBJECT IDENTIFIER
85
"The vendor's authoritative identification of the
86
network management subsystem contained in the
87
entity. This value is allocated within the SMI
88
enterprises subtree (1.3.6.1.4.1) and provides an
89
easy and unambiguous means for determining `what
90
kind of box' is being managed. For example, if
91
vendor `Flintstones, Inc.' was assigned the
92
subtree 1.3.6.1.4.1.4242, it could assign the
93
identifier 1.3.6.1.4.1.4242.1.1 to its `Fred
102
"The time (in hundredths of a second) since the
103
network management portion of the system was last
107
sysContact OBJECT-TYPE
108
SYNTAX DisplayString (SIZE (0..255))
112
"The textual identification of the contact person
113
for this managed node, together with information
114
on how to contact this person."
118
SYNTAX DisplayString (SIZE (0..255))
122
"An administratively-assigned name for this
123
managed node. By convention, this is the node's
124
fully-qualified domain name."
127
sysLocation OBJECT-TYPE
128
SYNTAX DisplayString (SIZE (0..255))
132
"The physical location of this node (e.g.,
133
`telephone closet, 3rd floor')."
136
sysServices OBJECT-TYPE
137
SYNTAX INTEGER (0..127)
141
"A value which indicates the set of services that
142
this entity primarily offers.
144
The value is a sum. This sum initially takes the
145
value zero, Then, for each layer, L, in the range
146
1 through 7, that this node performs transactions
147
for, 2 raised to (L - 1) is added to the sum. For
148
example, a node which performs primarily routing
149
functions would have a value of 4 (2^(3-1)). In
150
contrast, a node which is a host offering
151
application services would have a value of 72
152
(2^(4-1) + 2^(7-1)). Note that in the context of
153
the Internet suite of protocols, values should be
154
calculated accordingly:
157
1 physical (e.g., repeaters)
158
2 datalink/subnetwork (e.g., bridges)
159
3 internet (e.g., IP gateways)
160
4 end-to-end (e.g., IP hosts)
161
7 applications (e.g., mail relays)
163
For systems including OSI protocols, layers 5 and
164
6 may also be counted."
167
-- the Interfaces group
169
-- Implementation of the Interfaces group is mandatory for
177
"The number of network interfaces (regardless of
178
their current state) present on this system."
181
-- the Interfaces table
183
-- The Interfaces table contains information on the entity's
184
-- interfaces. Each interface is thought of as being
185
-- attached to a `subnetwork'. Note that this term should
186
-- not be confused with `subnet' which refers to an
187
-- addressing partitioning scheme used in the Internet suite
191
SYNTAX SEQUENCE OF IfEntry
192
ACCESS not-accessible
195
"A list of interface entries. The number of
196
entries is given by the value of ifNumber."
201
ACCESS not-accessible
204
"An interface entry containing objects at the
205
subnetwork layer and below for a particular
263
"A unique value for each interface. Its value
264
ranges between 1 and the value of ifNumber. The
265
value for each interface must remain constant at
266
least from one re-initialization of the entity's
267
network management system to the next re-
272
SYNTAX DisplayString (SIZE (0..255))
276
"A textual string containing information about the
277
interface. This string should include the name of
278
the manufacturer, the product name and the version
279
of the hardware interface."
284
other(1), -- none of the following
291
iso88024-tokenBus(8),
292
iso88025-tokenRing(9),
302
e1(19), -- european equiv. of T-1
304
primaryISDN(21), -- proprietary serial
305
propPointToPointSerial(22),
307
softwareLoopback(24),
308
eon(25), -- CLNP over IP [11]
310
nsip(27), -- XNS over IP
311
slip(28), -- generic SLIP
312
ultra(29), -- ULTRA technologies
320
"The type of interface, distinguished according to
321
the physical/link protocol(s) immediately `below'
322
the network layer in the protocol stack."
330
"The size of the largest datagram which can be
331
sent/received on the interface, specified in
332
octets. For interfaces that are used for
333
transmitting network datagrams, this is the size
334
of the largest network datagram that can be sent
343
"An estimate of the interface's current bandwidth
344
in bits per second. For interfaces which do not
345
vary in bandwidth or for those where no accurate
346
estimation can be made, this object should contain
347
the nominal bandwidth."
350
ifPhysAddress OBJECT-TYPE
355
"The interface's address at the protocol layer
356
immediately `below' the network layer in the
357
protocol stack. For interfaces which do not have
359
such an address (e.g., a serial line), this object
360
should contain an octet string of zero length."
363
ifAdminStatus OBJECT-TYPE
365
up(1), -- ready to pass packets
367
testing(3) -- in some test mode
372
"The desired state of the interface. The
373
testing(3) state indicates that no operational
374
packets can be passed."
377
ifOperStatus OBJECT-TYPE
379
up(1), -- ready to pass packets
381
testing(3) -- in some test mode
386
"The current operational state of the interface.
387
The testing(3) state indicates that no operational
388
packets can be passed."
391
ifLastChange OBJECT-TYPE
396
"The value of sysUpTime at the time the interface
397
entered its current operational state. If the
398
current state was entered prior to the last re-
399
initialization of the local network management
400
subsystem, then this object contains a zero
404
ifInOctets OBJECT-TYPE
409
"The total number of octets received on the
410
interface, including framing characters."
413
ifInUcastPkts OBJECT-TYPE
418
"The number of subnetwork-unicast packets
419
delivered to a higher-layer protocol."
422
ifInNUcastPkts OBJECT-TYPE
427
"The number of non-unicast (i.e., subnetwork-
428
broadcast or subnetwork-multicast) packets
429
delivered to a higher-layer protocol."
432
ifInDiscards OBJECT-TYPE
437
"The number of inbound packets which were chosen
438
to be discarded even though no errors had been
439
detected to prevent their being deliverable to a
440
higher-layer protocol. One possible reason for
441
discarding such a packet could be to free up
445
ifInErrors OBJECT-TYPE
450
"The number of inbound packets that contained
451
errors preventing them from being deliverable to a
452
higher-layer protocol."
455
ifInUnknownProtos OBJECT-TYPE
460
"The number of packets received via the interface
461
which were discarded because of an unknown or
462
unsupported protocol."
465
ifOutOctets OBJECT-TYPE
470
"The total number of octets transmitted out of the
471
interface, including framing characters."
474
ifOutUcastPkts OBJECT-TYPE
479
"The total number of packets that higher-level
480
protocols requested be transmitted to a
481
subnetwork-unicast address, including those that
482
were discarded or not sent."
485
ifOutNUcastPkts OBJECT-TYPE
490
"The total number of packets that higher-level
491
protocols requested be transmitted to a non-
492
unicast (i.e., a subnetwork-broadcast or
493
subnetwork-multicast) address, including those
494
that were discarded or not sent."
497
ifOutDiscards OBJECT-TYPE
502
"The number of outbound packets which were chosen
504
to be discarded even though no errors had been
505
detected to prevent their being transmitted. One
506
possible reason for discarding such a packet could
507
be to free up buffer space."
510
ifOutErrors OBJECT-TYPE
515
"The number of outbound packets that could not be
516
transmitted because of errors."
519
ifOutQLen OBJECT-TYPE
524
"The length of the output packet queue (in
528
ifSpecific OBJECT-TYPE
529
SYNTAX OBJECT IDENTIFIER
533
"A reference to MIB definitions specific to the
534
particular media being used to realize the
535
interface. For example, if the interface is
536
realized by an ethernet, then the value of this
537
object refers to a document defining objects
538
specific to ethernet. If this information is not
539
present, its value should be set to the OBJECT
540
IDENTIFIER { 0 0 }, which is a syntatically valid
541
object identifier, and any conformant
542
implementation of ASN.1 and BER must be able to
543
generate and recognize this value."
546
-- the Address Translation group
548
-- Implementation of the Address Translation group is
549
-- mandatory for all systems. Note however that this group
550
-- is deprecated by MIB-II. That is, it is being included
552
-- solely for compatibility with MIB-I nodes, and will most
553
-- likely be excluded from MIB-III nodes. From MIB-II and
554
-- onwards, each network protocol group contains its own
555
-- address translation tables.
557
-- The Address Translation group contains one table which is
558
-- the union across all interfaces of the translation tables
559
-- for converting a NetworkAddress (e.g., an IP address) into
560
-- a subnetwork-specific address. For lack of a better term,
561
-- this document refers to such a subnetwork-specific address
562
-- as a `physical' address.
564
-- Examples of such translation tables are: for broadcast
565
-- media where ARP is in use, the translation table is
566
-- equivalent to the ARP cache; or, on an X.25 network where
567
-- non-algorithmic translation to X.121 addresses is
568
-- required, the translation table contains the
569
-- NetworkAddress to X.121 address equivalences.
572
SYNTAX SEQUENCE OF AtEntry
573
ACCESS not-accessible
576
"The Address Translation tables contain the
577
NetworkAddress to `physical' address equivalences.
578
Some interfaces do not use translation tables for
579
determining address equivalences (e.g., DDN-X.25
580
has an algorithmic method); if all interfaces are
581
of this type, then the Address Translation table
582
is empty, i.e., has zero entries."
587
ACCESS not-accessible
590
"Each entry contains one NetworkAddress to
591
`physical' address equivalence."
606
atIfIndex OBJECT-TYPE
611
"The interface on which this entry's equivalence
612
is effective. The interface identified by a
613
particular value of this index is the same
614
interface as identified by the same value of
618
atPhysAddress OBJECT-TYPE
623
"The media-dependent `physical' address.
625
Setting this object to a null string (one of zero
626
length) has the effect of invaliding the
627
corresponding entry in the atTable object. That
628
is, it effectively dissasociates the interface
629
identified with said entry from the mapping
630
identified with said entry. It is an
631
implementation-specific matter as to whether the
632
agent removes an invalidated entry from the table.
633
Accordingly, management stations must be prepared
634
to receive tabular information from agents that
635
corresponds to entries not currently in use.
636
Proper interpretation of such entries requires
637
examination of the relevant atPhysAddress object."
640
atNetAddress OBJECT-TYPE
641
SYNTAX NetworkAddress
645
"The NetworkAddress (e.g., the IP address)
646
corresponding to the media-dependent `physical'
652
-- Implementation of the IP group is mandatory for all
655
ipForwarding OBJECT-TYPE
657
forwarding(1), -- acting as a gateway
658
not-forwarding(2) -- NOT acting as a gateway
663
"The indication of whether this entity is acting
664
as an IP gateway in respect to the forwarding of
665
datagrams received by, but not addressed to, this
666
entity. IP gateways forward datagrams. IP hosts
667
do not (except those source-routed via the host).
669
Note that for some managed nodes, this object may
670
take on only a subset of the values possible.
671
Accordingly, it is appropriate for an agent to
672
return a `badValue' response if a management
673
station attempts to change this object to an
674
inappropriate value."
677
ipDefaultTTL OBJECT-TYPE
682
"The default value inserted into the Time-To-Live
683
field of the IP header of datagrams originated at
684
this entity, whenever a TTL value is not supplied
685
by the transport layer protocol."
688
ipInReceives OBJECT-TYPE
693
"The total number of input datagrams received from
694
interfaces, including those received in error."
697
ipInHdrErrors OBJECT-TYPE
702
"The number of input datagrams discarded due to
703
errors in their IP headers, including bad
704
checksums, version number mismatch, other format
705
errors, time-to-live exceeded, errors discovered
706
in processing their IP options, etc."
709
ipInAddrErrors OBJECT-TYPE
714
"The number of input datagrams discarded because
715
the IP address in their IP header's destination
716
field was not a valid address to be received at
717
this entity. This count includes invalid
718
addresses (e.g., 0.0.0.0) and addresses of
719
unsupported Classes (e.g., Class E). For entities
720
which are not IP Gateways and therefore do not
721
forward datagrams, this counter includes datagrams
722
discarded because the destination address was not
726
ipForwDatagrams OBJECT-TYPE
731
"The number of input datagrams for which this
732
entity was not their final IP destination, as a
733
result of which an attempt was made to find a
734
route to forward them to that final destination.
735
In entities which do not act as IP Gateways, this
736
counter will include only those packets which were
737
Source-Routed via this entity, and the Source-
738
Route option processing was successful."
741
ipInUnknownProtos OBJECT-TYPE
746
"The number of locally-addressed datagrams
747
received successfully but discarded because of an
748
unknown or unsupported protocol."
751
ipInDiscards OBJECT-TYPE
756
"The number of input IP datagrams for which no
757
problems were encountered to prevent their
758
continued processing, but which were discarded
759
(e.g., for lack of buffer space). Note that this
760
counter does not include any datagrams discarded
761
while awaiting re-assembly."
764
ipInDelivers OBJECT-TYPE
769
"The total number of input datagrams successfully
770
delivered to IP user-protocols (including ICMP)."
773
ipOutRequests OBJECT-TYPE
778
"The total number of IP datagrams which local IP
779
user-protocols (including ICMP) supplied to IP in
780
requests for transmission. Note that this counter
781
does not include any datagrams counted in
785
ipOutDiscards OBJECT-TYPE
790
"The number of output IP datagrams for which no
792
problem was encountered to prevent their
793
transmission to their destination, but which were
794
discarded (e.g., for lack of buffer space). Note
795
that this counter would include datagrams counted
796
in ipForwDatagrams if any such packets met this
797
(discretionary) discard criterion."
800
ipOutNoRoutes OBJECT-TYPE
805
"The number of IP datagrams discarded because no
806
route could be found to transmit them to their
807
destination. Note that this counter includes any
808
packets counted in ipForwDatagrams which meet this
809
`no-route' criterion. Note that this includes any
810
datagarms which a host cannot route because all of
811
its default gateways are down."
814
ipReasmTimeout OBJECT-TYPE
819
"The maximum number of seconds which received
820
fragments are held while they are awaiting
821
reassembly at this entity."
824
ipReasmReqds OBJECT-TYPE
829
"The number of IP fragments received which needed
830
to be reassembled at this entity."
833
ipReasmOKs OBJECT-TYPE
838
"The number of IP datagrams successfully re-
842
ipReasmFails OBJECT-TYPE
847
"The number of failures detected by the IP re-
848
assembly algorithm (for whatever reason: timed
849
out, errors, etc). Note that this is not
850
necessarily a count of discarded IP fragments
851
since some algorithms (notably the algorithm in
852
RFC 815) can lose track of the number of fragments
853
by combining them as they are received."
856
ipFragOKs OBJECT-TYPE
861
"The number of IP datagrams that have been
862
successfully fragmented at this entity."
865
ipFragFails OBJECT-TYPE
870
"The number of IP datagrams that have been
871
discarded because they needed to be fragmented at
872
this entity but could not be, e.g., because their
873
Don't Fragment flag was set."
876
ipFragCreates OBJECT-TYPE
881
"The number of IP datagram fragments that have
882
been generated as a result of fragmentation at
886
-- the IP address table
888
-- The IP address table contains this entity's IP addressing
891
ipAddrTable OBJECT-TYPE
892
SYNTAX SEQUENCE OF IpAddrEntry
893
ACCESS not-accessible
896
"The table of addressing information relevant to
897
this entity's IP addresses."
900
ipAddrEntry OBJECT-TYPE
902
ACCESS not-accessible
905
"The addressing information for one of this
906
entity's IP addresses."
907
INDEX { ipAdEntAddr }
908
::= { ipAddrTable 1 }
924
ipAdEntAddr OBJECT-TYPE
929
"The IP address to which this entry's addressing
930
information pertains."
931
::= { ipAddrEntry 1 }
933
ipAdEntIfIndex OBJECT-TYPE
938
"The index value which uniquely identifies the
939
interface to which this entry is applicable. The
940
interface identified by a particular value of this
941
index is the same interface as identified by the
942
same value of ifIndex."
943
::= { ipAddrEntry 2 }
945
ipAdEntNetMask OBJECT-TYPE
950
"The subnet mask associated with the IP address of
951
this entry. The value of the mask is an IP
952
address with all the network bits set to 1 and all
953
the hosts bits set to 0."
954
::= { ipAddrEntry 3 }
956
ipAdEntBcastAddr OBJECT-TYPE
961
"The value of the least-significant bit in the IP
962
broadcast address used for sending datagrams on
963
the (logical) interface associated with the IP
964
address of this entry. For example, when the
965
Internet standard all-ones broadcast address is
966
used, the value will be 1. This value applies to
967
both the subnet and network broadcasts addresses
968
used by the entity on this (logical) interface."
969
::= { ipAddrEntry 4 }
971
ipAdEntReasmMaxSize OBJECT-TYPE
972
SYNTAX INTEGER (0..65535)
976
"The size of the largest IP datagram which this
977
entity can re-assemble from incoming IP fragmented
978
datagrams received on this interface."
979
::= { ipAddrEntry 5 }
981
-- the IP routing table
983
-- The IP routing table contains an entry for each route
984
-- presently known to this entity.
986
ipRouteTable OBJECT-TYPE
987
SYNTAX SEQUENCE OF IpRouteEntry
988
ACCESS not-accessible
991
"This entity's IP Routing table."
994
ipRouteEntry OBJECT-TYPE
996
ACCESS not-accessible
999
"A route to a particular destination."
1000
INDEX { ipRouteDest }
1001
::= { ipRouteTable 1 }
1033
ipRouteDest OBJECT-TYPE
1038
"The destination IP address of this route. An
1039
entry with a value of 0.0.0.0 is considered a
1040
default route. Multiple routes to a single
1041
destination can appear in the table, but access to
1042
such multiple entries is dependent on the table-
1043
access mechanisms defined by the network
1044
management protocol in use."
1045
::= { ipRouteEntry 1 }
1047
ipRouteIfIndex OBJECT-TYPE
1052
"The index value which uniquely identifies the
1053
local interface through which the next hop of this
1054
route should be reached. The interface identified
1055
by a particular value of this index is the same
1056
interface as identified by the same value of
1058
::= { ipRouteEntry 2 }
1060
ipRouteMetric1 OBJECT-TYPE
1065
"The primary routing metric for this route. The
1066
semantics of this metric are determined by the
1067
routing-protocol specified in the route's
1068
ipRouteProto value. If this metric is not used,
1069
its value should be set to -1."
1070
::= { ipRouteEntry 3 }
1072
ipRouteMetric2 OBJECT-TYPE
1077
"An alternate routing metric for this route. The
1078
semantics of this metric are determined by the
1079
routing-protocol specified in the route's
1080
ipRouteProto value. If this metric is not used,
1081
its value should be set to -1."
1082
::= { ipRouteEntry 4 }
1084
ipRouteMetric3 OBJECT-TYPE
1089
"An alternate routing metric for this route. The
1090
semantics of this metric are determined by the
1091
routing-protocol specified in the route's
1092
ipRouteProto value. If this metric is not used,
1093
its value should be set to -1."
1094
::= { ipRouteEntry 5 }
1096
ipRouteMetric4 OBJECT-TYPE
1101
"An alternate routing metric for this route. The
1102
semantics of this metric are determined by the
1103
routing-protocol specified in the route's
1104
ipRouteProto value. If this metric is not used,
1105
its value should be set to -1."
1106
::= { ipRouteEntry 6 }
1108
ipRouteNextHop OBJECT-TYPE
1113
"The IP address of the next hop of this route.
1114
(In the case of a route bound to an interface
1115
which is realized via a broadcast media, the value
1116
of this field is the agent's IP address on that
1118
::= { ipRouteEntry 7 }
1120
ipRouteType OBJECT-TYPE
1122
other(1), -- none of the following
1124
invalid(2), -- an invalidated route
1126
-- route to directly
1127
direct(3), -- connected (sub-)network
1129
-- route to a non-local
1130
indirect(4) -- host/network/sub-network
1135
"The type of route. Note that the values
1136
direct(3) and indirect(4) refer to the notion of
1137
direct and indirect routing in the IP
1140
Setting this object to the value invalid(2) has
1141
the effect of invalidating the corresponding entry
1142
in the ipRouteTable object. That is, it
1143
effectively dissasociates the destination
1144
identified with said entry from the route
1145
identified with said entry. It is an
1146
implementation-specific matter as to whether the
1147
agent removes an invalidated entry from the table.
1148
Accordingly, management stations must be prepared
1149
to receive tabular information from agents that
1150
corresponds to entries not currently in use.
1151
Proper interpretation of such entries requires
1152
examination of the relevant ipRouteType object."
1153
::= { ipRouteEntry 8 }
1155
ipRouteProto OBJECT-TYPE
1157
other(1), -- none of the following
1159
-- non-protocol information,
1160
-- e.g., manually configured
1161
local(2), -- entries
1163
-- set via a network
1164
netmgmt(3), -- management protocol
1166
-- obtained via ICMP,
1167
icmp(4), -- e.g., Redirect
1169
-- the remaining values are
1170
-- all gateway routing
1186
"The routing mechanism via which this route was
1187
learned. Inclusion of values for gateway routing
1188
protocols is not intended to imply that hosts
1189
should support those protocols."
1190
::= { ipRouteEntry 9 }
1192
ipRouteAge OBJECT-TYPE
1197
"The number of seconds since this route was last
1198
updated or otherwise determined to be correct.
1199
Note that no semantics of `too old' can be implied
1200
except through knowledge of the routing protocol
1201
by which the route was learned."
1202
::= { ipRouteEntry 10 }
1204
ipRouteMask OBJECT-TYPE
1209
"Indicate the mask to be logical-ANDed with the
1210
destination address before being compared to the
1211
value in the ipRouteDest field. For those systems
1212
that do not support arbitrary subnet masks, an
1213
agent constructs the value of the ipRouteMask by
1214
determining whether the value of the correspondent
1215
ipRouteDest field belong to a class-A, B, or C
1216
network, and then using one of:
1221
255.255.255.0 class-C
1223
If the value of the ipRouteDest is 0.0.0.0 (a
1224
default route), then the mask value is also
1225
0.0.0.0. It should be noted that all IP routing
1226
subsystems implicitly use this mechanism."
1227
::= { ipRouteEntry 11 }
1229
ipRouteMetric5 OBJECT-TYPE
1234
"An alternate routing metric for this route. The
1235
semantics of this metric are determined by the
1236
routing-protocol specified in the route's
1237
ipRouteProto value. If this metric is not used,
1238
its value should be set to -1."
1239
::= { ipRouteEntry 12 }
1241
ipRouteInfo OBJECT-TYPE
1242
SYNTAX OBJECT IDENTIFIER
1246
"A reference to MIB definitions specific to the
1247
particular routing protocol which is responsible
1248
for this route, as determined by the value
1249
specified in the route's ipRouteProto value. If
1250
this information is not present, its value should
1251
be set to the OBJECT IDENTIFIER { 0 0 }, which is
1252
a syntatically valid object identifier, and any
1253
conformant implementation of ASN.1 and BER must be
1254
able to generate and recognize this value."
1255
::= { ipRouteEntry 13 }
1257
-- the IP Address Translation table
1259
-- The IP address translation table contain the IpAddress to
1260
-- `physical' address equivalences. Some interfaces do not
1261
-- use translation tables for determining address
1262
-- equivalences (e.g., DDN-X.25 has an algorithmic method);
1263
-- if all interfaces are of this type, then the Address
1264
-- Translation table is empty, i.e., has zero entries.
1266
ipNetToMediaTable OBJECT-TYPE
1267
SYNTAX SEQUENCE OF IpNetToMediaEntry
1268
ACCESS not-accessible
1271
"The IP Address Translation table used for mapping
1272
from IP addresses to physical addresses."
1275
ipNetToMediaEntry OBJECT-TYPE
1276
SYNTAX IpNetToMediaEntry
1277
ACCESS not-accessible
1280
"Each entry contains one IpAddress to `physical'
1281
address equivalence."
1282
INDEX { ipNetToMediaIfIndex,
1283
ipNetToMediaNetAddress }
1284
::= { ipNetToMediaTable 1 }
1286
IpNetToMediaEntry ::=
1290
ipNetToMediaPhysAddress
1292
ipNetToMediaNetAddress
1298
ipNetToMediaIfIndex OBJECT-TYPE
1303
"The interface on which this entry's equivalence
1304
is effective. The interface identified by a
1305
particular value of this index is the same
1306
interface as identified by the same value of
1308
::= { ipNetToMediaEntry 1 }
1310
ipNetToMediaPhysAddress OBJECT-TYPE
1315
"The media-dependent `physical' address."
1316
::= { ipNetToMediaEntry 2 }
1318
ipNetToMediaNetAddress OBJECT-TYPE
1323
"The IpAddress corresponding to the media-
1324
dependent `physical' address."
1325
::= { ipNetToMediaEntry 3 }
1327
ipNetToMediaType OBJECT-TYPE
1329
other(1), -- none of the following
1330
invalid(2), -- an invalidated mapping
1337
"The type of mapping.
1339
Setting this object to the value invalid(2) has
1340
the effect of invalidating the corresponding entry
1341
in the ipNetToMediaTable. That is, it effectively
1342
dissasociates the interface identified with said
1343
entry from the mapping identified with said entry.
1344
It is an implementation-specific matter as to
1345
whether the agent removes an invalidated entry
1346
from the table. Accordingly, management stations
1347
must be prepared to receive tabular information
1348
from agents that corresponds to entries not
1349
currently in use. Proper interpretation of such
1350
entries requires examination of the relevant
1351
ipNetToMediaType object."
1352
::= { ipNetToMediaEntry 4 }
1354
-- additional IP objects
1356
ipRoutingDiscards OBJECT-TYPE
1361
"The number of routing entries which were chosen
1362
to be discarded even though they are valid. One
1363
possible reason for discarding such an entry could
1364
be to free-up buffer space for other routing
1371
-- Implementation of the ICMP group is mandatory for all
1374
icmpInMsgs OBJECT-TYPE
1379
"The total number of ICMP messages which the
1380
entity received. Note that this counter includes
1381
all those counted by icmpInErrors."
1384
icmpInErrors OBJECT-TYPE
1389
"The number of ICMP messages which the entity
1390
received but determined as having ICMP-specific
1391
errors (bad ICMP checksums, bad length, etc.)."
1394
icmpInDestUnreachs OBJECT-TYPE
1399
"The number of ICMP Destination Unreachable
1403
icmpInTimeExcds OBJECT-TYPE
1408
"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
1509
such as a lack of buffers. This value should not
1510
include errors discovered outside the ICMP layer
1511
such as the inability of IP to route the resultant
1512
datagram. In some implementations there may be no
1513
types of error which contribute to this counter's
1517
icmpOutDestUnreachs OBJECT-TYPE
1522
"The number of ICMP Destination Unreachable
1526
icmpOutTimeExcds OBJECT-TYPE
1531
"The number of ICMP Time Exceeded messages sent."
1534
icmpOutParmProbs OBJECT-TYPE
1539
"The number of ICMP Parameter Problem messages
1543
icmpOutSrcQuenchs OBJECT-TYPE
1548
"The number of ICMP Source Quench messages sent."
1551
icmpOutRedirects OBJECT-TYPE
1556
"The number of ICMP Redirect messages sent. For a
1558
host, this object will always be zero, since hosts
1559
do not send redirects."
1562
icmpOutEchos OBJECT-TYPE
1567
"The number of ICMP Echo (request) messages sent."
1570
icmpOutEchoReps OBJECT-TYPE
1575
"The number of ICMP Echo Reply messages sent."
1578
icmpOutTimestamps OBJECT-TYPE
1583
"The number of ICMP Timestamp (request) messages
1587
icmpOutTimestampReps OBJECT-TYPE
1592
"The number of ICMP Timestamp Reply messages
1596
icmpOutAddrMasks OBJECT-TYPE
1601
"The number of ICMP Address Mask Request messages
1605
icmpOutAddrMaskReps OBJECT-TYPE
1610
"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."
1654
tcpRtoMax OBJECT-TYPE
1659
"The maximum value permitted by a TCP
1660
implementation for the retransmission timeout,
1661
measured in milliseconds. More refined semantics
1662
for objects of this type depend upon the algorithm
1663
used to determine the retransmission timeout. In
1664
particular, when the timeout algorithm is rsre(3),
1665
an object of this type has the semantics of the
1666
UBOUND quantity described in RFC 793."
1669
tcpMaxConn OBJECT-TYPE
1674
"The limit on the total number of TCP connections
1675
the entity can support. In entities where the
1676
maximum number of connections is dynamic, this
1677
object should contain the value -1."
1680
tcpActiveOpens OBJECT-TYPE
1685
"The number of times TCP connections have made a
1686
direct transition to the SYN-SENT state from the
1690
tcpPassiveOpens OBJECT-TYPE
1695
"The number of times TCP connections have made a
1696
direct transition to the SYN-RCVD state from the
1700
tcpAttemptFails OBJECT-TYPE
1705
"The number of times TCP connections have made a
1706
direct transition to the CLOSED state from either
1707
the SYN-SENT state or the SYN-RCVD state, plus the
1708
number of times TCP connections have made a direct
1709
transition to the LISTEN state from the SYN-RCVD
1713
tcpEstabResets OBJECT-TYPE
1718
"The number of times TCP connections have made a
1719
direct transition to the CLOSED state from either
1720
the ESTABLISHED state or the CLOSE-WAIT state."
1723
tcpCurrEstab OBJECT-TYPE
1728
"The number of TCP connections for which the
1729
current state is either ESTABLISHED or CLOSE-
1733
tcpInSegs OBJECT-TYPE
1738
"The total number of segments received, including
1739
those received in error. This count includes
1740
segments received on currently established
1744
tcpOutSegs OBJECT-TYPE
1749
"The total number of segments sent, including
1750
those on current connections but excluding those
1751
containing only retransmitted octets."
1754
tcpRetransSegs OBJECT-TYPE
1759
"The total number of segments retransmitted - that
1760
is, the number of TCP segments transmitted
1761
containing one or more previously transmitted
1765
-- the TCP Connection table
1767
-- The TCP connection table contains information about this
1768
-- entity's existing TCP connections.
1770
tcpConnTable OBJECT-TYPE
1771
SYNTAX SEQUENCE OF TcpConnEntry
1772
ACCESS not-accessible
1775
"A table containing TCP connection-specific
1779
tcpConnEntry OBJECT-TYPE
1781
ACCESS not-accessible
1784
"Information about a particular current TCP
1785
connection. An object of this type is transient,
1786
in that it ceases to exist when (or soon after)
1787
the connection makes the transition to the CLOSED
1789
INDEX { tcpConnLocalAddress,
1793
::= { tcpConnTable 1 }
1809
tcpConnState OBJECT-TYPE
1827
"The state of this TCP connection.
1829
The only value which may be set by a management
1830
station is deleteTCB(12). Accordingly, it is
1831
appropriate for an agent to return a `badValue'
1832
response if a management station attempts to set
1833
this object to any other value.
1835
If a management station sets this object to the
1836
value deleteTCB(12), then this has the effect of
1837
deleting the TCB (as defined in RFC 793) of the
1838
corresponding connection on the managed node,
1839
resulting in immediate termination of the
1842
As an implementation-specific option, a RST
1844
segment may be sent from the managed node to the
1845
other TCP endpoint (note however that RST segments
1846
are not sent reliably)."
1847
::= { tcpConnEntry 1 }
1849
tcpConnLocalAddress OBJECT-TYPE
1854
"The local IP address for this TCP connection. In
1855
the case of a connection in the listen state which
1856
is willing to accept connections for any IP
1857
interface associated with the node, the value
1859
::= { tcpConnEntry 2 }
1861
tcpConnLocalPort OBJECT-TYPE
1862
SYNTAX INTEGER (0..65535)
1866
"The local port number for this TCP connection."
1867
::= { tcpConnEntry 3 }
1869
tcpConnRemAddress OBJECT-TYPE
1874
"The remote IP address for this TCP connection."
1875
::= { tcpConnEntry 4 }
1877
tcpConnRemPort OBJECT-TYPE
1878
SYNTAX INTEGER (0..65535)
1882
"The remote port number for this TCP connection."
1883
::= { tcpConnEntry 5 }
1885
-- additional TCP objects
1887
tcpInErrs OBJECT-TYPE
1892
"The total number of segments received in error
1893
(e.g., bad TCP checksums)."
1896
tcpOutRsts OBJECT-TYPE
1901
"The number of TCP segments sent containing the
1907
-- Implementation of the UDP group is mandatory for all
1908
-- systems which implement the UDP.
1910
udpInDatagrams OBJECT-TYPE
1915
"The total number of UDP datagrams delivered to
1919
udpNoPorts OBJECT-TYPE
1924
"The total number of received UDP datagrams for
1925
which there was no application at the destination
1929
udpInErrors OBJECT-TYPE
1934
"The number of received UDP datagrams that could
1935
not be delivered for reasons other than the lack
1936
of an application at the destination port."
1939
udpOutDatagrams OBJECT-TYPE
1944
"The total number of UDP datagrams sent from this
1948
-- the UDP Listener table
1950
-- The UDP listener table contains information about this
1951
-- entity's UDP end-points on which a local application is
1952
-- currently accepting datagrams.
1954
udpTable OBJECT-TYPE
1955
SYNTAX SEQUENCE OF UdpEntry
1956
ACCESS not-accessible
1959
"A table containing UDP listener information."
1962
udpEntry OBJECT-TYPE
1964
ACCESS not-accessible
1967
"Information about a particular current UDP
1969
INDEX { udpLocalAddress, udpLocalPort }
1980
udpLocalAddress OBJECT-TYPE
1985
"The local IP address for this UDP listener. In
1987
the case of a UDP listener which is willing to
1988
accept datagrams for any IP interface associated
1989
with the node, the value 0.0.0.0 is used."
1992
udpLocalPort OBJECT-TYPE
1993
SYNTAX INTEGER (0..65535)
1997
"The local port number for this UDP listener."
2002
-- Implementation of the EGP group is mandatory for all
2003
-- systems which implement the EGP.
2005
egpInMsgs OBJECT-TYPE
2010
"The number of EGP messages received without
2014
egpInErrors OBJECT-TYPE
2019
"The number of EGP messages received that proved
2023
egpOutMsgs OBJECT-TYPE
2028
"The total number of locally generated EGP
2032
egpOutErrors OBJECT-TYPE
2037
"The number of locally generated EGP messages not
2038
sent due to resource limitations within an EGP
2042
-- the EGP Neighbor table
2044
-- The EGP neighbor table contains information about this
2045
-- entity's EGP neighbors.
2047
egpNeighTable OBJECT-TYPE
2048
SYNTAX SEQUENCE OF EgpNeighEntry
2049
ACCESS not-accessible
2052
"The EGP neighbor table."
2055
egpNeighEntry OBJECT-TYPE
2056
SYNTAX EgpNeighEntry
2057
ACCESS not-accessible
2060
"Information about this entity's relationship with
2061
a particular EGP neighbor."
2062
INDEX { egpNeighAddr }
2063
::= { egpNeighTable 1 }
2089
egpNeighIntervalHello
2091
egpNeighIntervalPoll
2095
egpNeighEventTrigger
2099
egpNeighState OBJECT-TYPE
2110
"The EGP state of the local system with respect to
2111
this entry's EGP neighbor. Each EGP state is
2112
represented by a value that is one greater than
2113
the numerical value associated with said state in
2115
::= { egpNeighEntry 1 }
2117
egpNeighAddr OBJECT-TYPE
2122
"The IP address of this entry's EGP neighbor."
2123
::= { egpNeighEntry 2 }
2125
egpNeighAs OBJECT-TYPE
2130
"The autonomous system of this EGP peer. Zero
2131
should be specified if the autonomous system
2132
number of the neighbor is not yet known."
2133
::= { egpNeighEntry 3 }
2135
egpNeighInMsgs OBJECT-TYPE
2140
"The number of EGP messages received without error
2141
from this EGP peer."
2142
::= { egpNeighEntry 4 }
2144
egpNeighInErrs OBJECT-TYPE
2149
"The number of EGP messages received from this EGP
2150
peer that proved to be in error (e.g., bad EGP
2152
::= { egpNeighEntry 5 }
2154
egpNeighOutMsgs OBJECT-TYPE
2159
"The number of locally generated EGP messages to
2161
::= { egpNeighEntry 6 }
2163
egpNeighOutErrs OBJECT-TYPE
2168
"The number of locally generated EGP messages not
2169
sent to this EGP peer due to resource limitations
2170
within an EGP entity."
2171
::= { egpNeighEntry 7 }
2173
egpNeighInErrMsgs OBJECT-TYPE
2178
"The number of EGP-defined error messages received
2179
from this EGP peer."
2180
::= { egpNeighEntry 8 }
2182
egpNeighOutErrMsgs OBJECT-TYPE
2187
"The number of EGP-defined error messages sent to
2189
::= { egpNeighEntry 9 }
2191
egpNeighStateUps OBJECT-TYPE
2196
"The number of EGP state transitions to the UP
2197
state with this EGP peer."
2198
::= { egpNeighEntry 10 }
2200
egpNeighStateDowns OBJECT-TYPE
2205
"The number of EGP state transitions from the UP
2206
state to any other state with this EGP peer."
2207
::= { egpNeighEntry 11 }
2209
egpNeighIntervalHello OBJECT-TYPE
2214
"The interval between EGP Hello command
2215
retransmissions (in hundredths of a second). This
2216
represents the t1 timer as defined in RFC 904."
2217
::= { egpNeighEntry 12 }
2219
egpNeighIntervalPoll OBJECT-TYPE
2224
"The interval between EGP poll command
2226
retransmissions (in hundredths of a second). This
2227
represents the t3 timer as defined in RFC 904."
2228
::= { egpNeighEntry 13 }
2230
egpNeighMode OBJECT-TYPE
2231
SYNTAX INTEGER { active(1), passive(2) }
2235
"The polling mode of this EGP entity, either
2237
::= { egpNeighEntry 14 }
2239
egpNeighEventTrigger OBJECT-TYPE
2240
SYNTAX INTEGER { start(1), stop(2) }
2244
"A control variable used to trigger operator-
2245
initiated Start and Stop events. When read, this
2246
variable always returns the most recent value that
2247
egpNeighEventTrigger was set to. If it has not
2248
been set since the last initialization of the
2249
network management subsystem on the node, it
2250
returns a value of `stop'.
2252
When set, this variable causes a Start or Stop
2253
event on the specified neighbor, as specified on
2254
pages 8-10 of RFC 904. Briefly, a Start event
2255
causes an Idle peer to begin neighbor acquisition
2256
and a non-Idle peer to reinitiate neighbor
2257
acquisition. A stop event causes a non-Idle peer
2258
to return to the Idle state until a Start event
2259
occurs, either via egpNeighEventTrigger or
2261
::= { egpNeighEntry 15 }
2263
-- additional EGP objects
2270
"The autonomous system number of this EGP entity."
2273
-- the Transmission group
2275
-- Based on the transmission media underlying each interface
2276
-- on a system, the corresponding portion of the Transmission
2277
-- group is mandatory for that system.
2279
-- When Internet-standard definitions for managing
2280
-- transmission media are defined, the transmission group is
2281
-- used to provide a prefix for the names of those objects.
2283
-- Typically, such definitions reside in the experimental
2284
-- portion of the MIB until they are "proven", then as a
2285
-- part of the Internet standardization process, the
2286
-- definitions are accordingly elevated and a new object
2287
-- identifier, under the transmission group is defined. By
2288
-- convention, the name assigned is:
2290
-- type OBJECT IDENTIFIER ::= { transmission number }
2292
-- where "type" is the symbolic value used for the media in
2293
-- the ifType column of the ifTable object, and "number" is
2294
-- the actual integer value corresponding to the symbol.
2298
-- Implementation of the SNMP group is mandatory for all
2299
-- systems which support an SNMP protocol entity. Some of
2300
-- the objects defined below will be zero-valued in those
2301
-- SNMP implementations that are optimized to support only
2302
-- those functions specific to either a management agent or
2303
-- a management station. In particular, it should be
2304
-- observed that the objects below refer to an SNMP entity,
2305
-- and there may be several SNMP entities residing on a
2306
-- managed node (e.g., if the node is hosting acting as
2307
-- a management station).
2309
snmpInPkts OBJECT-TYPE
2314
"The total number of Messages delivered to the
2315
SNMP entity from the transport service."
2318
snmpOutPkts OBJECT-TYPE
2323
"The total number of SNMP Messages which were
2324
passed from the SNMP protocol entity to the
2328
snmpInBadVersions OBJECT-TYPE
2333
"The total number of SNMP Messages which were
2334
delivered to the SNMP protocol entity and were for
2335
an unsupported SNMP version."
2338
snmpInBadCommunityNames OBJECT-TYPE
2343
"The total number of SNMP Messages delivered to
2344
the SNMP protocol entity which used a SNMP
2345
community name not known to said entity."
2348
snmpInBadCommunityUses OBJECT-TYPE
2353
"The total number of SNMP Messages delivered to
2354
the SNMP protocol entity which represented an SNMP
2355
operation which was not allowed by the SNMP
2356
community named in the Message."
2359
snmpInASNParseErrs OBJECT-TYPE
2364
"The total number of ASN.1 or BER errors
2365
encountered by the SNMP protocol entity when
2366
decoding received SNMP Messages."
2369
-- { snmp 7 } is not used
2371
snmpInTooBigs OBJECT-TYPE
2376
"The total number of SNMP PDUs which were
2377
delivered to the SNMP protocol entity and for
2378
which the value of the error-status field is
2382
snmpInNoSuchNames OBJECT-TYPE
2387
"The total number of SNMP PDUs which were
2388
delivered to the SNMP protocol entity and for
2389
which the value of the error-status field is
2393
snmpInBadValues OBJECT-TYPE
2398
"The total number of SNMP PDUs which were
2399
delivered to the SNMP protocol entity and for
2400
which the value of the error-status field is
2404
snmpInReadOnlys OBJECT-TYPE
2409
"The total number valid SNMP PDUs which were
2410
delivered to the SNMP protocol entity and for
2411
which the value of the error-status field is
2412
`readOnly'. It should be noted that it is a
2413
protocol error to generate an SNMP PDU which
2414
contains the value `readOnly' in the error-status
2415
field, as such this object is provided as a means
2416
of detecting incorrect implementations of the
2421
snmpInGenErrs 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
snmpInTotalReqVars OBJECT-TYPE
2437
"The total number of MIB objects which have been
2438
retrieved successfully by the SNMP protocol entity
2439
as the result of receiving valid SNMP Get-Request
2443
snmpInTotalSetVars OBJECT-TYPE
2448
"The total number of MIB objects which have been
2449
altered successfully by the SNMP protocol entity
2450
as the result of receiving valid SNMP Set-Request
2454
snmpInGetRequests OBJECT-TYPE
2459
"The total number of SNMP Get-Request PDUs which
2460
have been accepted and processed by the SNMP
2464
snmpInGetNexts OBJECT-TYPE
2469
"The total number of SNMP Get-Next PDUs which have
2470
been accepted and processed by the SNMP protocol
2474
snmpInSetRequests OBJECT-TYPE
2479
"The total number of SNMP Set-Request PDUs which
2480
have been accepted and processed by the SNMP
2484
snmpInGetResponses OBJECT-TYPE
2489
"The total number of SNMP Get-Response PDUs which
2490
have been accepted and processed by the SNMP
2494
snmpInTraps OBJECT-TYPE
2499
"The total number of SNMP Trap PDUs which have
2500
been accepted and processed by the SNMP protocol
2504
snmpOutTooBigs OBJECT-TYPE
2509
"The total number of SNMP PDUs which were
2510
generated by the SNMP protocol entity and for
2511
which the value of the error-status field is
2515
snmpOutNoSuchNames OBJECT-TYPE
2520
"The total number of SNMP PDUs which were
2521
generated by the SNMP protocol entity and for
2522
which the value of the error-status is
2526
snmpOutBadValues OBJECT-TYPE
2531
"The total number of SNMP PDUs which were
2532
generated by the SNMP protocol entity and for
2533
which the value of the error-status field is
2537
-- { snmp 23 } is not used
2539
snmpOutGenErrs OBJECT-TYPE
2544
"The total number of SNMP PDUs which were
2545
generated by the SNMP protocol entity and for
2546
which the value of the error-status field is
2550
snmpOutGetRequests OBJECT-TYPE
2555
"The total number of SNMP Get-Request PDUs which
2556
have been generated by the SNMP protocol entity."
2559
snmpOutGetNexts OBJECT-TYPE
2564
"The total number of SNMP Get-Next PDUs which have
2565
been generated by the SNMP protocol entity."
2568
snmpOutSetRequests OBJECT-TYPE
2573
"The total number of SNMP Set-Request PDUs which
2574
have been generated by the SNMP protocol entity."
2577
snmpOutGetResponses OBJECT-TYPE
2582
"The total number of SNMP Get-Response PDUs which
2583
have been generated by the SNMP protocol entity."
2586
snmpOutTraps OBJECT-TYPE
2591
"The total number of SNMP Trap PDUs which have
2592
been generated by the SNMP protocol entity."
2595
snmpEnableAuthenTraps OBJECT-TYPE
2596
SYNTAX INTEGER { enabled(1), disabled(2) }
2600
"Indicates whether the SNMP agent process is
2601
permitted to generate authentication-failure
2602
traps. The value of this object overrides any
2603
configuration information; as such, it provides a
2604
means whereby all authentication-failure traps may
2607
Note that it is strongly recommended that this
2608
object be stored in non-volatile memory so that it
2609
remains constant between re-initializations of the
2610
network management system."
added
removed
install-files/bin/php/php5.2.5/extras/mibs/RFC1213-MIB.txt
