test test-name: Specifies a test name, a case-insensitive string of 1 to 31 characters. To obtain the value range for this option, execute the diagnostic test ? command. If you do not specify this option, this command configures all test items.

test-item: Specifies a test item, a case-insensitive string of 1 to 31 characters. To obtain the value range for this option, execute the diagnostic test test-name ? command.

Usage guidelines

You can perform diagnostic troubleshooting for services running on the device only after you enable diagnostic troubleshooting.

By default, diagnostic troubleshooting is enabled for all services to facilitate device maintenance at any time. Some tests require history running data to perform diagnostic troubleshooting. After you enable diagnostic troubleshooting for a service, the service module will record the running data monitored by the test item in such tests in the GOLD module for the GOLD module to perform diagnostic troubleshooting. Recording running data consumes device resources and affects system performance. If you are not concerned about the running status of a specific service, you can disable diagnostic troubleshooting for a test item to reduce the impact on system performance.

Examples

# Enable diagnostic troubleshooting for SNMP packet processing failures.

<Sysname> system-view

[Sysname] diagnostic troubleshooting snmp-agent packet-process-failure enable

Related commands

diagnostic troubleshooting test

diagnostic troubleshooting health enable

Use diagnostic health enable to enable health diagnostic troubleshooting for a service module.

Use undo diagnostic enable to disable health diagnostic troubleshooting for a service module.

Syntax

diagnostic troubleshooting health [ module module-name ] enable

undo diagnostic troubleshooting health [ module module-name ] enable

Views

System view

Default

Health diagnostic troubleshooting is enabled for service modules.

Predefined user roles

network-admin

Parameters

module module-name: Specifies a module by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, this command enables health diagnostic troubleshooting for all service modules supported on the device.

Usage guidelines

You can perform health diagnostic troubleshooting for services running on the device only after you enable health diagnostic troubleshooting.

With health diagnostic troubleshooting enabled and configuration completed for a service module, the service module records unhealthy service information in the GOLD module for the GOLD module to perform diagnostic troubleshooting. Recording such data consumes device resources and affects system performance. If you are not concerned about the health status of a service module, you can disable health diagnostic troubleshooting for that module to reduce the impact on system performance.

Examples

# Enable health diagnostic troubleshooting for the MPLS TE module.

<Sysname> system-view

[Sysname] diagnostic troubleshooting health module te enable

Related commands

diagnostic troubleshooting health

CPU diagnostic troubleshooting commands

diagnostic troubleshooting test cpu high-ratio

Use diagnostic test cpu high-ratio to perform diagnostic troubleshooting for CPU usage threshold exceeding events.

Syntax

diagnostic troubleshooting test cpu high-ratio

Views

System view

Predefined user roles

network-admin

Usage guidelines

Operating mechanism

The system samples the CPU usage at 1-minute intervals. With diagnostic troubleshooting for CPU usage threshold exceeding events enabled, if the sample is greater than the CPU usage threshold, the device logs a CPU usage threshold exceeding event in the memory of the GOLD module. To configure the CPU usage threshold, use the monitor cpu-usage threshold command.

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.

Restrictions and guidelines

For this command to take effect, first use the diagnostic troubleshooting test cpu high-ratio enable command to enable diagnostic troubleshooting for CPU exceeding threshold events (enabled by default).

Examples

# Perform diagnostic troubleshooting for CPU usage threshold exceeding events.

<Sysname> system-view

[Sysname] diagnostic troubleshooting test cpu high-ratio

Slot 1 CPU 0 usage:

Time Usage

2022-07-25 02:37:52 30%

2022-07-25 02:32:16 28%

2022-07-25 02:22:16 28%

2022-07-25 02:12:16 27%

2022-07-25 02:52:16 29%

2022-07-25 01:32:16 28%

2022-07-25 01:12:16 25%

Slot 1 CPU 0 recent high usage records:

Time Severe threshold Minor threshold Usage

2022-07-25 02:18:52 80% 25% 30%

2022-07-25 02:18:53 80% 25% 28%

2022-07-25 02:22:16 80% 25% 28%

2022-07-25 02:12:16 80% 25% 27%

2022-07-25 02:52:16 80% 25% 29%

2022-07-25 01:32:16 80% 25% 28%

2022-07-25 01:12:16 80% 25% 25%

Top 5 slot 1 CPU 0 usage processes in the last record:

JID PID PRI State FDs HH:MM:SS Usage Name

1026 1026 120 S 1188 00:11:16 12.61% forward

999 999 120 S 190 00:00:37 5.55% ifmond

847 847 120 S 183 00:01:10 5.29% drv_app

983 983 120 S 94 00:01:00 4.76% diagd

1201 1201 120 S 199 00:02:09 4.26% pppd

Table 1 Command output

Field	Description
Slot 1 CPU 0 usage	CPU usage of CPU 0 in slot 1. A maximum of 7 events can be recorded.
Time	Time when the CPU usage was sampled.
Usage	CPU usage.
Slot 1 CPU 0 recent high usage records	CPU usage threshold exceeding events on CPU 0 of slot 1. A maximum of 7 events can be recorded.
Severe threshold	Severe CPU usage alarm threshold in percentage. If the sample is greater than the severe CPU usage threshold, the GOLD module logs a CPU usage threshold exceeding event.
Minor threshold	Minor CPU usage alarm threshold in percentage. If the sample is greater than the minor CPU usage threshold, the GOLD module logs a CPU usage threshold exceeding event.
Top 5 slot 1 CPU 0 usage processes in the last record	Information about the top five processes with the highest CPU usage on CPU 0 of slot 1 when the most recent CPU usage threshold exceeding event occurred.
JID	Job ID, which uniquely identifies a process. This ID can survive a process restart.
PID	Process ID.
PRI	Process priority. A process with a higher priority is scheduled the first.
State	State of the process: · R—Running. · S—Sleeping. · T—Traced or stopped. · D—Uninterruptible sleep. · Z—Zombie.
FDs	Number of FDs used by the process.
HH:MM:SS	Uptime of the process after the most recent startup of the process. This field displays the uptime only in hours when the uptime is equal to or longer than 100 hours.
Name	Name of the process.

Related commands

diagnostic troubleshooting enable

monitor cpu-usage threshold (System Management Command Reference)

diagnostic troubleshooting test cpu overload

Use diagnostic troubleshooting test cpu overload to perform diagnostic troubleshooting for CPU overload events.

Syntax

diagnostic troubleshooting test cpu overload

Views

System view

Predefined user roles

network-admin

Usage guidelines

Operating mechanism

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. To enable the CPU overload diagnostic test (enabled by default), use the diagnostic monitor enable command. The default execution interval for the CPU overload monitoring diagnostic test is 30 minutes. To set the interval, execute the diagnostic monitor interval command.

With diagnostic troubleshooting for CPU overload events enabled, if the difference 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.

When you execute this command, 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

For this command to take effect, first use the diagnostic troubleshooting test cpu overload enable command to enable diagnostic troubleshooting for CPU overload (enabled by default).

Examples

# Perform diagnostic troubleshooting for CPU overload events.

<Sysname> system-view

[Sysname] diagnostic troubleshooting test cpu overload

Slot 1 CPU 0 recent uasge burst records:

Time Usage(%)

2022-07-25 02:18:52 From 10 to 30

Top 5 slot 1 CPU 0 usage processes in the last record:

Process 1011 (forward)

TID LAST_CPU Stack PRI State HH:MM:SS:MSEC Name

1011 12 136K 120 S 0:8:24:620 forward

Thread (LWP 1011):

Switch counts: 1

User stack:

#0 0x00007fb893904dbd in syscall+0x1d/0x37

#1 0x00007fb896160748 in futex_async+0x48/0x50

#2 0x00007fb896161e98 in call_rcu_wait+0xa8/0xb5

#3 0x00007fb896162646 in call_rcu_thread+0x556/0x6ed

#4 0x00007fb899e742de in start_thread+0xfe/0x3e0

Kernel stack:

[<ffffffff9a1090b4>] futex_wait_queue_me+0xc4/0x120

[<ffffffff9a109d16>] futex_wait+0x116/0x270

[<ffffffff9a10bbf7>] do_futex+0x237/0xb40

[<ffffffff9a10c581>] SyS_futex+0x81/0x180

[<ffffffff9a87f3fb>] entry_SYSCALL_64_fastpath+0x1e/0xad

[<ffffffffffffffff>] 0xffffffffffffffff

Process 1016 (ifmond)

TID LAST_CPU Stack PRI State HH:MM:SS:MSEC Name

1016 5 136K 120 S 0:1:0:0 ifmond

Thread (LWP 1026):

Switch counts: 1

User stack:

#0 0x00007fb893904dbd in syscall+0x1d/0x37

#1 0x00007fb896160748 in futex_async+0x48/0x50

#2 0x00007fb896161e98 in call_rcu_wait+0xa8/0xb5

#3 0x00007fb896162646 in call_rcu_thread+0x556/0x6ed

#4 0x00007fb899e742de in start_thread+0xfe/0x3e0

Kernel stack:

[<ffffffff9a1090b4>] futex_wait_queue_me+0xc4/0x120

[<ffffffff9a109d16>] futex_wait+0x116/0x270

[<ffffffff9a10bbf7>] do_futex+0x237/0xb40

[<ffffffff9a10c581>] SyS_futex+0x81/0x180

[<ffffffff9a87f3fb>] entry_SYSCALL_64_fastpath+0x1e/0xad

[<ffffffffffffffff>] 0xffffffffffffffff

…

Table 2 Command output

Field	Description
Slot 1 CPU 0 recent uasge burst records	CPU overload events on CPU 0 of slot 1. A maximum of 7 events can be recorded.
Time	Time when the CPU usage was sampled.
Usage(%)	CPU usage in percentage.
Top 5 slot 1 CPU 0 usage processes in the last record	Information about the top five processes with the highest CPU usage on CPU 0 slot 1 when the most recent CPU overload event occurred.
Process 1011 (forward)	ID and name of the process.
TID	ID of the thread.
LAST_CPU	CPU where the process was running when the process was scheduled most recently.
Stack	Stack size, in KB.
PRI	Priority for the thread to use the CPU.
State	State of the thread: · R—Running. · S—Sleeping. · T—Traced or stopped. · D—Uninterruptible sleep. · Z—Zombie.
HH:MM:SS:MSEC	Uptime of the thread after the most recent startup of the thread.
Name	Name of the thread.
Thread (LWP 1026)	Sub thread of the thread to be tracked.
Switch counts	Number of calls for the thread.
User stack	User stack information. This field is displayed only for a user process.
Kernel stack	Kernel stack information. This field is displayed only for a kernel process.

Related commands

diagnostic monitor enable (System Management Command Reference)

diagnostic monitor interval (System Management Command Reference)

diagnostic troubleshooting enable

Memory diagnostic troubleshooting commands

diagnostic troubleshooting test memory high-ratio

Use diagnostic troubleshooting test memory high-ratio to perform diagnostic troubleshooting for insufficient free memory space events.

Syntax

diagnostic troubleshooting test memory high-ratio

Views

System view

Predefined user roles

network-admin

Usage guidelines

Operating mechanism

The system samples the free memory usage at 5-second intervals. With diagnostic troubleshooting for insufficient free memory space events enabled, if the sample is lower than the free memory usage threshold, the device logs a free memory threshold exceeding event in the memory of the GOLD module. To configure the free memory usage threshold, use the memory-threshold command.

When you execute this command, the device displays the current memory usage and the most insufficient free memory space events to help you locate the issue. The system can display a maximum of seven insufficient free memory space events.

Restrictions and guidelines

For this command to take effect, first use the diagnostic troubleshooting test memory high-ratio enable command to enable diagnostic troubleshooting for insufficient free memory space events.

Examples

# Perform diagnostic troubleshooting for insufficient free memory space events.

<Sysname> system-view

[Sysname] diagnostic troubleshooting memory high-ratio

Start diagnose at 2013-02-22 14:16:27.

End diagnose at 2013-02-22 14:16:27, Actual time:0 seconds.

Memory statistics are measured in KB:

Slot 1:

Total Used Free Shared Buffers Cached FreeRatio

Mem: 8086816 6971116 1115700 0 372 3907428 22.0%

-/+ Buffers/Cache: 30633165023500

Swap: 0 0 0

Container memory statistics are measured in KB:

Slot 1:

Total Used Free UsageRatio

Slot 1 recent high memory usage records:

Time Threshold FreeRatio

2013-02-21 13:28:21 13% 14.4%

Table 3 Command output

Field	Description
Memory statistics are measured in KB:	Memory usage information on the physical device, in KB.
Mem	Memory usage information.
Total	Total size of the physical memory space that can be allocated. The memory space is virtually divided into two parts. The size of part 2 equals the total size minus the size of part 1. Part 1 is solely used for kernel code and kernel management. Part 2 can be allocated and used for such tasks as running service modules and storing files.
Used	Used physical memory.
Free	Free physical memory.
Shared	Physical memory shared by processes. This field displays two hyphens (--) if it is not supported.
Buffers	Physical memory used for buffers. This field displays two hyphens (--) if it is not supported.
Cached	Physical memory used for caches. This field displays two hyphens (--) if it is not supported.
FreeRatio	Free memory ratio.
-/+ Buffers/Cache	-/+ Buffers/Cache:used = Mem:Used – Mem:Buffers – Mem:Cached, which indicates the physical memory used by applications. -/+ Buffers/Cache:free = Mem:Free + Mem:Buffers + Mem:Cached, which indicates the physical memory available for applications.
Swap	Memory space for swapping.
Container memory statistics are measured in KB	Container memory usage information: · Total—Total size of the physical memory space that can be allocated in the Comware container, in KB. · Used—Used physical memory in the Comware container, in KB. · Free—Free physical memory in the Comware container, in KB. · UsageRatio—Free physical memory usage in the Comware container.
Slot 1 recent high memory usage records	Memory threshold exceeding events on CPU 0 of slot 1. A maximum of 7 events can be recorded.
Time	Time when the insufficient free memory space event occurred.
Threshold	Memory threshold.

Related commands

diagnostic troubleshooting enable

memory-threshold (System Management Command Reference)

diagnostic troubleshooting test memory overload

Use diagnostic troubleshooting test memory overload to perform diagnostic troubleshooting for memory overload events.

Syntax

diagnostic troubleshooting test memory overload

Views

System view

Predefined user roles

network-admin

Usage guidelines

Operating mechanism

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. To enable the memory overload diagnostic test (enabled by default), use the diagnostic monitor enable command. The default execution interval for the memory overload monitoring diagnostic test is 12 hours. To set the interval, execute the diagnostic monitor interval command.

With diagnostic troubleshooting for memory overload events enabled, if the different 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.

When you execute this command, the device displays the following information to help you locate the 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

For this command to take effect, first use the diagnostic troubleshooting test memory overload enable command to enable diagnostic troubleshooting for memory overload events.

Examples

# Perform diagnostic troubleshooting for memory overload events.

<Sysname> system-view

[Sysname] diagnostic troubleshooting memory overload

Slot 1 recent memory usage burst records:

Time Memory used (MB)

2022-07-25 08:18:52 From 456 to 556

2022-07-25 07:18:52 From 456 to 556

2022-07-25 06:18:52 From 456 to 556

2022-07-25 05:18:52 From 456 to 556

2022-07-25 04:18:52 From 456 to 556

2022-07-25 03:18:52 From 456 to 556

2022-07-25 02:18:52 From 456 to 556

Slot 1 top 5 memory usage processes in the last record:

Process: scmd (jobID 1)

Total allocated memory: 393760 bytes

Total free memory: 144672 bytes

Heap usage of the job:

Tag UsedBlocks UsedBytes FreeBlocks FreeBytes

0x0 1412 362704 24 144304

0x1060000 2 96 0 0

0x1090000 0 0 3 240

0x10b0000 3 96 2 64

0x1120000 7 2496 0 0

0x1150000 1 64 1 64

0x1570000 1 11536 0 0

0x15a0000 26 16768 0 0

Process: aaa (jobID 2)

Total allocated memory: 393760 bytes

Total free memory: 144672 bytes

Heap usage of the job:

Tag UsedBlocks UsedBytes FreeBlocks FreeBytes

0x0 1412 362704 24 144304

0x1060000 2 96 0 0

0x1090000 0 0 3 240

0x10b0000 3 96 2 64

0x1120000 7 2496 0 0

0x1150000 1 64 1 64

0x1570000 1 11536 0 0

0x15a0000 26 16768 0 0

Table 4 Command output

Field	Description
Slot 1 recent memory usage burst records	Most recent memory overload events on slot 1. A maximum of 7 events can be recorded.
Time	Time when the memory overload event was triggered.
Memory used (MB)	Used memory in the last sample and the current sample in MB, respectively.
Slot 1 top 5 memory usage processes in the last record	Memory usage information for the top 5 processes with the highest memory usage increase.
Process: scmd (jobID 1)	Process with a name of scmd and job ID of 1.
Total allocated memory	Size of heap memory used by the process, in bytes.
Total free memory	Size of free heap memory for the process, in bytes.
Heap usage of the job	Heap memory usage of the process.
Tag	ID of the system internal software module.
UsedBlocks	Number of used memory blocks.
UsedBytes	Size of used memory, in bytes.
FreeBlocks	Number of free memory blocks.
FreeBytes	Size of free memory, in bytes.

Related commands

diagnostic monitor enable (System Management Command Reference)

diagnostic monitor interval (System Management Command Reference)

diagnostic troubleshooting enable

LDP diagnostic troubleshooting commands

diagnostic troubleshooting health module ldp

Use diagnostic troubleshooting health module ldp to enable health diagnostic troubleshooting for the LDP module.

Syntax

diagnostic troubleshooting health module ldp

Views

System view

Predefined user roles

network-admin

Usage guidelines

Use this command to identify whether the LDP module is running correctly. When you execute this command, the device displays the unhealthy information for you to locate the issue.

For this command to take effect, first use the diagnostic troubleshooting health module ldp enable command to enable health diagnostic troubleshooting for the LDP module.

Examples

# Perform health diagnostic troubleshooting for the LDP module.

<Sysname> system-view

[Sysname] diagnostic troubleshooting health module ldp enable

[Sysname] diagnostic troubleshooting health module ldp

Show LDP health events:

--------------------------------------------------------------------------------

Health event Detect time Description

--------------------------------------------------------------------------------

RES_LABEL_ALLOC_FAIL 2022-4-20 10:01:50 Failed to alloc labels to LDP. (ErrorCode=[1] )

Table 5 Command output

Field	Description
Health event	Health event type: · RES_LABEL_ALLOC_FAIL—The system fails to allocate LDP labels. · RES_LABEL_ALLOC_RESUME—The number of available LDP labels has restored.
Detect time	Time when the event was triggered.
Description	Description of the event.

Related commands

diagnostic troubleshooting health enable

diagnostic troubleshooting test neighbor-create-abnormal ldp

Use diagnostic troubleshooting test neighbor-create-abnormal ldp to perform diagnostic troubleshooting for LDP session setup failure events.

Syntax

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 ]

Views

System view

Predefined user roles

network-admin

Parameters

local: Specifies a local LDP session.

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, this command performs diagnostic troubleshooting for LDP session setup failure events for the public network.

peer peer-lsr-id: Specifies an LDP peer by its LSR ID.

interface-type interface-number: Specifies an interface by its type and number.

remote peer peer-lsr-id: Specifies a remote LDP peer by its LSR ID.

diagnostic-time diagnostic-time: Specifies the estimated diagnostic troubleshooting duration, in the range of 1 to 60 seconds. The default value is 30 seconds. The actual duration might be different, but will not be greater than 2*diagnostic-time.

Usage guidelines

For this command to take effect, first use the diagnostic troubleshooting test neighbor-create-abnormal ldp enable command to enable diagnostic troubleshooting for LDP session setup failure events.

With health diagnostic troubleshooting enabled and configuration completed for the LDP module, the LDP module records LDP session setup failure events in the GOLD module for the GOLD module to perform diagnostic troubleshooting.

Recording LDP session setup failure 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 session setup failure events.

Examples

# Perform diagnostic troubleshooting for LDP session setup failure events.

<Sysname> system-view

[Sysname] diagnostic troubleshooting test neighbor-create-abnormal ldp enable

[Sysname] diagnostic troubleshooting test neighbor-create-abnormal ldp remote peer 2.2.2.2

Start diagnose at 2022-09-29 06:41:20, Estimated time:30 seconds.

Please wait.....................Done.

End diagnose at 2022-09-29 06:41:40, Actual time:30 seconds.

Diagnosis report:

--------------------------------------------------------------------------------

PeerID Status Reason

2.2.2.2 NOT_EXISTENT No LSR-ID

--------------------------------------------------------------------------------

Table 6 Command output

Field	Description
Peer ID	LSR ID of the LDP peer.
Status	LDP session status: · NOT_EXISTENT—The session does not exist. · INITIALIZED—The session is being initialized. · OPEN_SENT—The session has sent an Init message and is waiting for the Init message from the peer. · OPEN_RECV—The session has been sent an Open message and is waiting for the Open message from the peer. · OPER—The session is in up state.
Reason	Reason why the LDP session cannot be set up: · Device in memory-threshold. · No LSR-ID. · Local interface down. · Local interface has no IPv4 address. · Local interface has no MPLS capability. · Local interface has no LDP capability. · No hello packet received. · No target peer.

Related commands

diagnostic troubleshooting enable

diagnostic troubleshooting test neighbor-flap ldp

Use diagnostic troubleshooting test neighbor-flap ldp to perform diagnostic troubleshooting for LDP peer down events.

Syntax

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

Views

System view

Predefined user roles

network-admin

Parameters

peer peer-lsr-id: Specifies an LDP peer by its LSR ID.

Usage guidelines

For this command to take effect, first use the diagnostic troubleshooting test neighbor-flap ldp enable command to enable diagnostic troubleshooting for LDP peer down events.

With health diagnostic troubleshooting enabled and configuration completed for the LDP module, the LDP module records LDP peer down events in the GOLD module for the GOLD module to perform diagnostic troubleshooting. 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.

Examples

# Perform diagnostic troubleshooting for down events of the LDP peer at 2.2.2.2.

<Sysname> system-view

[Sysname] diagnostic troubleshooting neighbor-flap ldp enable

[Sysname] diagnostic troubleshooting neighbor-flap ldp peer 2.2.2.2

Started at: 2022-06-29 07:08:38, estimated duration: 30 seconds.

Please wait......................

Ended at: 2022-06-29 07:09:08, actual duration: 30 seconds.

Diagnosis report:

--------------------------------------------------------------------------------

PeerID Down time Duration time Reason

2.2.2.2 2022-04-01 10:15:35 1h32m19s Interface not operational

--------------------------------------------------------------------------------

Table 7 Command output

Field	Description
PeerID	LSR ID of the LDP peer.
Down time	Time when the LDP peer was down.
Duration time	Duration that the peer is in down state.
Reason	Reason that the LDP peer was down: · Interface not operational. · MPLS disabled on interface. · LDP disabled on interface. · LDP auto-configure disabled on interface. · VPN instance changed on interface. · LDP instance deleted. · Targeted peer deleted. · L2VPN disabled targeted peer. · TE tunnel disabled targeted peer. · Session protection disabled targeted peer. · OSPF Remote LFA disabled targeted peer. · IS-IS Remote LFA disabled targeted peer. · Process deactivated. · Failed to receive the initialization message. · Graceful restart reconnect timer expired. · Failed to recover adjacency by NSR. · Failed to upgrade session by NSR. · Closed the GR session. · Keepalive hold timer expired. · Hello hold timer expired. · Session reset. · TCP connection down. · Received a fatal notification message. · Internal error. · Memory in critical state. · Transport address changed on interface. · MD5 password changed.

MPLS TE diagnostic troubleshooting commands

diagnostic troubleshooting health module te

Use diagnostic troubleshooting health module te to enable health diagnostic troubleshooting for the MPLS TE module.

Syntax

diagnostic troubleshooting health module te

Views

System view

Predefined user roles

network-admin

Usage guidelines

Use this command to identify when the MPLS TE module is running correctly. When you execute this command, the device displays the unhealthy information for you to locate the issue.

For this command to take effect, first use the diagnostic troubleshooting health module te enable command to enable health diagnostic troubleshooting for the MPLS TE module.

Examples

# Perform health diagnostic troubleshooting for the MPLS TE module.

<Sysname> system-view

[Sysname] diagnostic troubleshooting health module te enable

[Sysname] diagnostic troubleshooting health module te

Show TE health events:

--------------------------------------------------------------------------------

Health event Detect time Description

--------------------------------------------------------------------------------

BSID_ALLOC_FAILED 2022-4-20 10:01:50 Tunnel 1 allocated

binding-sid label

15999 failed.

Table 8 Command output

Field	Description
Health event	Health event type. The value is BSID_ALLOC_FAILED, which indicates that the MPLS TE tunnel has failed to apply for a BSID.
Detect time	Time when the event was triggered.
Description	Description of the event.

Related commands

diagnostic troubleshooting health module te enable

diagnostic troubleshooting test te-tunnel establish-abnormal

Use diagnostic troubleshooting test te-tunnel establish-abnormal to perform diagnostic troubleshooting for MPLS TE tunnel setup failure events.

Syntax

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

Views

System view

Predefined user roles

network-admin

Parameters

tunnel tunnel-id: Specifies a tunnel ID.

diagnostic-time diagnostic-time: Specifies the estimated diagnostic troubleshooting duration, in the range of 10 to 300 seconds. The default value is 120 seconds. The actual duration might be different, but will not be greater than 2*diagnostic-time.

Usage guidelines

For this command to take effect, first use the diagnostic troubleshooting test te-tunnel establish-abnormal enable command to enable diagnostic troubleshooting for MPLS TE tunnel setup failure events.

With health diagnostic troubleshooting enabled and configuration completed for the MPLS TE module, the LDP module records MPLS TE tunnel setup failure events in the GOLD module for the GOLD module to perform diagnostic troubleshooting. 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.

Examples

# Perform diagnostic troubleshooting for tunnel setup failure events of MPLS TE tunnel 1.

<Sysname> system-view

[Sysname] diagnostic troubleshooting test te-tunnel establish-abnormal enable

[Sysname] diagnostic troubleshooting test te-tunnel establish-abnormal tunnel 1

Started at: 2022-06-29 07:08:38, estimated duration: 30 seconds.

Please wait......................

Ended at: 2022-06-29 07:09:08, actual duration: 30 seconds.

Diagnosis report:

(M): Modify LSP

--------------------------------------------------------------------------------

Tunnel Name: Tunnel1

Ingress LSR ID: 1.1.1.1 Egress LSR ID: 3.3.3.3

LSP type : Main Detect time: 2022-4-20 10:01:50

Reason: RSVP not configured on interface HGE1/0/1 with IP address 10.1.1.1 on LSR 1.1.1.1.

LSP type : Hot-standby Detect time: 2022-4-20 10:01:52

Reason: CSPF computation failed.

--------------------------------------------------------------------------------

Table 9 Command output

Field	Description
LSP type	LSP type. Options include: · Main. · Hot-standby. · (M)—LSP through MBB.
Detect Time	Time when the diagnostic troubleshooting result was obtained.
Reason	Reason for the MPLS TE tunnel setup failure: · Establish success. · The destination not configured. · The MPLS LSR-ID not configured. · The MPLS TE not configured. · The tunnel has been shut down. · LSPM isn't running. · SRM isn't running. · RSVP isn't running. · LSPM isn't running. · No out segment of the SR label. · Segment routing path compute failed. · Segment routing path verification failed. · Equal-cost backup LSP not supported. · Backup LSP is the same as main LSP. · SR path compute element not respond. · Backup LSP sharing the same SRLG with the main LSP. · Main and backup LSPs can't be equal-cost paths. · SR out segment is tunnel itself. · SR out segment is too deep. · Modify unchanged. · RSVP path compute failed. · RSVP not configured on interface HGE1/0/1 of LSR 1.1.1.1. · RSVP signaling error(24,1) occurred on the LSR 1.1.1.1. · RSVP LSP can't be established with nextsid in explicit-path. · RSVP downstream is not responding. · RSVP busy. · Unreferenced to any static CRLSP or SRLSP.Static CRLSP is down. · Static CRLSP busy. · LSP or tunnel BFD down. · Delegated tunnel without PCE update. · Minor memory-threshold. · Critical memory-threshold. · Unknown error. · Backup LSP is the same as main LSP.

Related commands

diagnostic troubleshooting test te-tunnel establish-abnormal enable

diagnostic troubleshooting test te-tunnel lsp-event

Use diagnostic troubleshooting test te-tunnel lsp-event to perform diagnostic troubleshooting for MPLS TE tunnel down and path switchover events.

Syntax

diagnostic troubleshooting test te-tunnel lsp-event [ flap | switch ] tunnel tunnel-id

Views

System view

Predefined user roles

network-admin

Parameters

flap: Specifies MPLS TE tunnel down events.

switch: Specifies MPLS TE path switchover events.

tunnel tunnel-id: Specifies a tunnel interface number.

Usage guidelines

If you do not specify the flap and switch keywords, the command performs diagnostic troubleshooting for both MPLS TE tunnel down and path switchover events.

For this command to take effect, first use the diagnostic troubleshooting test te-tunnel lsp-event enable command to enable diagnostic troubleshooting for MPLS TE tunnel down and path switchover events.

When you execute this command, the device displays the most recent five MPLS TE tunnel down events and most recent five path switchover events to help you locate the issue.

This task is applicable only to MPLS TE tunnels set up using segment routing.

With health diagnostic troubleshooting enabled and configuration completed for the MPLS TE module, the MPLS TE module records MPLS TE tunnel down and path switchover events in the GOLD module for the GOLD module to perform diagnostic troubleshooting.

Recording MPLS TE tunnel down and path switchover 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 down and path switchover events.

Examples

# Perform diagnostic troubleshooting for tunnel down and path switchover events of the MPLS TE tunnel with a tunnel interface number of 1.

<Sysname> system-view

[Sysname] diagnostic troubleshooting test te-tunnel lsp-event enable

[Sysname] diagnostic troubleshooting test te-tunnel lsp-event tunnel 1

Tunnel Name:Tunnel1

IngressLSRID:1.1.1.1 EgressLSRID:3.3.3.3

Admin state: Normal Tunnel state: Up

Path state:

Main path info : 1.1.1.1/1/61103 State: Active

Backup path info: 1.1.1.1/1/61104 State: Up

--------------------------------------------------------------------------------

Last five lsp-flap events:

LSP type:Main Down time:2022-4-20 10:01:50

Reason: The interface with IP address 10.1.1.1 went down.

LSP Type:Hot-standby Down Time: 2022-4-20 10:01:52

Reason: Configuration changed.[shutdown]

--------------------------------------------------------------------------------

Last five lsp-switch events:

Switch type : Main LSP recovered Switch time: 2021-8-14 14:30:29.734

Reason : Main LSP up

Path details:

Old path : 16010 - 2371 - 17030

New path : 16010 – 1802

Switch type : Backup LSP inused Switch time: 2021-8-14 14:30:29.734

Reason : Main LSP down

Path detail:

Old path : 16010 – 1802

New path : 16010 - 2371 - 17030

Table 10 Command output

Field	Description
Admin state	Administrative state of the tunnel interface: · Normal—The interface is not shut down by the shutdown command. · Shutdown—The tunnel interface is shut down by the shutdown command.
Tunnel state	Running state of the tunnel: Down or Up.
Path state	State of each LSP on the tunnel.
Main path info	Main path information: · Ingress LSR ID. · Tunnel ID. · LSP ID.
Backup path info	Backup path information: · Ingress LSR ID. · Tunnel ID. · LSP ID.
State	State of the path: · Active—The SRLSP has been set up successfully and the SRLSP is used to forward traffic. · Up—The SRLSP has been set up successfully. · Down—The SRLSP is not set up or has failed to be set up.
Last five times lsp-flap record	Most recent five tunnel down events.
LSP type	LSP type: · Main. · Hot-standby.
Down time	Time when the tunnel went down.
Reason	Tunnel down reason: · No out segment. · IGP calculated path failed. · SRLG check failed. · Configuration changed. · PCE state recover.
Switch Type	Path switching type: · Backup LSP inused—Traffic has been switched to the backup path because the primary path failed. · Main LSP recovered—Traffic has been switched back to the primary path because the primary path recovered. · Main LSP make-before-break—Primary path MBB caused by configuration change or other reasons.
Switch Time	Time when the SRLSP switched its path.
Reason	Reason why a path switching has occurred: · Main LSP down. · Main LSP up. · Main LSP BFD down. · Main LSP BFD up. · Configuration changed.
Path detail	Detailed information for the path.
Old path	Path before switching, which is displayed as a stack of labels from top to bottom and the next hop address.
New path	Path after switching, which is displayed as a stack of labels from top to bottom and the next hop address.

Related commands

diagnostic troubleshooting test te-tunnel lsp-event enable

MPLS L2VPN diagnostic troubleshooting commands

diagnostic troubleshooting health module l2vpn

Use diagnostic troubleshooting health module l2vpn to perform heath diagnostic troubleshooting for the MPLS L2VPN module.

Syntax

diagnostic troubleshooting health module l2vpn

Views

System view

Predefined user roles

network-admin

Usage guidelines

Use this command to identify when the MPLS L2VPN module is running correctly. When you execute this command, the device displays the unhealthy information for you to locate the issue.

For this command to take effect, first use the diagnostic troubleshooting health module l2vpn enable command to enable health diagnostic troubleshooting for the MPLS L2VPN module.

Examples

# Perform health diagnostic troubleshooting for the MPLS L2VPN module.

<Sysname> system

[Sysname] diagnostic troubleshooting health module l2vpn enable

[Sysname] diagnostic troubleshooting health module l2vpn

Show L2VPN health events:

--------------------------------------------------------------------------------

Health event Detect time Description

LABEL_NOT_ALLOCATED 04-15 07:37:06 ESI failed to apply for the label.

(IfName=Vpna)

LABEL_NOT_ALLOCATED 04-15 07:37:06 Upwesi failed to apply for the

label.(VsiName=Vpna,PwId=200)

LABEL_NOT_ALLOCATED 04-15 07:37:06 EVPN VPLS failed to apply for the

label.(VsiName=Vpna)

LABEL_NOT_ALLOCATED 04-15 07:37:06 EVPN VPWS failed to apply for the

label.(XcgName=Xpna)

VN_EXCEED 04-15 07:38:16 Too many VNs.(

VsiName=Vpna,IpAaddr=1.1.1.1,PwId=200)

SRV6SID_NOT_ALLOCATED 04-15 07:38:16 SRv6 SID alloc failed.(VsiName=Vpna)

CONNECT_FAIL 04-15 07:38:16 The connection between l2vpn and l3vpn

failed. (ModeName=L3vpn)

AC_VIBRATE 04-15 07:38:16 AC flapping.(Minute=10,DataNum=20,

OscillationNum=30)

PW_VIBRATE 04-15 07:38:16 PW flapping.(Minute=10,DataNum=20,

OscillationNum=30)

COMMUNICATION_FAIL 04-15 07:38:16 RIB tunnel exception.(IpAddr=

10.1.1.2)

SMOOTH_SUCCESS 04-15 07:38:16 After l2vpn and ldp are smoothed,10 pwm

data are aged.(DataType=Ldp,Uismooth=10)

SMOOTH_EXCEED 04-15 07:38:16 L2vpn timed out for 60 minutes waiting for

ldp smooth end.(DataType=Ldp)

HA_RECOVER_FAIL 04-15 07:38:16 VSI vpna link ID HA recovery failed.

Table 11 Command output

Field	Description
Diag_Type	Health event type: · LABEL_NOT_ALLOCATED. · LINKID_NOT_ALLOCATED. · VN_EXCEED. · SRV6SID_NOT_ALLOCATED. · CONNECT_FAIL. · COMMUNICATION_FAIL. · HA_RECOVER_FAIL. · SMOOTH_EXCEED. · SMOOTH_SUCCESS. · PW_VIBRATE. · AC_VIBRATE.
Detect-Time	Time when the event was detected.
Description	Description of the event.

Related commands

diagnostic troubleshooting health module l2vpn enable

diagnostic troubleshooting test l2vpn-pw establish-abnormal

Use diagnostic troubleshooting test l2vpn-pw establish-abnormal to perform diagnostic troubleshooting for PW setup failure events.

Syntax

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

Views

System view

Predefined user roles

network-admin

Parameters

vsi vsi-name: Specifies a VSI by its name, a case-sensitive string of 1 to 31 characters.

xconnect-group-name group-name: Specifies a cross-connect group by its name, a case-sensitive string of 1 to 31 characters.

connection connection-name: Specifies a cross-connect by its name, a case-sensitive string of 1 to 20 characters. The name cannot contain hyphens (-).

peer ip-address: Specifies a peer PE by its LSR ID.

pw-id pw-id: Specifies the PW ID in the range of 1 to 4294967295.

Usage guidelines

For this command to take effect, first use the diagnostic troubleshooting test l2vpn-pw establish-abnormal enable command to enable diagnostic troubleshooting for PW setup failure events.

With health diagnostic troubleshooting enabled and configuration completed for the MPLS L2VPN module, the MPLS L2VPN module records PW setup failure events in the GOLD module for the GOLD module to perform diagnostic troubleshooting.

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.

Examples

# Perform diagnostic troubleshooting for setup events of the PW in the VSI with a name of vpna.

<Sysname> system-view

[Sysname] diagnostic troubleshooting test l2vpn-pw establish-abnormal enable

[Sysname] diagnostic troubleshooting test l2vpn-pw establish-abnormal vsi vpna peer 1.1.1.9 pw-id 1

Started at: 2022-06-29 07:08:38, estimated duration: 30 seconds.

Please wait......................

Ended at: 2022-06-29 07:09:08, actual duration: 30 seconds.

Diagnosis report:

--------------------------------------------------------------------------------

Peer IP PW ID PW Type Reason(All need resolved)

1.1.1.9 1 vlan MTU not match

--------------------------------------------------------------------------------

Table 12 Command output

Field	Description
Peer IP	IP address of the peer PE.
PW Type	Data encapsulation type for the MPLS PW. Optional data encapsulation types for an MPLS PW include Ethernet and VLAN. This field displays a hyphen (-) if no data encapsulation type is specified for the MPLS PW.
Reason	Reason why the PW went down: · BFD session for PW down. · BGP RD was deleted. · BGP RD was empty. · Control word not match. · Encapsulation not match. · Label not allocated. · LDP interface parameter not match. · Local and remote LDP PWs have different TAIIs. · Non-existent remote LDP PW. · Local AC Down. · Local AC was non-existent. · Local LDP PW VN defect. · Local LDP PW was not sent mapping message. · Local VSI Down. · MTU not match. · Remote AC Down. · Remote LDP PW VN defect. · PW down after created. · Tunnel Down.

Related commands

diagnostic troubleshooting test l2vpn-pw establish-abnormal enable

diagnostic troubleshooting test l2vpn-pw flap

Use diagnostic troubleshooting test l2vpn-pw flap to perform diagnostic troubleshooting for PW down events.

Syntax

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

Views

System view

Predefined user roles

network-admin

Parameters

vsi vsi-name: Specifies a VSI by its name, a case-sensitive string of 1 to 31 characters.

xconnect-group-name group-name: Specifies a cross-connect group by its name, a case-sensitive string of 1 to 31 characters.

connection connection-name: Specifies a cross-connect by its name, a case-sensitive string of 1 to 20 characters. The name cannot contain hyphens (-).

peer ip-address: Specifies a peer PE by its LSR ID.

pw-id pw-id: Specifies the PW ID in the range of 1 to 4294967295.

Usage guidelines

For this command to take effect, first use the diagnostic troubleshooting test l2vpn-pw flap enable command to enable diagnostic troubleshooting for PW down events.

With health diagnostic troubleshooting enabled and configuration completed for the MPLS L2VPN module, the MPLS L2VPN module records PW down events in the GOLD module for the GOLD diagnostic perform diagnostic troubleshooting.

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.

Examples

# Perform diagnostic troubleshooting for PW down events of the PW in the VSI with a name of vpna.

<Sysname> system

[Sysname] diagnostic troubleshooting test l2vpn-vsi-pw flap vsi vpna peer 1.1.1.9 pw-id 1

Started at: 2022-06-29 07:08:38, estimated duration: 30 seconds.

Please wait......................

Ended at: 2022-06-29 07:09:08, actual duration: 30 seconds.

Diagnosis report:

----------------------------------------------------------------------------------------Peer IP PW ID PW type State Change time Reason

1.1.1.9 1 vlan Down->Up 2018/08/01 07:33:22 Tunnel Up

1.1.1.9 1 vlan Up->Down 2018/08/01 07:29:58 Tunnel Down

Table 13 Command output

Field	Description
Peer IP	IP address of the peer PE.
PW ID	ID of the PW.
PW type	Data encapsulation type for the MPLS PW. Optional data encapsulation types for an MPLS PW include Ethernet, VLAN, and Unknown. This field displays a hyphen (-) if no data encapsulation type is specified for the MPLS PW.
State	State change of the PW.
Change time	Time when the PW state changed.
Reason	Reason why the PW went down: · BFD session for PW down. · BGP RD was deleted. · BGP RD was empty. · Control word not match. · Encapsulation not match. · Label not allocated. · LDP interface parameter not match. · Local and remote LDP PWs have different TAIIs. · Non-existent remote LDP PW. · Local AC Down. · Local AC was non-existent. · Local LDP PW VN defect. · Local LDP PW was not sent mapping message. · Local VSI Down. · MTU not match. · Remote AC Down. · Remote LDP PW VN defect. · PW down after created. · Tunnel Down.

Related commands

diagnostic troubleshooting test l2vpn-pw flap enable

Ping diagnostic troubleshooting commands

diagnostic troubleshooting test ping failed-reason

Use diagnostic troubleshooting test ping failed-reason to perform diagnostic troubleshooting for ping failure events.

Syntax

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 }

Views

System view

Predefined user roles

network-admin

Parameters

-a source-ip: Specifies an IP address of the device as the source IP address of ICMP echo requests. If this option is not specified, the source IP address of ICMP echo requests is the primary IP address of the outbound interface.

-f: Sets the "Don’t Fragment" bit in the IP header.

-i interface-type interface-number: Specifies the source interface for ICMP echo requests. If you do not specify this option, the system uses the primary IP address of the matching route's egress interface as the source interface for ICMP echo requests.

-s packet-size: Specifies the length (in bytes) of ICMP echo requests (excluding the IP packet header and the ICMP packet header). The value range is 20 to 9600, and the default is 56.

-t timeout: Specifies the timeout time (in milliseconds) of an ICMP echo reply. The value range is 0 to 65535, and the default is 2000. If the source does not receive an ICMP echo reply within the timeout, it determines that the ICMP echo reply has timed out.

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance to which the destination belongs. The vpn-instance-name argument represents the VPN instance name, a case-sensitive string of 1 to 31 characters. If the destination is on the public network, do not specify this option.

ip-address ipv4-address: Specifies IPv4 trap packets by its destination IPv4 address.

ipv6-address ipv6-address: Specifies IPv6 trap packets by its destination IPv6 address.

Usage guidelines

Operating mechanism

When you execute this command, 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 issue.

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

Restrictions and guidelines

For this command to take effect, first use the diagnostic troubleshooting test ping failed-reason enable command to enable diagnostic troubleshooting for ping failure events (enabled by default).

Examples

# Perform diagnostic troubleshooting for the ping operation to the destination at 2.1.1.1. The outgoing interface is Gigabitethernet 1/0/1.

<Sysname> system-view

[Sysname] diagnostic troubleshooting test ping fail-reason –i gigabitethernet 1/0/1 ip 2.1.1.1

Diagnosis report:

Ping failed.

Failure reason: An incorrect outgoing interface was specified.

# Perform diagnostic troubleshooting for the ping operation to the destination at 1.1.1.1.

<Sysname> system-view

[Sysname] diagnostic troubleshooting test ping fail-reason ip-address 1.1.1.1

Diagnosis report:

Ping succeeded.

Table 14 Command output

Field	Description
Diagnosis report	Diagnosis report
Failure reason	For the failure reason, see Table 15.

Table 15 Ping failure reason description

Field
The link transmission delay is too long.
The ping packet is too large and discarded.
An incorrect outgoing interface was specified.
No reachable routes exist between the source and destination IPs.
The specified destination VPN is incorrect.
No APR entry to the destination exists.
No FIB entry to the destination exists.
ICMP packets are discarded due to ICMP attack defense.
Unknown reason.

Related commands

diagnostic troubleshooting enable

SNMP diagnostic troubleshooting commands

diagnostic troubleshooting test snmp-agent packet-process-failure

Use diagnostic troubleshooting test snmp-agent packet-process-failure to perform diagnostic troubleshooting for SNMP packet processing failure events.

Syntax

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 ]

Views

System view

Predefined user roles

network-admin

Parameters

ip-address ipv4-address: Specifies an IPv4 address. For received SNMP packets, this address is used to filter SNMP source addresses. For sent SNMP packets, this address is used to filter SNMP destination addresses.

ipv6-address ipv6-address: Specifies an IPv6 address. For received SNMP packets, this address is used to filter SNMP source addresses. For sent SNMP packets, this address is used to filter SNMP destination addresses.

diagnostic-time diagnostic-time: Specifies the estimated diagnostic troubleshooting duration, in the range of 60 to 1800 seconds. The default value is 300 seconds. The actual duration might be different, but will not be greater than 2*diagnostic-time.

Usage guidelines

Operating mechanism

When you execute this command, 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 issue.

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

Restrictions and guidelines

For this command to take effect, first use the diagnostic troubleshooting test snmp-agent packet-process-failure enable command to enable diagnostic troubleshooting for SNMP packet processing failure events (enabled by default).

Examples

# Perform diagnostic troubleshooting for SNMP packet processing failure events.

<Sysname> system-view

[Sysname] diagnostic troubleshooting test snmp-agent packet-process-failure ip-address 1.1.1.1

Started at: 2022-06-29 07:08:38, estimated duration: 30 seconds.

Please wait.....................

Ended at: 2022-06-29 07:09:08, actual duration: 30 seconds.

Diagnosis report:

SNMP global statistics

SNMP packets received: 4

SNMP packets sent: 4

Receiving failure detailed information:

RecvTime : 2022-06-07, 15:20:38:230

ReqID : 0

SourceIP/VPN : 10.1.1.1/--

Verison/PDU type: v3/--

FailReason : Unknown user name.

Solution : Please check the corresponding configuration.

RecvTime : 2022-06-07, 15:20:38:230

ReqID : 0

SourceIP/VPN : 10.1.1.1/--

Verison/PDU type: v3/--

FailReason : Unknown username.

Solution : Please check the corresponding configuration.

RecvTime : 2022-06-07, 15:20:38:230

ReqID : 0

SourceIP/VPN : 10.1.1.1/--

Verison/PDU type: v3/--

FailReason : Unknown username.

Solution : Please check the corresponding configuration.

Sending failure detailed information:

SendTime : 2022-06-10, 19:30:35:288

ReqID : 1683

DestIP/VPN : 10.1.1.15/vpn1

Verison/PDU type : v3/--

FailReason : SNMP PDUs had OuttooBig error-status.

Solution : Please check the corresponding configuration.

SendTime : 2022-06-10, 19:30:35:288

ReqID : 1683

DestIP/VPN : 10.1.1.15/vpn1

Verison/PDU type : v3/--

FailReason : SNMP PDUs had OuttooBig error-status.

Solution : Please check the corresponding configuration.

Table 16 Command output

Field	Description
RecvTime	Time when the SNMP packets were received.
SendTime	Time when the SNMP packets were sent.
ReqID	Request ID carried in the SNMP packets.
SourceIP/VPN	Source IP address and VPN information in the received SNMP packets.
DestIP/VPN	Destination IP address and VPN information in the sent SNMP packets.
FailReason	For the failure reason, see Table 17.
Solution	Solution for the failure. The value is Please check the corresponding configuration.

Table 17 SNMP packet processing failure reason

Field
Unknown securitymodel
Invalid messages
Unknown PDU handlers
Unsupported security level
Message is not in the time window
Unknown username
Unknown engine IDs
Wrong digests
Decryption error
Unsupported version
ASN.1 or BER errors in the process of decoding
Unknown SNMP community name
Operation not supported by the community
SNMP PDUs had an IntooBig error
SNMP PDUs had an InnoSuchName error
SNMP PDUs had an InBadValue error
SNMP PDUs had an IngenErr error
SNMP PDUs had an OuttooBig erro
SNMP PDUs had an OutnoSuchName error
SNMP PDUs had an OutBadValue error
SNMP PDUs had an OutgenErr error
Alternate response class PDUs dropped silently
Forwarded confirmed class PDUs dropped silently
Unavailable contexts
Unknown contexts

Related commands

diagnostic troubleshooting enable

diagnostic troubleshooting test snmp-agent packet-process-time

Use diagnostic troubleshooting test snmp-agent packet-process-time to perform diagnostic troubleshooting for long SNMP packet processing duration events.

Syntax

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 ]

Views

System view

Predefined user roles

network-admin

Parameters

ip-address ipv4-address: Specifies the source IPv4 address in the received IPv4 SNMP packets.

ipv6-address ipv6-address: Specifies the source IPv6 address in the received IPv6 SNMP packets.

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance to which the destination belongs. The vpn-instance-name argument represents the VPN instance name, a case-sensitive string of 1 to 31 characters. If the destination is on the public network, do not specify this option.

Usage guidelines

Operating mechanism

When you execute this command, 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 issue.

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

Restrictions and guidelines

For this command to take effect, first use the diagnostic troubleshooting test snmp-agent packet-process-time enable command to enable diagnostic troubleshooting for long SNMP packet processing duration events (enabled by default).

Examples

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

<Sysname> system-view

[Sysname] diagnostic troubleshooting snmp-agent packet-process-time

Started at: 2022-06-29 07:08:38, estimated duration: 30 seconds.

Please wait......................

Ended at: 2022-06-29 07:09:08, actual duration: 30 seconds.

Diagnosis report:

SNMP global statistics

SNMP packets received : 2

RecvTime : 2022-06-08, 09:07:20:568

ReqID : 1121

SourceIP/VPN : 10.1.1.1/-

Version/PDU type: v2c/get-next

SNMPTime (ms) : 0

APPTime (ms) : 0

TotalTime (ms) : 0

VBNum : 3

VB : sysUpTime.0(1.3.6.1.2.1.1.3.0)=1008561, sysName.0(1.3.6.1.2.1.1.5.0)=Sysname, sysServices.0(1.3.6.1.2.1.1.7.0)=86

RecvTime : 2022-06-08, 10:25:20:568

ReqID : 1650

SourceIP/VPN : 10.1.1.5/-

Version/PDU type: v1/get-next

SnmpTime(ms) : 0

AppTime(ms) : 0

TotalTime(ms) : 0

VBNum : 3

VB : sysUpTime.0(1.3.6.1.2.1.1.3.0)=100881, sysName.0(1.3.6.1.2.1.1.5.0)=Sysname, sysServices.0(1.3.6.1.2.1.1.7.0)=65

Table 18 Command output

Field	Description
RecvTime	Time when the SNMP packets were received.
ReqID	Request ID carried in the SNMP packets.
SNMPTime (ms)	Packet processing duration for the SNMP plug-in, in milliseconds.
APPTime (ms)	Packet processing duration for the SNMP process, in milliseconds.
TotalTime (ms)	Total packet processing duration, in milliseconds.
VBNum	Number of variable bindings in the SNMP packets.
VB	Variable binding information. A maximum of eight entries can be displayed.

Related commands

diagnostic troubleshooting enable

diagnostic troubleshooting test snmp-agent trap-send-failure

Use diagnostic troubleshooting test snmp-agent trap-send-failure to perform diagnostic troubleshooting for SNMP notification sending failure events.

Syntax

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

Views

System view

Predefined user roles

network-admin

Parameters

ip-address ipv4-address: Specifies IPv4 notification packets by its destination IPv4 address.

ipv6-address ipv6-address: Specifies IPv6 notification packets by its destination IPv6 address.

Usage guidelines

Operating mechanism

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

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

Restrictions and guidelines

For this command to take effect, first use the diagnostic troubleshooting test snmp-agent trap-send-failure enable command to enable diagnostic troubleshooting for SNMP notification sending failure events (enabled by default).

Examples

# Perform diagnostic troubleshooting for SNMP notification sending failure events.

<Sysname> system-view

[Sysname] diagnostic troubleshooting test snmp-agent trap-send-failure

Trap name: coldStart

Target host:

Host 1:

IP address : 192.168.1.1

SendTime : 2022-06-08 15:50:31:296

SecurityName : abc

Version : v3

VBNum : 2

VB : sysUpTime.0=286976,snmpTrapOID.0=1.3.6.1.6.3.1.1.5.1

Host 2:

IP address : 192.168.1.35

SendTime : 2022-06-08 15:55:32:368

SecurityName : def

Version : v2c

VBNum : 2

VB : sysUpTime.0=365898, snmpTrapOID.0=1.3.6.1.6.3.1.1.5.1

Trap name : warmStart

Target host:

Host 1:

IP address : 192.168.1.1

SendTime : 2022-06-08 15:55:36:259

SecurityName : abc

Version : v2c

VBNum : 2

VB : sysUpTime.0=687682, snmpTrapOID.0=1.3.6.1.6.3.1.1.5.2

Host 2:

IP address : 192.168.1.35

SendTime : 2022-06-08 16:15:12:566

SecurityName : def

Version : v3

VBNum : 2

VB : sysUpTime.0=351528, snmpTrapOID.0=1.3.6.1.6.3.1.1.5.2

Table 19 Command output

Field	Description
VBNum	Number of variable bindings in the SNMP packets.
VB	Variable binding information. A maximum of eight entries can be displayed.

Related commands

diagnostic troubleshooting enable

BGP diagnostic troubleshooting commands

diagnostic troubleshooting health module bgp

Use diagnostic troubleshooting health module bgp to perform health diagnostic troubleshooting for the BGP module.

Syntax

diagnostic troubleshooting health module bgp

Views

System view

Predefined user roles

network-admin

Usage guidelines

For this command to take effect, first use the diagnostic troubleshooting health module bgp enable command to enable health diagnostic troubleshooting for the BGP module.

Use this command to identify whether the BGP module is running correctly. When you execute this command, the device displays the unhealthy information for you to locate the issue.

The system can perform health diagnostic troubleshooting for one module at a time.

Examples

# Perform health diagnostic troubleshooting for the BGP module.

<Sysname> system-view

[Sysname] diagnostic troubleshooting health module bgp

Start diagnose at 2022-11-21 08:08:44

please wait.Done.

End diagnose at 2022-11-21 08:08:45,Actual time:1 seconds.

PADS_Type Time Reason

OPEN_ERROR 01-27 20:23:30 wrong AS number(Instance=bgp1, peer=1.1.1.1, VPN

instance=vpn1)

HEADER_ERROR 01-27 20:23:30 bad message length(Instance=bgp1, peer=2.1.1.1,

VPN instance=vpn1)

Table 20 Command output

Field	Description
PADS_Type	Error type: · HEADER_ERROR. · OPEN_ERROR. · UPDATE_ERROR. · FSM_ERROR. · SESSION_CEASE.
Time	Time when health diagnostic troubleshooting information was recorded.
Reason	Reason for the unhealthy event and information about the BGP sessions that trigged the event. The session format is Instance=instance, peer=peer, VPN instance=instance-name. instance represents the BGP instance to which the BGP session belongs. peer represents the peer IP address. Instance-name represents the VPN instance to which the BGP session belongs. When the BGP session is on the public network, instance-name is empty. Reasons include the following: · Reason corresponding to the HEADER_ERROR unhealthy type: ¡ invalid Marker field: The value for the Marker field in the BGP header is not all Fs. ¡ bad message length. ¡ bad message type. · Reason corresponding to the OPEN_ERROR unhealthy type: ¡ version unsupported. ¡ wrong AS number. ¡ BGP identifier conflicted. ¡ unsupported optional parameter. ¡ authentication failure. ¡ unacceptable hold time. ¡ unsupported capability type. · Reason corresponding to the UPDATE_ERROR unhealthy type: ¡ malformed attribute list. ¡ unrecognized well known attribute. ¡ well known attribute missing. ¡ attribute flags error. ¡ attribute length error. ¡ invalid NEXT HOP Attribute. ¡ optional attribute error. ¡ invalid destination network. ¡ malformed AS path attribute. · Reason corresponding to the FSM_ERROR unhealthy type: ¡ receive unexpected message in OpenSent state. ¡ receive unexpected message in OpenConfirm state. ¡ receive unexpected message in Established state. · Reason corresponding to the SESSION_CEASE unhealthy type: ¡ maximum number of prefixes reached. ¡ administrative shutdown. ¡ address family deleted. ¡ administrative reset. ¡ connection rejected. ¡ other configuration change. ¡ connection collision resolution. ¡ insufficient of resources.

Related commands

diagnostic troubleshooting health enable

diagnostic troubleshooting test establish-abnormal bgp

Use diagnostic troubleshooting test establish-abnormal bgp to perform diagnostic troubleshooting for BGP session setup failure events in a BGP instance.

Syntax

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

Views

System view

Predefined user roles

network-admin

Parameters

instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command performs diagnostic troubleshooting for BGP session setup failure events in the default BGP instance.

vpn-instance vpn- instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command performs diagnostic troubleshooting for BGP session setup failure events on the public network.

Usage guidelines

For this command to take effect, first use the diagnostic troubleshooting test establish-abnormal bgp enable command to enable diagnostic troubleshooting for BGP session setup failure events (enabled by default).

With diagnostic troubleshooting for BGP session setup 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.

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

When the system is performing diagnostic troubleshooting for an event, do not start diagnostic troubleshooting for any other events.

Examples

# Perform diagnostic troubleshooting for BGP session setup failure events in the default BGP instance.

<Sysname> system-view

[Sysname] diagnostic troubleshooting test peer-establish-abnormal bgp

Start diagnose at 2022-11-21 08:08:44

please wait.Done.

End diagnose at 2022-11-21 08:08:45,Actual time:1 seconds.

BGP local router ID: 10.1.1.1

IPv4-family for VPN instance vpn1:

Peer Time State Reason

1.1.1.1 01-27 20:23:30 OpenConfirm memory threshold was reached

2.1.1.1 01-27 20:23:30 OpenConfirm bad message head

Table 21 Command output

Field	Description
Time	Time when the BGP session setup failure occurred.
State	State of the BGP session when the BGP session setup failure occurred.
Reason	BGP session setup failure reason: · router ID missing. · memory threshold was reached. · peer limit was reached. · peer not exist. · direct EBGP session source interface check failed. · source interface update failed upon TCP reconnection. · TCP connection-socket bind failed. · TCP connection failed. · TCP connection info not exist. · send buffer full. · bad message head. · bad message length. · bad message type. · received messages not matching the FSM state. · inconsistent BGP version or holdtime. · failed to parse optional parameters in open message. · not enabled peer in correct address family. · inconsistent AS number. · conflicting router id. · keepalive message sending failed. · failed to obtain TCP connection info in openconfirm state. · failed to create keepalive timer.

Related commands

diagnostic troubleshooting enable

diagnostic troubleshooting test flap bgp

Use diagnostic troubleshooting test flap bgp to perform diagnostic troubleshooting for BGP session down events in a BGP instance.

Syntax

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

Views

System view

Predefined user roles

network-admin

Parameters

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command performs diagnostic troubleshooting for BGP session down events on the public network.

Usage guidelines

For this command to take effect, first use the diagnostic troubleshooting test flap bgp enable command to enable diagnostic troubleshooting for BGP session down events (enabled by default).

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

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

When the system is performing diagnostic troubleshooting for an event, do not start diagnostic troubleshooting for any other events.

Examples

# Perform diagnostic troubleshooting for BGP session down events in the default BGP instance.

<Sysname> system-view

[Sysname] diagnostic troubleshooting test flap bgp

Start diagnose at 2022-11-21 08:08:44

please wait.Done.

End diagnose at 2022-11-21 08:08:45,Actual time:1 seconds.

BGP local router ID: 10.1.1.1

IPv4-family for VPN instance vpn1:

Peer Time State Reason

1.1.1.1 01-27 20:23:30 Established->Idle address family deleted

Table 22 Command output

Field	Description
Time	Time when the BGP session went down.
State	State change of the BGP session after it went down.
Reason	Reason why the BGP session went down: · connection not synchronized. · bad message length. · bad message type. · withdrawn message too long. · route attribute length too long. · route attribute appears multiple times. · route attribute length field shorter than 2 bytes. · extended attribute length field shorter than 2 bytes. · attribute length field shorter than 1 byte. · link-state attribute error. · unrecognized well-known attribute. · attribute-type attribute missed: ¡ ORIGIN. ¡ AS_PATH. ¡ LOCAL_PREF. ¡ NEXT_HOP. · attribute flags error. · attribute-type attribute length error: ¡ AS_PATH. ¡ AS4_PATH. ¡ CLUSTER_LIST. ¡ AGGREGATOR. ¡ AS4_AGGREGATOR. ¡ ORIGIN. ¡ NEXT_HOP. ¡ MED. ¡ LOCAL_PREF. ¡ ATOMIC_AGGREGATE. ¡ ORIGINATOR_ID. ¡ MP_REACH_NLRI. ¡ COMMUNITY. ¡ EXT-COMMUNITY. · attribute length exceeded the limit. · invalid ORIGIN attribute. · invalid NEXT_HOP attribute. · invalid next hop length in MP_REACH_NLRI (address-family): ¡ 4U—IPv4 unicast address family. ¡ MPLS. ¡ VPNv4. ¡ 6U—IPv6 unicast address family. ¡ VPNv6. ¡ L2VPN. · the length of MP_UNREACH_NLRI attribute is less than 3 bytes. · the length of MP_REACH_NLRI or MP_UNREACH_NLRI attribute exceeds the limit · erroneous MP_REACH_NLRI or MP_UNREACH_NLRI attribute end position. · invalid network field. · malformed AS_PATH. · hold timer expiration caused by local device. · hold timer expiration caused by peer device. · connect retry timer expired. · TCP_CR_Acked event received. · TCP_Connection_Confirmed event received. · open message received. · manualstop event received. · physical interface configuration changed. · BFD session down event received. · physical interface configuration changed. · maximum number of prefixes reached. · maximum number of prefixes reached in address-family: The number of routes received from the peer exceeded the limit specified by the peer route-limit command. address-family represents the address family name. Options include: ¡ IPv4 unicast. ¡ IPv6 unicast. ¡ VPNv4. ¡ VPNv6. ¡ The peer is configured with the peer ignore command. · address family deleted. · peer disabled. · administrative reset. · connection rejected. · other configuration change. · connection collision resolution. · two connections exist and one uses MD5. · no memory to parse the attribute. · no memory for the route. · no memory to generate unreachable NLRI. · no memory for message encapsulation. · can’t get the VPN RD. · can’t get the VPN routing table. · can’t get the attributes. · entered severe memory state. · entered critical memory state.

Related commands

diagnostic troubleshooting enable

diagnostic troubleshooting test peer-establish-abnormal bgp

Use diagnostic troubleshooting test peer-establish-abnormal bgp to perform diagnostic troubleshooting for BGP session setup failure events.

Syntax

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 ]

Views

System view

Predefined user roles

network-admin

Parameters

peer ip-address ipv4-address: Specifies a BGP peer by its IPv4 address.

peer ipv6-address ipv6-address: Specifies a BGP peer by its IPv6 address.

diagnostic-time diagnostic-time: Specifies the estimated duration of diagnostic troubleshooting, in the range of 1 to 60 seconds. The default value is 30 seconds. The actual duration might be different, but will not be higher than 2 × diagnostic-time.

Usage guidelines

For this command to take effect, first use the diagnostic troubleshooting test peer-establish-abnormal bgp enable command to enable diagnostic troubleshooting for BGP session setup failure events (enabled by default).

When you execute this command, the device tries to re-establish 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.

The system can perform diagnostic troubleshooting for one type of event at a time.

Examples

# Perform diagnostic troubleshooting for BGP session setup failure events of the BGP peer at 1.1.1.1 in the default BGP instance.

<Sysname> system-view

[Sysname] diagnostic troubleshooting test peer-establish-abnormal bgp peer ip-address 1.1.1.1 diagnostic-time 20

Start diagnose at 2022-11-21 08:08:44, Estimated time:20 seconds.

please wait.....................Done.

End diagnose at 2022-11-21 08:09:05,Actual time:21 seconds.

Diagnosis report:

BGP local router ID: 10.1.1.1

IPv4-family for VPN instance vpn1:

Peer Time State Reason

1.1.1.1 01-27 20:23:30 OpenConfirm memory threshold was reached

Table 23 Command output

Field	Description
Time	Time when the BGP session setup failure occurred.
State	State of the BGP session when the BGP session setup failure occurred.
Reason	BGP session setup failure reason: · router ID missing. · memory threshold was reached. · peer limit was reached. · session not exist. · direct EBGP session source interface check failed. · source interface update failed upon TCP reconnection. · TCP connection-socket bind failed. · TCP connection failed. · TCP connection info not exist. · send buffer full. · bad message head. · bad message length. · bad message type. · received messages not matching the FSM state. · inconsistent BGP version or holdtime. · failed to parse optional parameters in open message. · not enabled peer in correct address family. · inconsistent AS number. · conflicting router id. · keepalive message sending failed. · failed to obtain TCP connection info in openconfirm state. · failed to create keepalive timer.

Related commands

diagnostic troubleshooting enable

diagnostic troubleshooting test peer-flap bgp

Use diagnostic troubleshooting test peer-flap bgp to perform diagnostic troubleshooting for session down events of sessions to a BGP peer.

Syntax

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

Views

System view

Predefined user roles

network-admin

Parameters

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command performs diagnostic troubleshooting for BGP session down events on the public network.

peer ip-address ipv4-address: Specifies a BGP peer by its IPv4 address.

peer ipv6-address ipv6-address: Specifies a BGP peer by its IPv6 address.

Usage guidelines

For this command to take effect, first use the diagnostic troubleshooting test peer-flap bgp enable command to enable diagnostic troubleshooting for BGP session down events (enabled by default).

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

The system can perform diagnostic troubleshooting for one type of event at a time.

Examples

# Perform diagnostic troubleshooting for BGP session down events in the default BGP instance.

<Sysname> system-view

[Sysname] diagnostic troubleshooting test peer-flap bgp peer ip-address 1.1.1.1

Start diagnose at 2022-11-21 08:08:44

please wait.Done.

End diagnose at 2022-11-21 08:08:45,Actual time:1 seconds.

BGP local router ID: 10.1.1.1

IPv4-family for VPN instance vpn1:

Peer Time State Reason

1.1.1.1 01-27 20:23:30 Established->Idle address family deleted

Table 24 Command output

Field	Description
Time	Time when the BGP session went down.
State	State change of the BGP session when the BGP session went down.
Reason	Reason why the BGP session went down: · connection not synchronized. · bad message length. · bad message type. · withdrawn message too long. · route attribute length too long. · route attribute appears multiple times. · route attribute length field shorter than 2 bytes. · extended attribute length field shorter than 2 bytes. · attribute length field shorter than 1 byte. · link-state attribute error. · unrecognized well-known attribute. · attribute-type attribute missed: ¡ ORIGIN. ¡ AS_PATH. ¡ LOCAL_PREF. ¡ NEXT_HOP. · attribute flags error. · attribute-type attribute length error: ¡ AS_PATH. ¡ AS4_PATH. ¡ CLUSTER_LIST. ¡ AGGREGATOR. ¡ AS4_AGGREGATOR. ¡ ORIGIN. ¡ NEXT_HOP. ¡ MED. ¡ LOCAL_PREF. ¡ ATOMIC_AGGREGATE. ¡ ORIGINATOR_ID. ¡ MP_REACH_NLRI. ¡ COMMUNITY. ¡ EXT-COMMUNITY. · attribute length exceeded the limit. · invalid ORIGIN attribute. · invalid NEXT_HOP attribute. · invalid next hop length in MP_REACH_NLRI (address-family): ¡ 4U—IPv4 unicast address family. ¡ MPLS. ¡ VPNv4. ¡ 6U—IPv6 unicast address family. ¡ VPNv6. ¡ L2VPN. · the length of MP_UNREACH_NLRI attribute is less than 3 bytes. · the length of MP_REACH_NLRI or MP_UNREACH_NLRI attribute exceeds the limit. · erroneous MP_REACH_NLRI or MP_UNREACH_NLRI attribute end position. · invalid network field. · malformed AS_PATH. · hold timer expiration caused by local device. · hold timer expiration caused by peer device. · connect retry timer expired. · TCP_CR_Acked event received. · TCP_Connection_Confirmed event received. · open message received. · manualstop event received. · physical interface configuration changed. · BFD session down event received. · physical interface configuration changed. · maximum number of prefixes reached. · maximum number of prefixes reached in address-family: The number of routes received from the peer exceeded the limit specified by the peer route-limit command. address-family represents the address family name. Options include: ¡ IPv4 unicast. ¡ IPv6 unicast. ¡ VPNv4. ¡ VPNv6. ¡ The peer is configured with the peer ignore command. · address family deleted. · peer disabled. · administrative reset. · connection rejected. · other configuration change. · connection collision resolution. · two connections exist and one uses MD5. · no memory to parse the attribute. · no memory for the route. · no memory to generate unreachable NLRI. · no memory for message encapsulation. · can’t get the VPN RD. · can’t get the VPN routing table. · can’t get the attributes. · entered severe memory state. · entered critical memory state.

Related commands

diagnostic troubleshooting enable

diagnostic troubleshooting test route-record bgp flowspec

Use diagnostic troubleshooting test route-record bgp flowspec to perform diagnostic troubleshooting for BGP Flowspec route adding and deletion events.

Syntax

diagnostic troubleshooting test route-record bgp [ instance instance-name ] flowspec

Views

System view

Predefined user roles

network-admin

Parameters

instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command performs diagnostic troubleshooting for BGP flowspec route adding and deletion events in the default BGP instance.

Usage guidelines

For this command to take effect, first use the diagnostic troubleshooting test test route-record bgp enable command to enable diagnostic troubleshooting for BGP flowspec route adding and deletion events (enabled by default).

With diagnostic troubleshooting for BGP flowspec route adding and deletion events enabled, the device records the flowspec route adding and deletion information in the memory of the GOLD module automatically. After you execute this command, the device displays the flowspec route adding and deletion information stored in the GOLD module.

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

The system can perform diagnostic troubleshooting for one type of event at a time.

Examples

# Perform diagnostic troubleshooting for BGP flowspec route adding and deletion events.

<Sysname> system-view

[Sysname] diagnose trouble-shooting test route-record bgp flowspec

ChangeType : ADD

Time : 2022-02-21 18:24:36

VPN-Instance Name : vpn1

From : 10.1.1.1

Network:

Source IP : 10.10.1.0/24

Protocol : =0|=1|=6

Dest.Port : =1000

Src.Port : =179

ICMP Type : =10

ICMP Code : =200|=300

TCPFlags : =255

Length : =1024

DSCP : =6|=2

Frag : =4/528

Ext-Community :

CO-Flag : Color(01:1)

FLOWSPEC RATE : 324 Bps

FLOWSPEC ACTION : 32

ChangeType : DEL

Time : 2022-02-21 18:24:36

VPN-Instance Name : vpn2

From : 11.1.1.1

Network:

Source IP : 11.10.1.0/24

Protocol : =0|=1|=6

Dest.Port : =1000

Src.Port : =179

ICMP Type : =10

ICMP Code : =200|=300

TCPFlags : =255

Length : =1024

DSCP : =6|=2

Frag : =4/528

Ext-Community :

CO-Flag : Color(01:1)

FLOWSPEC RATE : 324 Bps

FLOWSPEC ACTION : 32

Table 25 Command output

Field	Description
ChangeType	Event type: · ADD-Routes were added to the BGP flowspec routing table. · DEL-Routes were deleted from the BGP flowspec routing table.
Time	Time when a BGP Flowspec route was added or deleted.
From	IP address of the peer that sent the BGP Flowspec route.
Network	Prefix of the BGP Flowspec route.
Ext-Community	Extended community in the BGP Flowspec route.

Related commands

diagnostic troubleshooting enable

22-Intelligent Operations Command Reference

Diagnostic troubleshooting commands

Operating mechanism

Restrictions and guidelines

Operating mechanism

Restrictions and guidelines

Operating mechanism

Restrictions and guidelines

Operating mechanism

Restrictions and guidelines

MPLS TE diagnostic troubleshooting commands

MPLS L2VPN diagnostic troubleshooting commands

Operating mechanism

Restrictions and guidelines

SNMP diagnostic troubleshooting commands

diagnostic troubleshooting test snmp-agent packet-process-failure

Operating mechanism

Restrictions and guidelines

Operating mechanism

Restrictions and guidelines

diagnostic troubleshooting test snmp-agent trap-send-failure

Operating mechanism

Restrictions and guidelines

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

Company Information

News & Events

Contact Us