Login
- Released At: 18-11-2019
- Page Views:
- Downloads:
- Table of Contents
- Related Documents
-
|
|
|
H3C S9820 Switch Series |
|
Troubleshooting Guide |
|
|
|
|
Document version: 6W100-20190815
Copyright © 2019 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
Collecting log and operating information
Collecting common log messages
Collecting diagnostic log messages
Collecting operating statistics
Operating power module failure
Newly installed power module failure
ACL application failure with an error message
ACL application failure without an error message
Troubleshooting Ethernet link aggregation
A QSFP28 fiber port fails to come up
Non-H3C transceiver module error message
Transceiver module does not support digital diagnosis
Error frames (for example, CRC errors) on a port
EBGP or IBGP neighbor relationship setup failure
Troubleshooting system management
Introduction
This document provides information about troubleshooting common software and hardware problems with the S9820 switch series.
This document is not restricted to specific software or hardware versions.
General guidelines
|
|
IMPORTANT: To prevent a problem 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 problem, 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: 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 problems.
|
|
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 problem:
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 problem 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 problem:
1. Execute the display power command to display power module information.
<H3C>display power
Slot 3:
Input Power: 301(W)
PowerID State Mode Current(A) Voltage(V) Power(W) FanDirction
1 Absent -- -- -- -- --
2 Absent -- -- -- -- --
3 Absent -- -- -- -- --
4 Normal AC 24.91 12.10 301 PowerToPort
If the power module is in Absent state, go to step 2. If the power module is in Fault state, go to step 3.
2. Remove and reinstall the power module to make sure the power module is installed securely. Then, execute the display power command to verify that the power module has changed to Normal state. If the power module remains in Absent state, replace the power module.
3. When the power module is in Fault state, do the following:
a. Verify that the power module is connected to the power source securely. If it has been disconnected from the power source, connect the power source to it.
b. Determine whether the power module is in high temperature. If dust accumulation on the power module causes the high temperature, remove the dust. Then remove and reinstall the power module. Execute the display power command to verify that 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 verify that the power module has changed to Normal state in the new slot. If the power module remains in Fault state, replace the power module.
4. If the problem 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 problem:
1. Execute the display power command to display power module information.
<H3C>display power
Slot 3:
Input Power: 301(W)
PowerID State Mode Current(A) Voltage(V) Power(W)
1 Absent -- -- -- -- --
2 Absent -- -- -- -- --
3 Absent -- -- -- -- --
4 Normal AC 24.91 12.10 301 PowerToPort
If the power module is in Absent state, go to step 2. If the power module is in Fault state, go to step 3.
2. When the power module is in Absent state, do the following:
a. Remove and reinstall the power module to make sure the power module is installed securely. Then execute the display power command to verify that the power module has changed to Normal state. If the power module remains in Absent state, go to step b.
b. Remove and install the power module into an empty power module slot. Then execute the display power command to verify that the power module has changed to Normal state in the new slot. If the power module remains in Absent state, go to step 4.
3. Remove and install the power module into an idle power module slot. Then execute the display power command to verify that the power module has changed to Normal state in the new slot. If the power module remains in Fault state, go to step 4.
4. If the problem 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 problem:
1. Execute the display fan command to display the operating states of the fan tray.
[H3C]display fan
Slot 3:
Fan 1:
State : FanDirectionFault
Airflow Direction: Power-to-port
Prefer Airflow Direction: Port-to-power
Fan 2:
State : FanDirectionFault
Airflow Direction: Power-to-port
Prefer Airflow Direction: Port-to-power
Fan 3:
State : FanDirectionFault
Airflow Direction: Power-to-port
Prefer Airflow Direction: Port-to-power
¡ 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.
¡ If the fan tray is in Absent state, go to step 2.
¡ If the fan tray is in Fault state, go to step 3.
2. 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. 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. If the fan tray remains in Fault state, replace the fan tray.
You must make sure the switch operating temperature is below 60°C (140°F) while you replace the fan tray. If a new fan tray is not readily available, power off the switch to avoid damage caused by high temperature.
4. If the problem 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 problems with ACLs.
ACL application failure with an error message
Symptom
The system fails to apply a packet filter or an ACL-based QoS policy to the hardware. It also displays the "Reason: Not enough hardware resource" message.
Solution
To resolve the problem:
1. Execute the display qos-acl resource command, and then check the Remaining field for ACL resources insufficiency.
If this field displays 0, the ACL hardware resources are exhausted.
2. To free hardware resources, delete unnecessary ACLs.
3. If the problem persists, contact H3C Support.
ACL application failure without an error message
Symptom
The system applies a packet filter or an ACL-based QoS policy to the hardware. However, the ACL does not take effect.
Troubleshooting flowchart
Figure 2 Troubleshooting ACL application failure
Solution
Choose a solution depending on the module that uses the ACL.
ACL used in a QoS policy
To resolve the problem when the ACL is used in a QoS policy:
1. Verify that the QoS policy is configured correctly:
a. Use one of the following commands to check the QoS policy for configuration errors, depending on the policy application destination:
|
Destination |
Command |
|
Interface |
display qos policy interface |
|
VLAN |
display qos vlan-policy |
|
Global |
display qos policy global |
|
Control plane |
display qos policy control-plane slot slot-number |
b. If the QoS policy does not contain a class-behavior association, associate the traffic behavior with the traffic class.
c. If the QoS policy contains a class-behavior association, execute the display traffic classifier user-defined command and the display traffic behavior user-defined command to check for traffic class and behavior configuration errors, respectively.
- If they are configured incorrectly, reconfigure them.
- If they are configured correctly, go to step 2.
2. Verify that the ACL is configured correctly.
Execute the display acl command to check whether the ACL is configured correctly.
¡ If the ACL is configured incorrectly, reconfigure it.
¡ If the ACL is configured correctly, go to step 3.
3. If the problem persists, contact H3C Support.
ACL used in a packet filter
To resolve the problem when the ACL is used in a packet filter:
1. Verify that the packet filter is configured correctly.
Execute the display packet-filter command to check whether the packet filter is configured correctly.
¡ If there are any configuration errors, reconfigure the packet filter.
¡ If there is no configuration error, go to step 2.
2. Verify that the ACL is configured correctly.
Execute the display acl command to check whether the ACL is configured correctly.
¡ If the ACL is configured incorrectly, reconfigure it.
¡ If the ACL is configured correctly, go to step 3.
3. If the problem persists, contact H3C Support.
Related commands
This section lists the commands that you might use for troubleshooting ACLs.
|
Command |
Description |
|
display acl |
Displays configuration and match statistics for ACLs. |
|
display diagnostic-information |
Displays operating statistics for multiple feature modules in the system. |
|
display packet-filter |
Displays whether an ACL has been successfully applied to an interface for packet filtering. |
|
display qos-acl resource |
Displays QoS and ACL resource usage. |
|
display qos policy control-plane |
Displays information about the QoS policies applied to the specified control plane. |
|
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 to all interfaces. |
|
display qos policy user-defined |
Displays user-defined QoS policies. |
|
display qos vlan-policy |
Displays information about QoS policies applied to VLANs. |
|
display traffic classifier user-defined |
Displays traffic class configuration. |
|
display traffic behavior user-defined |
Displays traffic behavior configuration. |
Troubleshooting IRF
This section provides troubleshooting information for common problems with IRF.
IRF fabric setup failure
Symptom
An IRF fabric cannot be set up.
Troubleshooting flowchart
Figure 3 Troubleshooting IRF fabric setup failure
Solution
To resolve the problem:
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 QSFP28 ports on the front panel of the S9820-64H switch as IRF physical interfaces. The 10-GE or 25-GE breakout interfaces of a QSFP28 port cannot be used as IRF physical interfaces. If there are binding errors, reconfigure the IRF port bindings.
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:
¡ Use QSFP28 transceiver modules and fibers to connect IRF physical interfaces for a long-distance connection.
¡ Use QSFP28 AOC or DAC cables to connect IRF physical interfaces for a short-distance connection.
|
|
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. |
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.
5. 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 6.
- 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: 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. |
6. 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. |
7. 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).
8. If the problem 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 problems 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 4 Troubleshooting link aggregation failure
Solution
To resolve the problem:
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 problem.
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 problem 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 problems.
A QSFP28 fiber port fails to come up
Symptom
A QSFP28 fiber port fails to come up.
Troubleshooting flowchart
Figure 5 Troubleshooting link up failure on a QSFP28 fiber port
Solution
To resolve the problem:
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. Verify that the ports at both ends are operating correctly:
a. For a QSFP28 fiber port, use a 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.
4. 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.
5. 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.
6. If the problem 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
HundredGigE 1/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 6 Troubleshooting non-H3C transceiver module error message
Solution
To resolve the problem:
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 hundredgige 1/0/1
HundredGigE 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 problem 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 hundredgige 1/0/1
The transceiver does not support this function.
Troubleshooting flowchart
Figure 7 Troubleshooting digital diagnosis failure on a transceiver module
Solution
To resolve the problem:
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 hundredgige 1/0/1
HundredGigE 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 problem 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 8 Troubleshooting error frames (for example, CRC errors) on a port
Solution
To resolve the problem:
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 hundredgige 1/0/1
HundredGigE 1/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 problem persists, contact H3C Support.
Failure to receive packets
Symptom
A port is up, but it cannot receive packets.
Troubleshooting flowchart
Figure 9 Troubleshooting failure to receive packets
Solution
To resolve the problem:
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 problem.
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 problem persists, contact H3C Support.
Failure to send packets
Symptom
A port is up, but it cannot send packets.
Troubleshooting flowchart
Figure 10 Troubleshooting failure to send packets
Solution
To resolve the problem:
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 problem.
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 problem 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 problems with EVPN.
EBGP or IBGP neighbor relationship setup failure
Symptom
Two devices cannot set up an EBGP or IBGP neighbor relationship.
Troubleshooting flowchart
Figure 11 Troubleshooting EBGP or IBGP neighbor relationship setup failure
Solution
To resolve the problem:
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.
Related commands
This section lists the commands that you might use for troubleshooting EVPN.
|
Command |
Description |
|
display bgp l2vpn evpn |
Displays BGP EVPN routes. |
|
display bgp peer l2vpn evpn |
Displays BGP peer or peer group information for EVPN. |
|
display evpn auto-discovery |
Displays information about peers that are automatically discovered through BGP. |
|
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 problems.
High CPU utilization
Symptom
The sustained CPU utilization of the device is over 80%.
Troubleshooting flowchart
Figure 12 Troubleshooting high CPU utilization
Solution
To resolve the problem:
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 13 Troubleshooting high memory utilization
Solution
To resolve the problem:
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 problems.
2. Save the information displayed in the previous step.
3. Contact Hewlett Packard Enterprise Support.
|
|
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 problems
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 14 Troubleshooting Layer 2 packet loss failure
Solution
To resolve the problem:
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 problem 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.
[H3C-probe]debug port mapping slot 1
[Interface] [Unit] [Port] [Name] [Combo?] [Active?] [IfIndex] [MID] [Link]
[PipeNum]
===============================================================================
HGE1/0/1 0 34 ce16 no no 0x1 16 down
1
HGE1/0/2 0 37 ce17 no no 0x6 16 down
1
HGE1/0/3 0 38 ce18 no no 0x7 16 down
1
HGE1/0/4 0 41 ce19 no no 0xc 16 down
1
HGE1/0/5 0 42 ce20 no no 0xd 16 down
1
HGE1/0/6 0 45 ce21 no no 0x12 16 down
1
HGE1/0/7 0 46 ce22 no no 0x13 16 down
1
HGE1/0/8 0 49 ce23 no no 0x18 16 down
1
HGE1/0/9 0 50 ce24 no no 0x19 16 down
1
HGE1/0/10 0 53 ce25 no no 0x1e 16 down
1
HGE1/0/11 0 54 ce26 no no 0x1f 16 down
1
HGE1/0/12 0 57 ce27 no no 0x24 16 down
1
HGE1/0/13 0 58 ce28 no no 0x25 16 down
1
HGE1/0/14 0 61 ce29 no no 0x2a 16 down
1
HGE1/0/15 0 62 ce30 no no 0x2b 16 down
1
HGE1/0/16 0 65 ce31 no no 0x30 16 down
1
HGE1/0/17 0 68 ce32 no no 0x31 16 down
2
HGE1/0/18 0 71 ce33 no no 0x36 16 down
2
HGE1/0/19 0 72 ce34 no no 0x37 16 down
2
HGE1/0/20 0 75 ce35 no no 0x3c 16 down
2
HGE1/0/21 0 76 ce36 no no 0x3d 16 down
2
HGE1/0/22 0 79 ce37 no no 0x42 16 down
2
HGE1/0/23 0 80 ce38 no no 0x43 16 down
2
HGE1/0/24 0 83 ce39 no no 0x48 16 down
2
HGE1/0/25 0 84 ce40 no no 0x49 16 down
2
HGE1/0/26 0 87 ce41 no no 0x4e 16 down
2
HGE1/0/27 0 88 ce42 no no 0x4f 16 down
2
HGE1/0/28 0 91 ce43 no no 0x54 16 down
2
HGE1/0/29 0 92 ce44 no no 0x55 16 down
2
HGE1/0/30 0 95 ce45 no no 0x5a 16 down
2
HGE1/0/31 0 96 ce46 no no 0x5b 16 down
2
HGE1/0/32 0 99 ce47 no no 0x60 16 down
2
HGE1/0/33 0 1 ce0 no no 0x61 16 down
0
HGE1/0/34 0 4 ce1 no no 0x66 16 down
0
HGE1/0/35 0 5 ce2 no no 0x67 16 down
0
HGE1/0/36 0 8 ce3 no no 0x6c 16 down
0
HGE1/0/37 0 9 ce4 no no 0x6d 16 down
0
HGE1/0/38 0 12 ce5 no no 0x72 16 down
0
HGE1/0/39 0 13 ce6 no no 0x73 16 down
0
HGE1/0/40 0 16 ce7 no no 0x78 16 down
0
HGE1/0/41 0 17 ce8 no no 0x79 16 down
0
HGE1/0/42 0 20 ce9 no no 0x7e 16 down
0
HGE1/0/43 0 21 ce10 no no 0x7f 16 down
0
HGE1/0/44 0 24 ce11 no no 0x84 16 down
0
HGE1/0/45 0 25 ce12 no no 0x85 16 down
0
HGE1/0/46 0 28 ce13 no no 0x8a 16 down
0
HGE1/0/47 0 29 ce14 no no 0x8b 16 down
0
HGE1/0/48 0 32 ce15 no no 0x90 16 down
0
HGE1/0/49 0 102 ce48 no no 0x91 16 down
3
HGE1/0/50 0 105 ce49 no no 0x96 16 down
3
HGE1/0/51 0 106 ce50 no no 0x97 16 down
3
HGE1/0/52 0 109 ce51 no no 0x9c 16 down
3
HGE1/0/53 0 110 ce52 no no 0x9d 16 down
3
HGE1/0/54 0 113 ce53 no no 0xa2 16 down
3
HGE1/0/55 0 114 ce54 no no 0xa3 16 down
3
HGE1/0/56 0 117 ce55 no no 0xa8 16 down
3
HGE1/0/57 0 118 ce56 no no 0xa9 16 down
3
HGE1/0/58 0 121 ce57 no no 0xae 16 down
3
HGE1/0/59 0 122 ce58 no no 0xaf 16 down
3
HGE1/0/60 0 125 ce59 no no 0xb4 16 down
3
HGE1/0/61 0 126 ce60 no no 0xb5 16 down
3
HGE1/0/62 0 129 ce61 no no 0xba 16 down
3
HGE1/0/63 0 130 ce62 no no 0xbb 16 down
3
HGE1/0/64 0 133 ce63 no no 0xc0 16 down
3
M-GE0/0/0 0 136 no no 0xc0 16 up
0
M-GE0/0/1 0 137 no no 0xc0 16 down
0
The output shows that HundredGigE 1/0/1 is associated with chip port ce8.
# Execute the bcm slot 1 chip 0 show/c/ce16 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/ce16
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 problem 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 problem 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 entries—Execute 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 limit—Execute 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 suppression—Execute 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 problem by referencing related congestion management documents.
6. If the problem 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 15 Troubleshooting Layer 3 forwarding failure
Solution
To resolve the problem:
1. Verify that the port is not faulty (due to hardware or configuration problems).
If the port is faulty, follow the solution in "Layer 2 forwarding failure" to troubleshoot the problem.
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 problem.
- 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 problem.
- 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 problem 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 16 Troubleshooting protocol flapping
Solution
To resolve the problem:
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
...
4. If the problem persists, contact Hewlett Packard Enterprise Support.
When you contact Hewlett Packard Enterprise Support, provide diagnostic information if software-related packet loss occurred.
