HUAWEI-DISMAN-PING-MIB
AI MIB Summary
The HUAWEI-DISMAN-PING-MIB extends the standard DISMAN-PING-MIB on Huawei network devices to enable advanced connectivity testing and monitoring for TCP, UDP, DLSP, DHCP, FTP, HTTP, and jitter metrics via five control and result tables. It manages probe configurations and server states through specific control nodes, providing granular visibility into protocol-specific reachability and performance statistics beyond basic ICMP ping capabilities.
This private mib file includes the test information of the device. It is supplementary for DISMAN-PING-MIB(rfc2925). By setting more parameters you can finish more types test such as tcp, udp, dlsw, dhcp, ftp, http and jitter . This mib contains 5 tables: hwPingCtlTable, hwpingResultsTable, hwPingJitterStatsTable, hwPingTcpServerTable, hwPingUdpServerTable, and 3 nodes: hwPingMIBVersion, hwPingAgentEnable, hwPingServerEnable.
Main OID:
hwDismanPing.1.3.6.1.4.1.2011.5.25.28
81
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
81 total| Object Name |
|---|
hwDismanPingThis private mib file includes the test information of the device.
It is supplementary for DISMAN-PING-MIB(rfc2925). By setting more
parameters you can finish more types test such as tcp, udp, dlsw,
dhcp, ftp, http and jitter .
This mib contains 5 tables:
hwPingCtlTable,
hwpingResultsTable,
hwPingJitterStatsTable,
hwPingTcpServerTable,
hwPingUdpServerTable,
and 3 nodes:
hwPingMIBVersion,
hwPingAgentEnable,
hwPingServerEnable. MODULE-IDENTITY .1.3.6.1.4.1.2011.5.25.28 |
hwPingObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2011.5.25.28.1 |
hwPingMIBVersionHuawei PING MIB version string.
The format will be:
'Version.Release.Patch: Textual-Description'
For example: '1.0.0: Initial Ping MIB'ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.2011.5.25.28.1.1 |
hwPingCtlTableDefines the ping Control Extend Table for providing, via SNMP,
the capability of performing ping operations at
a remote host. SEQUENCE OF HWPingCtlEntry .1.3.6.1.4.1.2011.5.25.28.1.2 |
hwPingCtlEntryDefines an entry in the hwpingCtlTable. The operation of this
table is same as that of pingResultsTable. HWPingCtlEntry .1.3.6.1.4.1.2011.5.25.28.1.2.1 |
hwpingCtlTargetPortThis object represents the target's port number. This
object is applicable to udpEcho, tcpConnect and jitter probes.rw Integer32 .1.3.6.1.4.1.2011.5.25.28.1.2.1.1 |
hwpingCtlSourcePortThis object represents the source's port number. If this
object is not specified, the application will get a
port allocated by the system. This object is applicable
to all probes except dns, dlsw.rw Integer32 .1.3.6.1.4.1.2011.5.25.28.1.2.1.2 |
hwpingCtlTTLSpecifies the value to store in the TTL Field in the IP packet used to
encapsulate the ping probe.rw Integer32 .1.3.6.1.4.1.2011.5.25.28.1.2.1.3 |
hwpingCtlJitterAdminIntervalThis value represents the inter-packet delay between packets
and is in milliseconds. This value is currently used for
Jitter probe. This object is applicable to jitter probe only.rw Integer32 UNITS "milliseconds" .1.3.6.1.4.1.2011.5.25.28.1.2.1.4 |
hwpingCtlJitterAdminNumPacketsThis value represents the number of packets that need to be
transmitted. This value is currently used for Jitter probe.
This object is applicable to jitter probe only.rw Integer32 .1.3.6.1.4.1.2011.5.25.28.1.2.1.5 |
hwpingCtlHttpOperationTypeHttp operation type:get or post.rw Enumeration .1.3.6.1.4.1.2011.5.25.28.1.2.1.6 |
hwpingCtlHttpOperationStringHttp operation string.for example,if you choose get operation type,the string will be
url , home page and http version.rw DisplayString .1.3.6.1.4.1.2011.5.25.28.1.2.1.7 |
hwpingCtlFtpOperationTypeFtp operation type:get or putrw Enumeration .1.3.6.1.4.1.2011.5.25.28.1.2.1.8 |
hwpingCtlFtpUsernameFtp usernamerw DisplayString .1.3.6.1.4.1.2011.5.25.28.1.2.1.9 |
hwpingCtlFtpPasswordFtp password.rw DisplayString .1.3.6.1.4.1.2011.5.25.28.1.2.1.10 |
hwpingCtlFtpOperationStringFtp operation string.If the ftp operation type is get,the string will be file name
that you will get from ftp server.rw DisplayString .1.3.6.1.4.1.2011.5.25.28.1.2.1.11 |
hwpingCtlVPNInstanceThis field is used to specify the VPN name in which the PING operation will be userd.
The agent will use the field to identify the VPN routing Table for this operation.rw DisplayString .1.3.6.1.4.1.2011.5.25.28.1.2.1.12 |
hwpingResultsTableDefines the Ping Results Extend Table for providing
the capability of performing ping operations at
a remote host. The results of these operations are
stored in the hwpingResultsTable . The operation of this
table is same as that of pingResultsTable. SEQUENCE OF HWPingResultsEntry .1.3.6.1.4.1.2011.5.25.28.1.3 |
hwpingResultsEntryThe operation of this table is same as that of pingResultsTable. HWPingResultsEntry .1.3.6.1.4.1.2011.5.25.28.1.3.1 |
hwpingResultsRttNumDisconnectsWhen the pingCtlType is 'icmpecho' , this
object represents the number of times that the target or
hop along the path to a target became disconnected. For
all other values of pingCtlType, this object will
remain zero.
For connectionless protocols this has no meaning,
and will consequently remain 0.
Since this error does not indicate any information about
the failure of an PING operation, no response time
information for this instance will be recorded in the
appropriate objects.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.3.1.1 |
hwpingResultsRttTimeoutsThe number of occasions when a PING operation was not
completed before a timeout occurred, i.e.
pingCtlTimeOut was exceeded.
Since the PING operation was never completed, the
completion time of these operations are not accumulated.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.3.1.2 |
hwpingResultsRttBusiesThe number of occasions when a PING operation could not
be initiated because a previous PING operation has not
been completed.
When the pingCtlType is 'pathEcho' this can occur for
both connection oriented protocols and connectionless
protocols.
When the initiation of a new operation cannot be started,
this object will be incremented and the operation will be
omitted. (The next operation will start at the next
Frequency).ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.3.1.3 |
hwpingResultsRttNoConnectionsWhen the pingCtlType is 'icmpecho' this is
the number of occasions when a PING operation could not be
initiated because the connection to the target has not
been established. For all other pingCtlTypes this
object will remain zero.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.3.1.4 |
hwpingResultsRttDropsThe number of occasions when a PING operation could not
be initiated because some necessary internal resource
(for example memory) was not available,or the operation
completion could not be recognized.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.3.1.5 |
hwpingResultsRttSequenceErrorsWhen the pingCtlType is 'icmpecho' this is
the number of PING operation completions received with
an unexpected sequence identifier. For all other values
of pingCtlType this object will remain zero.
When this has occurred some of the possible reasons may
be:
- a duplicate packet was received
- a response was received after it had timed-out
- a corrupted packet was received and was not detectedro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.3.1.6 |
hwpingResultsRttStatsErrorsThe number of some other errorsro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.3.1.7 |
hwpingResultsMaxDelaySDThe maximal delay from source device to destination device.
Currently this value is only used for JITTER test, and this
value must be 0 in other type test. In JITTER test, if
destination system time is not valid, the SD delay may be set 0.ro Gauge32 UNITS "milliseconds" .1.3.6.1.4.1.2011.5.25.28.1.3.1.8 |
hwpingResultsMaxDelayDSThe maximal delay from destination device to source device.
Currently this value is only used for JITTER test, and this
value is 0 in other type test. In JITTER test, if destination
system time is not valid, the DS delay may be set 0.ro Gauge32 UNITS "milliseconds" .1.3.6.1.4.1.2011.5.25.28.1.3.1.9 |
hwpingResultsLostPacketRatioThe value of this object reflects the drop rate of HWPing test.
For example, this value is 30 that means source device only
had received 70% packets of total sent packets.ro Gauge32 UNITS "milliseconds" .1.3.6.1.4.1.2011.5.25.28.1.3.1.10 |
hwPingJitterStatsTableA table which contains the status of latest Jitter
operation. SEQUENCE OF HWPingJitterStatsEntry .1.3.6.1.4.1.2011.5.25.28.1.4 |
hwPingJitterStatsEntryA table which contains the status of latest Jitter
operation.
This entry is created only if the pingCtlType
is hwpingjitter. HWPingJitterStatsEntry .1.3.6.1.4.1.2011.5.25.28.1.4.1 |
hwPingJitterStatsNumOfRTTThe number of Jitter's that are successfully measured.ro Counter32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.1 |
hwPingJitterStatsMinOfPositivesSDThe minimum of all positive jitter values from packets sent
from source to destination.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.2 |
hwPingJitterStatsMaxOfPositivesSDThe maximum of all positive jitter values from packets sent
from source to destination.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.3 |
hwPingJitterStatsNumOfPositivesSDThe sum of number of all positive jitter values from packets
sent from source to destination.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.4 |
hwPingJitterStatsSumOfPositivesSDThe sum of RTT's of all positive jitter values from packets
sent from source to destination.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.5 |
hwPingJitterStatsSum2PositivesSDThe sum of square of RTT's of all positive jitter values from
packets sent from source to destination.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.6 |
hwPingJitterStatsMinOfNegativesSDThe minimum of absolute values of all negative jitter values
from packets sent from source to destination.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.7 |
hwPingJitterStatsMaxOfNegativesSDThe maximum of absolute values of all negative jitter values
from packets sent from source to destination.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.8 |
hwPingJitterStatsNumOfNegativesSDThe sum of number of all negative jitter values from packets
sent from source to destination.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.9 |
hwPingJitterStatsSumOfNegativesSDThe sum of all negative jitter values from packets
sent from source to destination.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.10 |
hwPingJitterStatsSum2NegativesSDThe sum of square of RTT's of all negative jitter values from
packets sent from source to destination.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.11 |
hwPingJitterStatsMinOfPositivesDSThe minimum of all positive jitter values from packets sent
from destination to source.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.12 |
hwPingJitterStatsMaxOfPositivesDSThe maximum of all positive jitter values from packets sent
from destination to source.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.13 |
hwPingJitterStatsNumOfPositivesDSThe sum of number of all positive jitter values from packets
sent from destination to source.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.14 |
hwPingJitterStatsSumOfPositivesDSThe sum of RTT's of all positive jitter values from packets
sent from destination to source.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.15 |
hwPingJitterStatsSum2PositivesDSThe sum of squares of RTT's of all positive jitter values from
packets sent from destination to source.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.16 |
hwPingJitterStatsMinOfNegativesDSThe minimum of all negative jitter values from packets sent
from destination to source.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.17 |
hwPingJitterStatsMaxOfNegativesDSThe maximum of all negative jitter values from packets sent
from destination to source.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.18 |
hwPingJitterStatsNumOfNegativesDSThe sum of number of all negative jitter values from packets
sent from destination to source.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.19 |
hwPingJitterStatsSumOfNegativesDSThe sum of RTT's of all negative jitter values from packets
sent from destination to source.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.20 |
hwPingJitterStatsSum2NegativesDSThe sum of squares of RTT's of all negative jitter values from
packets sent from destination to source.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.21 |
hwPingJitterStatsPacketLossSDThe number of packets lost when sent from source to destination.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.22 |
hwPingJitterStatsPacketLossDSThe number of packets lost when sent from destination to source.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.23 |
hwPingJitterStatsAvePositivesSDThe average of RTT's of all positive jitter values from packets
sent from source to destination.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.24 |
hwPingJitterStatsAveNegativesSDThe average of all negative jitter values from packets
sent from source to destination.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.25 |
hwPingJitterStatsAvePositivesDSThe average of RTT's of all positive jitter values from packets
sent from destination to source.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.26 |
hwPingJitterStatsAveNegativesDSThe average of RTT's of all negative jitter values from packets
sent from destination to source.ro Gauge32 .1.3.6.1.4.1.2011.5.25.28.1.4.1.27 |
hwPingJitterStatsPktLossUnknownThe number of packets which lost but not knowing result .ro Gauge32 UNITS "milliseconds" .1.3.6.1.4.1.2011.5.25.28.1.4.1.28 |
hwPingAgentEnableEnable Huawei PING agent functionrw Enumeration .1.3.6.1.4.1.2011.5.25.28.1.5 |
hwPingTcpServerTableA table which contains the status of hwping tcp server
configuration information. SEQUENCE OF HWPingTcpServerEntry .1.3.6.1.4.1.2011.5.25.28.1.6 |
hwPingTcpServerEntryA table which contains the status of hwping tcp server
configuration information.
This entry is includeed not only the tcp server ip address
but also the tcp server udp port. If used for VPN it is also
included the VPN name. HWPingTcpServerEntry .1.3.6.1.4.1.2011.5.25.28.1.6.1 |
hwPingTcpServerIpAddressThis object represents the tcp server's ip address.
This object and hwpingTcpServerPort is hwPingTcpServerTable
index. InetAddress .1.3.6.1.4.1.2011.5.25.28.1.6.1.1 |
hwPingTcpServerPortThis object represents the tcp server's port number.
This object and hwPingTcpServerIpAddress is hwPingTcpServerTable
index. Integer32 .1.3.6.1.4.1.2011.5.25.28.1.6.1.2 |
hwpingTcpServerVPNInstanceThis field is used to specify the VPN name in which the PING operation will be userd.
The TCP server will use the field to identify the VPN routing Table for this operation. DisplayString .1.3.6.1.4.1.2011.5.25.28.1.6.1.3 |
hwpingTcpServerRowStatusThis object allows entries to be created and deleted
in the hwPingTcpServerTable.
A value MUST be specified for hwPingTcpServerIpAddress
and hwPingTcpServerPort prior to a transition to
active(1) state being accepted.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2011.5.25.28.1.6.1.4 |
hwPingUdpServerTableA table which contains the status of hwping udp server
configuration information. SEQUENCE OF HWPingUdpServerEntry .1.3.6.1.4.1.2011.5.25.28.1.7 |
hwPingUdpServerEntryA table which contains the status of hwping udp server
configuration information.
This entry is includeed not only the udp server ip address
but also the udp server udp port.If used for VPN it is also
included the VPN name. HWPingUdpServerEntry .1.3.6.1.4.1.2011.5.25.28.1.7.1 |
hwPingUdpServerIpAddressThis object represents the udp server's ip address.
This object and hwpingUdpServerPort is hwPingUdpServerEntry
index. InetAddress .1.3.6.1.4.1.2011.5.25.28.1.7.1.1 |
hwPingUdpServerPortThis object represents the udp server's port number.
This object and hwPingUdpServerIpAddress is hwPingUdpServerEntry
index. Integer32 .1.3.6.1.4.1.2011.5.25.28.1.7.1.2 |
hwpingUdpServerVPNInstanceThis field is used to specify the VPN name in which the PING operation will be userd.
The UDP server will use the field to identify the VPN routing Table for this operation. DisplayString .1.3.6.1.4.1.2011.5.25.28.1.7.1.3 |
hwpingUdpServerRowStatusThis object allows entries to be created and deleted
in the hwPingUdpServerTable.
A value MUST be specified for hwPingUdpServerIpAddress
and hwPingUdpServerPort prior to a transition to
active(1) state being accepted.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2011.5.25.28.1.7.1.4 |
hwPingServerEnableEnable Huawei PING server functionrw Enumeration .1.3.6.1.4.1.2011.5.25.28.1.8 |
hwPingImplementationTypeDomains OBJECT IDENTIFIER .1.3.6.1.4.1.2011.5.25.28.2 |
hwpingUdpEchoIndicates that an implementation is using the UDP based echo server.
Notes: The hwpingCtlTargetPort and hwpingCtlSourcePort need to be set. OBJECT IDENTIFIER .1.3.6.1.4.1.2011.5.25.28.2.1 |
hwpingTcpconnectIndicates that an implementation is attempting to
connect to a TCP port in order to calculate a round
trip time.
Notes: The hwpingCtlTargetPort and hwpingCtlSourcePort need to be set. OBJECT IDENTIFIER .1.3.6.1.4.1.2011.5.25.28.2.2 |
hwpingjitterIndicates that an implementation is using udp for packet transfers.
'jitter' will cause the PING application to perform delay variance analysis. OBJECT IDENTIFIER .1.3.6.1.4.1.2011.5.25.28.2.3 |
hwpingHttpIndicates that an implementation is using udp for name resolution,
tcp connect and tcp data transfer mechanisms for HTTP data download
from a particular HTTP Server.
it cause the PING application to perform a download of the object specified in the URL OBJECT IDENTIFIER .1.3.6.1.4.1.2011.5.25.28.2.4 |
hwpingdlswIndicates that an implementation is using tcp for sending keepalives.
'dlsw' will cause the PING application to perform a keepalive operation
to measure the response time of a DLSw peer. OBJECT IDENTIFIER .1.3.6.1.4.1.2011.5.25.28.2.5 |
hwpingdhcpIndicates that an implementation is using udp for sending dhcp requests.
'dhcp' will cause the PING application
to perform an IP Address lease request/teardown operation. OBJECT IDENTIFIER .1.3.6.1.4.1.2011.5.25.28.2.6 |
hwpingftpIndicates that an implementation is using tcp for connect & data transfer. OBJECT IDENTIFIER .1.3.6.1.4.1.2011.5.25.28.2.7 |