Contents

DISMAN-TRACEROUTE-MIB· 1

About this MIB· 1

MIB file name· 1

Notifications· 1

traceRoutePathChange· 1

traceRouteTestFailed· 2

traceRouteTestCompleted· 4

 

DISMAN-TRACEROUTE-MIB

About this MIB

This MIB contains information about the traceroute (tracert) utility defined by RFC 4560 and the traceroute notifications. The traceroute utility is implemented by NQA UDP traceroute operations.

MIB file name

rfc4560-disman-traceroute.mib

Notifications

traceRoutePathChange

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.81.0.1	The traceroute path changed.	Informational	Warning	N/A	OFF

 

Notification triggers

This notification is generated if the path obtained by the current traceroute operation is different from the path obtained by the last traceroute operation.

System impact

No impact on the system.

Status control

ON

CLI: Use the reaction trap path-change command.

OFF

CLI: Use the undo reaction trap path-change command.

Objects

OID (object name)	Description	Index nodes	Type	Value range
1.3.6.1.2.1.81.1.2.1.3 (traceRouteCtlTargetAddressType)	Destination address type.	traceRouteCtlOwnerIndex traceRouteCtlTestName	InetAddressType	Standard MIB values.
1.3.6.1.2.1.81.1.2.1.4 (traceRouteCtlTargetAddress)	Destination address.	traceRouteCtlOwnerIndex traceRouteCtlTestName	InetAddress	Standard MIB values.
1.3.6.1.2.1.81.1.3.1.4 (traceRouteResultsIpTgtAddrType)	Destination address type in the probe result.	traceRouteCtlOwnerIndex traceRouteCtlTestName	InetAddressType	Standard MIB values.
1.3.6.1.2.1.81.1.3.1.5 (traceRouteResultsIpTgtAddr)	Destination address in the probe result.	traceRouteCtlOwnerIndex traceRouteCtlTestName	InetAddress	Standard MIB values.

 

Recommended action

No action is required.

traceRouteTestFailed

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.81.0.2	A traceroute operation failed.	Informational	Warning	N/A	OFF

 

Notification triggers

This notification is generated when a traceroute operation fails. The following might be operation failure reasons:

·     The destination address does not exist.

·     The destination address exists but is unreachable.

·     The destination address exists and is reachable. However, the number of hops for probe packets of the traceroute operation to reach the destination address exceeds the maximum number of hops that the probe packets can traverse.

·     The network latency is large and the round-trip time of packets is larger than the specified timeout time.

System impact

No impact on the system.

Status control

ON

CLI: Use the reaction trap test-failure [ accumulate-probe-failures ] command.

OFF

CLI: Use the undo reaction trap test-failure [ accumulate-probe-failures ] command.

Objects

OID (object name)	Description	Index nodes	Type	Value range
1.3.6.1.2.1.81.1.2.1.3 (traceRouteCtlTargetAddressType)	Destination address type.	traceRouteCtlOwnerIndex traceRouteCtlTestName	InetAddressType	Standard MIB values.
1.3.6.1.2.1.81.1.2.1.4 (traceRouteCtlTargetAddress)	Destination address.	traceRouteCtlOwnerIndex traceRouteCtlTestName	InetAddress	Standard MIB values.
1.3.6.1.2.1.81.1.3.1.4 (traceRouteResultsIpTgtAddrType)	Destination address type in the probe result.	traceRouteCtlOwnerIndex traceRouteCtlTestName	InetAddressType	Standard MIB values.
1.3.6.1.2.1.81.1.3.1.5 (traceRouteResultsIpTgtAddr)	Destination address in the probe result.	traceRouteCtlOwnerIndex traceRouteCtlTestName	InetAddress	Standard MIB values.

 

Recommended action

1.     In NQA operation view, execute the display this command to identify whether the destination address is configured correctly.

¡     If the destination address is correct, go to step 2.

¡     If the destination address is incorrect, execute the destination ip command to change the destination address, and then perform the traceroute operation again.

-     If no notification is generated, the issue is cleared.

-     If the notification is generated, go to step 2.

2.     In NQA operation view, execute the ping command to identify whether the destination address is reachable.

¡     If the destination address is reachable, go to step 3.

¡     If the destination address is unreachable, locate routing issues. For example, execute the display ip routing-table command to verify routing table information.

3.     In NQA operation view, execute the display this command to display the maximum number of hops that the probe packets can traverse. You can execute the ttl command to change the maximum number as needed. Then, perform the traceroute operation again.

¡     If no notification is generated, the issue is cleared.

¡     If the notification is generated, go to step 4.

4.     In NQA operation view, execute the probe timeout command to set the probe timeout time, and then perform the traceroute operation again.

¡     If no notification is generated, the issue is cleared.

¡     If the notification is generated, go to step 5.

5.     Verify that the settings are correct on the destination device and the intermediate devices between the source and destination devices.

¡     IPv4:

-     Enable sending ICMP time exceeded messages on the intermediate devices between the source and destination devices. If the intermediate devices are H3C devices, use the ip ttl-expires enable command.

-     Enable sending ICMP destination unreachable messages on the destination device. If the destination device is an H3C device, use the ip unreachables enable command.

¡     IPv6:

-     Enable sending ICMPv6 time exceeded messages on the intermediate devices between the source and destination devices. If the intermediate devices are H3C devices, use the ipv6 hoplimit-expires enable command.

-     Enable sending ICMPv6 destination unreachable messages on the destination device. If the destination device is an H3C device, use the ipv6 unreachables enable command.

6.     If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

traceRouteTestCompleted

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.81.0.3	A traceroute operation completed.	Informational	Warning	N/A	OFF

 

Notification triggers

This notification is generated when a traceroute operation completes successfully.

System impact

No impact on the system.

Status control

ON

CLI: Use the reaction trap test-complete command.

OFF

CLI: Use the undo reaction trap test-complete command.

Objects

OID (object name)	Description	Index nodes	Type	Value range
1.3.6.1.2.1.81.1.2.1.3 (traceRouteCtlTargetAddressType)	Destination address type.	traceRouteCtlOwnerIndex traceRouteCtlTestName	InetAddressType	Standard MIB values.
1.3.6.1.2.1.81.1.2.1.4 (traceRouteCtlTargetAddress)	Destination address.	traceRouteCtlOwnerIndex traceRouteCtlTestName	InetAddress	Standard MIB values.
1.3.6.1.2.1.81.1.3.1.4 (traceRouteResultsIpTgtAddrType)	Destination address type in the probe result.	traceRouteCtlOwnerIndex traceRouteCtlTestName	InetAddressType	Standard MIB values.
1.3.6.1.2.1.81.1.3.1.5 (traceRouteResultsIpTgtAddr)	Destination address in the probe result.	traceRouteCtlOwnerIndex traceRouteCtlTestName	InetAddress	Standard MIB values.

 

Recommended action

No action is required.