Defines the ping Control Table for providing, via SNMP, the capability of performing ping operations at a remote host. The results of these operations are stored in the pingResultsTable and the pingProbeHistoryTable.
The indexes of the table are pingCtlOwnerIndex, pingCtlTestName.
|
OID |
Object |
Syntax |
Max Access |
Description |
Implemented Specifications |
|---|---|---|---|---|---|
|
1.3.6.1.2.1.80.1.2.1.1 |
pingCtlOwnerIndex |
OCTET STRING{(0,32)} |
not-accessible |
To facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (RFC 2575, VACM) for tables in which multiple users may need to create or modify entries independently, the initial index is used as an 'owner index'. Such an initial index has a syntax of SnmpAdminString and can thus be trivially mapped to a securityName or groupName defined in VACM, in accordance with a security policy. When used in conjunction with such a security policy, all entries in the table belonging to a particular user (or group) will have the same value for this initial index. For a given user's entries in a particular table, the object identifiers for the information in these entries will have the same subidentifiers (except for the 'column' subidentifier) up to the end of the encoded owner index. To configure VACM to permit access to this portion of the table, one would create vacmViewTreeFamilyTable entries with the value of vacmViewTreeFamilySubtree including the owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the column subidentifier. More elaborate configurations are possible. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.2.1.80.1.2.1.2 |
pingCtlTestName |
OCTET STRING{(0,32)} |
not-accessible |
The name of the ping test. This is locally unique, within the scope of a pingCtlOwnerIndex. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.2.1.80.1.2.1.3 |
pingCtlTargetAddressType |
INTEGER{unknown(0),ipv4(1),ipv6(2),ipv4z(3),ipv6z(4),dns(16)} |
read-create |
Specifies the type of host address to be used at a remote host for performing a ping operation. |
Only support the setting of value 'ipv4(1)'. |
|
1.3.6.1.2.1.80.1.2.1.4 |
pingCtlTargetAddress |
OCTET STRING{(0,255)} |
read-create |
Specifies the host address to be used at a remote host for performing a ping operation. The host address type is determined by the value of the corresponding pingCtlTargetAddressType. A value for this object MUST be set prior to transitioning its corresponding pingCtlEntry to active(1) via pingCtlRowStatus. |
Only support the ipv4 address. |
|
1.3.6.1.2.1.80.1.2.1.5 |
pingCtlDataSize |
Unsigned32{(0,65507)} |
read-create |
Specifies the size of the data portion to be transmitted in a ping operation, in octets. Whether this value can be applied depends on the selected implementation method for performing a ping operation, indicated by pingCtlType in the same conceptual row. If the method used allows applying the value contained in this object, then it MUST be applied. If the specified size is not appropriate for the chosen ping method, the implementation SHOULD use whatever size (appropriate to the method) is closest to the specified size. The maximum value for this object was computed by subtracting the smallest possible IP header size of 20 octets (IPv4 header with no options) and the UDP header size of 8 octets from the maximum IP packet size. An IP packet has a maximum size of 65535 octets (excluding IPv6 Jumbograms). |
Size list: 0 to 8100. |
|
1.3.6.1.2.1.80.1.2.1.6 |
pingCtlTimeOut |
Unsigned32{(1,60)} |
read-create |
Specifies the time-out value, in seconds, for a remote ping operation. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.2.1.80.1.2.1.7 |
pingCtlProbeCount |
Unsigned32{(1,15)} |
read-create |
Specifies the number of times to perform a ping operation at a remote host as part of a single ping test. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.2.1.80.1.2.1.8 |
pingCtlAdminStatus |
INTEGER{enabled(1),disabled(2)} |
read-create |
Reflects the desired state that a pingCtlEntry should be in: enabled(1) - Attempt to activate the test as defined by this pingCtlEntry. disabled(2) - Deactivate the test as defined by this pingCtlEntry. Refer to the corresponding pingResultsOperStatus to determine the operational state of the test defined by this entry. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.2.1.80.1.2.1.9 |
pingCtlDataFill |
OCTET STRING{(0,1024)} |
read-create |
The content of this object is used together with the corresponding pingCtlDataSize value to determine how to fill the data portion of a probe packet. The option of selecting a data fill pattern can be useful when links are compressed or have data pattern sensitivities. The contents of pingCtlDataFill should be repeated in a ping packet when the size of the data portion of the ping packet is greater than the size of pingCtlDataFill. |
Size list: 0 to 240. |
|
1.3.6.1.2.1.80.1.2.1.10 |
pingCtlFrequency |
Unsigned32 |
read-create |
The number of seconds to wait before repeating a ping test as defined by the value of the various objects in the corresponding row. A single ping test consists of a series of ping probes. The number of probes is determined by the value of the corresponding pingCtlProbeCount object. After a single test is completed the number of seconds as defined by the value of pingCtlFrequency MUST elapse before the next ping test is started. A value of 0 for this object implies that the test as defined by the corresponding entry will not be repeated. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.2.1.80.1.2.1.11 |
pingCtlMaxRows |
Unsigned32 |
read-create |
The maximum number of corresponding entries allowed in the pingProbeHistoryTable. An implementation of this MIB will remove the oldest corresponding entry in the pingProbeHistoryTable to allow the addition of an new entry once the number of corresponding rows in the pingProbeHistoryTable reaches this value. Old entries are not removed when a new test is started. Entries are added to the pingProbeHistoryTable until pingCtlMaxRows is reached before entries begin to be removed. A value of 0 for this object disables creation of pingProbeHistoryTable entries. |
Size list: 0 to 50. |
|
1.3.6.1.2.1.80.1.2.1.12 |
pingCtlStorageType |
INTEGER{other(1),volatile(2),nonVolatile(3),permanent(4),readOnly(5)} |
read-create |
The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row. |
The actually supported access is read-only. |
|
1.3.6.1.2.1.80.1.2.1.13 |
pingCtlTrapGeneration |
BITS{probeFailure(0),testFailure(1),testCompletion(2)} |
read-create |
The value of this object determines when and whether to generate a notification for this entry: probeFailure(0) - Generate a pingProbeFailed notification subject to the value of pingCtlTrapProbeFailureFilter. The object pingCtlTrapProbeFailureFilter can be used to specify the number of consecutive probe failures that are required before a pingProbeFailed notification can be generated. testFailure(1) - Generate a pingTestFailed notification. In this instance the object pingCtlTrapTestFailureFilter can be used to determine the number of probe failures that signal when a test fails. testCompletion(2) - Generate a pingTestCompleted notification. By default, no bits are set, indicating that none of the above options is selected. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.2.1.80.1.2.1.14 |
pingCtlTrapProbeFailureFilter |
Unsigned32{(0,15)} |
read-create |
The value of this object is used to determine when to generate a pingProbeFailed NOTIFICATION. Setting BIT probeFailure(0) of object pingCtlTrapGeneration to '1' implies that a pingProbeFailed NOTIFICATION is generated only when a number of consecutive ping probes equal to the value of pingCtlTrapProbeFailureFilter fail within a given ping test. After triggering the notification, the probe failure counter is reset to zero. |
Size list: 1 to 15. |
|
1.3.6.1.2.1.80.1.2.1.15 |
pingCtlTrapTestFailureFilter |
Unsigned32{(0,15)} |
read-create |
The value of this object is used to determine when to generate a pingTestFailed NOTIFICATION. Setting BIT testFailure(1) of object pingCtlTrapGeneration to '1' implies that a pingTestFailed NOTIFICATION is generated only when a number of consecutive ping tests equal to the value of pingCtlTrapProbeFailureFilter fail. After triggering the notification, the test failure counter is reset to zero. |
Size list: 1 to 15. |
|
1.3.6.1.2.1.80.1.2.1.16 |
pingCtlType |
OBJECT IDENTIFIER |
read-create |
The value of this object is used either to report or to select the implementation method to be used for calculating a ping response time. The value of this object MAY be selected from pingImplementationTypeDomains. Additional implementation types SHOULD be allocated as required by implementers of the DISMAN-PING-MIB under their enterprise-specific registration point and not beneath pingImplementationTypeDomains. |
The supported test types are:pingIcmpEcho,pingUdpEcho,pingSnmpQuery,,pingTcpConnectionAttempt. |
|
1.3.6.1.2.1.80.1.2.1.17 |
pingCtlDescr |
OCTET STRING{(0,255)} |
read-create |
The purpose of this object is to provide a descriptive name of the remote ping test. |
Size list: 0 to 240. |
|
1.3.6.1.2.1.80.1.2.1.18 |
pingCtlSourceAddressType |
INTEGER{unknown(0),ipv4(1),ipv6(2),ipv4z(3),ipv6z(4),dns(16)} |
read-create |
Specifies the type of the source address, pingCtlSourceAddress, to be used at a remote host when a ping operation is performed. |
Only support the setting of value 'ipv4(1)'. |
|
1.3.6.1.2.1.80.1.2.1.19 |
pingCtlSourceAddress |
OCTET STRING{(0,255)} |
read-create |
Use the specified IP address (which must be given in numeric form, not as a hostname) as the source address in outgoing probe packets. On hosts with more than one IP address, this option can be used to select the address to be used. If the IP address is not one of this machine's interface addresses, an error is returned and nothing is sent. A zero-length octet string value for this object disables source address specification. The address type (InetAddressType) that relates to this object is specified by the corresponding value of pingCtlSourceAddressType. |
Only support the ipv4 address. |
|
1.3.6.1.2.1.80.1.2.1.20 |
pingCtlIfIndex |
Integer32{(0,2147483647)} |
read-create |
Setting this object to an interface's ifIndex prior to starting a remote ping operation directs the ping probes to be transmitted over the specified interface. A value of zero for this object means that this option is not enabled. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.2.1.80.1.2.1.21 |
pingCtlByPassRouteTable |
INTEGER{true(1),false(2)} |
read-create |
The purpose of this object is to enable optional bypassing the route table. If enabled, the remote host will bypass the normal routing tables and send directly to a host on an attached network. If the host is not on a directly attached network, an error is returned. This option can be used to perform the ping operation to a local host through an interface that has no route defined (e.g., after the interface was dropped by the routing daemon at the host). |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.2.1.80.1.2.1.22 |
pingCtlDSField |
Unsigned32{(0,255)} |
read-create |
Specifies the value to store in the Type of Service (TOS) octet in the IPv4 header or in the Traffic Class octet in the IPv6 header, respectively, of the IP packet used to encapsulate the ping probe. The octet to be set in the IP header contains the Differentiated Services (DS) Field in the six most significant bits. This option can be used to determine what effect an explicit DS Field setting has on a ping response. Not all values are legal or meaningful. A value of 0 means that the function represented by this option is not supported. DS Field usage is often not supported by IP implementations, and not all values are supported. Refer to RFC 2474 and RFC 3260 for guidance on usage of this field. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.2.1.80.1.2.1.23 |
pingCtlRowStatus |
INTEGER{active(1),notInService(2),notReady(3),createAndGo(4),createAndWait(5),destroy(6)} |
read-create |
This object allows entries to be created and deleted in the pingCtlTable. Deletion of an entry in this table results in the deletion of all corresponding (same pingCtlOwnerIndex and pingCtlTestName index values) pingResultsTable and pingProbeHistoryTable entries. A value MUST be specified for pingCtlTargetAddress prior to acceptance of a transition to active(1) state. When a value for pingCtlTargetAddress is set, the value of object pingCtlRowStatus changes from notReady(3) to notInService(2). Activation of a remote ping operation is controlled via pingCtlAdminStatus, not by changing this object's value to active(1). Transitions in and out of active(1) state are not allowed while an entry's pingResultsOperStatus is active(1), with the exception that deletion of an entry in this table by setting its RowStatus object to destroy(6) will stop an active ping operation. The operational state of a ping operation can be determined by examination of its pingResultsOperStatus object. |
Do not support notInService(2),notReady(3),createAndWait(5). Do not support notInService(2),notReady(3),createAndWait(5). |
1.When creating this table, you must specify index pingCtlOwnerIndex and pingCtlTestName.
2.When setting the row, make sure to be accordant with the snmp v2 row-creating standard.
1.pingCtlRowStatus is set when the table row is created. At the same time, when the pingCtlAdminStatus of a row is modified for carrying out test, the system judges the status of the current test team according to the parameters of the already configured test team, and modifies the pingCtlRowStatus correspondingly.
2.When the test team is carrying out the service testing, that is, when the pingCtlAdminStatus is enabled, the parameters, except pingCtlAdminStatus, of the test team cannot be modified.
3.Among the parameters of the current test team, pingCtlTargetAddressType and pingCtlSourceAddressType support IPv4 and IPv6 only; pingCtlStorageType supports nonvolatile only.