H3C S6805 & S6825 & S6850 & S9850 Switch Series Troubleshooting Guide-6W101

HomeSupportDiagnose & MaintainTroubleshootingH3C S6805 & S6825 & S6850 & S9850 Switch Series Troubleshooting Guide-6W101

 

H3C S6805 & S6825 & S6850 & S9850 Switch Series

Troubleshooting Guide

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Document version: 6W101-20220818

 

Copyright © 2019-2022 New H3C Technologies Co., Ltd. All rights reserved.

No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd.

Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners.

The information in this document is subject to change without notice


Contents

Introduction· 1

General guidelines· 1

Collecting log and operating information· 1

Collecting common log messages· 2

Collecting diagnostic log messages· 3

Collecting operating statistics· 3

Troubleshooting hardware· 4

Unexpected switch reboot 4

Symptom·· 4

Troubleshooting flowchart 5

Solution· 5

Operating power module failure· 6

Symptom·· 6

Solution· 6

Newly installed power module failure· 7

Symptom·· 7

Solution· 7

Fan tray failure· 8

Symptom·· 8

Solution· 8

Related commands· 9

Troubleshooting ACL· 10

Insufficient hardware resource for ACLs· 10

Symptom·· 10

Troubleshooting flowchart 10

Solution· 10

Applied ACLs fail to take effect 11

Symptom·· 11

Troubleshooting flowchart 12

Solution· 12

Troubleshooting IRF· 14

IRF fabric setup failure· 14

Symptom·· 14

Troubleshooting flowchart 15

Solution· 16

Related commands· 17

Troubleshooting Ethernet link aggregation· 19

Link aggregation failure· 19

Symptom·· 19

Troubleshooting flowchart 20

Solution· 20

Related commands· 21

Troubleshooting ports· 22

A GE SFP, 10-GE SFP+, 40-GE QSFP+, or 100-GE QSFP28 fiber port fails to come up· 22

Symptom·· 22

Troubleshooting flowchart 22

Solution· 23

A 25-GE SFP28 fiber port fails to come up· 24

Symptom·· 24

Troubleshooting flowchart 24

Solution· 25

A 1/10GBase-T 10-GE copper port fails to come up· 27

Symptom·· 27

Troubleshooting flowchart 27

Solution· 27

Non-H3C transceiver module error message· 28

Symptom·· 28

Troubleshooting flowchart 28

Solution· 28

Transceiver module does not support digital diagnosis· 29

Symptom·· 29

Troubleshooting flowchart 29

Solution· 29

Error frames (for example, CRC errors) on a port 30

Symptom·· 30

Troubleshooting flowchart 31

Solution· 31

Failure to receive packets· 32

Symptom·· 32

Troubleshooting flowchart 33

Solution· 33

Failure to send packets· 34

Symptom·· 34

Troubleshooting flowchart 34

Solution· 35

Related commands· 35

Troubleshooting EVPN·· 37

EBGP or IBGP neighbor relationship setup failure· 37

Symptom·· 37

Troubleshooting flowchart 37

Solution· 37

ECMP forwarding failure· 38

Symptom·· 38

Troubleshooting flowchart 39

Solution· 39

Related commands· 40

Troubleshooting system management 41

High CPU utilization· 41

Symptom·· 41

Troubleshooting flowchart 41

Solution· 41

High memory utilization· 43

Symptom·· 43

Troubleshooting flowchart 43

Solution· 43

Related commands· 44

Troubleshooting other issues· 45

Layer 2 forwarding failure· 45

Symptom·· 45

Troubleshooting flowchart 45

Solution· 46

Related commands· 51

Layer 3 forwarding failure· 51

Symptom·· 51

Troubleshooting flowchart 52

Solution· 52

Related commands· 53

Protocol flapping· 53

Symptom·· 53

Troubleshooting flowchart 54

Solution· 54


Introduction

This document provides information about troubleshooting common software and hardware issues with the S6805, S6825, S6850, and S9850 switch series.

This document is not restricted to specific software or hardware versions.

General guidelines

IMPORTANT

IMPORTANT:

To prevent an issue from causing loss of configuration, save the configuration each time you finish configuring a feature. For configuration recovery, regularly back up the configuration to a remote server.

 

When you troubleshoot the switch, follow these general guidelines:

·     To help identify the cause of the issue, collect system and configuration information, including:

¡     Symptom, time of failure, and configuration.

¡     Network topology information, including the network diagram, port connections, and points of failure.

¡     Common log messages and diagnostic log information. For more information about collecting this information, see "Collecting log and operating information."

¡     Physical evidence of failure:

-     Photos of the hardware.

-     Status of the LEDs.

¡     Steps you have taken, such as reconfiguration, cable swapping, and reboot.

¡     Output from the commands executed during the troubleshooting process.

·     To ensure safety, wear an ESD wrist strap when you replace or maintain a hardware component.

·     If hardware replacement is required, use the release notes to verify the hardware and software compatibility.

Collecting log and operating information

IMPORTANT

IMPORTANT:

To facilitate quick troubleshooting, execute the following commands:

·     info-center enable—Enables the information center. By default, the information center is enabled.

·     info-center logfile enable—Enables the log file feature so the system outputs logs to log files. By default, the log file feature is enabled.

·     info-center diagnostic-logfile enable—Enables saving diagnostic logs to the diagnostic log file. By default, saving diagnostic logs to the diagnostic log file is enabled.

 

During operation, the device generates common log messages and diagnostic log messages to record information about routine operations and operating status. Table 1 shows the types of files that the system uses to store the log messages. You can export these files by using FTP, TFTP, or USB.

In an IRF system, log files are stored on the master device. Multiple devices will have log files if master/subordinate switchovers have occurred. You must collect log files from all member devices. To more easily identify log files from different member devices, use two directories to save the log files from each member device and include member IDs in the directory names.

Table 1 Log and operating information

Category

File name format

Log file directory

Content

Common log

logfile.log

flash:/logfile

Command execution, events, and status changes log messages.

Diagnostic log

diagfile.log

flash:/diagfile

Diagnostic log messages about device operation, including the following items:

·     Parameter settings in effect when an error occurs.

·     Information about a card startup error.

·     Handshaking information between member devices when a communication error occurs.

Operating statistics

file-basename.tar.gz

N/A

Current operating statistics for feature modules, including the following items:

·     Device status.

·     CPU status.

·     Memory status.

·     Configuration status.

·     Software entries.

·     Hardware entries.

 

Collecting common log messages

1.     Save common log messages from the log buffer to a log file.

By default, the log file is saved in the logfile directory of the flash memory on each member device.

<Sysname> logfile save

The contents in the log file buffer have been saved to the file flash:/logfile/logfile.log

2.     Identify the common log file on each member device:

# Display the common log file on the master device.

<Sysname> dir flash:/logfile/

Directory of flash:/logfile

   0 -rw-       21863 Jul 11 2013 16:00:37   logfile.log

 

1048576 KB total (38812 KB free)

 

# Display the common log file on each subordinate device:

<Sysname> dir slot2#flash:/logfile/

Directory of slot2#flash:/logfile

   0 -rw-       21863 Jul 11 2013 16:00:37   logfile.log

 

1048576 KB total (38812 KB free)

3.     Transfer the files to the desired destination by using FTP, TFTP, or USB. (Details not shown.)

Collecting diagnostic log messages

1.     Save diagnostic log messages from the diagnostic log file buffer to a diagnostic log file.

By default, the diagnostic log file is saved in the diagfile directory of the flash memory on each member device.

<Sysname> diagnostic-logfile save

The contents in the diagnostic log file buffer have been saved to the file flash:/diagfile/diagfile.log

2.     Identify the diagnostic log file on each member device:

# Display the diagnostic log file on the master device.

<Sysname> dir flash:/diagfile/

Directory of flash:/diagfile

   0 -rw-      161321 Jul 11 2013 16:16:00   diagfile.log

 

1048576 KB total (38812 KB free)

 

# Display the diagnostic log file on each subordinate device:

<Sysname> dir slot2#flash:/diagfile/

<Sysname> dir slot2#flash:/diagfile/

Directory of slot2#flash:/diagfile

   0 -rw-      161321 Jul 11 2013 16:16:00   diagfile.log

 

1048576 KB total (38812 KB free)

3.     Transfer the files to the desired destination by using FTP, TFTP, or USB. (Details not shown.)

Collecting operating statistics

You can collect operating statistics by saving the statistics to a file or displaying the statistics on the screen.

When you collect operating statistics, follow these guidelines:

·     Log in to the device through a network or management port instead of the console port, if possible. Network and management ports are faster than the console port.

·     Do not execute commands while operating statistics are being collected.

·     Hewlett Packard Enterprise recommends saving operating statistics to a file to retain the information.

 

 

NOTE:

The amount of time to collect statistics increases along with the number of IRF member devices.

 

To collect operating statistics:

1.     Collect operating statistics for multiple feature modules.

<Sysname> display diagnostic-information

Save or display diagnostic information (Y=save, N=display)? [Y/N] :

2.     At the prompt, choose to save or display operating statistics:

# To save operating statistics, enter y at the prompt and then specify the destination file name.

Save or display diagnostic information (Y=save, N=display)? [Y/N] :y

Please input the file name(*.tar.gz)[flash:/diag_Sysname_20160101-000704.tar.gz] :

Diagnostic information is outputting to flash:/diag_Sysname_20160101-000704.tar.gz.

Please wait...

Save successfully.

<Sysname> dir flash:/

Directory of flash:

...

   6 -rw-      898180 Jun 26 2013 09:23:51   diag.tar.gz

 

1048576 KB total (38812 KB free)

# To display operating statistics on the monitor terminal, enter n at the prompt. (The output from this command varies by software version.)

Save or display diagnostic information (Y=save, N=display)? [Y/N] :N

===============================================

  ===============display clock===============

23:49:53 UTC Tue 01/01/2016

=================================================

...

3.     Extract and decompress the operating statistics file.

<Sysname> tar extract archive-file diag_Sysname_20160101-000704.tar.gz

Extracting archive flash:/diag_Sysname_20160101-000704.tar.gz Done.

<Sysname> gunzip diag_Sysname_20160101-000704.gz

Decompressing file flash:/diag_Sysname_20160101-000704.gz.... Done.

4.     Display the content of the operating statistics file.

<Sysname> more diag_Sysname_20160101-000704

===============================================

  ===============display clock===============

23:49:53 UTC Tue 01/01/2016

=================================================

---- More ----

Troubleshooting hardware

This section provides troubleshooting information for common hardware issues.

 

 

NOTE:

This section describes how to troubleshoot unexpected switch reboot, power module failure, and fan tray failure. To troubleshoot ports, see "Troubleshooting ports."

 

Unexpected switch reboot

Symptom

The switch reboots unexpectedly when it is operating.

Troubleshooting flowchart

Figure 1 Troubleshooting unexpected switch reboot

 

Solution

To resolve the issue:

1.     Verify that you can access the CLI after the switch reboots.

¡     If you can access the CLI, execute the display diagnostic-information command to collect operating information.

¡     If you cannot access the CLI, go to step 2.

2.     Verify that the system software image on the switch is correct.

Connect to the switch through the console port and restart the switch. If BootWare reports that a CRC error has occurred or that no system software image is available, perform the following steps:

a.     Use the BootWare menu to reload the system software image.

b.     Configure it as the current system software image.

3.     If the issue persists, contact H3C Support.

Operating power module failure

Symptom

A trap or log is generated indicating that an operating power module is faulty.

Solution

To resolve the issue:

1.     Execute the display power command to check whether the power module is in faulty or absent state.

<H3C> display power

 Slot 1:

 Input Power: 60(W)

 PowerID State         Mode   Current(A)  Voltage(V)  Power(W)  FanDirction

 1       Normal        AC        5.08       11.84        60     PowerToPort

 2       Absent        --        --          --          --     --

2.     Observe the status LED on the power module.

The power module status LED has the following indications:

¡     Steady green: The power module is operating correctly.

¡     Flashing green: The power module has power input but is not installed on the device.

¡     Steady red: The power module is faulty or in self-protection mode.

¡     Flashing green/red alternatively: An alarm is present on the power module and the power module is not in self-protection mode. The possible alarms include output overcurrent, output overpower, and overtemperature.

¡     Flashing red

-     The power module does not have power input, and the other power module installed on the same device has power input.

-     The power module is in input undervoltage protection mode.

¡     Off: The power module does not have power input.

3.     If the power module is in Absent state, no power module is in the slot or the power module is not installed securely in the slot.

If the power module is in the slot but its status is Absent, and the status LED on the power module is flashing green (connected to power) or off (not connected to power), remove and reinstall the power module to make sure the power module is installed securely. Then check whether the power module has changed to Normal state and whether its status LED is steady green. If the issue persists, replace the power module.

4.     If the power module is in Fault state, do the following:

a.     If no power is present on the power module (the status LED flashing red), connect power to the power module.

b.     If the power module is in high temperature (the status LED steady red or flashing red/green alternatively) because of dust accumulation, remove the dust and then remove and reinstall the power module. Execute the display power command to check whether the power module has changed to Normal state. If the power module remains in Fault state, go to step c.

c.     Install the power module into an empty power module slot. Then execute the display power command to check whether the power module has changed to Normal state in the new slot. If the power module remains in Fault state, replace the power module.

5.     If the issue persists, contact H3C Support.

Newly installed power module failure

Symptom

A trap or log is generated indicating that a newly installed power module is faulty.

Solution

To resolve the issue:

1.     Execute the display power command to display power module information.

<H3C>display power

 Slot 1:

 Input Power: 60(W)

 PowerID State         Mode   Current(A)  Voltage(V)  Power(W)  FanDirction

 1       Normal        AC        5.08       11.84        60     PowerToPort

 2       Absent        --        --          --          --     --

2.     Observe the status LED on the power module.

The power module status LED has the following indications:

¡     Steady green: The power module is operating correctly.

¡     Flashing green: The power module has power input but is not installed on the device.

¡     Steady red: The power module is faulty or in self-protection mode.

¡     Flashing green/red alternatively: An alarm is present on the power module and the power module is not in self-protection mode. The possible alarms include output overcurrent, output overpower, and overtemperature.

¡     Flashing red

-     The power module does not have power input, and the other power module installed on the same device has power input.

-     The power module is in input undervoltage protection mode.

¡     Off: The power module does not have power input.

3.     If the power module is in Absent state, and the status LED on the power module is flashing green (connected to power) or off (not connected to power), the power module is not installed securely.

a.     Remove and reinstall the power module to make sure the power module is installed securely. Then check whether the power module has changed to Normal state and whether its status LED is steady green. If the issue persists, go to step b.

b.     Remove and install the power module into an empty power module slot. Then check whether the power module has changed to Normal state and whether its status LED is steady green. If the issue persists, go to step 5.

4.     If the power module is in Fault state, perform the following tasks:

a.     If no power is present on the power module (the status LED flashing red), connect power to the power module.

b.     If the status LED on the power module is steady red or flashing red/green alternatively, the power module is faulty, an alarm is present on the power module, or the power module has entered into self-protection mode. Remove and install the power module into an empty power module slot. Then check whether the power module has changed to Normal state and whether its status LED is steady green. If the issue persists, go to step 5

5.     If the issue persists, contact H3C Support.

Fan tray failure

Symptom

A trap or log indicates that a fan tray is faulty, or the display fan command shows that a fan tray is not in Normal state.

Solution

To resolve the issue:

1.     Execute the display fan command to display the operating states of the fan tray.

<Sysname> display fan

 Slot 1:

 Fan 1:

 State    : FanDirectionFault

 Airflow Direction: Port-to-power

 Prefer Airflow Direction: Power-to-port

 Fan 2:

 State    : FanDirectionFault

 Airflow Direction: Port-to-power

 Prefer Airflow Direction: Power-to-port

If the fan tray is in FanDirectionFault state, the airflow direction of the fan tray is not as configured.  Replace the fan tray with a fan tray that has the same airflow direction as the equipment room, or use the fan prefer-direction command to change the preferred airflow direction.

2.     If the fan tray is in the slot but it is in Absent state, remove and reinstall the fan tray to make sure the fan tray is installed securely. Then execute the display fan command to verify that the fan tray has changed to Normal state. If the fan tray remains in Absent state, replace the fan tray.

3.     Observe the alarm LED on the fan tray.

¡     If the alarm LED is on, the fan tray is operating incorrectly.

¡     If the alarm LED is off, the fan tray is operating correctly.

4.     If the fan tray is in Fault state and its alarm LED is on, the fan tray is faulty. Perform the following tasks:

a.     Execute the display environment command to display temperature information. If the temperature continues to rise, put your hand at the air outlet to feel if air is being expelled out of the air outlet. If no air is being expelled out of the air outlet, remove and reinstall the fan tray. Then execute the display fan command to verify that the fan tray has changed to Normal state and observe whether its alarm LED is off.

b.     If the issue persists, replace the fan tray.

If no new fan tray is available, power off the switch to avoid damage caused by high temperature. If you can use cooling measures to ensure that the device operates in an temperature below 60°C (140°F), you can continue to use the device but prepare a new fan tray to replace the failed fan tray as soon as possible.

5.     If the issue persists, contact H3C Support.

Related commands

This section lists the commands that you might use for troubleshooting the hardware.

 

Command

Description

dir

Displays information about files and directories.

display boot-loader

Displays current configuration files and system software images.

display environment

Displays temperature information.

display fan

Displays the operating states of the fan tray.

display logbuffer

Displays the state of the log buffer and the log information in the log buffer.

display power

Displays power module information.

fan prefer-direction slot slot-number { power-to-port | port-to-power }

Specifies the preferred airflow direction.

 

 


Troubleshooting ACL

This section provides troubleshooting information for common issues with ACLs.

Insufficient hardware resource for ACLs

Symptom

ACL application fails and the system displays a message "Reason: Not enough hardware resource."

Troubleshooting flowchart

Figure 2 Troubleshooting insufficient hardware resource for ACLs

 

Solution

To resolve the issue:

1.     Execute display qos-acl resource command to view ACL resource usage information.

<Sysname> display qos-acl resource

Interfaces: WGE1/0/1 to WGE1/0/24, HGE1/0/25 to HGE1/0/28 (slot 1)

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

 Type             Total      Reserved   Configured Remaining  Usage

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

 VFP ACL          1024       257        1          766        25%

 IFP ACL          18432      9220       2          9210       50%

 IFP Meter        3072       97         1          2974       3%

 IFP Counter      9216       4610       1          4605       50%

 EFP ACL          2048       0          0          2048       0%

 EFP Meter        1024       0          0          1024       0%

 EFP Counter      1024       0          0          1024       0%

 

Interfaces: HGE1/0/29 to HGE1/0/32, WGE1/0/33 to WGE1/0/56

            GE1/0/57 to GE1/0/58 (slot 1)

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

 Type             Total      Reserved   Configured Remaining  Usage

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

 VFP ACL          1024       257        1          766        25%

 IFP ACL          18432      9220       2          9210       50%

 IFP Meter        3072       106        1          2965       3%

 IFP Counter      9216       4610       1          4605       50%

 EFP ACL          2048       0          0          2048       0%

 EFP Meter        1024       0          0          1024       0%

 EFP Counter      1024       0          0          1024       0%

IFP indicates ACL resources for the inbound traffic.

EFP indicates ACL resources for the outbound traffic.

2.     If the resources required for applying the ACLs exceed the remaining resources, the system reports hardware resources insufficiency. Delete unnecessary ACLs to release resources.

3.     If the resources are sufficient, the ACLs might conflict with an ASIC chip algorithm. Contact H3C Support to resolve the issue.

4.     If the issue persists, contact H3C Support.

Applied ACLs fail to take effect

Symptom

Applied ACLs fail to take effect.

Troubleshooting flowchart

Figure 3 Troubleshooting ACL failure to take effect

 

Solution

1.     Verify that the ACL rules are defined correctly.

Execute the display acl command to view the ACL settings, including the rules and the match order of the rules. Determine whether rules are configured correctly for packet match and whether packets are not matched because of the incorrect match order of the rules.

For example, if you configure the following ACL rules:

ACL number 3100

rule 0 permit ip source 2.2.2.2 0.0.255.255

rule 1 deny ip destination 3.3.3.3 0.0.255.255

Packets with source IP 2.2.2.2 and destination IP 3.3.3.3 will match only rule 0 and do not match rule 1.

For information about the rule match order, see ACL configuration in the ACL and QoS configuration guide for the switch.

2.     Check the applied ACLs for overlapping rules:

a.     Use the following commands to display applied ACLs:

-     display packet-filter

-     display qos policy user-defined

-     display traffic classifier user-defined

-     display ip policy-based-route

b.     Execute the display acl command to check for overlapping rules in the ACLs.

In the following example, rule 0 in ACL 3100 and rule 0 in ACL 3009 can both match traffic sourced from 2.2.2.2.

ACL number 3100

rule 0 permit ip source 2.2.2.2 0.0.255.255

ACL number 3009

rule 0 permit ip source 2.2.2.2 0.0.0.255

3.     Remove the action conflict between overlapping rules.

If two ACLs has overlapping rules, only actions in the ACL with higher priority take effect.

4.     Collect related information and contact H3C Support.

 


Troubleshooting IRF

This section provides troubleshooting information for common issues with IRF.

IRF fabric setup failure

Symptom

An IRF fabric cannot be set up.

 

 

NOTE:

·     S6850 switches can establish an IRF fabric with switches in the S6850 switch series and S9850 switch series.

·     S9850 switches can establish an IRF fabric with switches in the S9850 switch series and S6850 switch series.

·     S6805 switches can establish an IRF fabric only with switches in the S6805 switch series.

·     S6825 switches can establish an IRF fabric only with switches in the S6825 switch series.

 

Troubleshooting flowchart

Figure 4 Troubleshooting IRF fabric setup failure

 

Solution

To resolve the issue:

1.     Verify that the number of member devices does not exceed the upper limit (10).

If you are adding a new member device to an existing IRF fabric or merging IRF fabrics, use the display irf command to identify the number of member devices in the IRF fabrics. If the total number of member devices exceeds the upper limit, the IRF setup will fail.

2.     Verify that the member ID of each member device is unique:

a.     Execute the display irf command to view the member ID of each member device.

b.     Use the irf member renumber command to assign a unique member ID to each member.

-     If you are adding a new member device to an existing IRF fabric, assign the member device a member ID that is not being used in the IRF fabric.

-     If you are merging IRF fabrics, make sure each member device in these IRF fabrics has a unique member ID.

3.     Verify that the IRF port bindings and physical IRF link connections are correct:

a.     Execute the display irf configuration command, and check the IRF-Port1 and IRF-Port2 fields for IRF port bindings.

b.     Verify that the physical interfaces bound to IRF ports are IRF capable. You can use QSFP+ or QSFP28 ports for IRF links. If there are binding errors, reconfigure the IRF port bindings.

 

IMPORTANT

IMPORTANT:

QSFP28 ports on the LSWM18CQMSEC module cannot be used as IRF physical interfaces.

 

c.     Verify that the IRF physical interfaces are correct connected. When you connect two neighboring IRF members, you must connect the physical interfaces of IRF-port 1 on one member to the physical interfaces of IRF-port 2 on the other.

4.     Verify that the correct transceiver modules and cables are used:

¡     To connect QSFP+ ports in a long distance, use QSFP+ transceiver modules and fibers.

¡     To connect QSFP+ ports in a short distance, use QSFP+ DAC or AOC cables.

¡     To connect QSFP28 ports in a long distance, use QSFP28 or QSFP+ transceiver modules and fibers.

¡     To connect QSFP28 ports in a short distance, use QSFP28 or QSFP+ DAC or AOC cables.

 

IMPORTANT

IMPORTANT:

Except the above listed transceiver modules and fibers or cables, do not use any other transceiver modules and fibers or cables to connect IRF physical interfaces on the switch series.

 

When you use QSFP+ DAC cables to connect IRF physical interfaces for S6850 switch series and S9850 switch series, follow these restrictions and guidelines:

¡     The two ends of a physical IRF link must both use fixed ports as IRF physical interfaces or both use ports on interface modules as IRF physical interfaces. Do not connect a fixed port to a port on an interface module for IRF connection. However, you can bind fixed ports and ports on an interface module to the same IRF port.

¡     If you use ports on interface modules as IRF physical interfaces, make sure the interface modules at the two ends of a physical IRF link are the same type.

¡     To use a fixed QSFP28 port on the rear panel of an S6850-2C member as an IRF physical interface, you must make sure its IRF neighbor is also an S6850-2C switch. In addition, you can connect that port only to a fixed QSFP28 port on the rear panel of the neighboring S6850-2C switch.

5.     Verify that the two ends of an IRF link are operating at the same rate.

If you are using transceiver modules and fibers, verify that the transceiver modules at the two ends of an IRF link are the same type. If the transceiver modules are not the same type, replace them to be the same type.

6.     Verify that all IRF links are up:

a.     Execute the display irf topology command, and then check the Link field.

-     If the Link field for each IRF port does not display DOWN, go to step 7.

-     If the Link field for an IRF port displays DOWN, go to step b.

b.     Execute the display irf link command, and then check the Status field of the physical interfaces bound to the IRF port.

-     If the field displays DOWN or ADM (administratively down) for all the physical interfaces, remove the link failures or use the undo shutdown command to bring up the administratively down physical interfaces.

-     If the field displays UP for at least one of the physical interfaces, go to step c.

c.     Save the configuration, and then execute the irf-port-configuration active command in system view to activate the IRF port configuration.

 

IMPORTANT

IMPORTANT:

Activating IRF port configuration requires a reboot. To prevent configuration loss, you must save the configuration before you execute the irf-port-configuration active command.

 

7.     Verify that all member devices use the same software version:

a.     Execute the display version command to identify the software version of each member device.

b.     Upgrade the software of all member devices to the same version.

 

 

NOTE:

Typically, the irf auto-update enable command can automatically synchronize a member device with the software version of the master device. However, the synchronization might fail when the gap between the software versions is too large. For more information, see the release notes.

 

8.     Execute display commands to verify that all member devices use the same settings for the following features:

¡     System operating mode (set by using the system-working-mode command).

¡     Hardware resource mode for the MAC address table, ARP and ND tables, and routing tables (set by using the hardware-resource switch-mode command).

¡     Enhanced ECMP mode (set by using the ecmp mode enhanced command).

¡     Support for the IPv6 routes with prefixes longer than 64 bits (set by using the hardware-resource routing-mode ipv6-128 command).

¡     Enabling status of packet loss prevention for OpenFlow forwarding (set by using the openflow lossless enable command).

¡     VXLAN hardware resource allocation mode (set by using the hardware-resource vxlan command).

9.     If the issue persists, contact H3C Support.

Related commands

This section lists the commands that you might use for troubleshooting IRF.

Command

Description

display irf

Displays IRF fabric information, including the member ID, role, priority, bridge MAC address, and description of each IRF member.

display irf configuration

Displays basic IRF settings, including the current member ID, new member ID, and physical interfaces bound to the IRF ports on each IRF member device. The new member IDs take effect at reboot.

display irf link

Displays IRF link information.

Use this command to verify that each IRF port has a minimum of one physical interface in up state.

display irf topology

Displays the IRF fabric topology, including the member IDs, IRF port state, and adjacencies of IRF ports.

display version

Displays system version information.

irf-port-configuration active

Activates IRF configuration on IRF ports.


Troubleshooting Ethernet link aggregation

This section provides troubleshooting information for common issues with Ethernet link aggregation.

Link aggregation failure

Symptom

Some member ports fail to be placed in Selected state, and link aggregation does not operate correctly.

Troubleshooting flowchart

Figure 5 Troubleshooting link aggregation failure

 

Solution

To resolve the issue:

1.     Verify that all physical connections are correct.

You can verify the physical connections against your network plan.

2.     Verify that all member ports are up:

a.     Execute the display interface command to display the status of the member ports.

b.     If the member ports are down, follow the solution in "Troubleshooting ports" to troubleshoot the issue.

3.     Verify that the member ports have the same operational key and attribute configurations as the reference port:

a.     Execute the display link-aggregation verbose command to display the Selected state of the member ports.

b.     Execute the display current-configuration interface command to display the configurations of the aggregate interface and the Unselected ports.

c.     Configure the Unselected ports to make sure they have the same operational key and attribute configurations as the reference port.

4.     Identify the aggregation mode of the aggregation group.

¡     If the aggregation mode is static, proceed to step 6.

¡     If the aggregation mode is dynamic, proceed to step 5.

5.     Verify that the peer member ports have the same operational key and attribute configurations as the peer port of the reference port:

a.     Execute the display current-configuration interface command on the peer device to display the configurations of the peer member ports.

b.     Configure the peer member ports to make sure the peer ports have the same operational key and attribute configurations as the peer port of the reference port.

6.     Verify that the number of member ports in the aggregation group does not exceed the configured maximum number of Selected ports.

a.     Execute the link-aggregation selected-port maximum command to set the maximum number of Selected ports allowed in the aggregation group. The value range is 1 to 16.

b.     Execute the display link-aggregation verbose command to verify that the number of member ports does not exceed the configured maximum number of Selected ports.

If the number of member ports exceeds the maximum number of Selected ports, the ports with higher port numbers are in Unselected state.

c.     Use the undo port link-aggregation group command to remove undesired member ports from the aggregation group.

This makes sure all member ports you assign to the aggregation group can become Selected ports.

7.     If the issue persists, contact Hewlett Packard Enterprise Support.

Related commands

This section lists the commands that you might use for troubleshooting Ethernet link aggregation.

 

Commands

Description

display current-configuration interface

Displays interface configuration.

display interface

Displays Ethernet interface information.

display link-aggregation verbose

Display detailed information about the aggregation groups that correspond to the existing aggregate interfaces.

link-aggregation selected-port maximum

Configure the maximum number of Selected ports allowed in an aggregation group.

 

 


Troubleshooting ports

This section provides troubleshooting information for common port issues.

A GE SFP, 10-GE SFP+, 40-GE QSFP+, or 100-GE QSFP28 fiber port fails to come up

Symptom

A GE SFP, 10-GE SFP+, 40-GE QSFP+, or 100-GE QSFP28 fiber port fails to come up.

Troubleshooting flowchart

Figure 6 Troubleshooting link up failure on a fiber port

 

Solution

To resolve the issue:

1.     Verify that the speed and duplex mode of the local port match the speed and duplex mode of the peer port:

a.     Execute the display interface brief command to examine whether the speed and duplex mode of the port match the speed and duplex mode of the peer port.

b.     If they do not match, use the speed command and the duplex command to set the rate and duplex mode for the port.

2.     Verify that the speed and duplex mode of the local port match the speed and duplex mode of the transceiver module:

a.     Execute the display interface brief command to examine whether the speed and duplex mode of the port match the speed and duplex mode of the transceiver module.

b.     If they do not match, use the speed command and the duplex command to set the rate and duplex mode for the port.

3.     For a 100-GE port, verify that the local and peer ports use the same FEC mode.

In Release 6616 and later, you can use the port fec mode { auto | none | rs-fec } command on a 100-GE port of the switch to control the status of FEC. Then, the switch can interoperate with devices of different models.

4.     Verify that the ports at both ends are operating correctly:

a.     For an SFP+/QSFP+/QSFP28 fiber port, use an SFP+/QSFP+/QSFP28 cable to directly connect it to another fiber port of the same type on the local end.

b.     Identify whether the port can come up:

-     If the port can come up, you can determine that the peer port fails. Replace the peer port with a new port operating correctly.

-     If the port cannot come up, you can determine that the local port fails. Replace the local port with a new port operating correctly.

5.     Verify that the transceiver module and cable are operating correctly:

a.     Use the display transceiver alarm interface command to check for alarms on the transceiver module:

-     The device displays None if no error has occurred.

-     The device displays alarms if the transceiver module has failed or if the type of the transceiver module does not match the port type.

b.     Use an optical power meter to verify that the Tx power and Rx power of the transceiver module are stable and are within the correct range.

c.     Execute the display transceiver interface command to verify that the local transceiver module has the same wavelength and transmission distance as the peer transceiver module.

d.     If the transceiver module is not operating correctly, replace it with an H3C transceiver module that matches the fiber port.

For more information about transceiver modules and cables, see the installation guide for the switch.

 

 

NOTE:

When you use a QSFP+ to SFP+ cable to connect a 40-GE QSFP+ fiber port, you must use an optical attenuator because the Tx optical power of the QSFP+ transceiver module exceeds the upper Rx optical power limit of the SFP+ transceiver module.

 

6.     Verify that the fiber matches the transceiver module. If they do not match, replace the fiber with a new one that matches the transceiver module.

For more information about fibers, see the installation guide for the switch.

7.     If the issue persists, contact H3C Support.

A 25-GE SFP28 fiber port fails to come up

Symptom

A 25-GE SFP28 fiber port fails to come up.

Troubleshooting flowchart

Figure 7 Troubleshooting link up failure on a copper port

 

Solution

To resolve the issue:

1.     Verify that the speed and duplex mode of the local port match the speed and duplex mode of the peer port:

a.     Execute the display interface brief command to examine whether the speed and duplex mode of the port match the speed and duplex mode of the peer port.

b.     If they do not match, use the speed command and the duplex command to set the rate and duplex mode for the port.

2.     Verify that the speed and duplex mode of the local port match the speed and duplex mode of the transceiver module:

a.     Execute the display interface brief command to examine whether the speed and duplex mode of the port match the speed and duplex mode of the transceiver module.

b.     If they do not match, use the speed command and the duplex command to set the rate and duplex mode for the port.

25-GE ports can operate at 25 Gbps, 10 Gbps, or 1 Gbps. For a 25-GE port on an S6850 or S9850 switch to operate at 10 Gbps or 1 Gbps, you must use the speed command to specify that speed for the port. For the port to come up, the speed configured for the port must be the same as the speed of the transceiver module or cable installed in the port. 25-GE ports on an S6825 switch can operate at 10 Gbps or 1 Gbps without using the speed command. 25-GE breakout ports can operate at only 25 Gbps.

Ports in the same group must have the same speed settings.  When you modify the speed of a port in a group, the modification takes effect on all ports in the group. When you use the default command to restore the default settings for a port in a group, the speed will be restored to the default for the port and the other ports in the group.

25-GE ports on the S6850&S9850 switches are grouped as follows:

¡     For ports 1 through 24 and 33 through 56 on an S6850-56HF switch, four continuous ports starting from 1 or 33 are organized into one group.

¡     For ports on an LSWM124TG2H interface card, four continuous ports starting from 1 are organized into one group.

¡     When you use the using twenty-fivegige command to split a 100-GE port into four 25-GE breakout ports, the four breakout ports are organized into one group.

To use autonegotiation for 25-GE ports, follow these restrictions and guidelines:

¡     To use an SFP28 copper cable to connect an SFP28 port on an S6850-56HF or S6825-54HF switch to a peer port, use the speed, duplex full, and port fec mode command to configure the speed, full duplex mode, and a non-auto FEC mode for the port if the peer port does not support autonegotiation. For the port to come up, make sure the configured speed for the port is consistent with that of the transceiver module/cable installed in it.

¡     To use an SFP+ transceiver module/cable to connect an SFP28 port on an S6850-56HF switch to a peer port, you must configure the speed 10000 command for the port so that it can come up.

¡     The SFP28 ports on an LSWM124TG2H do not support autonegotiation. To use an SFP28 copper cable to connect an SFP28 port, disable autonegotiation on the peer port. To use an SFP+ transceiver module/cable to connect an SFP28 port, configure the speed 10000 command for the port so that the port can come up.

¡     To  use another type of SFP transceiver module than the SFP-GE-T or SFP-GE-T-D to connect an SFP28 port, disable autonegotiation on the peer port.

3.     Verify that the status of link compensation (also known as training) and FEC protocols is the same as the peer port.

You can use the port fec mode { auto | base-r | none | rs-fec } and port training { disable | enable } commands on 25-GE ports of the switch to control the status of FEC and training protocols. Then, the switch can interoperate with devices of different models.

¡     Make sure the FEC mode and training status is the same on the local and peer ports.

¡     To use a copper cable to connect a 25-GE port, make sure training is enabled on the port.

¡     Typically, training is enabled or disabled by the software. As a best practice, do not modify the training status. Use the port training { disable | enable } command to modify the training status only when the port cannot come up.

4.     Verify that the media type configuration of the port matches the media (transceiver module or cable) installed on the port.

For 25-GE ports on an LSWM124TG2H interface card, you must use the port media-type { copper | fiber } command to set the media type. Set the media type to fiber for a port that uses a transceiver module or fiber cable. Set the media type to copper for a port that uses a copper cable. The media type of ports in the same group is the same. When you set the media type for any port in a group, the setting is synchronized to the other ports in the group.

5.     Verify that the ports at both ends are operating correctly:

a.     If the port operates at 25 Gbps, use an SFP28 cable (used for short-haul connection) to directly connect it to another 25-GE port on the local end. If the port operates at 10 Gbps, use an SFP+ cable (used for short-haul connection) to directly connect it to another 10-GE port on the local end.

b.     Identify whether the port can come up:

-     If the port can come up, you can determine that the peer port fails. Replace the peer port with a new port operating correctly.

-     If the port cannot come up, you can determine that the local port fails. Replace the local port with a new port operating correctly.

6.     Verify that the transceiver module and cable are operating correctly:

a.     Use the display transceiver alarm interface command to check for alarms on the transceiver module:

-     The device displays None if no error has occurred.

-     The device displays alarms if the transceiver module has failed or if the type of the transceiver module does not match the port type.

b.     Use an optical power meter to verify that the Tx power and Rx power of the transceiver module are stable and are within the correct range.

c.     Execute the display transceiver interface command to verify that the local transceiver module has the same wavelength and transmission distance as the peer transceiver module.

d.     If the transceiver module is not operating correctly, replace it with an H3C transceiver module that matches the fiber port.

For more information about transceiver modules and cables, see the installation guide for the switch.

7.     Verify that the fiber matches the transceiver module. If they do not match, replace the fiber with a new one that matches the transceiver module.

For more information about fibers, see the installation guide for the switch.

8.     If the issue persists, contact H3C Support.

A 1/10GBase-T 10-GE copper port fails to come up

Symptom

A 1/10GBase-T 10-GE copper port fails to come up.

Troubleshooting flowchart

Figure 8 Troubleshooting link up failure on a copper port

 

Solution

To resolve the issue:

1.     Verify that the speed and duplex mode of the local port match the speed and duplex mode of the peer port:

The 1/10GBASE-T ports on the device can operate only at 10 Gbps or 1 Gbps and cannot operate at 10 Mbps or 100 Mbps.

a.     Execute the display interface brief command to examine whether the speed and duplex mode of the port match the speed and duplex mode of the peer port.

b.     If they do not match, use the speed command and the duplex command to set the rate and duplex mode for the port.

2.     Replace the network cable with a new one to verify that the network cable is in good condition.

3.     Replace the local port with a new one to verify that the local port is operating correctly.

4.     Replace the peer port with a new one to verify that the peer port is operating correctly.

5.     If the issue persists, contact H3C Support.

Non-H3C transceiver module error message

Symptom

The output from the display logbuffer command shows that the transceiver module is not an H3C transceiver module.

<Sysname> display logbuffer

   Twenty-FiveGigE1/0/5: This transceiver is NOT sold by H3C. H3C therefore shall NOT guarantee the normal function of the device or assume the maintenance responsibility thereof!

Troubleshooting flowchart

Figure 9 Troubleshooting non-H3C transceiver module error message

 

Solution

To resolve the issue:

1.     Verify that the transceiver module is an H3C transceiver module:

Execute the display transceiver interface command to view the vendor name of the transceiver module.

[Sysname] display transceiver interface twenty-fivegige 1/0/1

Twenty-FiveGigE 1/0/1 transceiver information:

  Transceiver Type              : 40G_BASE_LR4_QSFP_PLUS

  Connector Type                : LC

  Wavelength(nm)                : 1301

  Transfer Distance(km)         : 10(SMF)

  Digital Diagnostic Monitoring : YES

  Vendor Name                   : H3C

  Ordering Name                 : QSFP-40G-LR4-WDM1300

¡     If the vendor name field does not display H3C, replace the transceiver module with an H3C transceiver module.

¡     If the vendor name field displays H3C, perform the following tasks:

-     Execute the display hardware internal transceiver register interface command in probe view to save the transceiver module information.

-     Provide the information to H3C Support to verify that the transceiver module is an H3C transceiver module. If it is not, replace it with an H3C transceiver module.

2.     If the issue persists, contact H3C Support.

Transceiver module does not support digital diagnosis

Symptom

The output from the display transceiver diagnosis interface command shows that the transceiver module does not support the digital diagnosis function.

<Sysname> display transceiver diagnosis interface twenty-fivegige 1/0/1

The transceiver does not support this function.

Troubleshooting flowchart

Figure 10 Troubleshooting digital diagnosis failure on a transceiver module

 

Solution

To resolve the issue:

1.     Verify that the transceiver module is an H3C transceiver module:

Execute the display transceiver interface command to view the vendor name of the transceiver module.

¡     If the vendor name field does not display H3C, replace the transceiver module with an H3C transceiver module.

¡     If the vendor name field displays H3C, perform the following tasks:

-     Execute the display transceiver manuinfo interface command to save the transceiver module information.

-     Provide the information to H3C Support to verify that the transceiver module is an H3C transceiver module. If the module is not from H3C, replace it with an H3C transceiver module.

2.     Execute the display transceiver interface command to save the transceiver module information, and contact H3C Support to verify that the transceiver module supports the digital diagnosis function.

<Sysname> display transceiver interface twenty-fivegige 1/0/1

Twenty-FiveGigE 1/0/1 transceiver information:

  Transceiver Type              : 40G_BASE_LR4_QSFP_PLUS

  Connector Type                : LC

  Wavelength(nm)                : 1301

  Transfer Distance(km)         : 10(SMF)

  Digital Diagnostic Monitoring : YES

  Vendor Name                   : H3C

  Ordering Name                 : QSFP-40G-LR4-WDM1300

3.     If the issue persists, contact H3C Support.

Error frames (for example, CRC errors) on a port

Symptom

The output from the display interface command shows that error frames exist (for example, CRC error frames) on a port.

Troubleshooting flowchart

Figure 11 Troubleshooting error frames (for example, CRC errors) on a port

 

Solution

To resolve the issue:

1.     Examine the error frame statistics and identify the error frame type:

a.     (Optional.) Use the reset counter interface command in user view to clear the packet statistics of the port.

This command resets all packet counters to 0, so that you can view the statistics changes more clearly.

b.     Use the display interface command to display the incoming packet statistics and outgoing packet statistics of the port.

c.     Determine the type of error frames that are accumulating.

2.     If the port is a fiber port, verify that the optical power of the transceiver module is operating correctly:

a.     Use the display transceiver diagnosis interface command to view the present measured values of the digital diagnosis parameters for the transceiver module.

[Sysname] display transceiver diagnosis interface twenty-fivegige 1/0/1

Twenty-FiveGigE1/0/1 transceiver diagnostic information:

  Current diagnostic parameters:

    Temp.(°C) Voltage(V)  Bias(mA)  RX power(dBm)  TX power(dBm)             

    43         3.31        6.23      -6.50          -2.15                    

  Alarm thresholds:                                                          

          Temp(°C)  Voltage(V)  Bias(mA)  RX power(dBM)  TX power(dBM)        

    High   75         -63        10.50       2.00           1.50              

    Low    -5         2.97        2.00      -13.90         -11        

b.     If the optical power of the transceiver module is not within the correct range, replace the transceiver module with a transceiver module of the same model that is operating correctly.

3.     Verify that the port configurations are correct:

a.     Execute the display interface brief command.

b.     Determine whether the speed and duplex mode of the port match the speed and duplex mode of the peer port.

c.     If they do not match, use the speed command and the duplex command to set the speed and duplex mode for the port.

4.     Verify that the link medium connected to the port is operating correctly.

Plug the link medium into a new port that is operating correctly. If error frames still exist, replace the link medium.

5.     Verify that the port is operating correctly:

¡     If the port is a copper port, connect the port directly to a PC.

¡     If the port is a fiber port, replace the transceiver module in the port.

If error frames do not exist, troubleshoot the remaining possible points of failure on the transmission path. The troubleshooting process is beyond the scope of this document.

6.     Determine whether the port has received a large amount of flow control frames:

a.     Use the display interface command to view the number of pause frames.

If the number of pause frames is accumulating, you can determine that the port has sent or received a large amount of flow control frames.

b.     Verify that the incoming traffic and outgoing traffic have not exceeded the maximum traffic processing capability of the local device and the peer device.

7.     If the issue persists, contact H3C Support.

Failure to receive packets

Symptom

A port is up, but it cannot receive packets.

Troubleshooting flowchart

Figure 12 Troubleshooting failure to receive packets

 

Solution

To resolve the issue:

1.     Verify that the ports at both ends are up.

2.     Examine the packet statistics of the port:

a.     (Optional.) Use the reset counter interface command to clear the packet statistics of the port.

This command resets all packet counters to 0, so that you can view the statistics changes more clearly.

b.     Use the display interface command to verify that the number of incoming packets is accumulating.

c.     Verify that the number of error frames is not accumulating.

If the number of error frames is accumulating, remove the errors. For more information, see "Error frames (for example, CRC errors) on a port."

3.     Verify that the port configurations do not affect packet receiving:

a.     Use the display interface brief command to verify that the port configurations are correct.

The port configurations include the duplex mode, speed, port type, and VLAN configurations of the ports at both ends of the link. If configuration errors exist, modify the port configurations. If the port fails to receive packets, use the shutdown command and then the undo shutdown command to re-enable the port.

b.     If the port is configured with the spanning tree feature, use the display stp brief command to verify that the port is not in the discarding state.

If the port is set to the discarding state by the spanning tree feature, examine and modify the spanning tree feature configurations to resolve the issue.

As a best practice, configure the port as an edge port or disable the spanning tree feature on the port if it is directly connected to a terminal.

c.     If the port is in an aggregation group, use the display link-aggregation summary command to verify that the status of the port is Selected.

If the status of the port is Unselected, the port cannot send or receive data packets. Determine the reasons why the port becomes Unselected, for example, the attribute configurations of the port are different from the reference port. Modify the attribute configurations of the port to make the port become Selected.

4.     Verify that the link medium connected to the port is operating correctly.

Plug the link medium into a new port that is operating correctly. If the new port cannot receive packets, replace the link medium.

5.     Verify that the port is operating correctly:

¡     If the port is a copper port, connect the port directly to a PC.

¡     If the port is a fiber port, replace the transceiver module in the port.

If the port can receive packets, troubleshoot the remaining possible points of failure on the transmission path. The troubleshooting process is beyond the scope of this document.

6.     If the issue persists, contact H3C Support.

Failure to send packets

Symptom

A port is up, but it cannot send packets.

Troubleshooting flowchart

Figure 13 Troubleshooting failure to send packets

 

Solution

To resolve the issue:

1.     Verify that the ports at both ends are up.

2.     Examine the packet statistics of the port:

a.     (Optional.) Use the reset counter interface command to clear the packet statistics of the port.

This command resets all packet counters to 0, so that you can view the statistics changes more clearly.

b.     Use the display interface command to verify that the number of outgoing packets is accumulating.

c.     Verify that the number of error frames is not accumulating.

If the number of error frames is accumulating, remove the errors. For more information, see "Error frames (for example, CRC errors) on a port."

3.     Verify that the port configurations do not affect packet sending:

a.     Use the display interface brief command to verify that the port configurations are correct.

The port configurations include the duplex mode, speed, port type, and VLAN configurations of the ports at both ends of the link. If configuration errors exist, modify the port configurations. If the port fails to send packets, use the shutdown command and then the undo shutdown command to re-enable the port.

b.     If the port is configured with the spanning tree feature, use the display stp brief command to verify that the port is not in the discarding state.

If the port is set to the discarding state by the spanning tree feature, examine and modify the spanning tree feature configurations to resolve the issue.

As a best practice, configure the port as an edge port or disable the spanning tree feature on the port if it is directly connected to a terminal.

c.     If the port is in an aggregation group, use the display link-aggregation summary command to verify that the status of the port is Selected.

If the status of the port is Unselected, the port cannot send or receive data packets. Determine the reasons why the port becomes Unselected, for example, the attribute configurations of the port are different from the reference port. Modify the attribute configurations of the port to make the port become Selected.

4.     Verify that the link medium connected to the port is operating correctly.

Plug the link medium into a new port that is operating correctly. If the new port cannot send packets, replace the link medium.

5.     Verify that the port is operating correctly:

¡     If the port is a copper port, connect the port directly to a PC.

¡     If the port is a fiber port, replace the transceiver module in the port.

If the port can send packets, troubleshoot the remaining possible points of failure on the transmission path. The troubleshooting process is beyond the scope of this document.

6.     If the issue persists, contact H3C Support.

Related commands

This section lists the commands that you might use for troubleshooting ports.

 

Command

Description

display diagnostic-information

Displays or saves running status data for multiple feature modules.

display interface

Displays Ethernet interface information.

display interface brief

Displays brief interface information.

display link-aggregation summary

Displays the summary information for all aggregation groups.

display logbuffer

Displays the state of the log buffer and the log information in the log buffer.

display stp brief

Displays brief spanning tree status and statistics.

display transceiver alarm interface

Displays the current transceiver module alarms.

display transceiver diagnosis

Displays the present measured values of the digital diagnosis parameters for transceiver modules.

display transceiver interface

Displays the key parameters of transceiver modules.

display transceiver manuinfo interface

Displays electronic label information for the transceiver module in an interface.

 


Troubleshooting EVPN

This section provides troubleshooting information for common issues with EVPN.

EBGP or IBGP neighbor relationship setup failure

Symptom

Two devices cannot set up an EBGP or IBGP neighbor relationship.

Troubleshooting flowchart

Figure 14 Troubleshooting EBGP or IBGP neighbor relationship setup failure

 

Solution

To resolve the issue:

1.     Verify that BGP is correctly configured:

a.     Execute the display bgp peer l2vpn evpn command on the devices to view their BGP settings.

b.     Verify that the EBGP or IBGP peers on the devices have matching AS numbers. If the AS numbers do not match, use the peer as-number command to modify the AS numbers.

c.     Verify that the devices use different router IDs. If the devices use the same router ID, use the router-id command to modify the router ID of one device.

2.     Verify that the devices have connectivity:

a.     Verify that one device can ping the other device.

b.     If the ping fails, check for link failure and verify that the devices have routes to each other.

3.     Verify that the memory usage of each device is below the critical alarm threshold:

a.     Execute the display memory-threshold command on each device to view its memory usage.

b.     Verify that the memory usage is below the critical alarm threshold in the last 10 minutes.

c.     If the memory usage stays above the critical alarm threshold, contact Hewlett Packard Enterprise Support.

4.     Perform the following tasks to collect information and contact Hewlett Packard Enterprise Support:

a.     Execute the debugging bgp event command to view possible causes for neighbor relationship setup failure, such as connection setup errors and connection conflicts.

b.     Execute the debugging bgp open command to view errors in OPEN message transmission and receipt.

c.     Execute the debugging tcp packet command to view TCP packet exchange failure.

d.     Execute the display bgp peer l2vpn evpn verbose command to view neighbor address family negotiation information and packet transmission and receipt history.

e.     Execute the display bgp peer l2vpn evpn log-info command to view neighbor status changes and neighbor down reasons.

f.     Execute the display system internal bgp peer l2vpn evpn session statistics command to view session status details.

ECMP forwarding failure

Symptom

In an EVPN network, the device cannot forward packets through ECMP routes.

Troubleshooting flowchart

Figure 15 Troubleshooting ECMP forwarding failure

 

Solution

To resolve the issue:

1.     Verify that the device has routes to the destination network:

a.     Execute the display bgp l2vpn evpn route-distinguisher route-type ip-prefix command.

b.     Verify that the device has routes to the destination network.

The routes must have the same RD and different next hops. If only one route exists, ECMP forwarding cannot be performed.

2.     Verify that the routes have the same community attributes and extended community attributes:

a.     Execute the display bgp l2vpn evpn route-distinguisher route-distinguisher evpn-route route-length command.

b.     Verify that the routes have the same BGP community attributes and extended community attributes.

c.     If the routes have different BGP community attributes and extended community attributes, modify the attributes.

3.     Verify that the routes do not have the default-gateway attribute:

a.     Execute the display bgp l2vpn evpn route-distinguisher route-distinguisher evpn-route route-length command.

b.     Verify that the routes do not have the default-gateway attribute. Routes with this attribute cannot act as ECMP routes.

c.     If the routes have the default-gateway attribute, delete the attribute.

4.     Verify that the routes are all BGP routes:

a.     Execute the display ip routing-table vpn-instance command.

b.     Verify that the routes are all BGP routes.

c.     If some of the routes are from other protocols, raise the priority of BGP routes by using the preference command.

5.     Verify that the number of BGP ECMP routes is larger than one:

a.     Execute the display bgp routing-table ipv4 vpn-instance command to verify that multiple routes have the same prefix.

b.     If one of the routes that have the same prefix has the optimal sign (>), execute the display current-configuration configuration bgp command to verify that the balance command has been executed in BGP-VPN IPv4 unicast address family view.

c.     If the balance command is not executed, use it to set the number of BGP ECMP routes to a value larger than 1.

6.     If the issue persists, contact Hewlett Packard Enterprise Support.

Related commands

This section lists the commands that you might use for troubleshooting EVPN.

 

Command

Description

balance

Sets the maximum number of BGP ECMP routes for load balancing.

display bgp l2vpn evpn

Displays BGP EVPN routes.

display bgp peer l2vpn evpn

Displays BGP peer or peer group information for EVPN.

display bgp routing-table ipv4 vpn-instance

Displays BGP IPv4 unicast routing information for VPN instances.

display current-configuration configuration bgp

Displays the running configuration for BGP.

display evpn auto-discovery

Displays information about peers that are automatically discovered through BGP.

display ip routing-table vpn-instance

Displays routing table information for VPN instances.

display memory-threshold

Displays memory alarm thresholds and statistics.

display system internal bgp peer l2vpn evpn session statistics

Displays BGP peer session statistics.

peer as-number

Specifies an AS number for a peer.

preference

Configures preferences for BGP routes.

router-id

Configures a router ID.

debugging bgp event

Enables BGP event debugging.

debugging bgp open

Enables BGP OPEN message debugging.

debugging tcp packet

Enables TCP packet debugging.

 

Troubleshooting system management

This section provides troubleshooting information for common system management issues.

High CPU utilization

Symptom

The sustained CPU utilization of the device is over 80%.

Troubleshooting flowchart

Figure 16 Troubleshooting high CPU utilization

 

Solution

To resolve the issue:

1.     Identify the job that has a high CPU utilization.

<Sysname> system-view

[Sysname] probe

[Sysname-probe] display process cpu slot 1                                          

CPU utilization in 5 secs: 3.7%; 1 min: 3.1%; 5 mins: 3.8%                     

    JID      5Sec      1Min      5Min    Name                                  

      1      0.0%      0.0%      0.0%    scmd                                  

      2      0.0%      0.0%      0.0%    [kthreadd]                            

      3      0.0%      0.0%      0.0%    [migration/0]                         

      4      0.0%      0.0%      0.0%    [ksoftirqd/0]                         

      5      0.0%      0.0%      0.0%    [watchdog/0]                          

      6      0.0%      0.0%      0.0%    [migration/1]                         

      7      0.0%      0.0%      0.0%    [ksoftirqd/1]                         

      8      0.0%      0.0%      0.0%    [watchdog/1]                          

      9      0.0%      0.0%      0.0%    [migration/2]                         

     10      0.0%      0.0%      0.0%    [ksoftirqd/2]                          

     11      0.0%      0.0%      0.0%    [watchdog/2]                          

     12      0.0%      0.0%      0.0%    [migration/3]                         

     13      0.0%      0.0%      0.0%    [ksoftirqd/3]                          

     14      0.0%      0.0%      0.0%    [watchdog/3]                          

     15      0.0%      0.0%      0.0%    [migration/4]                         

     16      0.0%      0.0%      0.0%    [ksoftirqd/4]                         

     17      0.0%      0.0%      0.0%    [watchdog/4]                          

     18      0.0%      0.0%      0.0%    [migration/5]                         

     19      0.0%      0.0%      0.0%    [ksoftirqd/5]                         

     20      0.0%      0.0%      0.0%    [watchdog/5]                          

     21      0.0%      0.0%      0.0%    [migration/6]                         

---- More ----

The output shows the average CPU usage values of jobs for the last 5 seconds, 1 minute, and 5 minutes. Typically, the average CPU usage of a job is less than 5%.

2.     Display the job's stack. In this example, the job uses the ID of 14.

[Sysname-probe] follow job 14                                                   

Attaching to process 14 ([watchdog/3])                                         

Iteration 1 of 5                                                               

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

Kernel stack:                                                                  

[<80480754>] schedule+0x954/0x1250                                             

[<8028f720>] watchdog+0xb0/0x410                                               

[<802656d0>] kthread+0x130/0x140                                               

[<8021d730>] kernel_thread_helper+0x10/0x20                                    

                                                                               

Iteration 2 of 5                                                                

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

Kernel stack:                                                                  

[<80480754>] schedule+0x954/0x1250                                              

[<8028f720>] watchdog+0xb0/0x410                                               

[<802656d0>] kthread+0x130/0x140                                               

[<8021d730>] kernel_thread_helper+0x10/0x20                                     

                                                                               

Iteration 3 of 5                                                               

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

Kernel stack:                                                                  

[<80480754>] schedule+0x954/0x1250                                             

[<8028f720>] watchdog+0xb0/0x410                                               

[<802656d0>] kthread+0x130/0x140                                               

[<8021d730>] kernel_thread_helper+0x10/0x20                                    

                                                                               

Iteration 4 of 5                                                                

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

Kernel stack:                                                                  

[<80480754>] schedule+0x954/0x1250                                              

[<8028f720>] watchdog+0xb0/0x410                                               

[<802656d0>] kthread+0x130/0x140                                               

[<8021d730>] kernel_thread_helper+0x10/0x20                                    

                                                                               

Iteration 5 of 5                                                               

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

Kernel stack:                                                                  

[<80480754>] schedule+0x954/0x1250                                             

[<8028f720>] watchdog+0xb0/0x410                                                

[<802656d0>] kthread+0x130/0x140                                               

[<8021d730>] kernel_thread_helper+0x10/0x20

3.     Save the information displayed in the previous steps.

4.     Contact Hewlett Packard Enterprise Support.

High memory utilization

Symptom

The memory utilization of the device is over 60% for more than 30 minutes.

Troubleshooting flowchart

Figure 17 Troubleshooting high memory utilization

 

Solution

To resolve the issue:

1.     Execute the display system internal kernel memory pool command multiple times to display memory usage information.

<Sysname> system-view

[Sysname] probe

[Sysname-probe] display system internal kernel memory pool slot 1 

Active    Number  Size     Align Slab Pg/Slab ASlabs  NSlabs Name              

2         10      3072     0     10   8       1       1      sgpool-128        

0         0       900      0     34   8       0       0      LFIB_IlmEntryCache

0         0       656      0     23   4       0       0      MFW_FsCache       

2         39      768      0     39   8       1       1      biovec-64         

0         0       96       8     30   1       0       0      cfq_io_context    

0         0       52       0     42   1       0       0    ARP_Static_Entry_Cachep                                                                           

0         0       432      0     34   4       0       0      LFIB_IlmEntryCache

0         0       80       0     34   1       0       0      LFIB_NhlfeCacheCache                                                                              

0         0       536      0     28   4       0       0      jffs2_i           

11        92      52       4     46   1       2       2      pktpcb            

1         26      576      0     26   4       1       1      shmem_inode_cache 

515       650     256      8     25   2       24      26     kmalloc-256       

0         0       1936     0     16   8       0       0      MFW_FsCache       

0         42      4096     0     7    8       0       6      names_cache       

0         0       1104     0     28   8       0       0      MFW_FsCache       

0         0       336      4     21   2       0       0      ripcb             

0         0       8        0     85   1       0       0      L2VFIB_Ac_Ctr_Cache

599       680     440      4     34   4       20      20     socket            

0         0       104      0     28   1       0       0      memDSLITE         

0         0       68       0     39   1       0       0      mfib_l2m_source_cache                                                                             

16        26      108      0     26   1       1       1      ADJ4_Ext_Cachep   

0         0       48       0     46   1       0     0  L2VFIB_LpwEntryCacheName(1)

---- More ----

Each value line shows the memory information for a slab. The Number field shows the number of objects (memory blocks) allocated to the module. The Active field shows the number of objects used. If the percentage of the used objects keeps increasing, the slab might have memory leakage issues.

2.     Save the information displayed in the previous step.

3.     Contact Hewlett Packard Enterprise Support.

 

IMPORTANT

IMPORTANT:

Hewlett Packard Enterprise recommends not rebooting the device before you contact Hewlett Packard Enterprise Support. You might lose critical diagnostic information if you reboot the device.

 

Related commands

This section lists the commands that you might use for troubleshooting system management.

 

Command

Description

display cpu-usage

Displays the current CPU usage statistics.

display memory

Displays memory usage statistics.

display process cpu

Displays the CPU usage statistics for jobs.

display system internal kernel memory pool

Displays memory block usage statistics.

follow job job-id

Displays the stack of a job.

 

Troubleshooting other issues

Layer 2 forwarding failure

Symptom

Layer 2 packet loss occurs when the switch forwards packets to a peer on the same network segment and in the same VLAN.

Troubleshooting flowchart

Figure 18 Troubleshooting Layer 2 packet loss failure

 

Solution

To resolve the issue:

1.     Verify that no error packets have been received on the local port:

a.     Execute the display interface command and check for error packets.

<Sysname>display interface hundredgige 1/0/32

HundredGigE1/0/32 current state: UP

Line protocol state: UP

IP Packet Frame Type: PKTFMT_ETHNT_2, Hardware Address: 000f-e200-002b

……

Last 300 seconds input:  0 packets/sec 10 bytes/sec 0%

 Last 300 seconds output:  0 packets/sec 10 bytes/sec 0%

 Input (total):  1438 packets, 480292 bytes

          0 unicasts, 0 broadcasts, 1438 multicasts, 0 pauses

 Input (normal):  1438 packets, - bytes

          0 unicasts, 0 broadcasts, 1438 multicasts, 0 pauses

 Input:  0 input errors, 0 runts, 0 giants, 0 throttles

          0 CRC, 0 frame, - overruns, 0 aborts

          - ignored, - parity errors

 Output (total): 1440 packets, 475200 bytes

          0 unicasts, 0 broadcasts, 1440 multicasts, 0 pauses

 Output (normal): 1440 packets, - bytes

          0 unicasts, 0 broadcasts, 1440 multicasts, 0 pauses

 Output: 0 output errors, - underruns, - buffer failures

          0 aborts, 0 deferred, 0 collisions, 0 late collisions

          0 lost carrier, - no carrier

b.     If the statistics are not zero, the following failures might occur:

-     Interface hardware failure—To test such a failure, connect the cable that is connected to the local port to a correctly operating port (for example, Port A) with the same configurations as the local port. If Port A forwards traffic correctly, you can determine that the hardware of the local port fails. In this event, you must replace the local port with a correctly operating port.

-     Transceiver module, fiber, or twisted pair failure—To test and resolve such a failure, replace the transceiver module, fiber, or twisted pair with a good one.

-     Inconsistent configurations—Verify that the configurations (including speed and duplex mode) of the peer are consistent with the local port. If they are inconsistent, modify the configurations of the local port.

c.     If the issue persists, contact Hewlett Packard Enterprise Support.

When you contact Hewlett Packard Enterprise Support, provide the following diagnostic information if packet loss occurs on the chip port with which the interface is associated:

# Use the probe command to enter probe view. In probe view, execute the debug port mapping command to identify the chip port with which the interface is associated.

[Sysname-probe] debug port mapping slot 1

 [Interface]       [Unit] [Port] [Name] [Combo?] [Active?] [IfIndex] [MID] [Link]

[PipeNum]

===============================================================================

 WGE1/0/1         0       23     xe3     no        no      0x1       16    down

    0

 WGE1/0/2         0       24     xe4     no        no      0x2       16    down

    0

 WGE1/0/3         0       21     xe1     no        no      0x3       16    down

    0

 WGE1/0/4         0       22     xe2     no        no      0x4       16    down

    0

 WGE1/0/5         0       31     xe7     no        no      0x5       16    down(

shut)     0

 WGE1/0/6         0       32     xe8     no        no      0x6       16    down

    0

 WGE1/0/7         0       29     xe5     no        no      0x7       16    down

    0

 WGE1/0/8         0       30     xe6     no        no      0x8       16    down

    0

 WGE1/0/9         0       35     xe11    no        no      0x9       16    down

    0

 WGE1/0/10        0       36     xe12    no        no      0xa       16    down

    0

 WGE1/0/11        0       33     xe9     no        no      0xb       16    down

    0

 WGE1/0/12        0       34     xe10    no        no      0xc       16    down

    0

 WGE1/0/13        0       43     xe15    no        no      0xd       16    down

    0

 WGE1/0/14        0       44     xe16    no        no      0xe       16    down

    0

 WGE1/0/15        0       41     xe13    no        no      0xf       16    down

    0

 WGE1/0/16        0       42     xe14    no        no      0x10      16    down

    0

 WGE1/0/17        0       51     xe19    no        no      0x11      16    down

    0

 WGE1/0/18        0       52     xe20    no        no      0x12      16    down

    0

 WGE1/0/19        0       49     xe17    no        no      0x13      16    down

    0

 WGE1/0/20        0       50     xe18    no        no      0x14      16    down

    0

 WGE1/0/21        0       59     xe23    no        no      0x15      16    down

    0

 WGE1/0/22        0       60     xe24    no        no      0x16      16    down

    0

 WGE1/0/23        0       57     xe21    no        no      0x17      16    down

    0

 WGE1/0/24        0       58     xe22    no        no      0x18      16    down

    0

 HGE1/0/25        0       1      ce0     no        no      0x19      16    down

    0

 HGE1/0/26        0       5      ce1     no        no      0x1e      16    down

    0

 HGE1/0/27        0       13     ce2     no        no      0x23      16    down

    0

 HGE1/0/28        0       61     ce3     no        no      0x28      16    down

    0

 HGE1/0/29        0       115    ce5     no        no      0x2d      16    down

    1

 HGE1/0/30        0       67     ce4     no        no      0x32      16    down

    1

 HGE1/0/31        0       127    ce7     no        no      0x37      16    down

    1

 HGE1/0/32        0       123    ce6     no        no      0x3c      16    down

    1

 WGE1/0/33        0       73     xe27    no        no      0x41      16    down

    1

 WGE1/0/34        0       74     xe28    no        no      0x42      16    down

    1

 WGE1/0/35        0       71     xe25    no        no      0x43      16    down

    1

 WGE1/0/36        0       72     xe26    no        no      0x44      16    down

    1

 WGE1/0/37        0       81     xe32    no        no      0x45      16    down

    1

 WGE1/0/38        0       82     xe33    no        no      0x46      16    down

    1

 WGE1/0/39        0       79     xe30    no        no      0x47      16    down

    1

 WGE1/0/40        0       80     xe31    no        no      0x48      16    down

    1

 WGE1/0/41        0       89     xe36    no        no      0x49      16    down

    1

 WGE1/0/42        0       90     xe37    no        no      0x4a      16    down

    1

 WGE1/0/43        0       87     xe34    no        no      0x4b      16    down

    1

 WGE1/0/44        0       88     xe35    no        no      0x4c      16    down

    1

 WGE1/0/45        0       97     xe40    no        no      0x4d      16    down

    1

 WGE1/0/46        0       98     xe41    no        no      0x4e      16    down

    1

 WGE1/0/47        0       95     xe38    no        no      0x4f      16    down

    1

 WGE1/0/48        0       96     xe39    no        no      0x50      16    down

    1

 WGE1/0/49        0       101    xe44    no        no      0x51      16    down

    1

 WGE1/0/50        0       102    xe45    no        no      0x52      16    down

    1

 WGE1/0/51        0       99     xe42    no        no      0x53      16    down

    1

 WGE1/0/52        0       100    xe43    no        no      0x54      16    down

    1

 WGE1/0/53        0       109    xe48    no        no      0x55      16    down

    1

 WGE1/0/54        0       110    xe49    no        no      0x56      16    down

    1

 WGE1/0/55        0       107    xe46    no        no      0x57      16    down

    1

 WGE1/0/56        0       108    xe47    no        no      0x58      16    down

    1

 GE1/0/57         0       66     ge0     no        no      0x59      16    down

    1

 GE1/0/58         0       130    ge1     no        no      0x5a      16    down

    1

 M-GE0/0/0        0       136            no        no      0x5a      16    up

    0

 M-GE0/0/1        0       137            no        no      0x5a      16    down

    0

The output shows that WGE 1/0/1 is associated with chip port xe3.

# Execute the bcm slot 1 chip 0 show/c/xe3 command to check the RDBGC and TDBGC fields for Rx and Tx dropped packet statistics, respectively. The statistics displayed were generated between the last and the current execution of the command. To view the change in dropped packet statistics, execute the command twice or more.

[Sysname-probe] bcm slot 1 chip 0 show/c/xe3

RDBGC2.xe0        :                 8,118              +8,118

R511.xe0          :                 8,118              +8,118

RPKT.xe0          :                 8,118              +8,118

RMCA.xe0          :                 8,118              +8,118

RPOK.xe0          :                 8,118              +8,118

RBYT.xe0          :             2,726,553          +2,726,553

T511.xe0          :                 8,208              +8,208

TPOK.xe0          :                 8,208              +8,208

TPKT.xe0          :                 8,208              +8,208

TMCA.xe0          :                 8,208              +8,208

TBYT.xe0          :             2,741,472          +2,741,472

PERQ_PKT(3).xe0   :                 8,208              +8,208

PERQ_BYTE(3).xe0  :             2,741,472          +2,741,472             330/s

2.     Verify that packets are not mistakenly filtered out by ACLs:

a.     Examine the ACL and QoS policy configurations for packet filtering on the port, on the VLAN of the port, or globally. If packets are mistakenly filtered out, modify the ACL or QoS policy configuration.

-     To display the ACL configuration on the port for packet filtering, execute the display packet-filter command.

-     To display the QoS policy configuration on the port, execute the display qos policy command.

-     To display the QoS policy configuration on the VLAN of the port, execute the display qos vlan-policy command.

-     To display the global QoS policy configuration, execute the display qos policy global command.

b.     Verify that packets are not filtered out by ACLs automatically created by some features.

-     Execute the display this command in Ethernet interface view to verify that the ip source binding or ip verify source command is configured on the port. To display source guard binding entries, execute the display ip source binding or display ipv6 source binding command. If IP source guard is configured but the packets match no entry, further troubleshoot the issue based on the way the binding entries are created.

-     Determine whether the port is configured with the portal authentication. Packets of users that fail to pass the portal authentication will be dropped by the port. Use the display portal interface command to display the portal configuration information of the specified VLAN interface. Determine whether the portal authentication can be disabled based on the network conditions. To disable the portal authentication at Layer 3, use the undo portal server server-name command in VLAN interface view of the VLAN to which the port belongs.

3.     Verify that the port is not blocked:

¡     Execute the display stp brief command to verify that STP does not set the state of the port to discarding. When the port is in discarding state, it cannot forward traffic. Hewlett Packard Enterprise recommends disabling STP on the port, or configuring the port as an edge port if the port is connected to a terminal device.

¡     If the port belongs to an aggregation group, execute the display link-aggregation verbose command to identify the port status. When the port is an Unselected port, it cannot forward traffic. Locate the reasons why the port is in Unselected state. For example, the attribute configurations of the port are different from the configurations of the reference port.

¡     Identify whether the port is blocked by smart link. Use the display smart-link group command to view the port status. If the state of the port is STANDBY or DOWN, the port cannot forward traffic.

-     If the state of the port is DOWN, locate the reason for the port to be down. The possible reasons include: its uplink device is configured with monitor link, the link of the port fails, or the port is shut down. Further troubleshoot the issue based on the reason for the port to be down.

-     If the state of the port is STANDBY, perform an active/standby switchover in the smart link group.

4.     Examine the following configurations that might cause packet loss:

¡     VLAN configuration—Execute the display this command in Ethernet interface view to verify that the port is in the VLAN of the packets. If it is not, add the port to the VLAN.

¡     Blackhole MAC address entriesExecute the display mac-address blackhole command to display blackhole MAC address entries. If the packets are discarded because they match a blackhole MAC address entry, delete the entry. To delete the blackhole MAC address entry, execute the undo mac-address blackhole mac-address vlan vlan-id command.

¡     Rate limitExecute the display qos lr interface command to display the rate limit configuration on the port. If rate limit is configured on the port, make sure the committed information rate (CIR) and the committed burst size (CBS) are appropriate. To adjust the CIR and CBS values, execute the qos lr { inbound | outbound } cir committed-information-rate [ cbs committed-burst-size ] command.

¡     Storm suppressionExecute the display this command in Ethernet interface view to display the configuration of storm suppression. Storm suppression includes broadcast suppression, multicast suppression, and unknown unicast suppression. To adjust the suppression thresholds, execute the broadcast-suppression, multicast-suppression, and unicast-suppression commands, respectively.

5.     Verify that no congestion occurs by using the display qos queue-statistics interface command.

If congestion occurs, locate and resolve the issue by referencing related congestion management documents.

6.     If the issue persists, contact Hewlett Packard Enterprise Support.

Related commands

This section lists the commands that you might use for troubleshooting Layer 2 packet loss failure.

 

Command

Description

display interface

Displays Ethernet interface information.

display ip source binding/display ipv6 source binding

Displays source guard binding entries.

display link-aggregation verbose

Displays detailed information about the aggregation groups that correspond to the aggregate interfaces.

display mac-address blackhole

Displays blackhole MAC address entries.

display packet-filter

Displays whether an ACL has been successfully applied to an interface for packet filtering.

display portal interface

Displays portal configuration and portal running state on an interface.

display qos lr interface

Displays the rate limit configuration and statistics on a specified interface or all the interfaces.

display qos policy

Displays user-defined QoS policy configuration information.

display qos policy global

Displays information about global QoS policies.

display qos policy interface

Displays information about the QoS policies applied to an interface or all interfaces.

display qos queue-statistics interface

Displays traffic statistics collected for an interface on a per-queue basis.

display qos vlan-policy

Displays information about QoS policies applied to VLANs.

display smart-link group

Displays information about the specified or all smart link groups.

display this

Displays the running configuration in the current view.

 

Layer 3 forwarding failure

Symptom

Packet loss occurs when the switch forwards packets to a different network.

Troubleshooting flowchart

Figure 19 Troubleshooting Layer 3 forwarding failure

 

Solution

To resolve the issue:

1.     Verify that the port is not faulty (due to hardware or configuration issues).

If the port is faulty, follow the solution in "Layer 2 forwarding failure" to troubleshoot the issue.

2.     Verify that ARP entries are correct if Layer 3 forwarding is based on IPv4:

a.     Execute the display arp command to verify that ARP entries are correct.

-     If incorrect ARP entries exist, execute the debugging arp packet command to locate the issue.

-     If the switch learns no ARP entries, execute the arp static command to configure static ARP entries.

b.     Execute the display mac-address command to verify that the output interfaces in the MAC address entries and ARP entries are the same.

If the output interfaces are different, execute the reset arp command to clear the ARP entries. Then the switch can learn ARP entries again.

3.     Verify that ND entries are correct if Layer 3 forwarding is based on IPv6:

a.     Execute the display ipv6 neighbors command to verify that ND entries are correct.

-     If incorrect ND entries exist, execute the debugging ipv6 icmp command to locate the issue.

-     If the switch learns no ND entries, execute the ipv6 neighbor command to configure static ND entries.

b.     Execute the display mac-address command to verify that the output interfaces in the MAC address entries and ND entries are the same.

If the output interfaces are different, execute the reset ipv6 neighbors command to clear the ND entries. Then the switch can learn ND entries again.

4.     Verify that route entries are correct:

a.     Execute the display ip routing-table command to verify that route entries are correct.

If incorrect route entries exist, troubleshoot the protocol that learns the route entries.

b.     Execute the display fib command to verify that the output interfaces in the FIB entries and route entries are the same.

If the output interfaces are not the same, execute the reset command to clear the route entries. Then the switch can learn route entries again.

5.     If the issue persists, contact Hewlett Packard Enterprise Support.

Related commands

This section lists the commands that you might use for troubleshooting Layer 3 forwarding failure.

 

Command

Description

debugging arp packet

Enables ARP packet debugging.

debugging ipv6 icmp

Enables ICMPv6 debugging.

display arp

Displays ARP entries.

display fib

Displays FIB entries

display ip routing-table

Displays brief information about active routes in the routing table.

display ipv6 neighbors

Displays neighbor information.

display mac-address

Displays MAC address entries

 

Protocol flapping

Symptom

The switch cannot send or receive protocol packets.

Troubleshooting flowchart

Figure 20 Troubleshooting protocol flapping

 

Solution

To resolve the issue:

1.     Verify that Layer 2 is operating correctly, as described in "Layer 2 forwarding failure."

2.     Verify that Layer 3 is operating correctly, as described in "Layer 3 forwarding failure."

3.     Check for software-related packet loss.

[Sysname-probe] debug rxtx softcar show slot 1

 

ID  Type                RcvPps PpsMax Rcv_All    DisPkt_All Pps  Dyn Swi Hash AC

Lmax                                                                           

0   ROOT                0      0      0          0          3000 S   On  SMAC 0

1   ISIS                0      0      0          0          2000 D   On  SMAC 8

2   ESIS                0      0      0          0          600  S   On  SMAC 8

3   CLNP                0      0      0          0          1000 S   On  SMAC 8

4   VRRP                0      0      0          0          2000 S   On  SMAC 8

5   UNKNOWN_IPV4MC      0      0      0          0          600  S   On  SMAC 8

6   UNKNOWN_IPV6MC      0      0      0          0          600  S   On  SMAC 8

7   IPV4_MC_RIP         0      0      0          0          1000 D   On  SMAC 8

8   IPV4_BC_RIP         0      0      0          0          1000 D   On  SMAC 8

...

The DisPkt_All column shows the number of lost packets, the Rcv_All column shows the number of received packets, and the RcvPps column shows the packet receiving rate. If packet loss occurs, contact related information and go to step 4.

4.     If the issue persists, contact Hewlett Packard Enterprise Support.

When you contact Hewlett Packard Enterprise Support, provide diagnostic information if software-related packet loss occurred.

  • Cloud & AI
  • InterConnect
  • Intelligent Computing
  • Security
  • SMB Products
  • Intelligent Terminal Products
  • Product Support Services
  • Technical Service Solutions
All Services
  • Resource Center
  • Policy
  • Online Help
All Support
  • Become a Partner
  • Partner Resources
  • Partner Business Management
All Partners
  • Profile
  • News & Events
  • Online Exhibition Center
  • Contact Us
All About Us
新华三官网