HUAWEI-DISMAN-PING-MIB

All MIBs › HUAWEI-DISMAN-PING-MIB

Organization: Huawei Technologies co.,Ltd.

Last Updated: 2003-08-13

Category: Domain: Network Management, Vendor: Huawei

Description: Huawei distributed management ping MIB extending the DISMAN-PING-MIB for remote ping test scheduling and result collection on Huawei devices.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is HUAWEI-DISMAN-PING-MIB?

HUAWEI-DISMAN-PING-MIB is a Huawei-proprietary extension of the IETF's standard DISMAN-PING-MIB (RFC 2925), adding richer test-type support (TCP, UDP, DLSw, DHCP, FTP, HTTP, and jitter tests) beyond plain ICMP ping, per its module description. It defines five tables (hwPingCtlTable, hwpingResultsTable, hwPingJitterStatsTable, hwPingTcpServerTable, hwPingUdpServerTable) for configuring active reachability/latency tests and collecting their results, plus version and agent-enable status nodes. Its monitoring value is direct and software/network-path oriented: it lets an operator remotely trigger and read back latency, jitter, and reachability test results toward a target, which is a common tool for verifying service-path health and diagnosing performance degradation or outages from the device's perspective. It explicitly depends on and extends the standard DISMAN-PING-MIB (RFC 2925) framework. It is deployed on Huawei routers and switches used as active network-performance test agents in service-assurance and SLA-monitoring setups. Engineers can download the HUAWEI-DISMAN-PING-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in HUAWEI-DISMAN-PING-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Huawei router
Huawei switch

Monitoring Examples

An administrator would configure a test in hwPingCtlTable specifying a target and test type (e.g. jitter or HTTP), then poll hwpingResultsTable and hwPingJitterStatsTable for round-trip time, packet loss, and jitter statistics, catching a spike in latency or jitter that signals congestion or a failing path to the target. The hwPingTcpServerTable and hwPingUdpServerTable let the device act as a TCP/UDP test responder for tests initiated from elsewhere.

What Can Be Monitored

ping/test control configuration
round-trip time and packet loss results
jitter statistics
TCP/UDP test server status
ping agent enable state

Imported Objects

From DISMAN-PING-MIB

pingCtlEntry	OBJECT-TYPE
pingCtlOwnerIndex	OBJECT-TYPE
pingCtlTestName	OBJECT-TYPE

From HUAWEI-MIB

hwDatacomm

OBJECT-IDENTITY

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE
mib-2

From SNMPv2-TC

DateAndTime
DisplayString
RowStatus
TEXTUAL-CONVENTION
TimeStamp
Unsigned32

How to Use in IPNetwork Monitor

Example using hwPingJitterStatsNumOfRTT OID:

Select a Huawei router or switch (extended TCP/UDP/HTTP/jitter reachability tests) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type hwPingJitterStatsNumOfRTT into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of Jitter's that are successfully measured. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
hwDismanPing	1.3.6.1.4.1.2011.5.25.28			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.
INT hwPingAgentEnable	1.3.6.1.4.1.2011.5.25.28.1.5	INTEGER	read-write	Enable Huawei PING agent function
hwPingCtlEntry	1.3.6.1.4.1.2011.5.25.28.1.2.1		not-accessible	Defines an entry in the hwpingCtlTable. The operation of this table is same as that of pingResultsTable.
STR hwpingCtlFtpOperationString	1.3.6.1.4.1.2011.5.25.28.1.2.1.11	DisplayString	read-create	Ftp operation string.If the ftp operation type is get,the string will be file name that you will get from ftp server.
INT hwpingCtlFtpOperationType	1.3.6.1.4.1.2011.5.25.28.1.2.1.8	INTEGER	read-create	Ftp operation type:get or put
STR hwpingCtlFtpPassword	1.3.6.1.4.1.2011.5.25.28.1.2.1.10	DisplayString	read-create	Ftp password.
STR hwpingCtlFtpUsername	1.3.6.1.4.1.2011.5.25.28.1.2.1.9	DisplayString	read-create	Ftp username
STR hwpingCtlHttpOperationString	1.3.6.1.4.1.2011.5.25.28.1.2.1.7	DisplayString	read-create	Http operation string.for example,if you choose get operation type,the string will be url , home page and http version.
INT hwpingCtlHttpOperationType	1.3.6.1.4.1.2011.5.25.28.1.2.1.6	INTEGER	read-create	Http operation type:get or post.
I32 hwpingCtlJitterAdminInterval	1.3.6.1.4.1.2011.5.25.28.1.2.1.4	Integer32	read-create	This 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.
I32 hwpingCtlJitterAdminNumPackets	1.3.6.1.4.1.2011.5.25.28.1.2.1.5	Integer32	read-create	This 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.
I32 hwpingCtlSourcePort	1.3.6.1.4.1.2011.5.25.28.1.2.1.2	Integer32	read-create	This 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.
hwPingCtlTable	1.3.6.1.4.1.2011.5.25.28.1.2		not-accessible	Defines the ping Control Extend Table for providing, via SNMP, the capability of performing ping operations at a remote host.
I32 hwpingCtlTargetPort	1.3.6.1.4.1.2011.5.25.28.1.2.1.1	Integer32	read-create	This object represents the target's port number. This object is applicable to udpEcho, tcpConnect and jitter probes.
I32 hwpingCtlTTL	1.3.6.1.4.1.2011.5.25.28.1.2.1.3	Integer32	read-create	Specifies the value to store in the TTL Field in the IP packet used to encapsulate the ping probe.
STR hwpingCtlVPNInstance	1.3.6.1.4.1.2011.5.25.28.1.2.1.12	DisplayString	read-create	This 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.
hwpingdhcp	1.3.6.1.4.1.2011.5.25.28.2.6			Indicates 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.
hwpingdlsw	1.3.6.1.4.1.2011.5.25.28.2.5			Indicates 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.
hwpingftp	1.3.6.1.4.1.2011.5.25.28.2.7			Indicates that an implementation is using tcp for connect & data transfer.
hwpingHttp	1.3.6.1.4.1.2011.5.25.28.2.4			Indicates 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
hwPingImplementationTypeDomains	1.3.6.1.4.1.2011.5.25.28.2
hwpingjitter	1.3.6.1.4.1.2011.5.25.28.2.3			Indicates that an implementation is using udp for packet transfers. 'jitter' will cause the PING application to perform delay variance analysis.
G32 hwPingJitterStatsAveNegativesDS	1.3.6.1.4.1.2011.5.25.28.1.4.1.27	Gauge32	read-only	The average of RTT's of all negative jitter values from packets sent from destination to source.
G32 hwPingJitterStatsAveNegativesSD	1.3.6.1.4.1.2011.5.25.28.1.4.1.25	Gauge32	read-only	The average of all negative jitter values from packets sent from source to destination.
G32 hwPingJitterStatsAvePositivesDS	1.3.6.1.4.1.2011.5.25.28.1.4.1.26	Gauge32	read-only	The average of RTT's of all positive jitter values from packets sent from destination to source.
G32 hwPingJitterStatsAvePositivesSD	1.3.6.1.4.1.2011.5.25.28.1.4.1.24	Gauge32	read-only	The average of RTT's of all positive jitter values from packets sent from source to destination.
hwPingJitterStatsEntry	1.3.6.1.4.1.2011.5.25.28.1.4.1		not-accessible	A table which contains the status of latest Jitter operation. This entry is created only if the pingCtlType is hwpingjitter.
G32 hwPingJitterStatsMaxOfNegativesDS	1.3.6.1.4.1.2011.5.25.28.1.4.1.18	Gauge32	read-only	The maximum of all negative jitter values from packets sent from destination to source.
G32 hwPingJitterStatsMaxOfNegativesSD	1.3.6.1.4.1.2011.5.25.28.1.4.1.8	Gauge32	read-only	The maximum of absolute values of all negative jitter values from packets sent from source to destination.
G32 hwPingJitterStatsMaxOfPositivesDS	1.3.6.1.4.1.2011.5.25.28.1.4.1.13	Gauge32	read-only	The maximum of all positive jitter values from packets sent from destination to source.
G32 hwPingJitterStatsMaxOfPositivesSD	1.3.6.1.4.1.2011.5.25.28.1.4.1.3	Gauge32	read-only	The maximum of all positive jitter values from packets sent from source to destination.
G32 hwPingJitterStatsMinOfNegativesDS	1.3.6.1.4.1.2011.5.25.28.1.4.1.17	Gauge32	read-only	The minimum of all negative jitter values from packets sent from destination to source.
G32 hwPingJitterStatsMinOfNegativesSD	1.3.6.1.4.1.2011.5.25.28.1.4.1.7	Gauge32	read-only	The minimum of absolute values of all negative jitter values from packets sent from source to destination.
G32 hwPingJitterStatsMinOfPositivesDS	1.3.6.1.4.1.2011.5.25.28.1.4.1.12	Gauge32	read-only	The minimum of all positive jitter values from packets sent from destination to source.
G32 hwPingJitterStatsMinOfPositivesSD	1.3.6.1.4.1.2011.5.25.28.1.4.1.2	Gauge32	read-only	The minimum of all positive jitter values from packets sent from source to destination.
G32 hwPingJitterStatsNumOfNegativesDS	1.3.6.1.4.1.2011.5.25.28.1.4.1.19	Gauge32	read-only	The sum of number of all negative jitter values from packets sent from destination to source.
G32 hwPingJitterStatsNumOfNegativesSD	1.3.6.1.4.1.2011.5.25.28.1.4.1.9	Gauge32	read-only	The sum of number of all negative jitter values from packets sent from source to destination.
G32 hwPingJitterStatsNumOfPositivesDS	1.3.6.1.4.1.2011.5.25.28.1.4.1.14	Gauge32	read-only	The sum of number of all positive jitter values from packets sent from destination to source.
G32 hwPingJitterStatsNumOfPositivesSD	1.3.6.1.4.1.2011.5.25.28.1.4.1.4	Gauge32	read-only	The sum of number of all positive jitter values from packets sent from source to destination.
C32 hwPingJitterStatsNumOfRTTEx	1.3.6.1.4.1.2011.5.25.28.1.4.1.1	Counter32	read-only	The number of Jitter's that are successfully measured.
G32 hwPingJitterStatsPacketLossDS	1.3.6.1.4.1.2011.5.25.28.1.4.1.23	Gauge32	read-only	The number of packets lost when sent from destination to source.
G32 hwPingJitterStatsPacketLossSD	1.3.6.1.4.1.2011.5.25.28.1.4.1.22	Gauge32	read-only	The number of packets lost when sent from source to destination.
G32 hwPingJitterStatsPktLossUnknown	1.3.6.1.4.1.2011.5.25.28.1.4.1.28	Gauge32	read-only	The number of packets which lost but not knowing result .
G32 hwPingJitterStatsSum2NegativesDS	1.3.6.1.4.1.2011.5.25.28.1.4.1.21	Gauge32	read-only	The sum of squares of RTT's of all negative jitter values from packets sent from destination to source.
G32 hwPingJitterStatsSum2NegativesSD	1.3.6.1.4.1.2011.5.25.28.1.4.1.11	Gauge32	read-only	The sum of square of RTT's of all negative jitter values from packets sent from source to destination.
G32 hwPingJitterStatsSum2PositivesDS	1.3.6.1.4.1.2011.5.25.28.1.4.1.16	Gauge32	read-only	The sum of squares of RTT's of all positive jitter values from packets sent from destination to source.
G32 hwPingJitterStatsSum2PositivesSD	1.3.6.1.4.1.2011.5.25.28.1.4.1.6	Gauge32	read-only	The sum of square of RTT's of all positive jitter values from packets sent from source to destination.
G32 hwPingJitterStatsSumOfNegativesDS	1.3.6.1.4.1.2011.5.25.28.1.4.1.20	Gauge32	read-only	The sum of RTT's of all negative jitter values from packets sent from destination to source.
G32 hwPingJitterStatsSumOfNegativesSD	1.3.6.1.4.1.2011.5.25.28.1.4.1.10	Gauge32	read-only	The sum of all negative jitter values from packets sent from source to destination.
G32 hwPingJitterStatsSumOfPositivesDS	1.3.6.1.4.1.2011.5.25.28.1.4.1.15	Gauge32	read-only	The sum of RTT's of all positive jitter values from packets sent from destination to source.
G32 hwPingJitterStatsSumOfPositivesSD	1.3.6.1.4.1.2011.5.25.28.1.4.1.5	Gauge32	read-only	The sum of RTT's of all positive jitter values from packets sent from source to destination.
hwPingJitterStatsTable	1.3.6.1.4.1.2011.5.25.28.1.4		not-accessible	A table which contains the status of latest Jitter operation.
STR hwPingMIBVersion	1.3.6.1.4.1.2011.5.25.28.1.1	DisplayString	read-only	Huawei PING MIB version string. The format will be: 'Version.Release.Patch: Textual-Description' For example: '1.0.0: Initial Ping MIB'
hwPingObjects	1.3.6.1.4.1.2011.5.25.28.1
hwpingResultsEntry	1.3.6.1.4.1.2011.5.25.28.1.3.1		not-accessible	The operation of this table is same as that of pingResultsTable.
G32 hwpingResultsLostPacketRatio	1.3.6.1.4.1.2011.5.25.28.1.3.1.10	Gauge32	read-only	The 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.
G32 hwpingResultsMaxDelayDS	1.3.6.1.4.1.2011.5.25.28.1.3.1.9	Gauge32	read-only	The 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.
G32 hwpingResultsMaxDelaySD	1.3.6.1.4.1.2011.5.25.28.1.3.1.8	Gauge32	read-only	The 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.
G32 hwpingResultsRttBusies	1.3.6.1.4.1.2011.5.25.28.1.3.1.3	Gauge32	read-only	The 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).
G32 hwpingResultsRttDrops	1.3.6.1.4.1.2011.5.25.28.1.3.1.5	Gauge32	read-only	The 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.
G32 hwpingResultsRttNoConnections	1.3.6.1.4.1.2011.5.25.28.1.3.1.4	Gauge32	read-only	When 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.
G32 hwpingResultsRttNumDisconnects	1.3.6.1.4.1.2011.5.25.28.1.3.1.1	Gauge32	read-only	When 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.
G32 hwpingResultsRttSequenceErrors	1.3.6.1.4.1.2011.5.25.28.1.3.1.6	Gauge32	read-only	When 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 detected
G32 hwpingResultsRttStatsErrors	1.3.6.1.4.1.2011.5.25.28.1.3.1.7	Gauge32	read-only	The number of some other errors
G32 hwpingResultsRttTimeouts	1.3.6.1.4.1.2011.5.25.28.1.3.1.2	Gauge32	read-only	The 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.
hwpingResultsTable	1.3.6.1.4.1.2011.5.25.28.1.3		not-accessible	Defines 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.
INT hwPingServerEnable	1.3.6.1.4.1.2011.5.25.28.1.8	INTEGER	read-write	Enable Huawei PING server function
hwpingTcpconnect	1.3.6.1.4.1.2011.5.25.28.2.2			Indicates 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.
hwPingTcpServerEntry	1.3.6.1.4.1.2011.5.25.28.1.6.1		not-accessible	A 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.
IP hwPingTcpServerIpAddress	1.3.6.1.4.1.2011.5.25.28.1.6.1.1	InetAddress	not-accessible	This object represents the tcp server's ip address. This object and hwpingTcpServerPort is hwPingTcpServerTable index.
I32 hwPingTcpServerPort	1.3.6.1.4.1.2011.5.25.28.1.6.1.2	Integer32	not-accessible	This object represents the tcp server's port number. This object and hwPingTcpServerIpAddress is hwPingTcpServerTable index.
ROW hwpingTcpServerRowStatus	1.3.6.1.4.1.2011.5.25.28.1.6.1.4	RowStatus	read-create	This 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.
hwPingTcpServerTable	1.3.6.1.4.1.2011.5.25.28.1.6		not-accessible	A table which contains the status of hwping tcp server configuration information.
STR hwpingTcpServerVPNInstance	1.3.6.1.4.1.2011.5.25.28.1.6.1.3	DisplayString	not-accessible	This 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.
hwpingUdpEcho	1.3.6.1.4.1.2011.5.25.28.2.1			Indicates that an implementation is using the UDP based echo server. Notes: The hwpingCtlTargetPort and hwpingCtlSourcePort need to be set.
hwPingUdpServerEntry	1.3.6.1.4.1.2011.5.25.28.1.7.1		not-accessible	A 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.
IP hwPingUdpServerIpAddress	1.3.6.1.4.1.2011.5.25.28.1.7.1.1	InetAddress	not-accessible	This object represents the udp server's ip address. This object and hwpingUdpServerPort is hwPingUdpServerEntry index.
I32 hwPingUdpServerPort	1.3.6.1.4.1.2011.5.25.28.1.7.1.2	Integer32	not-accessible	This object represents the udp server's port number. This object and hwPingUdpServerIpAddress is hwPingUdpServerEntry index.
ROW hwpingUdpServerRowStatus	1.3.6.1.4.1.2011.5.25.28.1.7.1.4	RowStatus	read-create	This 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.
hwPingUdpServerTable	1.3.6.1.4.1.2011.5.25.28.1.7		not-accessible	A table which contains the status of hwping udp server configuration information.
STR hwpingUdpServerVPNInstance	1.3.6.1.4.1.2011.5.25.28.1.7.1.3	DisplayString	not-accessible	This 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.

RFC description

Extended PING diagnostic MIB for Huawei devices supporting TCP, UDP, DLSW, DHCP, FTP, HTTP and jitter testing.

Start monitoring Huawei router or switch (extended TCP/UDP/HTTP/jitter reachability tests) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download HUAWEI-DISMAN-PING-MIB