H3C S6800 Series Troubleshooting Manual
  1. Manuals
  2. Brands
  3. H3C Manuals
  4. Switch
  5. S6800 Series
  6. Troubleshooting manual
H3C S6800 Series Troubleshooting Manual

H3C S6800 Series Troubleshooting Manual

Hide thumbs Also See for S6800 Series:
Table of Contents

Advertisement

Quick Links

Download this manual
H3C S6800 Switch Series Troubleshooting
Guide
Document version: 6W100-20171220
Copyright © 2017 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.
The information in this document is subject to change without notice.

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the S6800 Series and is the answer not in the manual?

Questions and answers

Related Manuals for H3C S6800 Series

Summary of Contents for H3C S6800 Series

  • Page 1 Copyright © 2017 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. The information in this document is subject to change without notice.

  • 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 ························································································· 2   Collecting operating statistics ································································································· 3   Contacting technical support ········································································································ 4 Troubleshooting hardware ··································································...
  • Page 3   Symptom ························································································································· 22   Troubleshooting flowchart ··································································································· 22   Solution ··························································································································· 22   Non-H3C transceiver module error message ················································································· 23   Symptom ························································································································· 23   Troubleshooting flowchart ··································································································· 23   Solution ··························································································································· 23   Transceiver module does not support digital diagnosis ····································································· 24  ...
  • Page 4   Symptom ························································································································· 45   Troubleshooting flowchart ··································································································· 46   Solution ··························································································································· 46   Related commands ············································································································ 47   Protocol flapping ······················································································································ 47   Symptom ························································································································· 47   Troubleshooting flowchart ··································································································· 47   Solution ··························································································································· 47...

  • Page 5: Introduction

    Introduction This document provides information about troubleshooting common software and hardware problems with the S6800 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.

  • Page 6: Collecting Common Log Messages

    Table 1 Log and operating information Category File name format Content Common log logfile.log Command execution and operational log messages. Diagnostic log messages about device operation, including the following items: • Parameter settings in effect when an error occurs. Diagnostic log diagfile.log •...

  • Page 7: Collecting Operating Statistics

    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: # 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...

  • Page 8: Contacting Technical Support

    ---- More ---- Contacting technical support If you cannot resolve a problem 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: Troubleshooting Hardware

    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...

  • Page 10: Collecting Diagnostic Log Messages

    Use the BootWare menu to reload the system software image. b. Configure it as the current system software image. 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.

  • Page 11: Solution

    Normal state in the new slot. If the power module remains in Fault state, replace the power module. 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.

  • Page 12: Troubleshooting Flowchart

    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. If the problem persists, contact H3C Support.

  • Page 13: Fan Tray Failure

    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. Troubleshooting flowchart Figure 4 Troubleshooting fan tray failure Solution To resolve the problem: Execute the display fan command to display the operating states of the fan tray.

  • Page 14: Related Commands

    If a new fan tray is not readily available, power off the switch to avoid damage caused by high temperature. If the problem persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting the hardware.

  • Page 15: Troubleshooting Acl

    If this field displays 0, the ACL hardware resources are exhausted. To free hardware resources, delete unnecessary ACLs. 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...

  • Page 16: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 5 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: Verify that the QoS policy is configured correctly: a.

  • Page 17: Related Commands

    If the ACL is configured incorrectly, reconfigure it. If the ACL is configured correctly, go to step 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: Verify that the packet filter is configured correctly.
  • Page 18 Command Description display qos [ accounting | remarking ] policy diagnosis interface (The accounting and Displays diagnostic information about the QoS policies remarking keywords are available in Release applied to interfaces. 26xx.) display qos policy user-defined Displays user-defined QoS policies. Displays information about QoS policies applied to display qos vlan-policy VLANs.

  • Page 19: Troubleshooting Irf

    Troubleshooting IRF This section provides troubleshooting information for common problems with IRF. IRF fabric setup failure Symptom An IRF fabric cannot be set up.

  • Page 20: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 6 Troubleshooting IRF fabric setup failure IRF setup failure You cannot add devices Does the number to the IRF fabric or of members exceed the upper complete IRF merge limit? Replace with devices Can member that can join the same Resolved? devices join the same IRF IRF fabric...

  • Page 21: Solution

    Solution To resolve the problem: Verify that the number of member devices does not exceed the upper limit. When 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 22 Verify that the physical IRF links meet the rate requirements: a. Verify that the correct transceiver modules or cables are used: − Use Category 6A (or above) twisted-pair cables to connect 10GBase-T Ethernet ports in a short distance. − Use SFP+ DAC cables to connect SFP+ ports in a short distance. −...

  • Page 23: Related Commands

    The mode is set by using the hardware-resource vxlan command. This command is available in Release 25xx and Release 26xx. If the problem persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting IRF.
  • Page 24 Command Description display Displays system operating mode information. system-working-mode display version Displays system version information.

  • Page 25: Troubleshooting Ethernet Link Aggregation

    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.

  • Page 26: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 7 Troubleshooting link aggregation failure Solution To resolve the problem: Verify that all physical connections are correct. You can verify the physical connections against your network plan. Verify that all member ports are up: a. Execute the display interface command to display the status of the member ports.

  • Page 27: Related Commands

    This makes sure all member ports you assign to the aggregation group can become Selected ports. If the problem persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting Ethernet link aggregation.

  • Page 28: Troubleshooting Ports

    Troubleshooting ports This section provides troubleshooting information for common port problems. A 10-GE SFP+, 40-GE QSFP+, or 100-GE QSFP28 fiber port fails to come up Symptom A 10-GE SFP+, 40-GE QSFP+, or 100-GE QSFP28 fiber port fails to come up. Troubleshooting flowchart Figure 8 Troubleshooting link up failure on a copper port A port failed to come up...
  • Page 29 If the transceiver module is not operating correctly, replace it with a 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 10/100/1000Base-T Ge Copper Port Or 1/10Gbase-T 10-Ge Copper Port Fails To Come Up

    Replace the local port with a new one to verify that the local port is operating correctly. Replace the peer port with a new one to verify that the peer port is operating correctly. If the problem persists, contact H3C Support.

  • Page 31: Non-H3C Transceiver Module Error Message

    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 FortyGigE1/0/5: This transceiver is NOT sold by H3C. H3C therefore shall NOT guarantee...

  • Page 32: Transceiver Module Does Not Support Digital Diagnosis

    − 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. If the problem persists, contact H3C Support. Transceiver module does not support digital...

  • Page 33: Error Frames (For Example, Crc Errors) On A Port

    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 fortygige 1/0/1 FortyGigE 1/0/1 transceiver information: Transceiver Type : 40G_BASE_LR4_QSFP_PLUS...

  • Page 34: Solution

    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 problem persists, contact H3C Support.

  • Page 35: Failure To Receive Packets

    Failure to receive packets Symptom A port is up, but it cannot receive packets. Troubleshooting flowchart Figure 13 Troubleshooting failure to receive packets Solution To resolve the problem: Verify that the ports at both ends are up. Examine the packet statistics of the port: a.

  • Page 36: Failure To Send Packets

    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. If the problem persists, contact H3C Support. Failure to send packets Symptom...

  • Page 37: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 14 Troubleshooting failure to send packets A port failed to send 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 38: Related Commands

    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 problem persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting ports.

  • Page 39: Troubleshooting Evpn

    Troubleshooting EVPN This section provides troubleshooting information for common problems with EVPN. EVPN is supported only in Release 25XX and Release 26xx. EBGP or IBGP neighbor relationship setup failure Symptom Two devices cannot set up an EBGP or IBGP neighbor relationship. Troubleshooting flowchart Figure 15 Troubleshooting EBGP or IBGP neighbor relationship setup failure BGP neighbor...

  • Page 40: Ecmp Forwarding Failure

    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 H3C Support. Perform the following tasks to collect information and contact H3C Support: a.

  • Page 41: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 16 Troubleshooting ECMP forwarding failure Solution To resolve the problem: Verify that the device has routes to the destination network: a. Execute the display bgp l2vpn evpn route-distinguisher route-type ip-prefix command. b. Verify that the device has routes to the destination network. The routes must have the same RD and different next hops.

  • Page 42: Vxlan Tunnel Establishment Failure

    BGP-VPN IPv4 unicast address family view. c. If the balance command is not executed, use it to set the number of BGP ECMP routes to a value larger than 1. If the problem persists, contact H3C Support. VXLAN tunnel establishment failure Symptom In an EVPN network, two devices can establish a BGP neighbor relationship but cannot automatically set up a VXLAN tunnel between them.

  • Page 43: Troubleshooting Flowchart

    If a manual VXLAN tunnel has been established between the IP addresses used for automatic tunnel establishment, modify the tunnel settings to ensure that automatic and manual VXLAN tunnels do not share an IP address pair. If the problem persists, contact H3C Support. VXLAN tunnel forwarding failure Symptom...

  • Page 44: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 18 Troubleshooting VXLAN tunnel forwarding failure Solution To resolve the problem: Verify that the VXLAN hardware resource mode is correct: NOTE: The VXLAN hardware resource mode is not supported by switches with the following product codes: • LS-6800-2C.

  • Page 45: Related Commands

    MAC address and IP address as the VSI interfaces of the same VXLAN on the other distributed EVPN gateways. If the problem persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting EVPN.

  • Page 46: Troubleshooting System Management

    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 19 Troubleshooting high CPU utilization High CPU utilization Identify the job that has a high CPU utilization Display the job’s stack Save diagnostic information...
  • Page 47 0.0% 0.0% 0.0% [watchdog/1] 0.0% 0.0% 0.0% [migration/2] 0.0% 0.0% 0.0% [ksoftirqd/2] 0.0% 0.0% 0.0% [watchdog/2] 0.0% 0.0% 0.0% [migration/3] 0.0% 0.0% 0.0% [ksoftirqd/3] 0.0% 0.0% 0.0% [watchdog/3] 0.0% 0.0% 0.0% [migration/4] 0.0% 0.0% 0.0% [ksoftirqd/4] 0.0% 0.0% 0.0% [watchdog/4] 0.0% 0.0% 0.0%...

  • Page 48: High Memory Utilization

    [<8028f720>] watchdog+0xb0/0x410 [<802656d0>] kthread+0x130/0x140 [<8021d730>] kernel_thread_helper+0x10/0x20 Save the information displayed in the previous steps. Contact H3C Support. High memory utilization Symptom The memory utilization is over 75% for more than 30 minutes on the following models with 2 GB of memory: •...

  • Page 49: Related Commands

    Save the information displayed in the previous step. Contact H3C Support. IMPORTANT: As a best practice, do not reboot the device before you contact H3C 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.

  • Page 50: Troubleshooting Other Problems

    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 21 Troubleshooting Layer 2 packet loss failure Solution To resolve the problem:...
  • Page 51 If they are inconsistent, modify the configurations of the local port. c. If the problem persists, contact H3C Support. Verify that packets are not mistakenly filtered out by ACLs: a.
  • Page 52 − 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.

  • Page 53: Related Commands

    If congestion occurs, locate and resolve the problem by referencing related congestion management documents. If the problem persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting Layer 2 packet loss failure. Command...

  • Page 54: Troubleshooting Flowchart

    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 different, execute the reset command to clear the route entries. Then the switch can learn route entries again. If the problem persists, contact H3C Support.

  • Page 55: Related Commands

    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. display arp Displays ARP entries. display ip routing-table Displays routing table information. display mac-address Display MAC address entries display fib Display FIB entries...
  • Page 56 CLNP SMAC 8 VRRP 1024 S SMAC 8 UNKNOWN_IPV4MC SMAC 8 UNKNOWN_IPV6MC SMAC 8 IPV4_MC_RIP SMAC 8 IPV4_BC_RIP SMAC 8 If the problem persists, contact H3C Support. When you contact H3C Support, provide diagnostic information if software-related packet loss occurred.

Table of Contents