Table of Contents
Advertisement
Quick Links
Download this manual
See also:
Installation Manual
H3C S5560-EI Switch Series Troubleshooting
Guide
Copyright © 2015 Hangzhou 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 Hangzhou H3C Technologies Co., Ltd.
The information in this document is subject to change without notice.
Advertisement
Table of Contents
Troubleshooting
Subscribe to Our Youtube Channel
Related Manuals for H3C S5560-EI Series
Summary of Contents for H3C S5560-EI Series
- Page 1 H3C S5560-EI Switch Series Troubleshooting Guide Copyright © 2015 Hangzhou 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 Hangzhou H3C Technologies Co., Ltd.
-
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 ... - Page 3 Copper port remains in down state ····························································································································· 28 Symptom ································································································································································· 28 Troubleshooting flowchart ···································································································································· 28 Solution ··································································································································································· 28 Non-H3C transceiver module ······································································································································· 29 Symptom ································································································································································· 29 Troubleshooting flowchart ···································································································································· 29 Solution ··································································································································································· 29 ...
- Page 4 Solution ··································································································································································· 50 Related commands ················································································································································ 51 Protocol flapping ···························································································································································· 51 Symptom ································································································································································· 51 Troubleshooting flowchart ···································································································································· 51 Solution ··································································································································································· 52 Fan failure ······································································································································································· 52 Symptom ································································································································································· 52 Troubleshooting flowchart ···································································································································· 53 ...
-
Page 5: Introduction
Introduction This document provides information about troubleshooting common software and hardware problems with S5560-EI Switch Series. 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 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 used when an error occurs. Diagnostic log diagfile.log •... -
Page 7: Collecting Diagnostic Log Messages
Network and management ports are faster than the console port. Do not execute commands during operating statistics collection. • To ensure information completeness, H3C recommends that you save the statistics to a file. • NOTE: The amount of time to collect statistics increases along with the number of IRF member devices. -
Page 8: Contacting Technical Support
…… 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 guidelines."... -
Page 9: Troubleshooting Hardware
E-mail—service@h3c.com. • 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... -
Page 10: Troubleshooting Flowchart
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 11: Operating Power Module Failure
Operating power module failure Symptom An operating power module fails. Troubleshooting flowchart Figure 2 Troubleshooting operating power module failure Solution To resolve the problem: Identify the operating state of the power module. [Sysname]display power Slot 2: PowerID State Mode Current(A) Voltage(V) Power(W) Normal... -
Page 12: 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 problem persists, contact H3C Support. Newly installed power module failure Symptom A newly installed power module fails. -
Page 13: Fan Tray Failure
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. Fan tray failure Symptom An operating fan tray or a newly installed fan tray fails. -
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
Execute the display qos-acl resource command, and then check the Remaining field for ACL resources insufficiency. 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. -
Page 16: Acl Application Failure Without An Error Message
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 does not take effect. Troubleshooting flowchart Figure 6 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:... -
Page 17: Packet Loss Or Forwarding Failure
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: Troubleshooting Flowchart
Troubleshooting flowchart Figure 7 Troubleshooting a forwarding failure Solution To resolve the problem: Identify the characteristics of the packets that are not forwarded correctly. Use a packet capture tool to identify the characteristics of the traffic, such as the IP address, MAC address, or VLAN. - Page 19 [Sysname-behavior-count] quit [Sysname] qos policy count [Sysname-qospolicy-count] classifier count behavior count Apply the QoS policy to interfaces on devices along the forwarding path. In this example, apply the QoS policy to the incoming traffic on GigabitEthernet 1/0/1 on Device B and GigabitEthernet 2/0/1 on Device C.
-
Page 20: Related Commands
Related commands This section lists the commands that you might use for troubleshooting ACLs. Command Description display acl Displays configuration and match statistics for ACLs. Displays operating statistics for multiple feature modules in display diagnostic-information the system. Displays whether an ACL has been successfully applied to an display packet-filter interface for packet filtering. -
Page 21: 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 22: Troubleshooting Flowchart
Troubleshooting flowchart Figure 9 Troubleshooting IRF fabric establishment failure IRF setup failure You cannot add the device to Number of members the IRF fabric or complete IRF fewer than the upper limit? merge Assign a unique member ID to Member ID unique? Resolved? each member device IRF port bindings... - Page 23 Verify that the member ID of each member device is unique: Execute the display irf command to view the member ID of each member device. 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 −...
-
Page 24: 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 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 10 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: 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 Commands Description Configure the maximum number of Selected ports link-aggregation selected-port maximum allowed in an aggregation group.
-
Page 29: Troubleshooting Ports
Troubleshooting ports This section provides troubleshooting information for common port problems. Fiber port remains in down state Symptom A fiber port (SFP port, SFP+ port, or QSFP+ port) remains in down state. -
Page 30: Troubleshooting Flowchart
Troubleshooting flowchart Figure 11 Troubleshooting fiber port's failure to come up Solution To resolve the problem: Verify that the speed and duplex mode of the local port match the speed and duplex mode of the peer port: Execute the display interface brief command to examine whether the speed and duplex mode of the port match the speed and duplex mode of the peer port. - Page 31 If the transceiver module is not operating correctly, replace it with a H3C transceiver module that matches the fiber port.
-
Page 32: Copper Port Remains In Down State
Copper port remains in down state Symptom A 10/100/1000Base-T GE copper port or 1/10GBase-T 10-GE copper port remains in down state. Troubleshooting flowchart Figure 12 Troubleshooting copper port's failure to come up Copper port remains in down state Speed/duplex match Configure matching Resolved? on local and peer port? -
Page 33: Non-H3C Transceiver Module
If the problem persists, contact H3C Support. Non-H3C transceiver module Symptom The output from the display logbuffer command shows that the transceiver module is not an H3C transceiver module. <Sysname> display logbuffer Ten-GigabitEthernet1/0/25: This transceiver is NOT sold by H3C. H3C therefore shall... -
Page 34: Transceiver Module Does Not Support Digital Diagnosis
Provide the transceiver module information to H3C Support to verify that the transceiver module is an H3C transceiver module. If it is not an H3C transceiver module, replace it with an H3C transceiver module. -
Page 35: Troubleshooting Flowchart
If the vendor name field displays H3C, execute the display hardware internal transceiver register interface command in probe view. Provide the transceiver module 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. -
Page 36: Error Frames (For Example, Crc Errors) On A Port
Error frames (for example, CRC errors) on a port Symptom The output from the display interface command shows that error frames exist (for example, CRC error frames) on a port. Troubleshooting flowchart Figure 15 Troubleshooting error frames (for example, CRC errors) on a port Solution To resolve the problem: Examine the error frame statistics and identify the error frame type:... - Page 37 If the port is a fiber port, verify that the optical power of the transceiver module is operating correctly: Use the display transceiver diagnosis interface command to view the present measured values of the digital diagnosis parameters for the transceiver module. [Sysname] display transceiver diagnosis interface ten-gigabitethernet 1/0/51 Ten-GigabitEthernet1/0/51 transceiver diagnostic information: Current diagnostic parameters:...
-
Page 38: Failure To Receive Packets
If you determine that the configurations, the peer port, and the link are correct but the problem persists, perform the following tasks: Use the display diagnostic-information command to collect the diagnostic information. Contact H3C Support. <Sysname> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y... -
Page 39: Solution
If a port is set to the discarding state by STP, examine and modify the STP-related configurations to resolve the problem. H3C recommends that you configure the port as an edge port or disable STP on the port if it is directly connected to a terminal. -
Page 40: Failure To Send Packets
If you determine that the configurations, the peer port, and the link are correct but the problem persists, perform the following tasks: Use the display diagnostic-information command to collect the diagnostic information. Contact H3C Support. <Sysname> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y... - Page 41 If a port is set to the discarding state by STP, examine and modify the STP-related configurations to resolve the problem. H3C recommends that you configure the port as an edge port or disable STP on the port if it is directly connected to a terminal.
-
Page 42: Related Commands
Related commands This section lists the commands that you might use for troubleshooting ports. Command Description Displays or saves running status data for display diagnostic-information multiple feature modules. display interface Displays Ethernet interface information. display interface brief Displays brief interface information. Displays the summary information for all display link-aggregation summary aggregation groups. -
Page 43: Troubleshooting System Management
Troubleshooting system management This section provides troubleshooting information for common system management problems. High CPU utilization Symptom The display cpu-usage command shows that the CPU utilization of the device is continuously higher than 80%. Troubleshooting flowchart Figure 18 Troubleshooting high CPU utilization High CPU utilization Identify the job with a high... - Page 44 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% [ksoftirqd/1] 0.0% 0.0% 0.0% [watchdog/1] 0.0% 0.0% 0.0% [events/0] 0.0% 0.0% 0.0% [events/1] 0.0% 0.0% 0.0% [khelper] 0.0% 0.0% 0.0% [kblockd/0] 0.0% 0.0% 0.0%...
-
Page 45: High Memory Utilization
[Sysname-probe] Use the display diagnostic-information command to collect diagnostic information. Save the information displayed in the previous steps. Contact H3C Support. High memory utilization Symptom The display memory command shows that the memory utilization of the device is higher than 60% during a period of time (typically 30 minutes). -
Page 46: Solution
Save the information displayed in the previous step and contact H3C Support. IMPORTANT: For quick troubleshooting, do not reboot the device before you contact H3C Support. The previous step only identifies the memory portions that have problems. Further information is required to locate the code section that has problems. -
Page 47: Troubleshooting Other Problems
Command Description display cpu-usage Displays the current CPU usage statistics. display memory Displays memory usage statistics. display process cpu Displays the CPU usage statistics for jobs. display system internal kernel memory pool Displays memory block usage statistics. follow job job-id Displays the stack of a job. -
Page 48: Troubleshooting Flowchart
Troubleshooting flowchart Figure 20 Troubleshooting Layer 2 packet loss failure Solution To resolve the problem: Verify that no error packets have been received on the local port: Execute the display interface command and check for error packets. [Sysname-probe]display interface GigabitEthernet 1/0/17 GigabitEthernet1/0/17 Current state: UP Line protocol state: UP... - Page 49 In this event, you must replace the local port with a correctly operating port. Transceiver module, fiber, or twisted pair failure—To test and resolve such a failure, replace − the transceiver module, fiber, or twisted pair with a good one. If the problem persists, contact H3C Support.
- Page 50 When you contact H3C Support, provide the following diagnostic information if packet loss occurs on the chip port with which the interface is associated: # In probe view, execute the debug port mapping command to identify the chip port with which the interface is associated.
- Page 51 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...
-
Page 52: Related Commands
Verify that no congestion occurs by using the display qos queue-statistics interface command. 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. -
Page 53: Layer 3 Forwarding Failure
Command Description Displays information about the QoS policies applied display qos policy interface to an interface or all interfaces. Displays information about QoS policies applied to display qos vlan-policy VLANs. display qos policy global Displays information about global QoS policies. Displays the running configuration in the current display this view. -
Page 54: Troubleshooting Flowchart
Troubleshooting flowchart Figure 21 Troubleshooting Layer 3 forwarding failure Solution To resolve the problem: Verify that the port is not faulty (due to hardware or configuration problems). If the port is faulty, follow the solution in "Layer 2 forwarding failure" to troubleshoot the problem. Verify that the ARP entries are correct: Execute the display arp command to verify that the ARP entries are correct. -
Page 55: Related Commands
If the problem 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 56: Solution
IPV4_MC_PIM SMAC 8 IPV4_UC_PIM SMAC 8 IPV4_IGMP SMAC 8 SMAC 8 If the problem 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 57: Troubleshooting Flowchart
Troubleshooting flowchart Figure 23 Flowchart for troubleshooting fan failure Solution To resolve the problem: Verify that the airflow direction of the fans is as configured: Identify the airflow direction of the fans. [Sysname]display fan Slot 1 State : FanDirectionFault Wind Direction :Port-to-Power Prefer Wind Direction :Power-to-Port... -
Page 58: 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.
Need help?
Do you have a question about the S5560-EI Series and is the answer not in the manual?
Questions and answers