H3C S5560S-EI Series Troubleshooting Manual
  1. Manuals
  2. Brands
  3. H3C Manuals
  4. Switch
  5. S5560S-EI Series
  6. Troubleshooting manual

H3C S5560S-EI Series Troubleshooting Manual

Hide thumbs Also See for S5560S-EI Series:
Table of Contents

Advertisement

Quick Links

Download this manual
Troubleshooting Guide
H3C S5560S-EI & S5560S-SI Switch Series
H3C S5500V3-SI Switch Series
H3C S5130S-HI & S5130S-EI & S5130S-SI & S5130S-LI Switch Series
H3C S5120V2-SI & S5120V2-LI Switch Series
H3C S5110V2 & S5110V2-SI Switch Series
H3C S5000V3-EI & S5000E-X Switch Series
H3C S3100V3-EI & S3100V3-SI Switch Series
H3C E128C & E152C & E500C & E500D Switch Series
H3C MS4520V2 & MS4320V2 & MS4300V2 & MS4200 Switch Series
H3C WS5850-WiNet & WS5820-WiNet & WS5810-WiNet Switch Series
H3C WAS6000 Switch Series
Document version: 6W103-2020315
Copyright © 2020 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

Related Manuals for H3C S5560S-EI Series

Summary of Contents for H3C S5560S-EI 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   Contacting technical support ········································································································ 4 Troubleshooting hardware ··································································...
  • Page 3   Troubleshooting flowchart ··································································································· 21   Solution ··························································································································· 22   A copper port fails to come up ···································································································· 23   Symptom ························································································································· 23   Troubleshooting flowchart ··································································································· 23   Solution ··························································································································· 23   Related commands ·················································································································· 24 Troubleshooting other issues ···························································· 25  ...

  • Page 4: Introduction

    Introduction This document provides information about troubleshooting common software and hardware issues with the switches. This document is not restricted to specific software or hardware versions. General guidelines IMPORTANT: To prevent a failure from causing loss of configuration, save the configuration each time you finish configuring a feature.

  • Page 5: Collecting Common Log Messages

    To more easily locate log information, save the files to a separate folder for each member device, and include their member IDs in the folder names. Table 1 Log and operating information Category File name format Content Log messages about command executions, event Common log logfile.log occurrences, state changes, and so on.

  • Page 6: Collecting Diagnostic Log Messages

    Collecting diagnostic log messages Save the 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>...

  • Page 7: Contacting Technical Support

    23:49:53 UTC Tue 01/01/2016 ================================================= ---- More ---- Contacting technical support If an issue persists after you perform the troubleshooting procedures in this document, contact H3C Support. When you contact an authorized H3C support representative, be prepared to provide the following information: •...

  • Page 8: Unexpected Switch Reboot

    NOTE: • This section describes how to troubleshoot unexpected switch reboot, removable power modules, and fixed fan trays. To troubleshoot transceiver modules and ports, see "Troubleshooting ports." • Hardware varies by device model. For example, a switch might use fixed power modules or removable power modules.

  • Page 9: Operating Power Module Failure

    CRC error has occurred or that no system software image is available during the BootWare loading process, reload the system software image on the BootWare menu and configure it as the current system software image. If the issue persists, contact H3C Support. Operating power module failure Symptom A trap or log is generated indicating that an operating power module is faulty.

  • Page 10: Newly Installed Power Module 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 A fan tray is not operating correctly.

  • Page 11: Usb Device Anomaly

    If the USB device state is Absent, it has failed to be identified by the USB port. Go to 2. Verify that the USB device is operating correctly. Connect another USB device to the USB port. If this USB device cannot be identified, go to 3. If the issue persists, contact H3C Support. Interface card anomaly Symptom An interface card is in abnormal state.

  • Page 12: Related Commands

    If the issue persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting hardware. Command Description display device manuifo Displays information about the device. display device usb Displays operating information about USB devices.

  • Page 13: 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 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 14: 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 issue when the ACL is used in a QoS policy: Verify that the QoS policy is configured correctly: a.

  • Page 15: Related Commands

    If the ACL is configured incorrectly, reconfigure it. 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 16: 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 17: Troubleshooting Flowchart

    Upgrade software to the Same software version? Resolved? same version Contact H3C Support Solution To resolve the issue: Verify that the switch models can form an IRF fabric: a. Verify that the member switches are from the same switch series.
  • Page 18 Verify that the number of member devices does not exceed the upper limit (varies by software version and device model). To obtain the upper limit for your device, contain H3C Support. 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 19: 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 20 Command Description Displays IRF fabric information, including the member ID, role, priority, display irf bridge MAC address, and description of each IRF member. Displays IRF link information, including the member ID, IRF port, display irf link interfaces bound to each IRF port, and status of each IRF link. 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...

  • Page 21: 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 22: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 4 Troubleshooting link aggregation failure Solution To resolve the issue: 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 23: 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 24: Troubleshooting Ports

    Troubleshooting ports This section provides troubleshooting information for common port issues. A fiber port fails to come up Symptom A fiber port fails to come up. Troubleshooting flowchart Figure 5 Troubleshooting link up failure on a fiber port...

  • Page 25: Solution

    If the transceiver module is not operating correctly, replace it with a H3C transceiver module that matches the fiber port.

  • Page 26: A 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 issue persists, contact H3C Support.

  • Page 27: 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 28: Troubleshooting Other Issues

    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 29: Solution

    If they are inconsistent, modify the configurations of the local port. c. If the issue persists, contact H3C Support. Verify that packets are not mistakenly filtered out by ACLs: a.
  • Page 30 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 that you disable STP on the port, or configure the port as an edge port if the port is connected to a terminal device.

  • Page 31: Related Commands

    Related commands This section lists the commands that you might use for troubleshooting Layer 2 forwarding failure. Command Description Displays session information, statistics, and configurations about display dot1x 802.1X. display interface Displays Ethernet interface information. display ip source binding Displays IPv4 source guard binding entries. display ipv6 source binding Displays IPv6 source guard binding entries.

  • Page 32: 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 not the same, execute the reset command to clear the route entries. Then the switch can learn route entries again. If the issue persists, contact H3C Support.

  • Page 33: 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 fib Displays FIB entries. Displays brief information about active routes in the routing display ip routing-table table.

  • Page 34: Poe Power Supply Anomaly

    SMAC 8 MCAST_NTP SMAC 8 BCAST_NTP SMAC 8 If the issue persists, contact H3C Support. When you contact H3C Support, provide diagnostic information if software-related packet loss occurred. PoE power supply anomaly Symptom The PoE device cannot supply power correctly.

  • Page 35: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 10 Troubleshooting PoE power supply anomaly Solution To resolve the issue: Verify that the PoE power is correctly used. For a PoE switch, use the PoE power according to the PoE power supply scheme. For information about the power supply compatibility, see the installation guide for your device. Execute the following commands to display power supply information: a.
  • Page 36 Update firmware on the specific PSE(s) successfully! The output shows that the PSE processing software has been upgraded. c. Execute the display poe device command again to display PSE information, and check the on or off field for the PSE state. [Sysname] display poe device PSE ID SlotNo SubSNo PortNum...

  • Page 37: Related Commands

    PoE interface, execute the poe max-power command to configure the maximum power with higher-wattage supply. If the issue persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting PoE.

This manual is also suitable for:

S5560s-si seriesS5500v3-si seriesS5130s-hi seriesS5130s-ei seriesS5130s-si seriesS5130s-li series ... Show all

Table of Contents