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

H3C S7500E-XS Series Troubleshooting Manual

Hide thumbs Also See for S7500E-XS Series:
Table of Contents

Advertisement

Quick Links

Download this manual
H3C S7500E-XS Switch Series
Troubleshooting Guide
Copyright © 2016 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
loading
Need help?

Need help?

Do you have a question about the S7500E-XS Series and is the answer not in the manual?

Questions and answers

Related Manuals for H3C S7500E-XS Series

Summary of Contents for H3C S7500E-XS Series

  • Page 1 H3C S7500E-XS Switch Series Troubleshooting Guide Copyright © 2016 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 ······················································································································· 2 Collecting operating statistics ································································································································· 3 Contacting technical support ··········································································································································· 4 Troubleshooting hardware ·········································································································································· 5 Unexpected switch reboot ················································································································································...
  • Page 3 A 1/10GBase-T 10-GE copper port fails to come up ······························································································· 36 Symptom ································································································································································· 36 Troubleshooting flowchart ···································································································································· 36 Solution ··································································································································································· 36 Non-H3C transceiver module error message ·············································································································· 37 Symptom ································································································································································· 37 Troubleshooting flowchart ···································································································································· 37 Solution ··································································································································································· 37 Transceiver module does not support digital diagnosis ····························································································· 38 Symptom ·································································································································································...
  • Page 4 Symptom ································································································································································· 48 Troubleshooting flowchart ···································································································································· 48 Solution ··································································································································································· 48 Related commands ························································································································································· 49 Troubleshooting other problems ································································································································ 50 Layer 2 forwarding failure ············································································································································ 50 Symptom ································································································································································· 50 Troubleshooting flowchart ···································································································································· 50 Solution ··································································································································································· 51 Related commands ················································································································································ 54 Layer 3 forwarding failure ············································································································································ 54 Symptom ·································································································································································...

  • Page 5: Introduction

    Introduction This document provides information about troubleshooting common software and hardware problems with the S7500E-XS switch series. This document is not restricted to specific software or hardware versions. General guidelines IMPORTANT: To prevent a problem 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 in effect when an error occurs. Diagnostic log diagfile.log •...

  • Page 7: Collecting Operating Statistics

    By default, the diagnostic log file is saved in the diagfile directory of the Flash memory on each member device. <Sysname> diagnostic-logfile save The contents in the diagnostic log file buffer have been saved to the file flash:/diagfile/diagfile.log Identify the diagnostic log file on each member device: # Display the diagnostic log file on the master device.

  • 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

    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 The switch reboots unexpectedly when it is operating. Troubleshooting flowchart Figure 1 Troubleshooting unexpected switch reboot Solution...

  • Page 10: Operating Power Module Failure

    CRC error has occurred or that no system software image is available, access the BootWare menus and reload the system software image. The system software image is automatically set to the current system software image. If the problem persists, contact H3C Support. Operating power module failure Symptom A trap or log is generated indicating that an operating power module is faulty.

  • Page 11: Solution

    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 A trap or log indicates that a fan tray is faulty, or the display fan command shows that a fan tray is not in Normal state.

  • Page 12: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 2 Troubleshooting fan tray failure Solution To resolve the problem: Execute the display fan command to display the operating states of the fan tray. <Sysname> display fan Slot 1: Fan 1: State : FanDirectionFault Airflow Direction: Port-to-power Prefer Airflow Direction: Power-to-port Fan 2: State...

  • Page 13: 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 14: Troubleshooting Acl

    If this field displays 0, the ACL resources are exhausted. To free ACL resources, delete unnecessary 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. However, the ACL does...

  • Page 15: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 3 Troubleshooting 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: Use one of the following commands to check the QoS policy for configuration errors, depending on the policy application destination: Destination...

  • Page 16: 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 17: Troubleshooting Irf

    Troubleshooting IRF This section provides troubleshooting information for common problems with IRF. IRF fabric setup failure Symptom An IRF fabric cannot be set up.

  • Page 18: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 4 Troubleshooting IRF fabric setup failure IRF setup failure You cannot add the Number of members fewer device to the IRF fabric or than the upper limit? complete IRF merge Assign a unique member Member ID unique? ID to each member Resolved? device...

  • Page 19: Solution

    Solution To resolve the problem: Verify that the number of member devices does not exceed the upper limit (nine). 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. If the total number of member devices exceeds the upper limit, the IRF setup will fail.

  • Page 20: Irf Split

    Execute the display irf command to check the IRF operating mode on each device. If the modes are different, use the irf mode command to change the mode to the same one. The mode change takes effect after a reboot. If the problem persists, contact H3C Support. IRF split Symptom...

  • Page 21: Troubleshooting Flowchart

    "Troubleshooting hardware" to resolve the problem. If the problem persists, contact 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 settings,...

  • Page 22: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 6 Troubleshooting BFD MAD failure BFD MAD failure BFD MAD link Correct the connections Resolved? connections correct? All BFD MAD Bring up the ports Resolved? ports up? BFD MAD VLAN interface Correct the settings Resolved? configured correctly? BFD MAD VLAN and ports Correct the settings Resolved?
  • Page 23 If you do not use an intermediate device, verify that each pair of member chassis has a dedicated BFD MAD link. If you use an intermediate device, verify that each member chassis has a dedicated BFD MAD link with the intermediate device. Verify that all physical ports used for BFD MAD are up: Execute the display interface command.

  • Page 24: Lacp Mad Failure

    Execute the display trapbuffer command or use system logs to check for BFD MAD port-down events that occurred around the split time. Identify the cause of the events, and remove the issue. If the problem persists, contact H3C Support. LACP MAD failure Symptom LACP MAD fails to detect an IRF split event.

  • Page 25: Solution

    Solution To resolve the problem: Verify that the intermediate device is an H3C device that supports extended LACPDUs for MAD. If the intermediate device does not support extended LACPDUs for MAD, replace the intermediate device, or use BFD MAD for split detection.

  • Page 26: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 8 Troubleshooting PEX joining IRF 3 system failure A device fails to join an IRF 3 system as a PEX Is the device model The device cannot join the PEX capable? IRF 3 system as a PEX Enable IRF 3 capability Is IRF 3 capability enabled Resolved?
  • Page 27 Verify that you can use the device as a PEX. The following switches can be used as PEXs for the H3C S7500E-XS switch: The 5120-28SC-HI switch. The 5120-52SC-HI switch. All S5130-EI switches. All S6300 switches. Verify that IRF 3 capability is enabled on the parent fabric: Execute the display irf command and check the IRF mode field for IRF 3 capability status.
  • Page 28 If PEX mode is disabled, press Ctrl+Y to change the operating mode to PEX. By default, PEX mode is disabled for an S5130-EI switch. BOOT MENU 1. Download application file to flash 2. Select application file to boot 3. Display all files in flash 4.
  • Page 29 Method 2: <Sysname> boot-loader pex PEX-S5130EI file boot flash:/S5130EIPEX-S7500EXS-CMW710-BOOT-R7178.bin system flash:/S5130EIPEX-S7500EXS-CMW710-SYSTEM-R7178.bin Verify the result. <Sysname> display boot-loader pex Startup software image files for PEXs to load from the parent device: PEX model: PEX-S5130EI flash:/S5130EIPEX-S7500EXS-CMW710-BOOT-R7178.bin flash:/S5130EIPEX-S7500EXS-CMW710-SYSTEM-R7178.bin PEX model: PEX-S6300 None Verify that the PEX links are up: Execute the display interface pex command to check the PEX physical interface status.
  • Page 30 The S7500E-XS switch might support transceiver modules or DAC cables that provide higher speed than SFP+ or QSFP+, depending on the software version and expansion interface card H3C S7500E-XS Switch Series Virtual Technologies model. For more information, see the latest...
  • Page 31 Switch model Candidate PEX physical interfaces Use the 10-GE or 40-GE fiber ports on the following expansion interface cards for PEX links: • LSQM1QGS8A0. S7500E-XS (parent) • LSQM1TGS24QSA0. • LSQM1TGS24QSM0. • LSQM1TGT24QSM0. The 10-GE ports numbered 27 and 28 can be connected to S5120-28SC-HI the parent fabric.

  • Page 32: Pex Split

    Use transceiver modules instead of DAC cables to connect the 40-GE ports of PEXs to the parent fabric. For more information about the binding and connection restrictions, see H3C S7500E-XS Switch Series Virtual Technologies Configuration Guide. If the problem persists, contact H3C Support.

  • Page 33: Related Commands

    If the PEX split is caused by a reboot, use the methods described in "Troubleshooting hardware" to resolve the problem. If the problem persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting IRF.

  • Page 34: 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 35: 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:...

  • Page 36: 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 37 Commands Description Configure the maximum number of Selected ports link-aggregation selected-port maximum allowed in an aggregation group.

  • Page 38: 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 come up Symptom A 10-GE SFP+ fiber port or 40-GE QSFP+ fiber port fails to come up. Troubleshooting flowchart Figure 11 Troubleshooting link up failure on a copper port A port failed to come up...

  • Page 39: Solution

    Execute the display transceiver interface command to verify that the local transceiver module has the same wavelength and transmission distance as the peer transceiver module. If the transceiver module is not operating correctly, replace it with a H3C transceiver module that matches the fiber port.

  • Page 40: A 1/10Gbase-T 10-Ge Copper Port Fails To Come Up

    Verify that the fiber matches the transceiver module. If they do not match, replace the fiber with a new one that matches the transceiver module. For more information about fibers, see the installation guide for the switch. If the problem persists, contact H3C Support. A 1/10GBase-T 10-GE copper port fails to come Symptom A 1/10GBase-T 10-GE copper port fails to come up.

  • Page 41: Non-H3C Transceiver Module Error Message

    If the problem persists, contact H3C Support. Non-H3C transceiver module error message Symptom The output from the display logbuffer command shows that the transceiver module is not an H3C transceiver module. <Sysname> display logbuffer FortyGigE1/1/5: This transceiver is NOT sold by H3C. H3C therefore shall NOT guarantee...

  • Page 42: Transceiver Module Does Not Support Digital Diagnosis

    : H3C Ordering Name : QSFP-40G-LR4-WDM1300 If the vendor name field does not display H3C, replace the transceiver module with an H3C transceiver module. If the vendor name field displays H3C, perform the following tasks: Execute the display hardware internal transceiver register interface command in probe −...

  • Page 43: Solution

    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. If the vendor name field displays H3C, perform the following tasks: Execute the display transceiver manuinfo interface command to save the transceiver −...

  • Page 44: Troubleshooting Flowchart

    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: (Optional.) Use the reset counter interface command in user view to clear the packet statistics of the port.

  • Page 45: 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 problem persists, contact H3C Support. Failure to receive packets Symptom...

  • Page 46: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 16 Troubleshooting failure to receive packets Solution To resolve the problem: Verify that the ports at both ends are up. Examine the packet statistics of the port: (Optional.) Use the reset counter interface command to clear the packet statistics of the port. This command resets all packet counters to 0, so that you can view the statistics changes more clearly.

  • Page 47: Failure To Send Packets

    If the port is a fiber port, replace the transceiver module in the port. If the port can receive packets, troubleshoot the remaining possible points of failure on the transmission path. The troubleshooting process is beyond the scope of this document. If the problem persists, contact H3C Support. Failure to send packets Symptom...

  • Page 48: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 17 Troubleshooting failure to send packets A port failed to send packets Display packet statistics for the port Port configuration Modify port Problem resolved? affects packet receiving? configuration Port and link Use the correct port Problem resolved? and link medium medium correct? Contact the support...

  • Page 49: Related Commands

    If the port can send packets, troubleshoot the remaining possible points of failure on the transmission path. The troubleshooting process is beyond the scope of this document. If the problem persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting ports.

  • Page 50: Troubleshooting System Management

    Troubleshooting system management This section provides troubleshooting information for common system management problems. High CPU utilization Symptom The sustained CPU utilization of the device is over 80%. Troubleshooting flowchart Figure 18 Troubleshooting high CPU utilization High CPU utilization Identify the job that has a high CPU utilization Display the job’s stack Save diagnostic information...
  • Page 51 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% [migration/2] 0.0% 0.0% 0.0% [ksoftirqd/2] 0.0% 0.0% 0.0% [watchdog/2] 0.0% 0.0% 0.0% [migration/3] 0.0% 0.0% 0.0% [ksoftirqd/3] 0.0% 0.0% 0.0% [watchdog/3] 0.0% 0.0% 0.0% [migration/4] 0.0% 0.0% 0.0%...

  • Page 52: High Memory Utilization

    [<80480754>] schedule+0x954/0x1250 [<8028f720>] watchdog+0xb0/0x410 [<802656d0>] kthread+0x130/0x140 [<8021d730>] kernel_thread_helper+0x10/0x20 Save the information displayed in the previous steps. Contact H3C Support. High memory utilization Symptom The memory utilization of the device is over 60% for more than 30 minutes. Troubleshooting flowchart Figure 19 Troubleshooting high memory utilization...

  • Page 53: Related Commands

    Save the information displayed in the previous step. Contact H3C Support. IMPORTANT: As a best practice, do not reboot the device before you contact H3C Support. You might lose critical diagnostic information if you reboot the device. Related commands This section lists the commands that you might use for troubleshooting system management.

  • Page 54: Troubleshooting Other Problems

    Troubleshooting other problems Layer 2 forwarding failure Symptom Layer 2 packet loss occurs when the switch forwards packets to a peer on the same network segment and in the same VLAN. Troubleshooting flowchart Figure 20 Troubleshooting Layer 2 packet loss failure...

  • Page 55: 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: # Use the probe command to enter probe view. In probe view, execute the debug port mapping command to identify the chip port with which the interface is associated.
  • Page 56 FGE1/1/1 FGE1/1/2 down FGE1/1/3 down FGE1/1/4 down FGE1/1/5 down FGE1/1/6 down FGE1/1/7 down FGE1/1/8 down The output shows that FortyGigE 1/1/1 is associated with chip port xe0. # Execute the bcm slot 1 chip 0 show/count/xe0 command to check the RDBGC and TDBGC fields for Rx and Tx dropped packet statistics, respectively.
  • Page 57 interface command to display the portal configuration information of the specified VLAN interface. Determine whether the portal authentication can be disabled based on the network conditions. To disable the portal authentication at Layer 3, use the undo portal server server-name command in VLAN interface view of the VLAN to which the port belongs.

  • Page 58: Related Commands

    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. Command Description display interface Displays Ethernet interface information. Displays whether an ACL has been successfully display packet-filter applied to an interface for packet filtering.

  • Page 59: 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 ARP entries are correct: Execute the display arp command to verify that ARP entries are correct.

  • Page 60: 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 61: Solution

    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.

Table of Contents