H3C S6300 Series Troubleshooting Manual
H3C S6300 Series Troubleshooting Manual

H3C S6300 Series Troubleshooting Manual

Hide thumbs Also See for S6300 Series:

Advertisement

Quick Links

H3C S6300 Switch Series
Troubleshooting Guide
Copyright © 2021 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 S6300 Series and is the answer not in the manual?

Questions and answers

Summary of Contents for H3C S6300 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 Troubleshooting hardware ············································································· 1 Unexpected switch reboot ·································································································································· 1 Symptom ···················································································································································· 1 Troubleshooting flowchart ·························································································································· 2 Solution ······················································································································································ 2 Operating power supply failure ·························································································································· 3 Symptom ···················································································································································· 3 Solution ······················································································································································ 3 Newly-installed power supply failure ·················································································································· 3 Symptom ····················································································································································...
  • Page 3 Solution ···················································································································································· 21 Related commands ·································································································································· 24 Layer 3 forwarding failure································································································································· 24 Symptom ·················································································································································· 24 Troubleshooting flowchart ························································································································ 25 Solution ···················································································································································· 25 Related commands ·································································································································· 26 Protocol flapping ·············································································································································· 26 Symptom ·················································································································································· 26 Troubleshooting flowchart ························································································································ 26 Solution ···················································································································································· 26 Fan failure ························································································································································...
  • Page 4: Introduction

    Introduction Troubleshooting hardware This section provides troubleshooting information for common hardware issues. NOTE: This section describes how to troubleshoot unexpected switch reboot, power supply failure, and fan tray failure. To troubleshoot ports, see "Troubleshooting ports." Unexpected switch reboot Symptom The switch reboots unexpectedly when it is operating.
  • Page 5: Troubleshooting Flowchart

    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.
  • Page 6: Operating Power Supply Failure

    Normal state in the new slot. If the power supply remains in Fault state, replace the power supply. If the issue persists, contact H3C Support. Newly-installed power supply failure Symptom A trap or log is generated indicating that a newly-installed power supply is faulty.
  • Page 7: Fan Tray Failure

    Normal state in the new slot. If the power supply remains in Fault state, go to step 4. If the issue persists, contact H3C Support. Fan tray failure Symptom A trap or log is generated indicating that an operating fan tray or a newly-installed fan tray is faulty.
  • Page 8: Related Commands

    If there are cooling measures to maintain the switch operating temperature below 60°C  (140°F), the switch can be used temporarily. If the issue persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting the hardware.
  • Page 9: Troubleshooting Acl

    ACL resources insufficiency. If this field displays 0, the ACL hardware resources are exhausted. To free hardware resources for packet filtering or QoS classification, remove unused 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.
  • Page 10: Troubleshooting Flowchart

    ACL rule Reconfigure ACL rule Problem resolved? configured correctly? Contact H3C 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: a.
  • Page 11: Related Commands

     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 12: 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 13: Troubleshooting Flowchart

    IRF port configuration Upgrade software to the same Same software version? Resolved? version in the fabric Contact H3C Support Solution To resolve the issue: Verify that the number of member devices does not exceed the upper limit. 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.
  • Page 14 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. 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 15: 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 16: 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 17: Troubleshooting Flowchart

    More member ports than allowed max. number than or equal to allowed max. number of Resolved? of Selected ports? Selected ports Contact H3C Support Solution To resolve the issue: Verify that all physical connections are correct. You can verify the physical connections against your network plan.
  • Page 18: 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 19: Troubleshooting Ports

    Ports on both ends Replace the local and Resolved? operating correctly? peer ports Replace matching Transceiver module transceiver module and Resolved? and cable correct? cable Fiber correct? Replace fiber Resolved? Contact H3C Support Resolved Solution To resolve the issue:...
  • Page 20 If the transceiver module is not operating correctly, replace it with a H3C transceiver module that matches the fiber port.
  • Page 21: A 1/10Gbase-T Copper Port Fails To Go 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 issue persists, contact H3C Support.
  • Page 22: Related Commands

    Related commands This section lists the commands that you might use for troubleshooting ports. Command Remarks Displays or saves running status data for display diagnostic-information multiple feature modules. display interface brief Displays brief interface information. display transceiver alarm interface Displays alarms present on transceiver modules. Displays key parameters of the transceiver display transceiver interface module installed in an interface.
  • Page 23: Troubleshooting Other Issues

    Troubleshoot the Incoming error packets? Resolved? problem Packets filtered by Troubleshoot the Resolved? ACLs or QoS policies? problem Troubleshoot the Port blocked? Resolved? problem Locate and modify Port misconfigurations? Resolved? misconfigurations Troubleshoot the Port congestion? Resolved? problem Contact H3C Support...
  • Page 24: 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. <H3C>display interface Ten-GigabitEthernet1/0/36 Ten-GigabitEthernet1/0/36 Current state: Administratively DOWN Line protocol state: DOWN...
  • Page 25 If the issue persists, contact H3C Support. When you contact H3C Support, provide the following diagnostic information if packet loss occurs on the chip port with which the interface is associated: # Execute the debug port mapping slot 1 command in probe view to identify the chip port with which the interface is associated.
  • Page 26 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. H3C recommends disabling STP on the port, or configuring the port as an edge port if the port is connected to a terminal device.
  • Page 27: 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 28: Troubleshooting Flowchart

    Troubleshoot route Route entries are correct? Resolved? entries Contact H3C Support Solution To resolve the issue: Verify that the port is not faulty (due to hardware or configuration issues). If the port is faulty, follow the solution in "Layer 2 forwarding failure"...
  • Page 29: Related Commands

    If the issue persists, contact H3C 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. display arp Displays ARP entries. Displays brief information about active routes in the routing display ip routing-table table.
  • Page 30: Fan Failure

    DisPkt_All—Number of discarded packets.  Rcv_All—Number of received packets.  RcvPps—Packet receiving rate.  If the issue persists, contact H3C Support. When you contact H3C Support, provide diagnostic information if software-related packet loss occurred. Fan failure Symptom The fans do not operate correctly.
  • Page 31: Troubleshooting Flowchart

    Problem Replace the fan Fans are damaged? tray resolved? Contact H3C Support Solution To resolve the issue: Verify that the preferred airflow direction specified for the fans is the same as the airflow direction of the fans: a. Display fan operating status.
  • Page 32: Related Commands

    If the fans still cannot operate correctly, check whether the fans are damaged. If the fan 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.

Table of Contents