Table of Contents
Advertisement
Quick Links
H3C S5850 Switch Series
Troubleshooting Guide
Document version: 6W100-20201218
Copyright © 2020 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.
Advertisement
Table of Contents
Troubleshooting
Subscribe to Our Youtube Channel
Related Manuals for H3C S5850-54QS
Summary of Contents for H3C S5850-54QS
- Page 1 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.
-
Page 2: Table Of Contents
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 Contacting technical support ······························································································································ 4 Troubleshooting hardware ············································································· 4 Unexpected switch reboot ··································································································································... - Page 3 Copper port remains in down state ·················································································································· 25 Symptom ·················································································································································· 25 Troubleshooting flowchart ························································································································ 25 Solution ···················································································································································· 25 Non-H3C transceiver module ··························································································································· 26 Symptom ·················································································································································· 26 Troubleshooting flowchart ························································································································ 26 Solution ···················································································································································· 26 Transceiver module does not support digital diagnosis ··················································································· 27 Symptom ··················································································································································...
- Page 4 Related commands ·································································································································· 50...
-
Page 5: Introduction
Introduction This document provides information about troubleshooting common software and hardware issues with S5850 Switch Series. This document is not restricted to specific software or hardware versions. General guidelines IMPORTANT: To prevent a failure from causing loss of configuration, save the configuration each time you finish configuring a feature. -
Page 6: Collecting Common Log Messages
files from all these devices. To more easily locate log information, save log files to a separate folder for each member device and include their IRF member IDs in the folder names. Table 1 Log and operating information Category File name format Content Log messages about command executions, event occurrences, logfile.log... -
Page 7: Collecting Diagnostic Log Messages
Collecting diagnostic log messages Save the 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>... -
Page 8: Contacting Technical Support
---- More ---- Contacting technical support If you cannot resolve an issue after using the troubleshooting procedures in this document, contact H3C Support. When you contact an authorized H3C support representative, be prepared to provide the following information: • Information described in "General... -
Page 9: Unexpected Switch Reboot
NOTE: This section describes how to troubleshoot unexpected switch reboot, power module failure, and fan tray failure. To troubleshoot transceiver modules and ports, see "Troubleshooting ports." Unexpected switch reboot Symptom The switch reboots unexpectedly when it is operating. Troubleshooting flowchart Figure 1 Troubleshooting unexpected switch reboot Unexpected switch reboot Can you... -
Page 10: Operating Power Module Failure
CRC error has occurred or that no system software image is available, reload the system software image. The system software image is automatically set to the current system software image during the Boot ROM image running process. If the issue persists, contact H3C Support. Operating power module failure Symptom An operating power module fails. -
Page 11: Newly Installed Power Module Failure
Normal state in the new slot. If the power module remains in Fault state, replace the power module. If the issue persists, contact H3C Support. Newly installed power module failure Symptom A newly installed power module fails. -
Page 12: Fan Tray Failure
Normal state in the new slot. If the power module remains in Fault state, go to step 4. If the issue persists, contact H3C Support. Fan tray failure Symptom An operating fan tray or a newly installed fan tray fails. -
Page 13: Related Commands
If a new fan tray is not readily available, power off the switch to avoid damage caused by high temperature. If the issue persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting the hardware. -
Page 14: Troubleshooting Acl
ACL resources insufficiency. If this field displays 0, the ACL hardware resources are exhausted. To free hardware resources, delete unnecessary ACLs. If the issue 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... -
Page 15: Troubleshooting Flowchart
Troubleshooting flowchart Figure 6 Troubleshooting an ACL application failure Failure to apply an ACL QoS policy/packet filter Reconfigure QoS Resolved? configured correctly? policy/packet filter Reconfigure ACL Resolved? configured correctly? Contact the support Solution Choose a solution depending on the module that uses the ACL. ACL used in a QoS policy To resolve the issue when the ACL is used in a QoS policy: Verify that the QoS policy is configured correctly:... -
Page 16: Packet Loss Or Forwarding Failure
If the ACL is configured correctly, go to step 3. If the issue persists, contact H3C Support. ACL used in a packet filter To resolve the issue when the ACL is used in a packet filter: Verify that the packet filter is configured correctly. -
Page 17: Solution
Solution To resolve the issue: Identify the characteristics of the packets that are not forwarded correctly. Use a packet capture tool to identify the characteristics of the traffic, such as the IP address, MAC address, or VLAN. Make sure the characteristics are unique among traffic to be forwarded. -
Page 18: Related Commands
Classifier: count Operator: AND Rule(s) : If-match ACL 3000 Behavior: count Accounting Enable: 251 (Packets) The output shows that a total of 251 packets match ACL 3000. On GigabitEthernet 2/0/1 of Device C: [Sysname-GigabitEthernet2/0/1] display qos policy interface gigabitethernet 2/0/1 Interface:GigabitEthernet2/0/1 Direction: Inbound Direction: Inbound... - Page 19 Command Description display traffic behavior Displays traffic behavior configuration. user-defined...
-
Page 20: Troubleshooting Irf
Troubleshooting IRF This section provides troubleshooting information for common issues with IRF. IRF fabric establishment failure Symptom An IRF fabric cannot be established. -
Page 21: Troubleshooting Flowchart
Troubleshooting flowchart Figure 9 Troubleshooting IRF fabric establishment failure IRF setup failure You cannot add the device to Number of members the IRF fabric or complete IRF fewer than the upper limit? merge Assign a unique member ID to Member ID unique? Resolved? each member device IRF port bindings... - Page 22 a. Execute the display irf command to view the member ID of each member device. b. 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.
-
Page 23: Related Commands
However, the synchronization might fail when the gap between the software versions is too large. For more information, see the release notes. If the issue persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting IRF. -
Page 24: Troubleshooting Ethernet Link Aggregation
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. -
Page 25: Troubleshooting Flowchart
Troubleshooting flowchart Figure 10 Troubleshooting link aggregation failure Link aggregation failure Are all physical connections correct? Connect physical links correctly Resolved? Are all member ports up? Bring all member ports up Resolved? Set operational key/attribute Operational key/attribute configurations same configurations same as the reference Resolved? as the reference port? port... -
Page 26: Related Commands
This makes sure all member ports you assign to the aggregation group can become Selected ports. If the issue persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting Ethernet link aggregation. -
Page 27: Troubleshooting Ports
Troubleshooting ports This section provides troubleshooting information for common port issues. Fiber port remains in down state Symptom A fiber port (SFP+ port or QSFP+ port) remains in down state. Troubleshooting flowchart Figure 11 Troubleshooting fiber port's failure to come up Fiber port remains in down state Speed/duplex match... -
Page 28: Solution
If the transceiver module is not operating correctly, replace it with a H3C transceiver module that matches the fiber port. -
Page 29: Copper Port Remains In Down State
<Sysname> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y Copper port remains in down state Symptom A 10/100/1000Base-T GE copper port remains in down state. Troubleshooting flowchart Figure 12 Troubleshooting copper port's failure to come up Copper port remains in down state Speed/duplex match Configure matching... -
Page 30: Non-H3C Transceiver Module
The S5850-54QS switch does not support the half-duplex mode. If the S5850-54QS switch and its peer operate in half-duplex mode after negotiation, the ports on the S5850-54QS switch will not come up. b. If they do not match, use the speed command and the duplex command to set the rate and duplex mode for the port. -
Page 31: Transceiver Module Does Not Support Digital Diagnosis
Vendor Name : H3C Perform either of the following tasks: 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, execute the display hardware internal ... -
Page 32: Troubleshooting Flowchart
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. -
Page 33: Error Frames (For Example, Crc Errors) On A Port
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 15 Troubleshooting error frames (for example, CRC errors) on a port Error frames on the port Determine the type of error frames accumulating... - Page 34 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 ten-gigabitethernet 1/0/51 Ten-GigabitEthernet1/0/51 transceiver diagnostic information: Current diagnostic parameters: [module] Temp.(°C) 1stTX 2ndTX 1stRX 2ndRX...
-
Page 35: Failure To Receive Packets
If you determine that the configurations, the peer port, and the link are correct but the issue persists, perform the following tasks: a. Use the display diagnostic-information command to collect the diagnostic information. b. Contact H3C Support. <Sysname> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y Failure to receive packets Symptom A port is up, but it cannot receive packets. - Page 36 If you determine that the configurations, the peer port, and the link are correct but the issue persists, perform the following tasks: a. Use the display diagnostic-information command to collect the diagnostic information. b. Contact H3C Support. <Sysname> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y...
-
Page 37: Failure To Send Packets
Failure to send packets Symptom A port is up, but it cannot send packets. Troubleshooting flowchart Figure 17 Troubleshooting the failure to send packets A port fails to send packets View packet statistics of the port Port Modify port configurations affect packet Resolved? configurations sending? -
Page 38: Related Commands
If you determine that the configurations, the peer port, and the link are correct but the issue persists, perform the following tasks: a. Use the display diagnostic-information command to collect the diagnostic information. b. Contact H3C Support. <Sysname> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y Related commands This section lists the commands that you might use for troubleshooting ports. - Page 39 Command Description aggregation groups. Displays the state of the log buffer and the log display logbuffer information in the log buffer. Displays brief spanning tree status and display stp brief statistics. Displays the current transceiver module display transceiver alarm interface alarms.
-
Page 40: Troubleshooting System Management
Troubleshooting system management This section provides troubleshooting information for common system management issues. High CPU utilization Symptom The display cpu-usage command shows that the CPU utilization of the device is continuously higher than 80%. Troubleshooting flowchart Figure 18 Troubleshooting high CPU utilization High CPU utilization Identify the job with a high... - Page 41 0.0% 0.0% 0.0% [migration/1] 0.0% 0.0% 0.0% [ksoftirqd/1] 0.0% 0.0% 0.0% [watchdog/1] 0.0% 0.0% 0.0% [events/0] 0.0% 0.0% 0.0% [events/1] 0.0% 0.0% 0.0% [khelper] 0.0% 0.0% 0.0% [kblockd/0] 0.0% 0.0% 0.0% [kblockd/1] 0.0% 0.0% 0.0% [khubd] 0.0% 0.0% 0.0% [kseriod] 0.0% 0.0% 0.0%...
-
Page 42: High Memory Utilization
[Sysname-probe] Use the display diagnostic-information command to collect diagnostic information. Save the information displayed in the previous steps. Contact H3C Support. High memory utilization Symptom The display memory command shows that the memory utilization of the device is higher than 60% during a period of time (typically 30 minutes). -
Page 43: Related Commands
Save the information displayed in the previous step and contact H3C Support. IMPORTANT: For quick troubleshooting, do not reboot the device before you contact H3C Support. The previous step only identifies the memory portions that have issues. Further information is required to locate the code section that has issues. -
Page 44: Troubleshooting Other Issues
Command Description display memory Displays memory usage statistics. display process cpu Displays the CPU usage statistics for jobs. display system internal kernel memory Displays memory block usage statistics. pool 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... -
Page 45: Troubleshooting Flowchart
Troubleshooting flowchart Figure 20 Troubleshooting Layer 2 packet loss failure Layer 2 packet loss Troubleshoot the Incoming error packets? Resolved? problem Packets filtered by Troubleshoot the Resolved? ACLs or QoS policies? problem Troubleshoot the Resolved? Port blocked? problem Locate and modify Port misconfigurations? Resolved? misconfigurations... - Page 46 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. b. If the issue persists, contact H3C Support.
- Page 47 When you contact H3C Support, provide the following diagnostic information if packet loss occurs on the chip port with which the interface is associated: # In probe view, execute the debug port mapping command to identify the chip port with which the interface is associated.
- Page 48 R64.ge17 R127.ge17 RPKT.ge17 RMCA.ge17 RBCA.ge17 RPOK.ge17 RBYT.ge17 21,974 +582 261/s 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.
-
Page 49: Related Commands
If congestion occurs, locate and resolve the issue by referencing related congestion management documents. If the issue persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting Layer 2 packet loss failure. -
Page 50: Layer 3 Forwarding Failure
Command Description Displays user-defined QoS policy configuration display qos policy information. display qos policy global Displays information about global QoS policies. Displays information about the QoS policies display qos policy interface applied to an interface or all interfaces. Displays traffic statistics collected for an interface display qos queue-statistics interface on a per-queue basis. -
Page 51: Solution
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. If the issue persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting Layer 3 forwarding failure. -
Page 52: Troubleshooting Flowchart
Troubleshooting flowchart Figure 22 Troubleshooting protocol flapping Layer 3 protocol flapping Troubleshoot the Layer 2 packet loss occurs? Resolved? problem Troubleshoot the Layer 3 packet loss occurs? Resolved? problem Software-related Collect diagnostic packet loss occurs? information Contact the support Solution To resolve the issue: Verify that Layer 2 is operating correctly, as described in "Layer 2 forwarding... -
Page 53: Fan Tray Failure
SMAC 8 IPV4_IGMP SMAC 8 SMAC 8 If the issue persists, contact H3C Support. When you contact H3C Support, provide diagnostic information if software-related packet loss occurred. Fan tray failure Symptom A fan tray does not operate correctly. Troubleshooting flowchart... - Page 54 If the fan tray still cannot operate correctly, check whether the fan tray is damaged. If the fan tray status is fault, replace the fan tray. If the issue persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting fans.
Need help?
Do you have a question about the S5850-54QS and is the answer not in the manual?
Questions and answers