1
RFC1213-MIB DEFINITIONS ::= BEGIN
4
mgmt, NetworkAddress, IpAddress, Counter, Gauge,
12
mib-2 OBJECT IDENTIFIER ::= { mgmt 1 }
24
system OBJECT IDENTIFIER ::= { mib-2 1 }
26
interfaces OBJECT IDENTIFIER ::= { mib-2 2 }
28
at OBJECT IDENTIFIER ::= { mib-2 3 }
30
ip OBJECT IDENTIFIER ::= { mib-2 4 }
32
icmp OBJECT IDENTIFIER ::= { mib-2 5 }
34
tcp OBJECT IDENTIFIER ::= { mib-2 6 }
36
udp OBJECT IDENTIFIER ::= { mib-2 7 }
38
egp OBJECT IDENTIFIER ::= { mib-2 8 }
41
transmission OBJECT IDENTIFIER ::= { mib-2 10 }
43
snmp OBJECT IDENTIFIER ::= { mib-2 11 }
48
SYNTAX DisplayString (SIZE (0..255))
52
"A textual description of the entity. This value
53
should include the full name and version
54
identification of the system's hardware type,
55
software operating-system, and networking
56
software. It is mandatory that this only contain
57
printable ASCII characters."
60
sysObjectID OBJECT-TYPE
61
SYNTAX OBJECT IDENTIFIER
65
"The vendor's authoritative identification of the
66
network management subsystem contained in the
67
entity. This value is allocated within the SMI
68
enterprises subtree (1.3.6.1.4.1) and provides an
69
easy and unambiguous means for determining `what
70
kind of box' is being managed. For example, if
71
vendor `Flintstones, Inc.' was assigned the
72
subtree 1.3.6.1.4.1.4242, it could assign the
73
identifier 1.3.6.1.4.1.4242.1.1 to its `Fred
82
"The time (in hundredths of a second) since the
83
network management portion of the system was last
87
sysContact OBJECT-TYPE
88
SYNTAX DisplayString (SIZE (0..255))
92
"The textual identification of the contact person
93
for this managed node, together with information
94
on how to contact this person."
98
SYNTAX DisplayString (SIZE (0..255))
102
"An administratively-assigned name for this
103
managed node. By convention, this is the node's
104
fully-qualified domain name."
107
sysLocation OBJECT-TYPE
108
SYNTAX DisplayString (SIZE (0..255))
112
"The physical location of this node (e.g.,
113
`telephone closet, 3rd floor')."
116
sysServices OBJECT-TYPE
117
SYNTAX INTEGER (0..127)
121
"A value which indicates the set of services that
122
this entity primarily offers.
124
The value is a sum. This sum initially takes the
125
value zero, Then, for each layer, L, in the range
126
1 through 7, that this node performs transactions
127
for, 2 raised to (L - 1) is added to the sum. For
128
example, a node which performs primarily routing
129
functions would have a value of 4 (2^(3-1)). In
130
contrast, a node which is a host offering
131
application services would have a value of 72
132
(2^(4-1) + 2^(7-1)). Note that in the context of
133
the Internet suite of protocols, values should be
134
calculated accordingly:
137
1 physical (e.g., repeaters)
138
2 datalink/subnetwork (e.g., bridges)
139
3 internet (e.g., IP gateways)
140
4 end-to-end (e.g., IP hosts)
141
7 applications (e.g., mail relays)
143
For systems including OSI protocols, layers 5 and
144
6 may also be counted."
154
"The number of network interfaces (regardless of
155
their current state) present on this system."
161
SYNTAX SEQUENCE OF IfEntry
162
ACCESS not-accessible
165
"A list of interface entries. The number of
166
entries is given by the value of ifNumber."
171
ACCESS not-accessible
174
"An interface entry containing objects at the
175
subnetwork layer and below for a particular
233
"A unique value for each interface. Its value
234
ranges between 1 and the value of ifNumber. The
235
value for each interface must remain constant at
236
least from one re-initialization of the entity's
237
network management system to the next re-
242
SYNTAX DisplayString (SIZE (0..255))
246
"A textual string containing information about the
247
interface. This string should include the name of
248
the manufacturer, the product name and the version
249
of the hardware interface."
254
other(1), -- none of the following
261
iso88024-tokenBus(8),
262
iso88025-tokenRing(9),
272
e1(19), -- european equiv. of T-1
274
primaryISDN(21), -- proprietary serial
275
propPointToPointSerial(22),
277
softwareLoopback(24),
278
eon(25), -- CLNP over IP [11]
280
nsip(27), -- XNS over IP
281
slip(28), -- generic SLIP
282
ultra(29), -- ULTRA technologies
290
"The type of interface, distinguished according to
291
the physical/link protocol(s) immediately `below'
292
the network layer in the protocol stack."
300
"The size of the largest datagram which can be
301
sent/received on the interface, specified in
302
octets. For interfaces that are used for
303
transmitting network datagrams, this is the size
304
of the largest network datagram that can be sent
313
"An estimate of the interface's current bandwidth
314
in bits per second. For interfaces which do not
315
vary in bandwidth or for those where no accurate
316
estimation can be made, this object should contain
317
the nominal bandwidth."
320
ifPhysAddress OBJECT-TYPE
325
"The interface's address at the protocol layer
326
immediately `below' the network layer in the
327
protocol stack. For interfaces which do not have
329
such an address (e.g., a serial line), this object
330
should contain an octet string of zero length."
333
ifAdminStatus OBJECT-TYPE
335
up(1), -- ready to pass packets
337
testing(3) -- in some test mode
342
"The desired state of the interface. The
343
testing(3) state indicates that no operational
344
packets can be passed."
347
ifOperStatus OBJECT-TYPE
349
up(1), -- ready to pass packets
351
testing(3) -- in some test mode
356
"The current operational state of the interface.
357
The testing(3) state indicates that no operational
358
packets can be passed."
361
ifLastChange OBJECT-TYPE
366
"The value of sysUpTime at the time the interface
367
entered its current operational state. If the
368
current state was entered prior to the last re-
369
initialization of the local network management
370
subsystem, then this object contains a zero
374
ifInOctets OBJECT-TYPE
379
"The total number of octets received on the
380
interface, including framing characters."
383
ifInUcastPkts OBJECT-TYPE
388
"The number of subnetwork-unicast packets
389
delivered to a higher-layer protocol."
392
ifInNUcastPkts OBJECT-TYPE
397
"The number of non-unicast (i.e., subnetwork-
398
broadcast or subnetwork-multicast) packets
399
delivered to a higher-layer protocol."
402
ifInDiscards OBJECT-TYPE
407
"The number of inbound packets which were chosen
408
to be discarded even though no errors had been
409
detected to prevent their being deliverable to a
410
higher-layer protocol. One possible reason for
411
discarding such a packet could be to free up
415
ifInErrors OBJECT-TYPE
420
"The number of inbound packets that contained
421
errors preventing them from being deliverable to a
422
higher-layer protocol."
425
ifInUnknownProtos OBJECT-TYPE
430
"The number of packets received via the interface
431
which were discarded because of an unknown or
432
unsupported protocol."
435
ifOutOctets OBJECT-TYPE
440
"The total number of octets transmitted out of the
441
interface, including framing characters."
444
ifOutUcastPkts OBJECT-TYPE
449
"The total number of packets that higher-level
450
protocols requested be transmitted to a
451
subnetwork-unicast address, including those that
452
were discarded or not sent."
455
ifOutNUcastPkts OBJECT-TYPE
460
"The total number of packets that higher-level
461
protocols requested be transmitted to a non-
462
unicast (i.e., a subnetwork-broadcast or
463
subnetwork-multicast) address, including those
464
that were discarded or not sent."
467
ifOutDiscards OBJECT-TYPE
472
"The number of outbound packets which were chosen
474
to be discarded even though no errors had been
475
detected to prevent their being transmitted. One
476
possible reason for discarding such a packet could
477
be to free up buffer space."
480
ifOutErrors OBJECT-TYPE
485
"The number of outbound packets that could not be
486
transmitted because of errors."
489
ifOutQLen OBJECT-TYPE
494
"The length of the output packet queue (in
498
ifSpecific OBJECT-TYPE
499
SYNTAX OBJECT IDENTIFIER
503
"A reference to MIB definitions specific to the
504
particular media being used to realize the
505
interface. For example, if the interface is
506
realized by an ethernet, then the value of this
507
object refers to a document defining objects
508
specific to ethernet. If this information is not
509
present, its value should be set to the OBJECT
510
IDENTIFIER { 0 0 }, which is a syntatically valid
511
object identifier, and any conformant
512
implementation of ASN.1 and BER must be able to
513
generate and recognize this value."
522
SYNTAX SEQUENCE OF AtEntry
523
ACCESS not-accessible
526
"The Address Translation tables contain the
527
NetworkAddress to `physical' address equivalences.
528
Some interfaces do not use translation tables for
529
determining address equivalences (e.g., DDN-X.25
530
has an algorithmic method); if all interfaces are
531
of this type, then the Address Translation table
532
is empty, i.e., has zero entries."
537
ACCESS not-accessible
540
"Each entry contains one NetworkAddress to
541
`physical' address equivalence."
556
atIfIndex OBJECT-TYPE
561
"The interface on which this entry's equivalence
562
is effective. The interface identified by a
563
particular value of this index is the same
564
interface as identified by the same value of
568
atPhysAddress OBJECT-TYPE
573
"The media-dependent `physical' address.
575
Setting this object to a null string (one of zero
576
length) has the effect of invaliding the
577
corresponding entry in the atTable object. That
578
is, it effectively dissasociates the interface
579
identified with said entry from the mapping
580
identified with said entry. It is an
581
implementation-specific matter as to whether the
582
agent removes an invalidated entry from the table.
583
Accordingly, management stations must be prepared
584
to receive tabular information from agents that
585
corresponds to entries not currently in use.
586
Proper interpretation of such entries requires
587
examination of the relevant atPhysAddress object."
590
atNetAddress OBJECT-TYPE
591
SYNTAX NetworkAddress
595
"The NetworkAddress (e.g., the IP address)
596
corresponding to the media-dependent `physical'
602
ipForwarding OBJECT-TYPE
604
forwarding(1), -- acting as a gateway
605
not-forwarding(2) -- NOT acting as a gateway
610
"The indication of whether this entity is acting
611
as an IP gateway in respect to the forwarding of
612
datagrams received by, but not addressed to, this
613
entity. IP gateways forward datagrams. IP hosts
614
do not (except those source-routed via the host).
616
Note that for some managed nodes, this object may
617
take on only a subset of the values possible.
618
Accordingly, it is appropriate for an agent to
619
return a `badValue' response if a management
620
station attempts to change this object to an
621
inappropriate value."
624
ipDefaultTTL OBJECT-TYPE
629
"The default value inserted into the Time-To-Live
630
field of the IP header of datagrams originated at
631
this entity, whenever a TTL value is not supplied
632
by the transport layer protocol."
635
ipInReceives OBJECT-TYPE
640
"The total number of input datagrams received from
641
interfaces, including those received in error."
644
ipInHdrErrors OBJECT-TYPE
649
"The number of input datagrams discarded due to
650
errors in their IP headers, including bad
651
checksums, version number mismatch, other format
652
errors, time-to-live exceeded, errors discovered
653
in processing their IP options, etc."
656
ipInAddrErrors OBJECT-TYPE
661
"The number of input datagrams discarded because
662
the IP address in their IP header's destination
663
field was not a valid address to be received at
664
this entity. This count includes invalid
665
addresses (e.g., 0.0.0.0) and addresses of
666
unsupported Classes (e.g., Class E). For entities
667
which are not IP Gateways and therefore do not
668
forward datagrams, this counter includes datagrams
669
discarded because the destination address was not
673
ipForwDatagrams OBJECT-TYPE
678
"The number of input datagrams for which this
679
entity was not their final IP destination, as a
680
result of which an attempt was made to find a
681
route to forward them to that final destination.
682
In entities which do not act as IP Gateways, this
683
counter will include only those packets which were
684
Source-Routed via this entity, and the Source-
685
Route option processing was successful."
688
ipInUnknownProtos OBJECT-TYPE
693
"The number of locally-addressed datagrams
694
received successfully but discarded because of an
695
unknown or unsupported protocol."
698
ipInDiscards OBJECT-TYPE
703
"The number of input IP datagrams for which no
704
problems were encountered to prevent their
705
continued processing, but which were discarded
706
(e.g., for lack of buffer space). Note that this
707
counter does not include any datagrams discarded
708
while awaiting re-assembly."
711
ipInDelivers OBJECT-TYPE
716
"The total number of input datagrams successfully
717
delivered to IP user-protocols (including ICMP)."
720
ipOutRequests OBJECT-TYPE
725
"The total number of IP datagrams which local IP
726
user-protocols (including ICMP) supplied to IP in
727
requests for transmission. Note that this counter
728
does not include any datagrams counted in
732
ipOutDiscards OBJECT-TYPE
737
"The number of output IP datagrams for which no
739
problem was encountered to prevent their
740
transmission to their destination, but which were
741
discarded (e.g., for lack of buffer space). Note
742
that this counter would include datagrams counted
743
in ipForwDatagrams if any such packets met this
744
(discretionary) discard criterion."
747
ipOutNoRoutes OBJECT-TYPE
752
"The number of IP datagrams discarded because no
753
route could be found to transmit them to their
754
destination. Note that this counter includes any
755
packets counted in ipForwDatagrams which meet this
756
`no-route' criterion. Note that this includes any
757
datagarms which a host cannot route because all of
758
its default gateways are down."
761
ipReasmTimeout OBJECT-TYPE
766
"The maximum number of seconds which received
767
fragments are held while they are awaiting
768
reassembly at this entity."
771
ipReasmReqds OBJECT-TYPE
776
"The number of IP fragments received which needed
777
to be reassembled at this entity."
780
ipReasmOKs OBJECT-TYPE
785
"The number of IP datagrams successfully re-
789
ipReasmFails OBJECT-TYPE
794
"The number of failures detected by the IP re-
795
assembly algorithm (for whatever reason: timed
796
out, errors, etc). Note that this is not
797
necessarily a count of discarded IP fragments
798
since some algorithms (notably the algorithm in
799
RFC 815) can lose track of the number of fragments
800
by combining them as they are received."
803
ipFragOKs OBJECT-TYPE
808
"The number of IP datagrams that have been
809
successfully fragmented at this entity."
812
ipFragFails OBJECT-TYPE
817
"The number of IP datagrams that have been
818
discarded because they needed to be fragmented at
819
this entity but could not be, e.g., because their
820
Don't Fragment flag was set."
823
ipFragCreates OBJECT-TYPE
828
"The number of IP datagram fragments that have
829
been generated as a result of fragmentation at
835
ipAddrTable OBJECT-TYPE
836
SYNTAX SEQUENCE OF IpAddrEntry
837
ACCESS not-accessible
840
"The table of addressing information relevant to
841
this entity's IP addresses."
844
ipAddrEntry OBJECT-TYPE
846
ACCESS not-accessible
849
"The addressing information for one of this
850
entity's IP addresses."
851
INDEX { ipAdEntAddr }
852
::= { ipAddrTable 1 }
868
ipAdEntAddr OBJECT-TYPE
873
"The IP address to which this entry's addressing
874
information pertains."
875
::= { ipAddrEntry 1 }
877
ipAdEntIfIndex OBJECT-TYPE
882
"The index value which uniquely identifies the
883
interface to which this entry is applicable. The
884
interface identified by a particular value of this
885
index is the same interface as identified by the
886
same value of ifIndex."
887
::= { ipAddrEntry 2 }
889
ipAdEntNetMask OBJECT-TYPE
894
"The subnet mask associated with the IP address of
895
this entry. The value of the mask is an IP
896
address with all the network bits set to 1 and all
897
the hosts bits set to 0."
898
::= { ipAddrEntry 3 }
900
ipAdEntBcastAddr OBJECT-TYPE
905
"The value of the least-significant bit in the IP
906
broadcast address used for sending datagrams on
907
the (logical) interface associated with the IP
908
address of this entry. For example, when the
909
Internet standard all-ones broadcast address is
910
used, the value will be 1. This value applies to
911
both the subnet and network broadcasts addresses
912
used by the entity on this (logical) interface."
913
::= { ipAddrEntry 4 }
915
ipAdEntReasmMaxSize OBJECT-TYPE
916
SYNTAX INTEGER (0..65535)
920
"The size of the largest IP datagram which this
921
entity can re-assemble from incoming IP fragmented
922
datagrams received on this interface."
923
::= { ipAddrEntry 5 }
927
ipRouteTable OBJECT-TYPE
928
SYNTAX SEQUENCE OF IpRouteEntry
929
ACCESS not-accessible
932
"This entity's IP Routing table."
935
ipRouteEntry OBJECT-TYPE
937
ACCESS not-accessible
940
"A route to a particular destination."
941
INDEX { ipRouteDest }
942
::= { ipRouteTable 1 }
974
ipRouteDest OBJECT-TYPE
979
"The destination IP address of this route. An
980
entry with a value of 0.0.0.0 is considered a
981
default route. Multiple routes to a single
982
destination can appear in the table, but access to
983
such multiple entries is dependent on the table-
984
access mechanisms defined by the network
985
management protocol in use."
986
::= { ipRouteEntry 1 }
988
ipRouteIfIndex OBJECT-TYPE
993
"The index value which uniquely identifies the
994
local interface through which the next hop of this
995
route should be reached. The interface identified
996
by a particular value of this index is the same
997
interface as identified by the same value of
999
::= { ipRouteEntry 2 }
1001
ipRouteMetric1 OBJECT-TYPE
1006
"The primary routing metric for this route. The
1007
semantics of this metric are determined by the
1008
routing-protocol specified in the route's
1009
ipRouteProto value. If this metric is not used,
1010
its value should be set to -1."
1011
::= { ipRouteEntry 3 }
1013
ipRouteMetric2 OBJECT-TYPE
1018
"An alternate routing metric for this route. The
1019
semantics of this metric are determined by the
1020
routing-protocol specified in the route's
1021
ipRouteProto value. If this metric is not used,
1022
its value should be set to -1."
1023
::= { ipRouteEntry 4 }
1025
ipRouteMetric3 OBJECT-TYPE
1030
"An alternate routing metric for this route. The
1031
semantics of this metric are determined by the
1032
routing-protocol specified in the route's
1033
ipRouteProto value. If this metric is not used,
1034
its value should be set to -1."
1035
::= { ipRouteEntry 5 }
1037
ipRouteMetric4 OBJECT-TYPE
1042
"An alternate routing metric for this route. The
1043
semantics of this metric are determined by the
1044
routing-protocol specified in the route's
1045
ipRouteProto value. If this metric is not used,
1046
its value should be set to -1."
1047
::= { ipRouteEntry 6 }
1049
ipRouteNextHop OBJECT-TYPE
1054
"The IP address of the next hop of this route.
1055
(In the case of a route bound to an interface
1056
which is realized via a broadcast media, the value
1057
of this field is the agent's IP address on that
1059
::= { ipRouteEntry 7 }
1061
ipRouteType OBJECT-TYPE
1063
other(1), -- none of the following
1065
invalid(2), -- an invalidated route
1067
-- route to directly
1068
direct(3), -- connected (sub-)network
1070
-- route to a non-local
1071
indirect(4) -- host/network/sub-network
1076
"The type of route. Note that the values
1077
direct(3) and indirect(4) refer to the notion of
1078
direct and indirect routing in the IP
1081
Setting this object to the value invalid(2) has
1082
the effect of invalidating the corresponding entry
1083
in the ipRouteTable object. That is, it
1084
effectively dissasociates the destination
1085
identified with said entry from the route
1086
identified with said entry. It is an
1087
implementation-specific matter as to whether the
1088
agent removes an invalidated entry from the table.
1089
Accordingly, management stations must be prepared
1090
to receive tabular information from agents that
1091
corresponds to entries not currently in use.
1092
Proper interpretation of such entries requires
1093
examination of the relevant ipRouteType object."
1094
::= { ipRouteEntry 8 }
1096
ipRouteProto OBJECT-TYPE
1098
other(1), -- none of the following
1100
-- non-protocol information,
1101
-- e.g., manually configured
1102
local(2), -- entries
1104
-- set via a network
1105
netmgmt(3), -- management protocol
1107
-- obtained via ICMP,
1108
icmp(4), -- e.g., Redirect
1110
-- the remaining values are
1111
-- all gateway routing
1127
"The routing mechanism via which this route was
1128
learned. Inclusion of values for gateway routing
1129
protocols is not intended to imply that hosts
1130
should support those protocols."
1131
::= { ipRouteEntry 9 }
1133
ipRouteAge OBJECT-TYPE
1138
"The number of seconds since this route was last
1139
updated or otherwise determined to be correct.
1140
Note that no semantics of `too old' can be implied
1141
except through knowledge of the routing protocol
1142
by which the route was learned."
1143
::= { ipRouteEntry 10 }
1145
ipRouteMask OBJECT-TYPE
1150
"Indicate the mask to be logical-ANDed with the
1151
destination address before being compared to the
1152
value in the ipRouteDest field. For those systems
1153
that do not support arbitrary subnet masks, an
1154
agent constructs the value of the ipRouteMask by
1155
determining whether the value of the correspondent
1156
ipRouteDest field belong to a class-A, B, or C
1157
network, and then using one of:
1162
255.255.255.0 class-C
1164
If the value of the ipRouteDest is 0.0.0.0 (a
1165
default route), then the mask value is also
1166
0.0.0.0. It should be noted that all IP routing
1167
subsystems implicitly use this mechanism."
1168
::= { ipRouteEntry 11 }
1170
ipRouteMetric5 OBJECT-TYPE
1175
"An alternate routing metric for this route. The
1176
semantics of this metric are determined by the
1177
routing-protocol specified in the route's
1178
ipRouteProto value. If this metric is not used,
1179
its value should be set to -1."
1180
::= { ipRouteEntry 12 }
1182
ipRouteInfo OBJECT-TYPE
1183
SYNTAX OBJECT IDENTIFIER
1187
"A reference to MIB definitions specific to the
1188
particular routing protocol which is responsible
1189
for this route, as determined by the value
1190
specified in the route's ipRouteProto value. If
1191
this information is not present, its value should
1192
be set to the OBJECT IDENTIFIER { 0 0 }, which is
1193
a syntatically valid object identifier, and any
1194
conformant implementation of ASN.1 and BER must be
1195
able to generate and recognize this value."
1196
::= { ipRouteEntry 13 }
1200
ipNetToMediaTable OBJECT-TYPE
1201
SYNTAX SEQUENCE OF IpNetToMediaEntry
1202
ACCESS not-accessible
1205
"The IP Address Translation table used for mapping
1206
from IP addresses to physical addresses."
1209
ipNetToMediaEntry OBJECT-TYPE
1210
SYNTAX IpNetToMediaEntry
1211
ACCESS not-accessible
1214
"Each entry contains one IpAddress to `physical'
1215
address equivalence."
1216
INDEX { ipNetToMediaIfIndex,
1217
ipNetToMediaNetAddress }
1218
::= { ipNetToMediaTable 1 }
1220
IpNetToMediaEntry ::=
1224
ipNetToMediaPhysAddress
1226
ipNetToMediaNetAddress
1232
ipNetToMediaIfIndex OBJECT-TYPE
1237
"The interface on which this entry's equivalence
1238
is effective. The interface identified by a
1239
particular value of this index is the same
1240
interface as identified by the same value of
1242
::= { ipNetToMediaEntry 1 }
1244
ipNetToMediaPhysAddress OBJECT-TYPE
1249
"The media-dependent `physical' address."
1250
::= { ipNetToMediaEntry 2 }
1252
ipNetToMediaNetAddress OBJECT-TYPE
1257
"The IpAddress corresponding to the media-
1258
dependent `physical' address."
1259
::= { ipNetToMediaEntry 3 }
1261
ipNetToMediaType OBJECT-TYPE
1263
other(1), -- none of the following
1264
invalid(2), -- an invalidated mapping
1271
"The type of mapping.
1273
Setting this object to the value invalid(2) has
1274
the effect of invalidating the corresponding entry
1275
in the ipNetToMediaTable. That is, it effectively
1276
dissasociates the interface identified with said
1277
entry from the mapping identified with said entry.
1278
It is an implementation-specific matter as to
1279
whether the agent removes an invalidated entry
1280
from the table. Accordingly, management stations
1281
must be prepared to receive tabular information
1282
from agents that corresponds to entries not
1283
currently in use. Proper interpretation of such
1284
entries requires examination of the relevant
1285
ipNetToMediaType object."
1286
::= { ipNetToMediaEntry 4 }
1289
ipRoutingDiscards OBJECT-TYPE
1294
"The number of routing entries which were chosen
1295
to be discarded even though they are valid. One
1296
possible reason for discarding such an entry could
1297
be to free-up buffer space for other routing
1304
icmpInMsgs OBJECT-TYPE
1309
"The total number of ICMP messages which the
1310
entity received. Note that this counter includes
1311
all those counted by icmpInErrors."
1314
icmpInErrors OBJECT-TYPE
1319
"The number of ICMP messages which the entity
1320
received but determined as having ICMP-specific
1321
errors (bad ICMP checksums, bad length, etc.)."
1324
icmpInDestUnreachs OBJECT-TYPE
1329
"The number of ICMP Destination Unreachable
1333
icmpInTimeExcds OBJECT-TYPE
1338
"The number of ICMP Time Exceeded messages
1342
icmpInParmProbs OBJECT-TYPE
1347
"The number of ICMP Parameter Problem messages
1351
icmpInSrcQuenchs OBJECT-TYPE
1356
"The number of ICMP Source Quench messages
1360
icmpInRedirects OBJECT-TYPE
1365
"The number of ICMP Redirect messages received."
1368
icmpInEchos OBJECT-TYPE
1373
"The number of ICMP Echo (request) messages
1377
icmpInEchoReps OBJECT-TYPE
1382
"The number of ICMP Echo Reply messages received."
1385
icmpInTimestamps OBJECT-TYPE
1390
"The number of ICMP Timestamp (request) messages
1394
icmpInTimestampReps OBJECT-TYPE
1399
"The number of ICMP Timestamp Reply messages
1403
icmpInAddrMasks OBJECT-TYPE
1408
"The number of ICMP Address Mask Request messages
1412
icmpInAddrMaskReps OBJECT-TYPE
1417
"The number of ICMP Address Mask Reply messages
1421
icmpOutMsgs OBJECT-TYPE
1426
"The total number of ICMP messages which this
1427
entity attempted to send. Note that this counter
1428
includes all those counted by icmpOutErrors."
1431
icmpOutErrors OBJECT-TYPE
1436
"The number of ICMP messages which this entity did
1437
not send due to problems discovered within ICMP
1439
such as a lack of buffers. This value should not
1440
include errors discovered outside the ICMP layer
1441
such as the inability of IP to route the resultant
1442
datagram. In some implementations there may be no
1443
types of error which contribute to this counter's
1447
icmpOutDestUnreachs OBJECT-TYPE
1452
"The number of ICMP Destination Unreachable
1456
icmpOutTimeExcds OBJECT-TYPE
1461
"The number of ICMP Time Exceeded messages sent."
1464
icmpOutParmProbs OBJECT-TYPE
1469
"The number of ICMP Parameter Problem messages
1473
icmpOutSrcQuenchs OBJECT-TYPE
1478
"The number of ICMP Source Quench messages sent."
1481
icmpOutRedirects OBJECT-TYPE
1486
"The number of ICMP Redirect messages sent. For a
1488
host, this object will always be zero, since hosts
1489
do not send redirects."
1492
icmpOutEchos OBJECT-TYPE
1497
"The number of ICMP Echo (request) messages sent."
1500
icmpOutEchoReps OBJECT-TYPE
1505
"The number of ICMP Echo Reply messages sent."
1508
icmpOutTimestamps OBJECT-TYPE
1513
"The number of ICMP Timestamp (request) messages
1517
icmpOutTimestampReps OBJECT-TYPE
1522
"The number of ICMP Timestamp Reply messages
1526
icmpOutAddrMasks OBJECT-TYPE
1531
"The number of ICMP Address Mask Request messages
1535
icmpOutAddrMaskReps OBJECT-TYPE
1540
"The number of ICMP Address Mask Reply messages
1547
tcpRtoAlgorithm OBJECT-TYPE
1549
other(1), -- none of the following
1551
constant(2), -- a constant rto
1552
rsre(3), -- MIL-STD-1778, Appendix B
1553
vanj(4) -- Van Jacobson's algorithm [10]
1558
"The algorithm used to determine the timeout value
1559
used for retransmitting unacknowledged octets."
1562
tcpRtoMin OBJECT-TYPE
1567
"The minimum value permitted by a TCP
1568
implementation for the retransmission timeout,
1569
measured in milliseconds. More refined semantics
1570
for objects of this type depend upon the algorithm
1571
used to determine the retransmission timeout. In
1572
particular, when the timeout algorithm is rsre(3),
1573
an object of this type has the semantics of the
1574
LBOUND quantity described in RFC 793."
1577
tcpRtoMax OBJECT-TYPE
1582
"The maximum value permitted by a TCP
1583
implementation for the retransmission timeout,
1584
measured in milliseconds. More refined semantics
1585
for objects of this type depend upon the algorithm
1586
used to determine the retransmission timeout. In
1587
particular, when the timeout algorithm is rsre(3),
1588
an object of this type has the semantics of the
1589
UBOUND quantity described in RFC 793."
1592
tcpMaxConn OBJECT-TYPE
1597
"The limit on the total number of TCP connections
1598
the entity can support. In entities where the
1599
maximum number of connections is dynamic, this
1600
object should contain the value -1."
1603
tcpActiveOpens OBJECT-TYPE
1608
"The number of times TCP connections have made a
1609
direct transition to the SYN-SENT state from the
1613
tcpPassiveOpens OBJECT-TYPE
1618
"The number of times TCP connections have made a
1619
direct transition to the SYN-RCVD state from the
1623
tcpAttemptFails OBJECT-TYPE
1628
"The number of times TCP connections have made a
1629
direct transition to the CLOSED state from either
1630
the SYN-SENT state or the SYN-RCVD state, plus the
1631
number of times TCP connections have made a direct
1632
transition to the LISTEN state from the SYN-RCVD
1636
tcpEstabResets OBJECT-TYPE
1641
"The number of times TCP connections have made a
1642
direct transition to the CLOSED state from either
1643
the ESTABLISHED state or the CLOSE-WAIT state."
1646
tcpCurrEstab OBJECT-TYPE
1651
"The number of TCP connections for which the
1652
current state is either ESTABLISHED or CLOSE-
1656
tcpInSegs OBJECT-TYPE
1661
"The total number of segments received, including
1662
those received in error. This count includes
1663
segments received on currently established
1667
tcpOutSegs OBJECT-TYPE
1672
"The total number of segments sent, including
1673
those on current connections but excluding those
1674
containing only retransmitted octets."
1677
tcpRetransSegs OBJECT-TYPE
1682
"The total number of segments retransmitted - that
1683
is, the number of TCP segments transmitted
1684
containing one or more previously transmitted
1690
tcpConnTable OBJECT-TYPE
1691
SYNTAX SEQUENCE OF TcpConnEntry
1692
ACCESS not-accessible
1695
"A table containing TCP connection-specific
1699
tcpConnEntry OBJECT-TYPE
1701
ACCESS not-accessible
1704
"Information about a particular current TCP
1705
connection. An object of this type is transient,
1706
in that it ceases to exist when (or soon after)
1707
the connection makes the transition to the CLOSED
1709
INDEX { tcpConnLocalAddress,
1713
::= { tcpConnTable 1 }
1729
tcpConnState OBJECT-TYPE
1747
"The state of this TCP connection.
1749
The only value which may be set by a management
1750
station is deleteTCB(12). Accordingly, it is
1751
appropriate for an agent to return a `badValue'
1752
response if a management station attempts to set
1753
this object to any other value.
1755
If a management station sets this object to the
1756
value deleteTCB(12), then this has the effect of
1757
deleting the TCB (as defined in RFC 793) of the
1758
corresponding connection on the managed node,
1759
resulting in immediate termination of the
1762
As an implementation-specific option, a RST
1764
segment may be sent from the managed node to the
1765
other TCP endpoint (note however that RST segments
1766
are not sent reliably)."
1767
::= { tcpConnEntry 1 }
1769
tcpConnLocalAddress OBJECT-TYPE
1774
"The local IP address for this TCP connection. In
1775
the case of a connection in the listen state which
1776
is willing to accept connections for any IP
1777
interface associated with the node, the value
1779
::= { tcpConnEntry 2 }
1781
tcpConnLocalPort OBJECT-TYPE
1782
SYNTAX INTEGER (0..65535)
1786
"The local port number for this TCP connection."
1787
::= { tcpConnEntry 3 }
1789
tcpConnRemAddress OBJECT-TYPE
1794
"The remote IP address for this TCP connection."
1795
::= { tcpConnEntry 4 }
1797
tcpConnRemPort OBJECT-TYPE
1798
SYNTAX INTEGER (0..65535)
1802
"The remote port number for this TCP connection."
1803
::= { tcpConnEntry 5 }
1806
tcpInErrs OBJECT-TYPE
1811
"The total number of segments received in error
1812
(e.g., bad TCP checksums)."
1815
tcpOutRsts OBJECT-TYPE
1820
"The number of TCP segments sent containing the
1826
udpInDatagrams OBJECT-TYPE
1831
"The total number of UDP datagrams delivered to
1835
udpNoPorts OBJECT-TYPE
1840
"The total number of received UDP datagrams for
1841
which there was no application at the destination
1845
udpInErrors OBJECT-TYPE
1850
"The number of received UDP datagrams that could
1851
not be delivered for reasons other than the lack
1852
of an application at the destination port."
1855
udpOutDatagrams OBJECT-TYPE
1860
"The total number of UDP datagrams sent from this
1866
udpTable OBJECT-TYPE
1867
SYNTAX SEQUENCE OF UdpEntry
1868
ACCESS not-accessible
1871
"A table containing UDP listener information."
1874
udpEntry OBJECT-TYPE
1876
ACCESS not-accessible
1879
"Information about a particular current UDP
1881
INDEX { udpLocalAddress, udpLocalPort }
1892
udpLocalAddress OBJECT-TYPE
1897
"The local IP address for this UDP listener. In
1899
the case of a UDP listener which is willing to
1900
accept datagrams for any IP interface associated
1901
with the node, the value 0.0.0.0 is used."
1904
udpLocalPort OBJECT-TYPE
1905
SYNTAX INTEGER (0..65535)
1909
"The local port number for this UDP listener."
1914
egpInMsgs OBJECT-TYPE
1919
"The number of EGP messages received without
1923
egpInErrors OBJECT-TYPE
1928
"The number of EGP messages received that proved
1932
egpOutMsgs OBJECT-TYPE
1937
"The total number of locally generated EGP
1941
egpOutErrors OBJECT-TYPE
1946
"The number of locally generated EGP messages not
1947
sent due to resource limitations within an EGP
1953
egpNeighTable OBJECT-TYPE
1954
SYNTAX SEQUENCE OF EgpNeighEntry
1955
ACCESS not-accessible
1958
"The EGP neighbor table."
1961
egpNeighEntry OBJECT-TYPE
1962
SYNTAX EgpNeighEntry
1963
ACCESS not-accessible
1966
"Information about this entity's relationship with
1967
a particular EGP neighbor."
1968
INDEX { egpNeighAddr }
1969
::= { egpNeighTable 1 }
1995
egpNeighIntervalHello
1997
egpNeighIntervalPoll
2001
egpNeighEventTrigger
2005
egpNeighState OBJECT-TYPE
2016
"The EGP state of the local system with respect to
2017
this entry's EGP neighbor. Each EGP state is
2018
represented by a value that is one greater than
2019
the numerical value associated with said state in
2021
::= { egpNeighEntry 1 }
2023
egpNeighAddr OBJECT-TYPE
2028
"The IP address of this entry's EGP neighbor."
2029
::= { egpNeighEntry 2 }
2031
egpNeighAs OBJECT-TYPE
2036
"The autonomous system of this EGP peer. Zero
2037
should be specified if the autonomous system
2038
number of the neighbor is not yet known."
2039
::= { egpNeighEntry 3 }
2041
egpNeighInMsgs OBJECT-TYPE
2046
"The number of EGP messages received without error
2047
from this EGP peer."
2048
::= { egpNeighEntry 4 }
2050
egpNeighInErrs OBJECT-TYPE
2055
"The number of EGP messages received from this EGP
2056
peer that proved to be in error (e.g., bad EGP
2058
::= { egpNeighEntry 5 }
2060
egpNeighOutMsgs OBJECT-TYPE
2065
"The number of locally generated EGP messages to
2067
::= { egpNeighEntry 6 }
2069
egpNeighOutErrs OBJECT-TYPE
2074
"The number of locally generated EGP messages not
2075
sent to this EGP peer due to resource limitations
2076
within an EGP entity."
2077
::= { egpNeighEntry 7 }
2079
egpNeighInErrMsgs OBJECT-TYPE
2084
"The number of EGP-defined error messages received
2085
from this EGP peer."
2086
::= { egpNeighEntry 8 }
2088
egpNeighOutErrMsgs OBJECT-TYPE
2093
"The number of EGP-defined error messages sent to
2095
::= { egpNeighEntry 9 }
2097
egpNeighStateUps OBJECT-TYPE
2102
"The number of EGP state transitions to the UP
2103
state with this EGP peer."
2104
::= { egpNeighEntry 10 }
2106
egpNeighStateDowns OBJECT-TYPE
2111
"The number of EGP state transitions from the UP
2112
state to any other state with this EGP peer."
2113
::= { egpNeighEntry 11 }
2115
egpNeighIntervalHello OBJECT-TYPE
2120
"The interval between EGP Hello command
2121
retransmissions (in hundredths of a second). This
2122
represents the t1 timer as defined in RFC 904."
2123
::= { egpNeighEntry 12 }
2125
egpNeighIntervalPoll OBJECT-TYPE
2130
"The interval between EGP poll command
2132
retransmissions (in hundredths of a second). This
2133
represents the t3 timer as defined in RFC 904."
2134
::= { egpNeighEntry 13 }
2136
egpNeighMode OBJECT-TYPE
2137
SYNTAX INTEGER { active(1), passive(2) }
2141
"The polling mode of this EGP entity, either
2143
::= { egpNeighEntry 14 }
2145
egpNeighEventTrigger OBJECT-TYPE
2146
SYNTAX INTEGER { start(1), stop(2) }
2150
"A control variable used to trigger operator-
2151
initiated Start and Stop events. When read, this
2152
variable always returns the most recent value that
2153
egpNeighEventTrigger was set to. If it has not
2154
been set since the last initialization of the
2155
network management subsystem on the node, it
2156
returns a value of `stop'.
2158
When set, this variable causes a Start or Stop
2159
event on the specified neighbor, as specified on
2160
pages 8-10 of RFC 904. Briefly, a Start event
2161
causes an Idle peer to begin neighbor acquisition
2162
and a non-Idle peer to reinitiate neighbor
2163
acquisition. A stop event causes a non-Idle peer
2164
to return to the Idle state until a Start event
2165
occurs, either via egpNeighEventTrigger or
2167
::= { egpNeighEntry 15 }
2175
"The autonomous system number of this EGP entity."
2186
snmpInPkts OBJECT-TYPE
2191
"The total number of Messages delivered to the
2192
SNMP entity from the transport service."
2195
snmpOutPkts OBJECT-TYPE
2200
"The total number of SNMP Messages which were
2201
passed from the SNMP protocol entity to the
2205
snmpInBadVersions OBJECT-TYPE
2210
"The total number of SNMP Messages which were
2211
delivered to the SNMP protocol entity and were for
2212
an unsupported SNMP version."
2215
snmpInBadCommunityNames OBJECT-TYPE
2220
"The total number of SNMP Messages delivered to
2221
the SNMP protocol entity which used a SNMP
2222
community name not known to said entity."
2225
snmpInBadCommunityUses OBJECT-TYPE
2230
"The total number of SNMP Messages delivered to
2231
the SNMP protocol entity which represented an SNMP
2232
operation which was not allowed by the SNMP
2233
community named in the Message."
2236
snmpInASNParseErrs OBJECT-TYPE
2241
"The total number of ASN.1 or BER errors
2242
encountered by the SNMP protocol entity when
2243
decoding received SNMP Messages."
2247
snmpInTooBigs OBJECT-TYPE
2252
"The total number of SNMP PDUs which were
2253
delivered to the SNMP protocol entity and for
2254
which the value of the error-status field is
2258
snmpInNoSuchNames OBJECT-TYPE
2263
"The total number of SNMP PDUs which were
2264
delivered to the SNMP protocol entity and for
2265
which the value of the error-status field is
2269
snmpInBadValues OBJECT-TYPE
2274
"The total number of SNMP PDUs which were
2275
delivered to the SNMP protocol entity and for
2276
which the value of the error-status field is
2280
snmpInReadOnlys OBJECT-TYPE
2285
"The total number valid SNMP PDUs which were
2286
delivered to the SNMP protocol entity and for
2287
which the value of the error-status field is
2288
`readOnly'. It should be noted that it is a
2289
protocol error to generate an SNMP PDU which
2290
contains the value `readOnly' in the error-status
2291
field, as such this object is provided as a means
2292
of detecting incorrect implementations of the
2297
snmpInGenErrs OBJECT-TYPE
2302
"The total number of SNMP PDUs which were
2303
delivered to the SNMP protocol entity and for
2304
which the value of the error-status field is
2308
snmpInTotalReqVars OBJECT-TYPE
2313
"The total number of MIB objects which have been
2314
retrieved successfully by the SNMP protocol entity
2315
as the result of receiving valid SNMP Get-Request
2319
snmpInTotalSetVars OBJECT-TYPE
2324
"The total number of MIB objects which have been
2325
altered successfully by the SNMP protocol entity
2326
as the result of receiving valid SNMP Set-Request
2330
snmpInGetRequests OBJECT-TYPE
2335
"The total number of SNMP Get-Request PDUs which
2336
have been accepted and processed by the SNMP
2340
snmpInGetNexts OBJECT-TYPE
2345
"The total number of SNMP Get-Next PDUs which have
2346
been accepted and processed by the SNMP protocol
2350
snmpInSetRequests OBJECT-TYPE
2355
"The total number of SNMP Set-Request PDUs which
2356
have been accepted and processed by the SNMP
2360
snmpInGetResponses OBJECT-TYPE
2365
"The total number of SNMP Get-Response PDUs which
2366
have been accepted and processed by the SNMP
2370
snmpInTraps OBJECT-TYPE
2375
"The total number of SNMP Trap PDUs which have
2376
been accepted and processed by the SNMP protocol
2380
snmpOutTooBigs OBJECT-TYPE
2385
"The total number of SNMP PDUs which were
2386
generated by the SNMP protocol entity and for
2387
which the value of the error-status field is
2391
snmpOutNoSuchNames OBJECT-TYPE
2396
"The total number of SNMP PDUs which were
2397
generated by the SNMP protocol entity and for
2398
which the value of the error-status is
2402
snmpOutBadValues OBJECT-TYPE
2407
"The total number of SNMP PDUs which were
2408
generated by the SNMP protocol entity and for
2409
which the value of the error-status field is
2414
snmpOutGenErrs OBJECT-TYPE
2419
"The total number of SNMP PDUs which were
2420
generated by the SNMP protocol entity and for
2421
which the value of the error-status field is
2425
snmpOutGetRequests OBJECT-TYPE
2430
"The total number of SNMP Get-Request PDUs which
2431
have been generated by the SNMP protocol entity."
2434
snmpOutGetNexts OBJECT-TYPE
2439
"The total number of SNMP Get-Next PDUs which have
2440
been generated by the SNMP protocol entity."
2443
snmpOutSetRequests OBJECT-TYPE
2448
"The total number of SNMP Set-Request PDUs which
2449
have been generated by the SNMP protocol entity."
2452
snmpOutGetResponses OBJECT-TYPE
2457
"The total number of SNMP Get-Response PDUs which
2458
have been generated by the SNMP protocol entity."
2461
snmpOutTraps OBJECT-TYPE
2466
"The total number of SNMP Trap PDUs which have
2467
been generated by the SNMP protocol entity."
2470
snmpEnableAuthenTraps OBJECT-TYPE
2471
SYNTAX INTEGER { enabled(1), disabled(2) }
2475
"Indicates whether the SNMP agent process is
2476
permitted to generate authentication-failure
2477
traps. The value of this object overrides any
2478
configuration information; as such, it provides a
2479
means whereby all authentication-failure traps may
2482
Note that it is strongly recommended that this
2483
object be stored in non-volatile memory so that it
2484
remains constant between re-initializations of the
2485
network management system."