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

H3C S5820V2 Series Troubleshooting Manual

Hide thumbs Also See for S5820V2 Series:
Table of Contents

Advertisement

Quick Links

Download this manual
H3C S5820V2 & S5830V2 Switch Series
Troubleshooting Guide
Copyright © 2018 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 S5820V2 Series and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for H3C S5820V2 Series

Summary of Contents for H3C S5820V2 Series

  • Page 1 Copyright © 2018 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 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 ············································································································ 23 Layer 3 forwarding failure ·········································································································· 24 Symptom ························································································································· 24 Troubleshooting flowchart ··································································································· 24 Solution ··························································································································· 24 Related commands ············································································································ 25 Protocol flapping ······················································································································ 25 Symptom ························································································································· 25 Troubleshooting flowchart ··································································································· 26 Solution ··························································································································· 26 Fan failure ······························································································································...

  • Page 4: Introduction

    Introduction Troubleshooting hardware This section provides troubleshooting information for common hardware problems. 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 problem 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 problem 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 problem 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 problem persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting the hardware.

  • Page 9: Troubleshooting Acl

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

  • Page 10: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 2 Troubleshooting an 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 11: 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 12: Troubleshooting Irf

    Troubleshooting IRF This section provides troubleshooting information for common problems with IRF. IRF fabric establishment failure Symptom An IRF fabric cannot be established.

  • Page 13: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 3 Troubleshooting IRF fabric establishment failure Solution To resolve the problem: 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 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 problem 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 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 17: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 4 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 18: 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 19: Troubleshooting Ports

    Troubleshooting ports This section provides troubleshooting information for common port problems. A 10-GE SFP+ fiber port or 40-GE QSFP+ fiber port fails to go up Symptom A 10-GE SFP+ fiber port or 40-GE QSFP+ fiber port fails to go up. Troubleshooting flowchart Figure 5 Troubleshooting link up failure on a copper port Solution...
  • 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 10/100/1000Base-T Ge Copper Port Or 1/10Gbase-T 10-Ge 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 problem 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. Displays alarms present transceiver display transceiver alarm interface modules.

  • Page 23: Troubleshooting Other Problems

    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 Troubleshoot the Port congestion? Resolved? problem Contact H3C Support...

  • Page 24: Solution

    If the problem 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 map 1 command in en_diag view to identify the chip port with which the interface is associated.
  • Page 25 Rx and Tx dropped packet statistics, respectively. The statistics displayed were generated between the last and the current execution of the command. To view the change in dropped packet statistics, execute the command twice or more. [H3C-diagnose] bcm 1 0 show/c/xe0 RDBGC2.xe0 8,118 +8,118 R511.xe0...

  • Page 26: Related Commands

    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: Layer 3 Forwarding Failure

    Command Description Displays the running configuration in the current display this view. display ip source binding/display ipv6 source Displays source guard binding entries. binding Displays detailed information about display link-aggregation verbose aggregation groups that correspond to the aggregate interfaces. display mac-address blackhole Displays blackhole MAC address entries.

  • Page 28: Related Commands

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

  • Page 29: Troubleshooting Flowchart

    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.

  • Page 30: Fan Failure

    Problem Replace the fan Fans are damaged? resolved? tray Contact H3C Support Solution To resolve the problem: 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 31: 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 problem persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting fans.

This manual is also suitable for:

S5830v2 series

Table of Contents