Diagnostic troubleshooting enables the device to automatically discover and diagnose failures on various service modules all day all round. You can enable or disable diagnostic troubleshooting as needed.

Features

Diagnostic troubleshooting provides the following features:

· Health diagnostic troubleshooting for service modules

This feature identifies whether a service module can provide services correctly. If exceptions or abnormal running status disable the service module from providing services correctly, the system determines that the service module has an unhealthy event and records the relevant information to help you obtain the running status of the service module.

· Diagnostic troubleshooting for features

This feature identifies whether a service module is running correctly to help you locate issues. For example, diagnostic troubleshooting for SNMP trap sending failure events is used to identify whether SNMP trap sending failure events have occurred and the reason for the failure.

Mechanism

This section describes the operating mechanism for diagnostic troubleshooting of features. Health diagnostic troubleshooting for service modules uses the current running data in the service template to determine whether the service modules are running correctly and healthy.

Tests and test items

The device provides tests and test items for diagnostic troubleshooting.

· A test is a script file in the device startup software package used to test the device hardware and software features.

· A test might contain multiple test items, each representing a component or feature in the device hardware.

Figure 1 Diagram of tests and test items

Overview

You run the test items on the device, and the device runs the script corresponding to the test items to automatically sample the running data of the device and obtain the running status of the device and the features. Then, the device automatically analyzes and diagnoses the data, provides diagnostic results and processing suggestions.

Diagnostic troubleshooting is a sub-function of the GOLD module. It can cooperate with the GOLD module to perform diagnostic troubleshooting for service modules. To address the diagnostic troubleshooting requirements of different service modules, the device provides the following diagnostic troubleshooting methods:

· Diagnostic troubleshooting based on history data.

· Diagnostic troubleshooting based on running data.

· Diagnostic troubleshooting based on history or running data.

· Diagnostic troubleshooting based on the results of one-time actions.

Diagnostic troubleshooting based on history data

Some tests can perform troubleshooting for a service module based on the history running data of that service module. As shown in Figure 2, diagnostic troubleshooting based on history data proceeds as follows:

1. After you enable diagnostic troubleshooting for a test item and complete service module configuration, the service module samples objects monitored by the test item periodically and records the samples in the database of the GOLD module.

The objects and sampling interval might differ depending on diagnostic troubleshooting features. The objects and sampling interval have been defined in the script and are not configurable from the CLI.

2. You execute a diagnostic troubleshooting command.

3. The GOLD module obtains the history data for the test from the database and the test analyzes the history data and obtains the result.

4. The device outputs the diagnostic troubleshooting results.

Figure 2 Diagnostic troubleshooting based on history data

For example, if you enable diagnostic troubleshooting for SNMP trap sending failure events, the SNMP trap sending failure test item will save the relevant information to the GOLD module during device operation. The information includes the IP address of the NMS, the sending time of the traps, and the security keys used. The device displays all trap sending failure information saved in the GOLD module to help you locate the issue.

Diagnostic troubleshooting based on running data

For some features, only their running status needs to be monitored. The test items of these features will collect the running data for a period of time after diagnostic troubleshooting is enabled, and perform diagnostic troubleshooting for the service modules based on the collected data. As shown in Figure 3, diagnostic troubleshooting based on running data proceeds as follows:

1. After you enable diagnostic troubleshooting and complete configuration for a service module, the service module will establish an LIPC connection with the GOLD module.

2. You execute a diagnostic troubleshooting command.

3. The GOLD module notifies the service module to start diagnostic troubleshooting and notifies it of parameters such as diagnostic troubleshooting duration.

4. The service module samples objects monitored by the test item periodically and records the samples in the database of the GOLD module. The sampling interval has been defined when the device is shipped.

5. The GOLD module notifies the service module when the estimated diagnostic troubleshooting period is reached.

6. The test notifies the GOLD module to obtain data from the database, analyze the data, and obtain the result.

7. The device outputs the diagnostic troubleshooting results.

Figure 3 Diagnostic troubleshooting based on running data

Diagnostic troubleshooting based on history or running data

For some test items, you can configure parameters from the CLI to perform diagnostic troubleshooting by using history data or running data.

Diagnostic troubleshooting based on the results of one-time actions

For some service modules, you execute one or multiple diagnostic troubleshooting commands to trigger the service modules to perform one or multiple actions for failure analysis and diagnosis.

For example, if you perform diagnostic troubleshooting for ping failure events, the device uses the parameters specified from the CLI to ping a specific IP address and displays the ping result. If the ping operation fails, the device displays the failure reason to help you locate the failure reason.

Service modules that support diagnostic troubleshooting

Service modules that support diagnostic troubleshooting include NETCONF, SNMP, CPU, MEMORY, and OSPF. To obtain service modules that support diagnostic troubleshooting, use the diagnostic troubleshooting test ? command. To obtain features that support diagnostic troubleshooting, use the diagnostic troubleshooting test test-name ? command.

Service modules that support health diagnostic troubleshooting include VXLAN. To obtain service modules that support health diagnostic troubleshooting, use the diagnostic troubleshooting health module ? command.

Diagnostic troubleshooting tasks at a glance

All diagnostic troubleshooting tasks in this document are optional. Select tasks as needed.

Configuring CPU diagnostic troubleshooting

Configuring diagnostic troubleshooting for CPU usage threshold exceeding events

About this task

The system samples the CPU usage at 1-minute intervals. If the sample is greater than the CPU usage threshold configured using the monitor cpu-usage threshold command, the device logs a CPU usage threshold exceeding event in the memory of the GOLD module.

With this feature enabled, the device displays the following information to help you locate the high CPU usage issue:

· A maximum of seven CPU usage samples.

· A maximum of seven CPU usage threshold exceeding events.

· Information about the top five processes with the highest CPU usage when the most recent CPU usage threshold exceeding event occurred.

For more information about CPU usage alarms, see “Managing hardware resources” in Device Management Configuration Guide.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for CPU usage threshold exceeding events.

diagnostic troubleshooting test cpu high-ratio enable

By default, diagnostic troubleshooting is enabled for CPU usage threshold exceeding events.

3. Perform diagnostic troubleshooting for CPU usage threshold exceeding events.

diagnostic troubleshooting test cpu high-ratio

Configuring diagnostic troubleshooting for CPU overload events

About this task

The system samples the CPU usage every time it runs the CPU overload monitoring diagnostic test. The sample is used for CPU overload diagnostic troubleshooting.

If the different between the current sample and the previous sample is greater than 10%, the device logs a CPU overload event in the memory of the GOLD module.

With this feature enabled, the device displays the following information to help you locate the CPU overload issue:

· A maximum of seven CPU overload events.

· Information about the top five processes with the highest CPU usage when the most recent CPU overload event occurred.

Restrictions and guidelines

To enable the CPU overload diagnostic test, use the diagnostic monitor enable command. The CPU overload diagnostic test is enabled by default.The default execution interval for the CPU overload monitoring diagnostic test is 30 minutes. For more information about the diagnostic monitor enable command, see Intelligent Operations Command Reference.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for CPU overload events.

diagnostic troubleshooting test cpu overload enable

By default, diagnostic troubleshooting is enabled for CPU overload events.

3. Perform diagnostic troubleshooting for CPU overload events.

diagnostic troubleshooting test cpu overload

Configuring memory diagnostic troubleshooting

Configuring diagnostic troubleshooting for insufficient free memory events

About this task

The system samples the free memory usage at 5-second intervals. If the sample is greater than the free memory usage threshold configured using the memory-threshold command, the device logs a free memory threshold exceeding event in the memory of the GOLD module.

With this feature enabled, the device displays the memory usage and the most recent insufficient free memory usage events to help you locate the insufficient free memory issue.

For more information about memory usage alarms, see “Managing hardware resources” in Device Management Configuration Guide.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for insufficient free memory events.

diagnostic troubleshooting test memory high-ratio enable

By default, diagnostic troubleshooting is enabled for insufficient free memory events.

3. Perform diagnostic troubleshooting for insufficient free memory events.

diagnostic troubleshooting test memory high-ratio

Configuring diagnostic troubleshooting for memory overload events

About this task

The system samples the memory usage every time it runs the memory overload monitoring diagnostic test. The sample is used for memory overload diagnostic troubleshooting.

If the difference between the current sample and the previous sample is greater than 50M, the device logs a memory overload event in the memory of the GOLD module.

With this feature enabled, the device displays the following information to help you locate the memory overload issue:

· A maximum of seven memory overload events.

· Information about the top five processes with the highest memory usage when the most recent memory overload event occurred.

Restrictions and guidelines

To enable the memory overload diagnostic test, use the diagnostic monitor enable command. The memory overload diagnostic test is enabled by default. The default execution interval for the memory overload monitoring diagnostic test is 12 hours.To set the interval, execute the diagnostic monitor interval command. For more information about the diagnostic monitor enable command, see Intelligent Operations Command Reference.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for memory overload events.

diagnostic troubleshooting test memory overload enable

By default, diagnostic troubleshooting is enabled for memory overload events.

3. Perform diagnostic troubleshooting for memory overload events.

diagnostic troubleshooting test memory overload

Configuring AAA diagnostic troubleshooting

Configuring diagnostic troubleshooting for unexpected user offline events

About this task

After you perform this task, the device will execute the display aaa abnormal offline-record command immediately. You can view the user abnormal offline records and locate the issue.

Prerequisites

Use the aaa abnormal-offline-record enable command to enable unexpected user offline event recording.

Procedure

1. Enter system view.

system-view

2. Configure diagnostic troubleshooting for unexpected user offline events.

diagnostic troubleshooting test aaa-fault abnormal-offline-record enable

By default, diagnostic troubleshooting is enabled for unexpected user offline events.

3. Perform diagnostic troubleshooting for unexpected user offline events.

diagnostic troubleshooting test aaa-fault online-fail-record [ access-type { ipoe | lan-access | login | portal | ppp } | domain domain-name | interface interface-type interface-number | { ip-address ipv4-address | ipv6-address ipv6-address } | mac-address mac-address | s-vlan svlan-id [ c-vlan cvlan-id ] | slot slot-number | username user-name ] *

Configuring diagnostic troubleshooting for abnormal user login events

About this task

This feature is applicable to scenarios where the following exceptions occur when a user tries to log in to the device through AAA:

· The user fails to log in to the device.

· The user is disabled from logging in to the device after the number of login attempts reaches the upper limit.

· The user does not have the privileges to some commands after login to the device.

· The user cannot create or edit a local user after it logs in to the device.

Log in to the device as a super administrator (with a role of network-admin, or level-15 user). Then perform this task to display the configuration to locate the issue.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for abnormal user login events.

diagnostic troubleshooting test aaa-fault login-exception enable

By default, diagnostic troubleshooting is enabled for abnormal user login events.

3. Perform diagnostic troubleshooting for abnormal user login events.

diagnostic troubleshooting test aaa-fault login-exception [ domain | local-user | line | role ]

Configuring diagnostic troubleshooting for user online failure events through AAA

About this task

After you perform this task, the device will execute the display aaa online-fail-record command immediately. You can view the user online failure records and locate the issue.

Prerequisites

Use the aaa online-fail-record enable command to enable user online failure recording.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for user online failure events through AAA.

diagnostic troubleshooting test aaa-fault online-fail-record enable

By default, diagnostic troubleshooting is enabled for user online failure events through AAA.

3. Perform diagnostic troubleshooting for user online failure events through AAA.

diagnostic troubleshooting test aaa-fault online-fail-record [ access-type { ipoe | lan-access | login | portal | ppp } | domain domain-name

| interface interface-type interface-number | { ip-address ipv4-address | ipv6-address ipv6-address } | mac-address mac-address | s-vlan svlan-id [ c-vlan cvlan-id ] | slot slot-number | username user-name ] *

Configuring diagnostic troubleshooting for local password control exceptions

About this task

When password control is enabled on the device, login password configuration and update for local users will be controlled. If local user password control has exceptions, the following failures might occur:

· Local user creation failure.

· Local user password configuration failure.

· A password modification is required at user login.

Log in to the device as a super administrator (with a role of network-admin, or level-15 user). Then perform this task to display the configuration to locate the issue.

After you execute this command, the device will execute the display memory-threshold, display password-control, and display local-user commands in turn immediately.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for local password control exceptions.

diagnostic troubleshooting test aaa-fault password-control-exception enable

By default, diagnostic troubleshooting is enabled for local password control exceptions.

3. Perform diagnostic troubleshooting for local password control exceptions.

diagnostic troubleshooting test aaa-fault password-control-exception

Configuring diagnostic troubleshooting for local authentication user online exceptions

About this task

This feature identifies the reasons for AAA local authentication user online exceptions. With this feature configured, the system continuously collects exception information occurred during authentication, authorization, and accounting by local RADIUS, HWTACACS, and LDAP servers and outputs failure information during the diagnostic troubleshooting period.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for local authentication user online exceptions.

diagnostic troubleshooting test aaa-process local enable

By default, diagnostic troubleshooting is enabled for local authentication user online exceptions.

3. Perform diagnostic troubleshooting for local authentication user online exceptions.

diagnostic troubleshooting test aaa-process local [ interface interface-type interface-number | username user-name ] * [ diagnostic-time diagnostic-time ]

Configuring diagnostic troubleshooting for remote authentication user online exceptions

About this task

This feature identifies the reasons for AAA remote authentication user online exceptions. When this command is executed, the system continuously collects exception information occurred during authentication, authorization, and accounting by remote RADIUS, LDAP, and HWTACACS, and servers and outputs failure information during the diagnostic troubleshooting period.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for remote authentication user online exceptions.

diagnostic troubleshooting test aaa-process remote enable

By default, diagnostic troubleshooting is enabled for remote authentication user online exceptions.

3. Perform diagnostic troubleshooting for remote authentication user online exceptions.

diagnostic troubleshooting test aaa-process remote [ interface interface-type interface-number | username user-name ] * [ diagnostic-time diagnostic-time ]

Configuring diagnostic troubleshooting for user abnormal user online and offline events.

About this task

Perform this task to identify the reasons for user online and offline exceptions. With this feature enabled, the system continuously collects user online and offline information and outputs user online failure information and offline information during the diagnostic troubleshooting period.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for user abnormal online and offline events.

diagnostic troubleshooting test aaa-process online-offline-record enable

By default, diagnostic troubleshooting is enabled for abnormal user online and offline events.

3. Perform diagnostic troubleshooting for abnormal user offline and offline events.

diagnostic troubleshooting aaa-process online-offline-record [ access-type { ipoe | lan-access | login | portal | ppp } | interface interface-type interface-number | username user-name ] * [ diagnostic-time diagnostic-time ]

Configuring LDP diagnostic troubleshooting

Configuring health diagnostic troubleshooting for the LDP module

About this task

With health diagnostic troubleshooting enabled for the LDP module and LDP configuration completed, the system starts to monitor the running status of the LDP module. The LDP module records unhealthy events detects in the GOLD module. When you perform health diagnostic troubleshooting for the LDP module, the LDP module obtains the unhealthy events from the GOLD module and determines whether the LDP module is in healthy state.

Procedure

1. Enter system view.

system-view

2. Enable health diagnostic troubleshooting for the LDP module.

diagnostic troubleshooting health module ldp enable

By default, health diagnostic troubleshooting is enabled for the LDP module.

3. Perform health diagnostic troubleshooting for the LDP module.

diagnostic troubleshooting health module ldp

Configuring diagnostic troubleshooting for LDP session setup failure events

About this task

With this feature configured, the LDP module records LDP session setup failure events in the GOLD module for the GOLD module to perform diagnostic troubleshooting for the events.

Restrictions and guidelines

Recording LDP session setup failure events consumes device resources and affects system performance. If you do not concern about the running status of the LDP module, you can disable diagnostic troubleshooting for LDP session setup failure events.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for LDP session setup failure events.

diagnostic troubleshooting test neighbor-create-abnormal ldp enable

By default, diagnostic troubleshooting is enabled for LDP session setup failure events.

3. Perform diagnostic troubleshooting for LDP session setup failure events.

diagnostic troubleshooting test neighbor-create-abnormal ldp { local [ vpn-instance vpn-instance-name ] peer peer-lsr-id interface interface-type interface number | remote peer peer-lsr-id } [ diagnostic-time diagnostic-time ]

Configuring diagnostic troubleshooting for LDP peer down events

About this task

With this feature configured, the LDP module records LDP peer down events in the GOLD module for the GOLD module to perform diagnostic troubleshooting for the events.

Restrictions and guidelines

Recording LDP peer down events consumes device resources and affects system performance. If you are not concerned about the running status of the LDP module, you can disable diagnostic troubleshooting for LDP peer down events.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for LDP peer down events.

diagnostic troubleshooting test neighbor-flap ldp enable

By default, diagnostic troubleshooting is enabled for LDP peer down events.

3. Perform diagnostic troubleshooting for LDP peer down events.

diagnostic troubleshooting test neighbor-flap ldp [ [ vpn-instance vpn-instance-name ] peer peer-id ]

Configuring MPLS TE diagnostic troubleshooting

Configuring health diagnostic troubleshooting for the MPLS TE module

About this task

With health diagnostic troubleshooting enabled for the MPLS TE module and MPLS TE configuration completed, the system starts to monitor the running status of the MPLS module. The MPLS TE module records unhealthy events detects in the GOLD module. When you perform health diagnostic troubleshooting for the MPLS TE module, the MPLS TE module obtains the unhealthy events from the GOLD module and determines whether the MPLS TE module is in healthy state.

Procedure

1. Enter system view.

system-view

2. Enable health diagnostic troubleshooting for the MPLS TE module.

diagnostic troubleshooting health module te enable

By default, health diagnostic troubleshooting is enabled for the MPLS TE module.

3. Perform health diagnostic troubleshooting for the MPLS TE module.

diagnostic troubleshooting health module te

Configuring diagnostic troubleshooting for MPLS TE tunnel setup failure events

About this task

With this feature configured, the MPLS TE module records MPLS TE tunnel setup failure events in the GOLD module for the GOLD module to perform diagnostic troubleshooting for the events.

Restrictions and guidelines

Recording MPLS setup failure events consumes device resources and affects system performance. If you are not concerned about the running status of the MPLS TE module, you can disable diagnostic troubleshooting for MPLS TE tunnel setup failure events.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for MPLS TE tunnel setup failure events.

diagnostic troubleshooting test te-tunnel establish-abnormal enable

By default, diagnostic troubleshooting is enabled for MPLS TE tunnel setup failure events.

3. Perform diagnostic troubleshooting for MPLS TE tunnel setup failure events.

diagnostic troubleshooting test te-tunnel establish-abnormal tunnel tunnel-id [ diagnostic-time diagnostic-time ]

Configuring MPLS L2VPN diagnostic troubleshooting

Configuring health diagnostic troubleshooting for the MPLS L2VPN module

About this task

With health diagnostic troubleshooting enabled for the MPLS L2VPN module and MPLS L2VPN configuration completed, the system starts to monitor the running status of the MPLS L2VPN module. The MPLS L2VPN module records unhealthy events detects in the GOLD module. When you perform health diagnostic troubleshooting for the MPLS L2VPN module, the MPLS L2VPN module obtains the unhealthy events from the GOLD module and determines whether the MPLS L2VPN module is in healthy state.

Procedure

1. Enter system view.

system-view

2. Enable health diagnostic troubleshooting for the MPLS L2VPN module.

diagnostic troubleshooting health module l2vpn enable

By default, health diagnostic troubleshooting is enabled for the MPLS L2VPN module.

3. Perform health diagnostic troubleshooting for the MPLS L2VPN module.

diagnostic troubleshooting health module l2vpn

Configuring diagnostic troubleshooting for PW setup failure events

About this task

With this feature configured, the MPLS L2VPN module records PW setup failure events in the GOLD module for the GOLD module to perform diagnostic troubleshooting for the events.

Restrictions and guidelines

Recording PW setup failure events consumes device resources and affects system performance. If you are not concerned about the running status of the MPLS L2VPN module, you can disable diagnostic troubleshooting for PW setup failure events.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for PW setup failure events.

diagnostic troubleshooting test l2vpn-pw establish-abnormal enable
By default, diagnostic troubleshooting is enabled for PW setup failure events.

3. Perform diagnostic troubleshooting for PW setup failure events.

diagnostic troubleshooting test l2vpn-pw establish-abnormal { vsi vsi-name | xconnect-group-name group-name connection connection-name } peer ip-address pw-id pw-id

Configuring diagnostic troubleshooting for PW down events

About this task

With this feature configured, the MPLS L2VPN module records PW down events in the GOLD module for the GOLD module to perform diagnostic troubleshooting for the events.

Restrictions and guidelines

Recording PW down events consumes device resources and affects system performance. If you are not concerned about the running status of the MPLS L2VPN module, you can disable diagnostic troubleshooting for PW down events.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for PW down events.

diagnostic troubleshooting test l2vpn-pw flap enable

By default, diagnostic troubleshooting is enabled for PW down events.

3. Perform diagnostic troubleshooting for PW down events.

diagnostic troubleshooting test l2vpn-pw flap { vsi vsi-name | xconnect-group-name group-name connection connection-name } peer ip-address pw-id pw-id

Configuring ping diagnostic troubleshooting

About this task

With this feature configured, the device uses the parameters specified from the CLI to ping a specific IP address and displays the ping result. If the ping operation fails, the device displays the failure reason to help you locate the failure reason.

For more information about the ping utility, see Network Management and Monitoring Configuration Guide.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for ping failure events.

diagnostic troubleshooting test ping failed-reason enable

By default, diagnostic troubleshooting is enabled for ping failure events.

3. Perform diagnostic troubleshooting for ping failure events.

diagnostic troubleshooting test ping failed-reason [ -a source-ip | -f | -i interface-type interface-number | -s packet-size | -t timeout ] [ vpn-instance vpn-instance-name ] { ip-address ipv4-address | ipv6-address ipv6-address }

Configuring SNMP diagnostic troubleshooting

Configuring diagnostic troubleshooting for SNMP packet processing failure events

About this task

With feature configured, the device records SNMP packet sending and receiving failure events within the diagnostic troubleshooting period. When the period is reached, the device displays the events for you to locate the failure reason.

For more information about configuring SNMP, see Network Management and Monitoring Configuration Guide.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for SNMP packet processing failure events.

diagnostic troubleshooting test snmp-agent packet-process-failure enable

By default, diagnostic troubleshooting is enabled for SNMP packet processing failure events.

3. Perform diagnostic troubleshooting for SNMP packet processing failure events.

diagnostic troubleshooting test snmp-agent packet-process-failure [ ip-address ipv4-address | ipv6-address ipv6-address ] [ vpn-instance vpn-instance-name ] [ diagnose-time diagnostic-time ]

Configuring diagnostic troubleshooting for long SNMP packet processing duration events

About this task

With this feature configured, the device records SNMP packet processing durations within the diagnostic troubleshooting period. When the period is reached, the device displays the durations for you to locate the failure reason.

For more information about configuring SNMP, see Network Management and Monitoring Configuration Guide.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for long SNMP packet processing duration events.

diagnostic troubleshooting test snmp-agent packet-process-time enable

By default, diagnostic troubleshooting is enabled for long SNMP packet processing duration events.

3. Perform diagnostic troubleshooting for long SNMP packet processing duration events.

diagnostic troubleshooting test snmp-agent packet-process-time [ ip-address ipv4-address | ipv6-address ipv6-address ] [ vpn-instance vpn-instance-name ] [ diagnose-time diagnostic-time ]

Configuring diagnostic troubleshooting for SNMP trap sending failure events

About this task

With diagnostic troubleshooting for SNMP trap sending failure events enabled, the device records the relevant information in the GOLD module. When you perform diagnostic troubleshooting for SNMP trap sending failure events, the device displays the information to help you locate the issue.

For more information about configuring SNMP, see Network Management and Monitoring Configuration Guide.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for SNMP trap sending failure events.

diagnostic troubleshooting test snmp-agent trap-send-failure enable

By default, diagnostic troubleshooting is enabled for SNMP trap sending failure events.

3. Perform diagnostic troubleshooting for SNMP trap sending failure events.

diagnostic troubleshooting test snmp-agent trap-send-failure [ ip-address ipv4-address | ipv6-address ipv6-address ]

Configuring BGP diagnostic troubleshooting

Configuring health diagnostic troubleshooting for the BGP module

About this task

With health diagnostic troubleshooting enabled for the BGP module and BGP configuration completed, the system starts to monitor the running status of the BGP module. The BGP module records unhealthy events in the GOLD module. When you perform health diagnostic troubleshooting for the BGP module, the BGP module obtains the unhealthy information from the GOLD module and determines whether the BGP module is in healthy state.

Procedure

1. Enter system view.

system-view

2. (Optional.) Enable health diagnostic troubleshooting for the BGP module.

diagnostic troubleshooting health module bgp enable

By default, health diagnostic troubleshooting is enabled for the BGP module.

3. Perform health diagnostic troubleshooting for the BGP module.

diagnostic troubleshooting health module bgp

Configuring diagnostic troubleshooting for BGP session setup failure events

About this task

Perform this task to configure diagnostic troubleshooting for BGP session setup failure events in a BGP instance or for a BGP peer.

· With diagnostic troubleshooting for BGP session setup failure events enabled in a BGP instance, the device records the failure information in the memory of the GOLD module automatically. After you configure this feature, the device displays the diagnostic troubleshooting information stored in the GOLD module to help you locate the failure reason.

· With diagnostic troubleshooting for BGP session setup failure events enabled for a BGP peer, the device tries to reestablish a BGP session with a BGP peer before the diagnostic troubleshooting period times out and displays the diagnostic troubleshooting information to help you locate the failure reason.

Procedure

1. Enter system view.

system-view

2. (Optional.) Enable diagnostic troubleshooting for BGP session setup failure events.

¡ Enable diagnostic troubleshooting for BGP session setup failure events in a BGP instance.

diagnostic troubleshooting test establish-abnormal bgp enable

By default, diagnostic troubleshooting is enabled for BGP session setup failure events in a BGP peer.

¡ Enable diagnostic troubleshooting for BGP session setup failure events for a BGP peer.

diagnostic troubleshooting test peer-establish-abnormal bgp enable

By default, diagnostic troubleshooting is enabled for BGP session setup failure events for a BGP peer.

3. Perform diagnostic troubleshooting for BGP session setup failure events.

¡ Perform diagnostic troubleshooting for BGP session setup failure events in a BGP instance.

diagnostic troubleshooting test establish-abnormal bgp [ instance instance-name ] [ vpn-instance vpn-instance-name ]

¡ Perform diagnostic troubleshooting for BGP session setup failure events for a BGP peer.

diagnostic troubleshooting test peer-establish-abnormal bgp [ instance instance-name ] [ vpn-instance vpn-instance-name ] peer { ip-address ipv4-address | ipv6-address ipv6-address } [ diagnostic-time diagnostic-time ]

Configuring diagnostic troubleshooting for BGP session down events

About this task

With diagnostic troubleshooting for BGP session down events enabled, the device records the session down information in the memory of the GOLD module automatically. After you execute this command, the device displays the failure information stored in the GOLD module to help you locate the failure reason.

Procedure

1. Enter system view.

system-view

2. (Optional.) Enable diagnostic troubleshooting for BGP session down events.

¡ Enable diagnostic troubleshooting for BGP session down events in a BGP instance.

diagnostic troubleshooting test flap bgp enable

By default, diagnostic troubleshooting for BGP session down events is enabled for all BGP peers.

¡ Enable diagnostic troubleshooting for BGP session down events for a BGP peer.

diagnostic troubleshooting test peer-flap bgp enable

By default, diagnostic troubleshooting for BGP session down events is enabled for a BGP peer.

3. Perform diagnostic troubleshooting for BGP session down events.

¡ Perform diagnostic troubleshooting for BGP session down events in a BGP instance.

diagnostic troubleshooting test flap bgp [ instance instance-name ] [ vpn-instance vpn-instance-name ]

¡ Perform diagnostic troubleshooting for BGP session down events for a BGP peer.

diagnostic troubleshooting test peer-flap bgp [ instance instance-name ] [ vpn-instance vpn-instance-name ] peer { ip-address ipv4-address | ipv6-address ipv6-address }

Configuring DHCP diagnostic troubleshooting

Configuring health diagnostic troubleshooting for the DHCP module

About this task

With health diagnostic troubleshooting enabled for the DHCP module and DHCP configuration completed, the system starts to monitor the running status of the DHCP module. The DHCP module records detected unhealthy events in the GOLD module. When you perform health diagnostic troubleshooting for the DHCP module, the DHCP module obtains the unhealthy events from the GOLD module and determines whether the DHCP module is in healthy state.

Procedure

1. Enter system view.

system-view

2. Enable health diagnostic troubleshooting for the DHCP module.

diagnostic troubleshooting health module dhcp enable

By default, health diagnostic troubleshooting is enabled for the DHCP module.

3. Perform health diagnostic troubleshooting for the DHCP module.

diagnostic troubleshooting health module dhcp

Configuring diagnostic troubleshooting for DHCP client offline events

About this task

When the device operates as a DHCP client, this feature enables the DHCP module to record DHCP client offline events in the GOLD module for the GOLD module to perform diagnostic troubleshooting.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for DHCP client offline events.

diagnostic troubleshooting test dhcp-client offline-record enable

By default, diagnostic troubleshooting is enabled for DHCP client offline events.

3. Perform diagnostic troubleshooting for DHCP client offline events.

diagnostic troubleshooting test dhcp-client offline-record

Configuring diagnostic troubleshooting for user online failure events on the DHCP relay agent

About this task

When the device operates as a DHCP relay agent, it can perform diagnostic troubleshooting for user online failure events based on running data and history data.

· Based on running data—Upon configuration of this feature, the DHCP relay agent module will continuously collect running data of the specified DHCP user within the diagnostic troubleshooting period and record it in the GOLD module. The GOLD module performs diagnostic troubleshooting for the DHCP user online failure events in real time.

· Based on history data—When this feature is configured, the DHCP relay agent module will record the online failure events of all DHCP users in the GOLD module based on history data. The GOLD module performs diagnostic troubleshooting for the DHCP user online failure events.

Configuring real-time diagnostic troubleshooting for user online failure events on the DHCP relay agent

1. Enter system view.

system-view

2. Enable real-time diagnostic troubleshooting for user online failure events on the DHCP relay agent.

diagnostic troubleshooting test dhcp-relay online-fail-capture enable

By default, real-time diagnostic troubleshooting is enabled for user online failure events on the DHCP relay agent.

3. Perform real-time diagnostic troubleshooting for online failure events of a DHCP user on the DHCP relay agent.

diagnostic troubleshooting test dhcp-relay online-fail-capture mac-address mac-address [ diagnostic-time diagnostic-time ]

Configuring diagnostic troubleshooting for user online failure history events on the DHCP relay agent

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for user online failure history events on the DHCP relay agent.

diagnostic troubleshooting test dhcp-relay online-fail-record enable

By default, diagnostic troubleshooting is enabled for user online failure history events on the DHCP relay agent.

3. Perform diagnostic troubleshooting for online failure history events of a DHCP user on the DHCP relay agent.

diagnostic troubleshooting test dhcp-relay online-fail-record

Configuring diagnostic troubleshooting for user offline events on the DHCP server

About this task

When the device operates as a DHCP server, this feature enables the DHCP server to record user offline events in the GOLD module for the GOLD module to perform diagnostic troubleshooting.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for user offline events on the DHCP server.

diagnostic troubleshooting test dhcp-server offline-record enable

By default, diagnostic troubleshooting is enabled for user offline events on the DHCP server.

3. Perform diagnostic troubleshooting for user offline events on the DHCP server.

diagnostic troubleshooting test dhcp-server offline-record [ abnormal | normal ]

Configuring diagnostic troubleshooting for user online failure events on the DHCP server

About this task

When the device operates as a DHCP server, it can perform diagnostic troubleshooting for user online failure events based on running data and history data.

· Based on running data—Upon configuration of this feature, the DHCP server module will continuously collect running data of the specified DHCP user within the diagnostic troubleshooting period and record it in the GOLD module. The GOLD module performs diagnostic troubleshooting for the DHCP user online failure events in real time.

· Based on history data—When this feature is configured, the DHCP server module will record the online failure events of all DHCP users in the GOLD module based on history data. The GOLD module performs diagnostic troubleshooting for the DHCP user online failure events.

Configuring real-time diagnostic troubleshooting for user online failure events on the DHCP server

1. Enter system view.

system-view

2. Enable real-time diagnostic troubleshooting for user online failure events on the DHCP server.

diagnostic troubleshooting test dhcp-server online-fail-capture enable

By default, real-time diagnostic troubleshooting is enabled for user online failure events on the DHCP server.

3. Perform real-time diagnostic troubleshooting for online failure events of a DHCP user on the DHCP server.

diagnostic troubleshooting test dhcp-server online-fail-capture mac-address mac-address [ diagnostic-time diagnostic-time ]

Configuring diagnostic troubleshooting for user online failure history events on the DHCP server

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for user online failure history events on the DHCP server.

diagnostic troubleshooting test dhcp-server online-fail-record enable

By default, diagnostic troubleshooting is enabled for user online failure history events on the DHCP server.

3. Perform diagnostic troubleshooting for online failure history events of a DHCP user on the DHCP server.

diagnostic troubleshooting test dhcp-server online-fail-record

Configuring OSPF diagnostic troubleshooting

Configuring diagnostic troubleshooting for OSPF neighbor relationship establishment failure events

About this task

With diagnostic troubleshooting for OSPF neighbor relationship establishment failure events enabled, the device records the failure information in the memory of the GOLD module automatically. After you execute this command, the device displays the failure information stored in the GOLD module to help you locate the failure reason.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for OSPF neighbor relationship establishment failure events.

diagnostic troubleshooting test neighbor-establish-abnormal ospf enable

By default, diagnostic troubleshooting is enabled for OSPF neighbor relationship establishment failure events.

3. Perform diagnostic troubleshooting for OSPF neighbor relationship establishment failure events.

diagnostic troubleshooting test neighbor-establish-abnormal ospf [ process-id ] [ interface interface-type interface-number ]

Configuring diagnostic troubleshooting for OSPF neighbor flapping events

About this task

With diagnostic troubleshooting OSPF neighbor flapping events enabled, the device records the failure information in the memory of the GOLD module automatically. After you execute this command, the device displays the failure information stored in the GOLD module to help you locate the failure reason.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for OSPF neighbor flapping events.

diagnostic troubleshooting test neighbor-flap ospf enable

By default, diagnostic troubleshooting is enabled for OSPF neighbor flapping events.

3. Perform diagnostic troubleshooting for OSPF neighbor flapping events.

diagnostic troubleshooting test neighbor-flap ospf [ process-id ] [ interface interface-type interface-number ]

Configuring IS-IS diagnostic troubleshooting

Configuring diagnostic troubleshooting for IS-IS route change events

About this task

With diagnostic troubleshooting for IS-IS route change events enabled, the device records the change information in the memory of the GOLD module automatically. After you execute this command, the device displays the route change information stored in the GOLD module to help you locate the reason.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for IS-IS route change events.

diagnostic troubleshooting test isis route enable

By default, diagnostic troubleshooting is enabled for IS-IS route change events.

3. Enable diagnostic troubleshooting for IS-IS route change events.

diagnostic troubleshooting test isis route { ipv4 { add | delete | modify } [ ipv4-address mask-length ] | ipv6 { add | delete | modify } [ ipv6-address prefix-length ] } [ level-1 | level-2 ] [ process-id ]

Configuring diagnostic troubleshooting for IS-IS neighbor down events

About this task

With diagnostic troubleshooting for IS-IS neighbor down events enabled, the device records the failure information in the memory of the GOLD module automatically. After you execute this command, the device displays the failure information stored in the GOLD module to help you locate the failure reason.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for IS-IS neighbor down events.

diagnostic troubleshooting test neighbor-establish-abnormal isis enable

By default, diagnostic troubleshooting is enabled for IS-IS neighbor down events.

3. Perform diagnostic troubleshooting for IS-IS neighbor down events.

diagnostic troubleshooting test neighbor-establish-abnormal isis [ process-id ] [ interface interface-type interface-number ]

Configuring diagnostic troubleshooting for IS-IS neighbor flapping events

About this task

With diagnostic troubleshooting for IS-IS neighbor flapping events enabled, the device records the failure information in the memory of the GOLD module automatically. After you execute this command, the device displays the failure information stored in the GOLD module to help you locate the failure reason.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for IS-IS neighbor flapping events.

diagnostic troubleshooting test neighbor-flap isis enable

By default, diagnostic troubleshooting is enabled for IS-IS neighbor flapping events.

3. Perform diagnostic troubleshooting for IS-IS neighbor flapping events.

diagnostic troubleshooting test neighbor-flap isis [ process-id ] [ interface interface-type interface-number ]

Configuring gRPC diagnostic troubleshooting

Configuring diagnostic troubleshooting for gRPC request failures

About this task

This feature is used to analyze the reasons for the failure for the device in gRPC dial-in mode (gRPC server) in processing request messages sent a gRPC client.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for gRPC request failures.

diagnostic troubleshooting test grpc-server failed-operation enable

By default, diagnostic troubleshooting is enabled for gRPC request failures.

3. Perform diagnostic troubleshooting for gRPC request failures.

diagnostic troubleshooting test grpc-server failed-operation

Configuring diagnostic troubleshooting for gRPC login failure events

About this task

Perform this task to analyze the reasons why the gRPC clients failed to establish a gRPC session with the device in gRPC dial-in mode (gRPC server).

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for gRPC login failure events.

diagnostic troubleshooting test grpc-server login enable

By default, diagnostic troubleshooting is enabled for gRPC login failure events.

3. Perform diagnostic troubleshooting for gRPC login failure events.

diagnostic troubleshooting test grpc-server login

Configuring diagnostic troubleshooting for gRPC sampling intervals

About this task

This feature is used to analyze whether the sampling interval for gRPC in dial-out mode to send subscription messages to the collector is consistent with the configured sampling interval.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for gRPC sampling intervals.

diagnostic troubleshooting test telemetry sample-interval enable

By default, diagnostic troubleshooting is enabled for gRPC sampling intervals.

3. Perform diagnostic troubleshooting for gRPC sampling intervals.

diagnostic troubleshooting test telemetry sample-interval [ diagnostic-time diagnostic-time ]

Configuring NETCONF diagnostic troubleshooting

Configuring diagnostic troubleshooting for NETCONF request failures

About this task

This feature is used to analyze the reasons for the failure in processing an <rpc> request message by the device (NETCONF server) after receiving it from the NETCONF client.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for NETCONF request failures.

diagnostic troubleshooting test netconf-server failed-operation enable

By default, diagnostic troubleshooting is enabled for NETCONF request failures.

3. Perform diagnostic troubleshooting for NETCONF request failures.

diagnostic troubleshooting test netconf-server failed-operation

Configuring diagnostic troubleshooting for NETCONF over SOAP login information

About this task

This feature is used to analyze the reasons why the NETCONF client failed to establish a NETCONF over SOAP session with the device (NETCONF server).

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for NETCONF over SOAP login information.

diagnostic troubleshooting test netconf-server netconf-over-soap enable

By default, diagnostic troubleshooting is enabled for NETCONF over SOAP login information.

3. Perform diagnostic troubleshooting for NETCONF over SOAP login information.

diagnostic troubleshooting test netconf-server netconf-over-soap

Configuring diagnostic troubleshooting for the IP multicast module

Configuring health diagnostic troubleshooting for the IP multicast module

About this task

With health diagnostic troubleshooting enabled for the IP multicast module and multicast configuration completed, the system starts to monitor the running status of the IP multicast module. The IP multicast module records detected unhealthy events in the GOLD module. When you perform health diagnostic troubleshooting for the IP multicast module, the IP multicast module obtains the unhealthy events from the GOLD module and determines whether the IP multicast module is in healthy state.

Procedure

1. Enter system view.

system-view

2. Enable health diagnostic troubleshooting for the IP multicast module.

diagnostic troubleshooting health module multicast enable

By default, health diagnostic troubleshooting is enabled for the multicast module.

3. Perform health diagnostic troubleshooting for the IP multicast module.

diagnostic troubleshooting health module multicast

Configuring diagnostic troubleshooting multicast routing and forwarding entry creation failure events

About this task

With this feature configured, the device records multicast entry creation failure events within the diagnostic troubleshooting period. When the period is reached, the device displays the events for you to locate the issue.

Procedure

The configured diagnostic troubleshooting duration must be larger than the interval for the downstream to send PIM join messages. If IGMP or MLD is also enabled on an interface, the diagnostic troubleshooting duration must also be larger than the sum of the IGMP/MLD general query interval (the default is 125 seconds) and the maximum response time (the default is 10 seconds). A too short diagnostic troubleshooting duration might cause the diagnostic troubleshooting result to be incomplete.

The device can perform diagnostic troubleshooting for creation failure events of only one multicast entry at a time.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for multicast routing and forwarding entry creation failure events.

diagnostic troubleshooting test multicast-route creation-abnormal enable

By default, diagnostic troubleshooting is enabled for multicast routing and forwarding entry creation failure events.

The device can perform diagnostic troubleshooting for creation failure events of only one multicast entry at a time.

diagnostic troubleshooting test multicast-route creation-abnormal [ vpn-instance vpn-instance-name ] { ipv4-source-address ipv4-group-address | ipv6-source-address ipv6-group-address } outgoing-interface interface-type interface-number [ diagnostic-time diagnostic-time ]

Configuring ARP diagnostic troubleshooting

Configuring health diagnostic troubleshooting for the ARP module

About this task

With health diagnostic troubleshooting enabled for the ARP module and ARP configuration completed, the system starts to monitor the running status of the ARP module. The ARP module records detected unhealthy events in the GOLD module. When you perform health diagnostic troubleshooting for the ARP module, the ARP module obtains the unhealthy events from the GOLD module and determines whether the ARP module is in healthy state.

Procedure

1. Enter system view.

system-view

2. Enable health diagnostic troubleshooting for the ARP module.

diagnostic troubleshooting health module arp enable

By default, health diagnostic troubleshooting is enabled for the ARP module.

3. Perform health diagnostic troubleshooting for the ARP module.

diagnostic troubleshooting health module arp

Configuring diagnostic troubleshooting for ARP packet sending and receiving events

About this task

To check reachability between the device and the destination network or host, use this command to perform diagnostic troubleshooting for ARP packet sending and receiving events. If ARP packets fail to be sent, you can check the output for failure location.

After this feature is enabled, the device displays diagnostic troubleshooting information only after the specified interface has sent an ARP packet with a specified destination IP address or received an ARP packet with a specified source IP address. The device can display diagnostic troubleshooting information for a maximum of 5 ARP packets at a time.

· If the number of sent or received ARP packets reaches 5 within the diagnostic troubleshooting period, the device will display diagnostic troubleshooting information only for the 5 ARP packets and will not display diagnostic troubleshooting information for subsequent ARP packets.

· If the number of ARP packets does not reach 5 within the estimated diagnostic troubleshooting duration or if the command is terminated using Ctrl+C, the device will display diagnostic troubleshooting information for the detected ARP packets.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for ARP packet sending and receiving events.

diagnostic troubleshooting test arp-learn packet-trace enable

By default, diagnostic troubleshooting is enabled for ARP packet sending and receiving events.

3. Perform diagnostic troubleshooting for ARP packet sending and receiving events.

diagnostic troubleshooting test arp-learn packet-trace ip-address ip-address interface interface-type interface-number [ diagnostic-time diagnostic-time ]

Configuring ND diagnostic troubleshooting

Configuring health diagnostic troubleshooting for the ND module

About this task

With health diagnostic troubleshooting enabled for the ND module and ND configuration completed, the system starts to monitor the running status of the ND module. The ND module records detected unhealthy events in the GOLD module. When you perform health diagnostic troubleshooting for the ND module, the ND module obtains the unhealthy events from the GOLD module and determines whether the ND module is in healthy state.

Procedure

1. Enter system view.

system-view

2. Enable health diagnostic troubleshooting for the ND module.

diagnostic troubleshooting health module nd enable

By default, health diagnostic troubleshooting is enabled for the ND module.

3. Perform health diagnostic troubleshooting for the ND module.

diagnostic troubleshooting health module nd

Configuring diagnostic troubleshooting for ND packet sending and receiving events

About this task

To check reachability between the device and the destination network or host, use this command to perform diagnostic troubleshooting for ND packet sending and receiving events. If ND packets fail to be sent, you can check the output for failure location.

After this feature is enabled, the device displays diagnostic troubleshooting information only after the specified interface has sent an ND packet with a specified destination IPv6 address or received an ND packet with a specified source IPv6 address. The device can display diagnostic troubleshooting information for a maximum of 5 ND packets at a time.

· If the number of sent or received ND packets reaches 5 within the diagnostic troubleshooting period, the device will display diagnostic troubleshooting information only for the 5 ND packets and will not display diagnostic troubleshooting information for subsequent ND packets.

· If the number of ND packets does not reach 5 within the estimated diagnostic troubleshooting duration or if the command is terminated using Ctrl+C, the device will display diagnostic troubleshooting information for the detected ND packets.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for ND packet sending and receiving events.

diagnostic troubleshooting test nd-learn packet-trace enable

By default, diagnostic troubleshooting is enabled for ND packet sending and receiving events.

3. Perform diagnostic troubleshooting for ND packet sending and receiving events.

diagnostic troubleshooting test nd-learn packet-trace ipv6-address ipv6-address interface interface-type interface-number [ diagnostic-time diagnostic-time ]

Configuring SSH diagnostic troubleshooting

Configuring diagnostic troubleshooting for SSH client login failure events

About this task

With this feature configured, the device records SSH client login failure events within the diagnostic troubleshooting period. When the period is reached, the device displays the events for you to locate the issue.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for SSH client login failure events.

diagnostic troubleshooting test ssh-server client-login enable

By default, diagnostic troubleshooting is enabled for SSH client login failure events.

3. Perform diagnostic troubleshooting for SSH client login failure events.

diagnostic troubleshooting test ssh-server client-login { client-ipv4 ipv4-address | client-ipv6 ipv6-address } [ vpn-instance vpn-instance-name ] [ diagnostic-time diagnostic-time ]

Configuring device login diagnostic troubleshooting

Configuring diagnostic troubleshooting for telnet client login failure events

About this task

With this feature configured, the device displays telnet client login information in the specified time period to help you locate the login failure issue.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for telnet client login failure events.

diagnostic troubleshooting test telnet-server client-login enable

By default, diagnostic troubleshooting is enabled for telnet client login failure events.

3. Perform diagnostic troubleshooting for telnet client login failure events.

diagnostic troubleshooting test telnet-server client-login { client-ipv4 ipv4-address | client-ipv6 ipv6-address } [ vpn-instance vpn-instance-name ] [ diagnostic-time diagnostic-time ]

Configuring IP routing basics diagnostic troubleshooting

Configuring diagnostic troubleshooting for IPv4 unicast route changes

About this task

With diagnostic troubleshooting enabled for IPv4 unicast route changes, the device records detected IPv4 unicast route change events in the GOLD module. When you perform health diagnostic troubleshooting for IPv4 unicast route changes, the device obtains the IPv4 unicast route change events from the GOLD module, including timestamps and reasons.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for IPv4 unicast route changes.

diagnostic troubleshooting test rib ipv4-unicast enable

By default, diagnostic troubleshooting is enabled for IPv4 unicast route changes.

3. Perform diagnostic troubleshooting for IPv4 unicast route changes.

diagnostic troubleshooting test rib ipv4-unicast

Configuring diagnostic troubleshooting for IPv6 unicast route changes

About this task

With diagnostic troubleshooting enabled for IPv6 unicast route changes, the device records detected IPv6 unicast route change events in the GOLD module. When you perform health diagnostic troubleshooting for IPv6 unicast route changes, the device obtains the IPv6 unicast route change events from the GOLD module, including timestamps and reasons.

Procedure

1. Enter system view.

system-view

2. Enable diagnostic troubleshooting for IPv6 unicast route changes.

diagnostic troubleshooting test rib ipv6-unicast enable

By default, diagnostic troubleshooting is enabled for IPv6 unicast route changes.

3. Perform diagnostic troubleshooting for IPv6 unicast route changes.

diagnostic troubleshooting test rib ipv6-unicast

Displaying information about diagnostic tests

Execute the following command in any view.

display diagnostic content [ slot slot-number ] [ verbose ]

For more information about the display diagnostic content command, see System Management Command Reference.

Displaying test results

Execute the following command in any view.

display diagnostic content [ slot slot-number [ test test-name ] ] [ verbose ]

For more information about the display diagnostic result command, see System Management Command Reference.

Clearing test results

Execute the following command in user view.

reset diagnostic result [ slot slot-number [ test test-name ] ]

For more information about the reset diagnostic result command, see System Management Command Reference.

28-Intelligent Operations Configuration Guide

Configuring diagnostic troubleshooting

About diagnostic troubleshooting

Tests and test items

Overview

Diagnostic troubleshooting based on history data

Diagnostic troubleshooting based on running data

Diagnostic troubleshooting based on history or running data

Diagnostic troubleshooting based on the results of one-time actions

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Prerequisites

Procedure

About this task

Procedure

About this task

Prerequisites

Procedure

About this task

Procedure

About this task

Procedure

About this task

Procedure

About this task

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Procedure

About this task

Procedure

About this task

Procedure

About this task

Procedure

About this task

Procedure

About this task

Procedure

About this task

Procedure

About this task

Procedure

About this task

Configuring real-time diagnostic troubleshooting for user online failure events on the DHCP relay agent

Configuring diagnostic troubleshooting for user online failure history events on the DHCP relay agent

About this task

Procedure

About this task