14
14
InterfaceIndexOrZero -- RFC2863
17
FROM SNMP-FRAMEWORK-MIB -- RFC2571
17
FROM SNMP-FRAMEWORK-MIB -- RFC3411
18
18
InetAddressType, InetAddress
19
FROM INET-ADDRESS-MIB; -- RFC2851
19
FROM INET-ADDRESS-MIB; -- RFC4001
21
21
pingMIB MODULE-IDENTITY
22
LAST-UPDATED "200009210000Z" -- 21 September 2000
22
LAST-UPDATED "200606130000Z" -- 13 June 2006
23
23
ORGANIZATION "IETF Distributed Management Working Group"
32
International Business Machines Corporation
33
Network Computing Software Division
34
Research Triangle Park, NC, USA
36
E-mail: wkenneth@us.ibm.com"
33
Phone: +49 6221 4342-115
35
Email: quittek@netlab.nec.de"
38
37
"The Ping MIB (DISMAN-PING-MIB) provides the capability of
39
38
controlling the use of the ping function at a remote
41
Copyright (C) The Internet Society (2006). This version of
42
this MIB module is part of RFC 4560; see the RFC itself for
42
45
-- Revision history
47
REVISION "200606130000Z" -- 13 June 2006
49
"Updated version, published as RFC 4560.
50
- Correctly considered IPv6 in DESCRIPTION
51
clause of pingCtlDataSize
52
- Replaced references to RFC 2575 by RFC 3415
53
- Replaced references to RFC 2571 by RFC 3411
54
- Replaced references to RFC 2851 by RFC 4001
55
- Added DEFVAL { {} } to definition of
57
- Changed DEFVAL of object pingCtlDescr from
58
DEFVAL { '00'H } to DEFVAL { ''H }
59
- Changed DEFVAL of object pingCtlSourceAddressType
60
from DEFVAL { ipv4 } to DEFVAL { unknown }
61
- Extended DESCRIPTION clause of pingResultsTable
62
describing re-initialization of entries
63
- Changed SYNTAX of pingResultsProbeResponses and
64
pingResultsSentProbes from Unsigned32 to Gauge32
65
- Changed status of pingCompliance to deprecated
66
- Added pingFullCompliance and pingMinimumCompliance
67
- Changed status of pingGroup and pingTimeStampGroup
69
- Added pingMinimumGroup, pingCtlRowStatusGroup,
44
72
REVISION "200009210000Z" -- 21 September 2000
46
74
"Initial version, published as RFC 2925."
50
77
-- Textual Conventions
622
611
MAX-ACCESS read-create
625
"Specifies the value to store in the Differentiated
626
Services (DS) Field in the IP packet used to
627
encapsulate the ping probe. The DS Field is defined
628
as the Type of Service (TOS) octet in a IPv4 header
629
or as the Traffic Class octet in a IPv6 header.
631
The value of this object must be a decimal integer
632
in the range from 0 to 255. This option can be used
633
to determine what effect an explicit DS Field setting
634
has on a ping response. Not all values are legal or
635
meaningful. A value of 0 means that the function
636
represented by this option is not supported. DS Field
637
usage is often not supported by IP implementations and
638
not all values are supported. Refer to RFC 2474 for
639
guidance on usage of this field."
614
"Specifies the value to store in the Type of Service
615
(TOS) octet in the IPv4 header or in the Traffic
616
Class octet in the IPv6 header, respectively, of the
617
IP packet used to encapsulate the ping probe.
619
The octet to be set in the IP header contains the
620
Differentiated Services (DS) Field in the six most
623
This option can be used to determine what effect an
624
explicit DS Field setting has on a ping response.
625
Not all values are legal or meaningful. A value of 0
626
means that the function represented by this option is
627
not supported. DS Field usage is often not supported
628
by IP implementations, and not all values are supported.
629
Refer to RFC 2474 and RFC 3260 for guidance on usage of
641
"Refer to RFC 2474 for the definition of the
642
Differentiated Services Field and to RFC 1812
643
Section 5.3.2 for Type of Service (TOS)."
632
"Refer to RFC 1812 for the definition of the IPv4 TOS
633
octet and to RFC 2460 for the definition of the IPv6
634
Traffic Class octet. Refer to RFC 2474 and RFC 3260
635
for the definition of the Differentiated Services Field."
645
637
::= { pingCtlEntry 22 }
1075
1053
-- Compliance statements
1055
pingFullCompliance MODULE-COMPLIANCE
1058
"The compliance statement for SNMP entities that
1059
fully implement the DISMAN-PING-MIB."
1060
MODULE -- this module
1063
pingCtlRowStatusGroup,
1065
pingNotificationsGroup
1068
OBJECT pingMaxConcurrentRequests
1069
MIN-ACCESS read-only
1071
"The agent is not required to support set
1072
operations to this object."
1074
OBJECT pingCtlStorageType
1075
MIN-ACCESS read-only
1077
"Write access is not required."
1080
MIN-ACCESS read-only
1082
"Write access is not required. In addition, the only
1083
value that MUST be supported by an implementation is
1086
OBJECT pingCtlSourceAddressType
1087
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
1088
MIN-ACCESS read-only
1090
"Write access to this object is not required by
1091
implementations that are not capable of binding the
1092
send socket with a source address. An implementation
1093
is only required to support IPv4 and IPv6 addresses."
1095
OBJECT pingCtlSourceAddress
1096
SYNTAX InetAddress (SIZE(0|4|16))
1097
MIN-ACCESS read-only
1099
"Write access to this object is not required by
1100
implementations that are not capable of binding the
1101
send socket with a source address. An implementation
1102
is only required to support IPv4 and IPv6 addresses."
1104
OBJECT pingCtlIfIndex
1105
MIN-ACCESS read-only
1107
"Write access is not required. If write access is
1108
not supported, return a 0 as the value of this object.
1109
A value of 0 means that the function represented by
1110
this option is not supported."
1112
OBJECT pingCtlByPassRouteTable
1113
MIN-ACCESS read-only
1115
"Write access to this object is not required by
1116
implementations that are not capable of its
1117
implementation. The function represented by this
1118
object is implementable if the setsockopt
1119
SOL_SOCKET SO_DONTROUTE option is supported."
1121
OBJECT pingCtlDSField
1122
MIN-ACCESS read-only
1124
"Write access is not required. If write access is
1125
not supported, return a 0 as the value of this object.
1126
A value of 0 means that the function represented by
1127
this option is not supported."
1129
OBJECT pingResultsIpTargetAddressType
1130
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
1132
"An implementation is only required to
1134
support IPv4 and IPv6 addresses."
1136
OBJECT pingResultsIpTargetAddress
1137
SYNTAX InetAddress (SIZE(0|4|16))
1139
"An implementation is only required to
1140
support IPv4 and globally unique IPv6 addresses."
1142
OBJECT pingResultsLastGoodProbe
1144
"This object is mandatory for implementations that have
1145
access to a system clock and that are capable of setting
1146
the values for DateAndTime objects. It is RECOMMENDED
1147
that when this object is not supported its values
1148
be reported as '0000000000000000'H."
1150
OBJECT pingProbeHistoryTime
1152
"This object is mandatory for implementations that have
1153
access to a system clock and that are capable of setting
1154
the values for DateAndTime objects. It is RECOMMENDED
1155
that when this object is not supported its values
1156
be reported as '0000000000000000'H."
1157
::= { pingCompliances 2 }
1159
pingMinimumCompliance MODULE-COMPLIANCE
1162
"The minimum compliance statement for SNMP entities
1163
that implement the minimal subset of the
1164
DISMAN-PING-MIB. Implementors might choose this
1165
subset for small devices with limited resources."
1166
MODULE -- this module
1167
MANDATORY-GROUPS { pingMinimumGroup }
1169
GROUP pingCtlRowStatusGroup
1171
"A compliant implementation does not have to implement
1172
the pingCtlRowStatusGroup."
1174
GROUP pingHistoryGroup
1176
"A compliant implementation does not have to implement
1177
the pingHistoryGroup."
1179
GROUP pingNotificationsGroup
1181
"A compliant implementation does not have to implement
1183
the pingNotificationsGroup."
1185
OBJECT pingMaxConcurrentRequests
1186
MIN-ACCESS read-only
1188
"The agent is not required to support set
1189
operations to this object."
1191
OBJECT pingCtlDataFill
1192
MIN-ACCESS read-only
1194
"The agent is not required to support set
1195
operations to this object."
1197
OBJECT pingCtlFrequency
1198
MIN-ACCESS read-only
1200
"Write access is not required. If write access is
1201
not supported, return a 0 as the value of this object.
1202
A value of 0 means that the function represented by
1203
this option is not supported."
1205
OBJECT pingCtlMaxRows
1206
MIN-ACCESS read-only
1208
"Write access is not required. If the
1209
pingHistoryGroup is not implemented, then write
1210
access to this object MUST be disabled, and the object
1211
MUST return a value of 0 when retrieved."
1213
OBJECT pingCtlStorageType
1214
MIN-ACCESS read-only
1216
"Write access is not required."
1218
OBJECT pingCtlTrapGeneration
1219
MIN-ACCESS read-only
1221
"Write access is not required. If the
1222
pingNotificationsGroup is not implemented, then write
1223
access to this object MUST be disabled, and the object
1224
MUST return a value with no bit set when retrieved.
1225
No bit set indicates that not notification is
1228
OBJECT pingCtlTrapProbeFailureFilter
1229
MIN-ACCESS read-only
1231
"If write access to pingCtlTrapGeneration is not
1232
supported, then write access to this object must also
1233
not be supported. In this case, return 0 as the value
1236
OBJECT pingCtlTrapTestFailureFilter
1237
MIN-ACCESS read-only
1239
"If write access to pingCtlTrapGeneration is not
1240
supported, then write access to this object must also
1241
not be supported. In this case, return 0 as the value
1245
MIN-ACCESS read-only
1247
"Write access is not required. In addition, the only
1248
value that MUST be supported by an implementation is
1252
MIN-ACCESS read-only
1254
"The agent is not required to support set
1255
operations to this object."
1257
OBJECT pingCtlSourceAddressType
1258
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
1259
MIN-ACCESS read-only
1261
"Write access to this object is not required by
1262
implementations that are not capable of binding the
1263
send socket with a source address. An implementation
1264
is only required to support IPv4 and IPv6 addresses."
1266
OBJECT pingCtlSourceAddress
1267
SYNTAX InetAddress (SIZE(0|4|16))
1268
MIN-ACCESS read-only
1270
"Write access to this object is not required by
1271
implementations that are not capable of binding the
1272
send socket with a source address. An implementation
1273
is only required to support IPv4 and IPv6 addresses."
1275
OBJECT pingCtlIfIndex
1276
MIN-ACCESS read-only
1278
"Write access is not required. If write access is
1280
not supported, return a 0 as the value of this object.
1281
A value of 0 means that the function represented by
1282
this option is not supported."
1284
OBJECT pingCtlByPassRouteTable
1285
MIN-ACCESS read-only
1287
"Write access is not required. If write access is
1288
not supported, return false(2) as the value of this
1289
object. A value of false(2) means that the function
1290
represented by this option is not supported."
1292
OBJECT pingCtlDSField
1293
MIN-ACCESS read-only
1295
"Write access is not required. If write access is
1296
not supported, return a 0 as the value of this object.
1297
A value of 0 means that the function represented by
1298
this option is not supported."
1300
OBJECT pingResultsIpTargetAddressType
1301
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
1303
"An implementation is only required to
1304
support IPv4 and IPv6 addresses."
1306
OBJECT pingResultsIpTargetAddress
1307
SYNTAX InetAddress (SIZE(0|4|16))
1309
"An implementation is only required to
1310
support IPv4 and globally unique IPv6 addresses."
1312
OBJECT pingResultsLastGoodProbe
1314
"This object is mandatory for implementations that have
1315
access to a system clock and that are capable of setting
1316
the values for DateAndTime objects. It is RECOMMENDED
1317
that when this object is not supported its values
1318
be reported as '0000000000000000'H."
1320
OBJECT pingProbeHistoryTime
1322
"If the pingHistoryGroup is implemented, then this
1323
object is mandatory for implementations that have
1324
access to a system clock and that are capable of setting
1325
the values for DateAndTime objects. It is RECOMMENDED
1326
that when this object is not supported its values
1328
be reported as '0000000000000000'H."
1329
::= { pingCompliances 3 }
1077
1331
pingCompliance MODULE-COMPLIANCE
1080
"The compliance statement for the DISMAN-PING-MIB."
1334
"The compliance statement for the DISMAN-PING-MIB. This
1335
compliance statement has been deprecated because the
1336
group pingGroup and the pingTimeStampGroup have been
1337
split and deprecated. The pingFullCompliance statement
1338
is semantically identical to the deprecated
1339
pingCompliance statement."
1081
1341
MODULE -- this module
1082
1342
MANDATORY-GROUPS {
1084
1344
pingNotificationsGroup
1091
1346
GROUP pingTimeStampGroup
1093
1348
"This group is mandatory for implementations that have
1094
access to a system clock and are capable of setting
1349
access to a system clock and that are capable of setting
1095
1350
the values for DateAndTime objects. It is RECOMMENDED
1096
that when this group is not supported that the values
1351
that when this group is not supported the values
1097
1352
for the objects in this group be reported as
1098
1353
'0000000000000000'H."