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.
Collecting log and operating information IMPORTANT: To quickly locate faults, verify that the following features are enabled: • Information center—Enabled by default. To enable the information center, use the info-center enable command. • Log file—Enabled by default. To enable the log file feature, use the info-center logfile enable command.
<Sysname> dir flash:/logfile/ Directory of flash:/logfile 0 -rw- 21863 Jul 11 2013 16:00:37 logfile.log 1038336 KB total (963860 KB free) # Display the log file on a subordinate device: <Sysname> dir slot2#flash:/logfile/ Directory of slot2#flash:/logfile 0 -rw- 21863 Jul 11 2013 16:00:37 logfile.log 1038336 KB total (963860 KB free) Transfer the files to the desired destination by using FTP, TFTP, or USB.
Page 7
===============display version=============== H3C Comware Software, Version 7.1.070, ESS 1108 Copyright (c) 2004-2017 New H3C Technologies Co., Ltd. All rights reserved. H3C S6520X-30QC-EI uptime is 0 weeks, 0 days, 5 hours, 57 minutes Last reboot reason : Cold reboot Boot image: flash:/s6520x-cmw710-boot-e1108.bin Boot image version: 7.1.070, ESS 1108...
Compiled Jul 18 2017 16:00:00 ---- 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: •...
CRC error has occurred or that no system software image is available, use the BootWare menu to download the system software image and reboot the switch. The switch loads the system software image. If the issue persists, contact H3C Support.
Operating power module failure Symptom An operating power module has failed. Troubleshooting flowchart Figure 2 Troubleshooting operating power module failure Solution To resolve the issue: Identify the operating state of the power module. <Sysname> display power Slot 2: PowerID State Mode Current(A) Voltage(V)
Normal state in the new slot. If the power module remains in Fault state, replace the power module. If the issue persists, contact H3C Support. Newly installed power module failure Symptom A newly installed power module has failed.
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 An operating fan tray or a newly installed fan tray has failed.
If a new fan tray is not readily available, power off the switch to avoid damage caused by high temperature. If the issue persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting the hardware.
ACL resources insufficiency. If this field displays 0, the ACL hardware resources are exhausted. To free hardware resources, delete unnecessary 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. However, the ACL...
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 issue when the ACL is used in a QoS policy: Verify that the QoS policy is configured correctly: a.
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.
Solution To resolve the issue: 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. Make sure the characteristics are unique among traffic to be forwarded.
IRF fabric establishment failure Symptom An IRF fabric cannot be established. Troubleshooting flowchart Figure 9 Troubleshooting IRF fabric establishment 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?
Solution To resolve the issue: Verify that the number of member devices does not exceed 9. 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.
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.
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.
Troubleshooting flowchart Figure 10 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. b.
This ensures that 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.
Troubleshooting ports This section provides troubleshooting information for common port issues. Fiber port remains in down state Symptom A fiber port remains in down state. Troubleshooting flowchart Figure 11 Troubleshooting fiber port's failure to come up...
Copper port remains in down state Symptom A copper port remains in down state. Troubleshooting flowchart Figure 12 Troubleshooting copper port's failure to come up Solution To resolve the issue: Verify that the speed and duplex mode of the local port match the speed and duplex mode of the peer port: a.
− If the port remains in down state, the local port fails. Replace the local port with a new port operating correctly. If the issue persists, contact H3C Support, and provide the following information: <Sysname> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y...
Vendor Name : H3C Perform either of the following tasks: 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, execute the display hardware internal transceiver register interface command in probe view.
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, execute the display hardware internal transceiver register interface command in probe view.
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 issue: Examine the error frame statistics and identify the error frame type:...
Page 32
a. 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/1 Ten-GigabitEthernet1/0/1 transceiver diagnostic information: Current diagnostic parameters: [module] Temp.(°C) 1stTX 2ndTX 1stRX 2ndRX...
If you determine that the configurations, the peer port, and the link are correct but the issue persists, perform the following tasks: a. Use the display diagnostic-information command to collect the diagnostic information. b. Contact H3C Support. <Sysname> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y Failure to receive packets Symptom A port is up, but it cannot receive packets.
Page 34
− If the port is a fiber port, replace the transceiver module plugged into the port. If you determine that the configurations, the peer port, and the link are correct but the issue persists, perform the following tasks: a. Use the display diagnostic-information command to collect the diagnostic information. b. Contact H3C Support.
<Sysname> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y Failure to send packets Symptom A port is up, but it cannot send packets. Troubleshooting flowchart Figure 17 Troubleshooting the failure to send packets Solution To resolve the issue: Examine the packet statistics of the port: a.
If you determine that the configurations, the peer port, and the link are correct but the issue persists, perform the following tasks: a. Use the display diagnostic-information command to collect the diagnostic information. b. Contact H3C Support. <Sysname> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y Related commands...
Command Description display Displays or saves running status data for multiple feature diagnostic-information modules. display interface Displays Ethernet interface information. display interface brief Displays brief interface information. display link-aggregation Displays the summary information for all aggregation groups. summary Displays the state of the log buffer and the log information in the display logbuffer log buffer.
Troubleshooting flowchart Figure 18 Troubleshooting high CPU utilization High CPU utilization Identify the job with a high CPU utilization Display the job’s stack Obtain diagnostic information Contact the support Solution To resolve the issue: Execute the display cpu-usage command multiple times to display CPU usage information. (Details not shown.) Identify the job with a high CPU utilization.
Page 39
0.0% 0.0% 0.0% [kseriod] 0.0% 0.0% 0.0% [vzmond] 0.0% 0.0% 0.0% [pdflush] 0.0% 0.0% 0.0% [pdflush] The output shows the average CPU usage values of jobs during the last 5-second, 1-minute, and 5-minute intervals. Typically, the average CPU usage of a job is approximately 5%. Display the job's stack.
[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).
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 issues. Further information is required to locate the code section that has issues.
Troubleshooting other issues 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...
Solution To resolve the issue: Verify that no error packets have been received on the local port: Execute the display interface command and check for error packets. <Sysname> display interface ten-gigabitethernet 1/0/1 Ten-GigabitEthernet1/0/1 Current state: DOWN Line protocol state: DOWN IP packet frame type: Ethernet II, hardware address: 38ad-be30-b9bb Description: Ten-GigabitEthernet1/0/1 Interface Bandwidth: 10000000 kbps...
Page 44
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: Verify that packets are not mistakenly filtered out by ACLs: a.
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.
Command Description Displays whether an ACL has been successfully applied to an display packet-filter interface for packet filtering. display qos policy Displays user-defined QoS policy configuration information. Displays information about the QoS policies applied to an display qos policy interface interface or all interfaces.
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.
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 display ip routing-table Displays the routing table. display mac - address Displays MAC address entries Protocol flapping...
SMAC 8 IPV6_RIPNG SMAC 8 If the issue persists, contact H3C Support. When you contact H3C Support, provide diagnostic information if software-related packet loss occurred. VXLAN configuration failure Symptom On a switch that acts as a leaf node, the system displays "The operation is not supported." message when one of the following operations is performed: •...
This command will reboot the device. Continue? [Y/N]:y c. Verify the switch-mode configuration after the switch finishes startup. <Sysname> display switch-mode status Switch-mode in use: VXLAN MODE. Switch-mode for next reboot: VXLAN MODE. If the issue persists, contact H3C Support.
Need help?
Do you have a question about the S6520X-HI Series and is the answer not in the manual?
Questions and answers