H3C S6890 Series Troubleshooting Manual
H3C S6890 Series Troubleshooting Manual

H3C S6890 Series Troubleshooting Manual

Hide thumbs Also See for S6890 Series:
Table of Contents

Advertisement

Quick Links

H3C S6890 Switch Series
Troubleshooting Guide
Document version: 6W100-20190725
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

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for H3C S6890 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

    100-GE QSFP28 fiber port fails to come up ····················································································· 23 Symptom ··························································································································· 23 Troubleshooting flowchart ····································································································· 24 Solution ····························································································································· 24 Non-H3C transceiver module error message ··················································································· 25 Symptom ··························································································································· 25 Troubleshooting flowchart ····································································································· 25 Solution ····························································································································· 25 Transceiver module does not support digital diagnosis ······································································ 26 Symptom ···························································································································...
  • Page 3 Solution ····························································································································· 27 Error frames (for example, CRC errors) on a port ············································································· 27 Symptom ··························································································································· 27 Troubleshooting flowchart ····································································································· 28 Solution ····························································································································· 28 Failure to receive packets ············································································································ 29 Symptom ··························································································································· 29 Troubleshooting flowchart ····································································································· 30 Solution ····························································································································· 30 Failure to send packets ···············································································································...
  • Page 4: Introduction

    Introduction This document provides information about troubleshooting common software and hardware issues with S6890 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

    Category File name format Content following items: • Parameter settings in effect when an error occurs. • Information about a device startup error. • Handshaking information between member devices when a communication error occurs. Current operating statistics for feature modules, including the following items: •...
  • Page 6: Collecting Operating Statistics

    0 -rw- 161321 Jul 11 2013 16:16:00 diagfile.log 1048576 KB total (38812 KB free) # Display the log file on each subordinate device: <Sysname> dir slot2#flash:/diagfile/ Directory of flash:/diagfile 0 -rw- 161321 Jul 11 2013 16:16:00 diagfile.log 1048576 KB total (38812 KB free) Transfer the files to the desired destination by using FTP, TFTP, or USB.
  • Page 7: Contacting Technical Support

    …… 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 8 Question Command or method Result Remarks • The power modules operating correctly. display power command shows that their state is Normal. The LED shows the status of the device: • Steady green—The switch operating correctly. □OK • Steady red—The Are the LEDs all displaying Visually check the status of □Not OK switch has failed to...
  • Page 9 • Port setting inconsistencies with the peer port. Fiber ports When you connect an H3C □OK device to a device from Do the ports at the two display another vendor, set the □Not OK current-configuration ends use the same port...
  • Page 10 Question Command or method Result Remarks configured as edge ports? interface display □Not OK current-configuratio □Not related n interface command contains "stp edged-port enable" string ports connected end-user devices. best practice, configure ports connected to end-user devices (PCs, for example) as edge ports, or disable the spanning tree feature on the ports.
  • Page 11 Question Command or method Result Remarks enable BPDU guard. Alternatively, disable the spanning tree feature on the ports. • Disable the spanning tree feature on ports connected to devices that do not support spanning tree protocols. • disable TC-BPDU guard. VRRP Change handshake...
  • Page 12 Question Command or method Result Remarks analyze the cause. You display command ospf lsdb multiple times to view the age of routes and locate the flapping route. □OK View the up time of the □Not OK Is the OSPF status stable? display ospf peer OSPF neighbor.
  • Page 13: Troubleshooting Hardware

    Question Command or method Result Remarks • mode: local logbuffer chassis chassis-number slot slot-number clear Troubleshooting hardware This section provides troubleshooting information for common hardware issues. NOTE: This section describes how to troubleshoot switch reboot failure, power module failure, and fan tray failure.
  • Page 14: Operating Power Module Failure

    Verify that no error is reported during the BootWare loading process. If the memory is running correctly but there are still errors reported during the BootWare loading process, replace the switch. If the issue persists, contact H3C Support. Operating power module failure Symptom An operating power module fails.
  • Page 15: 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 16: 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 17 You must make sure the switching 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. If the issue persists, contact H3C Support.
  • Page 18: Related Commands

    Related commands This section lists the commands that you might use for troubleshooting the hardware. Command Description display alarm Displays alarm information. display environment Displays temperature information. display fan Displays the operating states of the fan tray. display power Displays power module information. Troubleshooting system management This section provides troubleshooting information for common system management issues.
  • Page 19 CPU utilization in 5 secs: 6.0%; 1 min: 5.6%; 5 mins: 5.7% 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%...
  • Page 20: High Memory Utilization

    [<ffffffff8021d910>] kernel_thread_helper+0x10/0x20 Save the information displayed in the previous steps and use the display diagnostic-information command to collect diagnostic information. Contact H3C Support. High memory utilization Symptom The display memory command shows that the memory utilization of the device is higher than 60%...
  • Page 21: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 3 Troubleshooting high memory utilization High memory utilization Display memory usage information Display memory call information Contact the support Solution To resolve the issue: Execute the display system internal kernel memory pool command multiple times to display kernel memory pool usage information. Identify the memory pool that shows a suspicious utilization increase.
  • Page 22 The first field in the output shows the number of allocated memory blocks. The remaining fields show the call information. Save the information displayed in the previous steps. Contact H3C Support. IMPORTANT: As a best practice to retain critical diagnostic information, do not reboot the device before you...
  • Page 23: Temperature Alarms

    Temperature alarms Symptom Temperature alarms occur. Troubleshooting flowchart Figure 4 Troubleshooting temperature alarms Temperature alarm Ambient Lower the temperature Resolved? temperature too high? Device Resolve fan temperature Resolved? issues too high? Air filters clean? Clean air filters Resolved? Temperature Replace the alarm threshold device adjusted?
  • Page 24: Related Commands

    Replace the device. If the thresholds are adjusted but the issue persists, collect diagnostic information and contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting system management.
  • Page 25: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 5 Troubleshooting link up failure on a port 10-Gigabit SFP+Fiber port fails to come up Speed/duplex match on Configuring matching Resolved? local and peer port? speed/duplex Speed/duplex match on Configure matching Resolved? transceiver module and port? speed/duplex Local/peer port operating Replace local/peer port Resolved?
  • Page 26: 100-Ge Qsfp28 Fiber Port Fails To Come Up

    If the transceiver module or cable is not operating correctly, replace it with a new H3C transceiver module or cable that matches the fiber port.
  • Page 27: Troubleshooting Flowchart

    If the transceiver module is not operating correctly, replace it with a new H3C transceiver module that matches the fiber port. For more information about transceiver modules, see the installation guide for the switch.
  • Page 28: Non-H3C Transceiver Module Error Message

    Identify whether 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 29: Transceiver Module Does Not Support Digital Diagnosis

    0x50: 0x60: 0x70: b. 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 issue persists, contact H3C Support. Transceiver module does not support digital...
  • Page 30: Solution

    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 31: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 9 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 32: 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, collect diagnostic information and contact H3C Support. To collect diagnostic information, execute the display diagnostic-information command to display or save running status data for multiple feature modules.
  • Page 33: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 10 Troubleshooting failure to receive packets A port failed to receive packets View packet statistics of the port Port Modify port configurations affect packet Resolved? configurations receiving? Port and link Use correct port and Resolved? medium correct? link medium Contact the support Solution...
  • Page 34: Failure To Send Packets

    Plug the link medium into a new port that is operating correctly. If the new port cannot receive packets, replace the link medium. If the issue persists, collect diagnostic information and contact H3C Support. To collect diagnostic information, execute the display diagnostic-information command to display or save running status data for multiple feature modules.
  • Page 35: Solution

    Plug the link medium into a new port that is operating correctly. If the new port cannot send packets, replace the link medium. If the issue persists, collect diagnostic information and contact H3C Support. To collect diagnostic information, execute the display diagnostic-information command to display or save running status data for multiple feature modules.
  • Page 36: Troubleshooting Flowchart

    See the installation guide for the device to identify whether the transceiver module is supported. If the transceiver module is not supported, replace it with an H3C transceiver module supported by the device.
  • Page 37: A Port Fails To Come Up

    Read the Tx and Rx optical powers of the port multiple times. If a problem exists, troubleshoot the link. b. Execute the following command multiple times. If a problem occurs, contact H3C Support. ====debug port optical-module chassis 1 slot 0====...
  • Page 38: A Port Flaps

    =============================================================== XGE1/0/1 normal normal Execute commands in the following table to collect information and contact H3C Support. Command Description display transceiver diagnosis Displays the current values of the digital diagnosis interface parameters on transceiver modules. Displays the key parameters of transceiver display transceiver interface modules.
  • Page 39: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 14 Troubleshooting port flapping A port flaps Remove link, interface module, and port problems Known problem? Problem of local end? Resolve according to the Assist in joint known solution troubleshooting Collect information and Resolved? contact the support Solution Perform a basic replacement test to remove link, interface module, and port problems.
  • Page 40: Crc Error Packets On A Port

    Slot:2/0 link down reason. [0]: CallLine=1314 Time=03/23/2016 14:03:55:610 linkinfo=0xfd down. pma. pcs. xgs. fault. localfault [9]: CallLine=1314 Time=03/23/2016 05:05:14:565 linkinfo=0xbd down. pma. pcs. xgs. fault. rmtfault Execute commands in the following table to collect information and contact H3C Support. Command Description display transceiver...
  • Page 41: Troubleshooting Flowchart

    The three symptoms are sometimes related, and it is hard to locate the root cause. When one of the problems occurs, as a best practice, troubleshoot the three problems together. Execute commands in the following table to collect information and contact H3C Support.
  • Page 42: Related Commands

    Command Description display transceiver diagnosis Displays the current values of the digital diagnosis interface parameters on transceiver modules. display transceiver interface Displays the key parameters of transceiver modules. display transceiver manuinfo Displays electronic label information for transceiver interface modules. display transceiver information Displays transmission information for transceiver...
  • Page 43: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 16 Troubleshooting IRF fabric setup failure IRF setup failure Number of member devices You cannot add a new fewer than the upper limit? member to the fabric Replace with a device that is the same model as Same device model? Resolved? existing IRF member...
  • Page 44 Verify that the device is the same model as the member devices in the IRF fabric. The H3C S6890 switches must be the same model to form an IRF fabric. Verify that the member ID of the device is unique in the IRF fabric: a.
  • Page 45: Irf Split

    If the device has the same bridge MAC address as the IRF fabric, remove the bridge MAC conflict. If the issue persists, execute the display diagnostic-information command and collect the device diagnostic information, and then send the information to contact H3C Support. IRF split Symptom An IRF fabric splits.
  • Page 46: Solution

    If the issue persists, execute the display diagnostic-information command and collect the device diagnostic information, and then send the information to H3C Support. BFD MAD failure Symptom BFD MAD fails to detect an IRF split event. Two IRF fabrics are operating with the same Layer 3...
  • Page 47: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 18 Troubleshooting BFD MAD failure BFD MAD failure Correct the connections Resolved? BFD MAD link connections correct? All BFD MAD ports up? Bring up the ports Resolved? BFD MAD VLAN Correct the settings Resolved? and Layer 3 interface configured correctly? BFD MAD IP addresses Correct the settings...
  • Page 48 Verify that the Layer 3 interface used for BFD MAD and the BFD MAD VLAN (if any) are configured correctly: a. Execute the display mad verbose command. b. Check the MAD BFD enabled interface field to identify the Layer 3 interface used for BFD MAD.
  • Page 49 Identify the cause of the events, and remove the issue. If the issue persists, execute the display diagnostic-information command and collect the device diagnostic information, and then send the information to H3C Support.
  • Page 50: Lacp Mad Failure

    LACP MAD failure Symptom LACP MAD fails to detect an IRF split event. Two IRF fabrics are operating with the same Layer 3 configurations, including the same IP address. Troubleshooting flowchart Figure 19 Troubleshooting LACP MAD failure LACP MAD failure Intermediate device Replace the device or use Resolved?
  • Page 51: Related Commands

    Identify the event cause and remove the issue. If the issue persists, execute the display diagnostic-information command and collect the device diagnostic information, and then send the information to H3C Support. Related commands This section lists the commands that you might use for troubleshooting IRF:...
  • Page 52: Troubleshooting Qos And Acl

    Command Description display irf configuration Displays the IRF configuration on each member device. display irf topology Displays the IRF topology. display mad verbose Displays detailed MAD configuration. Displays the present measured values of the digital diagnosis display transceiver diagnosis parameters for transceiver modules. display logbuffer Displays log data in the log buffer.
  • Page 53: Troubleshooting Flowchart

    Identify the unsupported criterion according to the new error message. If the rule contains only one criterion, the criterion is not supported. If the issue persists, contact H3C Support. To resolve the issue in the case of insufficient hardware resources: Check the ACL, Counter, and Meter resource usage for insufficiency.
  • Page 54: Acl Application Failure Without An Error Message

    4. Apply the packet filter or QoS policy again. If the issue persists, collect diagnostic information by using the following command and contact H3C Support. <Sysname> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y ACL application failure without an error message Symptom The system applies a packet filter or an ACL-based QoS policy to the hardware.
  • Page 55: Related Commands

    Revise ACLs, packet filters, or QoS policies to remove the behavior conflict. If the issue persists, collect diagnostic information by using the following command and 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 QoS and ACLs.

Table of Contents