H3C S6805 Series Troubleshooting Manual
Hide thumbs
Also See for S6805 Series:
- Installation manual (61 pages) ,
- Hardware information (22 pages)
Table of Contents
Advertisement
Quick Links
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
Advertisement
Table of Contents
Troubleshooting
Related Manuals for H3C S6805 Series
Summary of Contents for H3C S6805 Series
- 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 Troubleshooting hardware ············································································· 4 Unexpected switch reboot ·································································································································· 4 Symptom ····················································································································································... - Page 3 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 ····················································································································································...
-
Page 4: Introduction
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: To prevent an issue from causing loss of configuration, save the configuration each time you finish configuring a feature. -
Page 5: Collecting Common Log Messages
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 Command execution, events, and status... -
Page 6: Collecting Diagnostic Log Messages
Collecting diagnostic log messages 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 Identify the diagnostic log file on each member device:... -
Page 7: Troubleshooting Hardware
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 ===============================================... -
Page 8: Troubleshooting Flowchart
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. If the issue persists, contact H3C Support. -
Page 9: Operating Power Module Failure
A trap or log is generated indicating that an operating power module is faulty. Solution To resolve the issue: 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... -
Page 10: Newly Installed Power Module Failure
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: Execute the display power command to display power module information. -
Page 11: Fan Tray Failure
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: Execute the display fan command to display the operating states of the fan tray. -
Page 12: Related Commands
Related commands This section lists the commands that you might use for troubleshooting the hardware. Command Description Displays information about files and directories. Displays current configuration files and system software display boot-loader images. display environment Displays temperature information. display fan Displays the operating states of the fan tray. -
Page 13: Troubleshooting Acl
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 ACL application failure Insufficient hardware... -
Page 14: Applied Acls Fail To Take Effect
Delete unnecessary ACLs to release resources. If the resources are sufficient, the ACLs might conflict with an ASIC chip algorithm. Contact H3C Support to resolve the issue. If the issue persists, contact H3C Support. Applied ACLs fail to take effect Symptom... -
Page 15: Troubleshooting Flowchart
Troubleshooting flowchart Figure 3 Troubleshooting ACL failure to take effect ACLs fail to take effect ACL rules defined Revise ACL Resolved correctly? rules ACL rules overlap? Actions of overlapping Remove the Resolved ACL rules conflict? conflicts Contact the support Solution Verify that the ACL rules are defined correctly. - Page 16 ACL number 3009 rule 0 permit ip source 2.2.2.2 0.0.0.255 Remove the action conflict between overlapping rules. If two ACLs has overlapping rules, only actions in the ACL with higher priority take effect. Collect related information and contact H3C Support.
-
Page 17: Troubleshooting Irf
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. -
Page 18: Troubleshooting Flowchart
Troubleshooting flowchart Figure 4 Troubleshooting IRF fabric setup failure IRF setup failure You cannot add additional devices to the Number of members fewer IRF fabric or complete than the upper limit? IRF merge Assign a unique member Member ID unique? ID to each member Resolved? device... -
Page 19: Solution
Solution To resolve the issue: 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. -
Page 20: Related Commands
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). If the issue persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting IRF. - Page 21 Command Description Displays IRF fabric information, including the member ID, role, priority, display irf bridge MAC address, and description of each IRF member. Displays basic IRF settings, including the current member ID, new display irf configuration member ID, and physical interfaces bound to the IRF ports on each IRF member device.
-
Page 22: 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 23: Troubleshooting Flowchart
Troubleshooting flowchart Figure 5 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 24: Related Commands
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. -
Page 25: Troubleshooting Ports
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 A fiber port fails to come up... -
Page 26: Solution
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. -
Page 27: A 25-Ge Sfp28 Fiber Port Fails To Come Up
For more information about fibers, see the installation guide for the switch. 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... -
Page 28: Solution
Solution To resolve the issue: 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. - Page 29 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.
-
Page 30: A 1/10Gbase-T 10-Ge Copper Port Fails To Come Up
A 1/10GBase-T 10-GE copper port fails to come 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 A port failed to come up Speed/duplex match Configure matching Resolved? on local and peer port? speed/duplex... -
Page 31: Non-H3C Transceiver Module Error Message
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... -
Page 32: Transceiver Module Does Not Support Digital Diagnosis
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. -
Page 33: Error Frames (For Example, Crc Errors) On A Port
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. -
Page 34: Troubleshooting Flowchart
Troubleshooting flowchart Figure 11 Troubleshooting error frames (for example, CRC errors) on a port Error frames on the port Determine the type of error frames accumulating Optical power Replace it with a transceiver of transceiver module with correct optical Resolved? module correct? power Speed and... -
Page 35: Failure To Receive Packets
Verify that the incoming traffic and outgoing traffic have not exceeded the maximum traffic processing capability of the local device and the peer device. If the issue persists, contact H3C Support. Failure to receive packets Symptom... -
Page 36: Troubleshooting Flowchart
Troubleshooting flowchart Figure 12 Troubleshooting failure to receive packets A port failed to receive packets Display packet statistics for the port Port configuration Modify port Problem resolved? affects packet receiving? configuration Port and link Use the correct port Problem resolved? medium correct? and link medium Contact the support... -
Page 37: Failure To Send Packets
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. If the issue persists, contact H3C Support. Failure to send packets Symptom A port is up, but it cannot send packets. -
Page 38: Solution
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. If the issue persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting ports. - Page 39 Command Description multiple feature modules. display interface Displays Ethernet interface information. display interface brief Displays brief interface information. Displays the summary information for all display link-aggregation summary aggregation groups. Displays the state of the log buffer and the log display logbuffer information in the log buffer.
-
Page 40: Troubleshooting Evpn
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 BGP neighbor relationship setup failure Problem... -
Page 41: Ecmp Forwarding Failure
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. -
Page 42: Troubleshooting Flowchart
Troubleshooting flowchart Figure 15 Troubleshooting ECMP forwarding failure ECMP forwarding failure Only one route to the destination No ECMP routes exist network? Configure the same Route community attributes and attributes for the Problem resolved? extended community attributes routes not match? Do routes carry the default- Delete the default- Problem resolved? -
Page 43: Related Commands
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. -
Page 44: Troubleshooting System Management
Command Description 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%. - Page 45 5Sec 1Min 5Min Name 0.0% 0.0% 0.0% scmd 0.0% 0.0% 0.0% [kthreadd] 0.0% 0.0% 0.0% [migration/0] 0.0% 0.0% 0.0% [ksoftirqd/0] 0.0% 0.0% 0.0% [watchdog/0] 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% [migration/2] 0.0% 0.0% 0.0%...
-
Page 46: High Memory Utilization
[<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 Save the information displayed in the previous steps. Contact Hewlett Packard Enterprise Support. -
Page 47: Related Commands
<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 3072 sgpool-128 LFIB_IlmEntryCache MFW_FsCache biovec-64 cfq_io_context ARP_Static_Entry_Cachep LFIB_IlmEntryCache LFIB_NhlfeCacheCache jffs2_i pktpcb shmem_inode_cache kmalloc-256 1936 MFW_FsCache 4096 names_cache 1104 MFW_FsCache ripcb L2VFIB_Ac_Ctr_Cache... -
Page 48: Troubleshooting Other Issues
Command Description 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 Layer 2 packet loss... -
Page 49: Solution
Solution To resolve the issue: 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 ……... - Page 50 WGE1/0/2 down WGE1/0/3 down WGE1/0/4 down WGE1/0/5 down( shut) WGE1/0/6 down WGE1/0/7 down WGE1/0/8 down WGE1/0/9 xe11 down WGE1/0/10 xe12 down WGE1/0/11 down WGE1/0/12 xe10 down WGE1/0/13 xe15 down WGE1/0/14 xe16 down WGE1/0/15 xe13 down WGE1/0/16 xe14 0x10 down WGE1/0/17 xe19 0x11 down...
- Page 51 HGE1/0/26 0x1e down HGE1/0/27 0x23 down HGE1/0/28 0x28 down HGE1/0/29 0x2d down HGE1/0/30 0x32 down HGE1/0/31 0x37 down HGE1/0/32 0x3c down WGE1/0/33 xe27 0x41 down WGE1/0/34 xe28 0x42 down WGE1/0/35 xe25 0x43 down WGE1/0/36 xe26 0x44 down WGE1/0/37 xe32 0x45 down WGE1/0/38 xe33...
- Page 52 WGE1/0/50 xe45 0x52 down WGE1/0/51 xe42 0x53 down WGE1/0/52 xe43 0x54 down WGE1/0/53 xe48 0x55 down WGE1/0/54 xe49 0x56 down WGE1/0/55 xe46 0x57 down WGE1/0/56 xe47 0x58 down GE1/0/57 0x59 down GE1/0/58 0x5a down M-GE0/0/0 0x5a M-GE0/0/1 0x5a down 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.
- Page 53 − 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. −...
-
Page 54: Related Commands
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. 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... -
Page 55: Troubleshooting Flowchart
Troubleshooting flowchart Figure 19 Troubleshooting Layer 3 forwarding failure Packet loss at Layer 3 Troubleshoot the The port is faulty? Resolved? port Troubleshoot ARP ARP or ND entries Resolved? are correct? or ND entries Troubleshoot route Route entries are correct? Resolved? entries Contact the support... -
Page 56: Related Commands
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. 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. -
Page 57: Troubleshooting Flowchart
Troubleshooting flowchart Figure 20 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 58 When you contact Hewlett Packard Enterprise Support, provide diagnostic information if software-related packet loss occurred.