ii
Troubleshooting ports ·················································································· 23
Fiber port remains in down state ······················································································································ 23
Symptom ·················································································································································· 23
Troubleshooting flowchart ························································································································ 23
Solution ···················································································································································· 24
Copper port remains in down state ·················································································································· 25
Symptom ·················································································································································· 25
Troubleshooting flowchart ························································································································ 25
Solution ···················································································································································· 25
Non-H3C transceiver module ··························································································································· 26
Symptom ·················································································································································· 26
Troubleshooting flowchart ························································································································ 26
Solution ···················································································································································· 26
Transceiver module does not support digital diagnosis ··················································································· 27
Symptom ·················································································································································· 27
Troubleshooting flowchart ························································································································ 28
Solution ···················································································································································· 28
Error frames (for example, CRC errors) on a port···························································································· 29
Symptom ·················································································································································· 29
Troubleshooting flowchart ························································································································ 29
Solution ···················································································································································· 29
Failure to receive packets ································································································································ 31
Symptom ·················································································································································· 31
Troubleshooting flowchart ························································································································ 31
Solution ···················································································································································· 31
Failure to send packets ···································································································································· 33
Symptom ·················································································································································· 33
Troubleshooting flowchart ························································································································ 33
Solution ···················································································································································· 33
Related commands ·········································································································································· 34
Troubleshooting system management ························································· 36
High CPU utilization ········································································································································· 36
Symptom ·················································································································································· 36
Troubleshooting flowchart ························································································································ 36
Solution ···················································································································································· 36
High memory utilization ···································································································································· 38
Symptom ·················································································································································· 38
Troubleshooting flowchart ························································································································ 38
Solution ···················································································································································· 38
Related commands ·········································································································································· 39
Troubleshooting other issues ······································································· 40
Layer 2 forwarding failure································································································································· 40
Symptom ·················································································································································· 40
Troubleshooting flowchart ························································································································ 41
Solution ···················································································································································· 41
Related commands ·································································································································· 45
Layer 3 forwarding failure································································································································· 46
Symptom ·················································································································································· 46
Troubleshooting flowchart ························································································································ 46
Solution ···················································································································································· 47
Related commands ·································································································································· 47
Protocol flapping ·············································································································································· 47
Symptom ·················································································································································· 47
Troubleshooting flowchart ························································································································ 48
Solution ···················································································································································· 48
Fan tray failure ················································································································································· 49
Symptom ·················································································································································· 49
Troubleshooting flowchart ························································································································ 49
Solution ···················································································································································· 49
Page 1: ...s 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 trademar...
Page 2: ...an tray failure 8 Symptom 8 Troubleshooting flowchart 8 Solution 8 Related commands 9 Troubleshooting ACL 10 ACL application failure with an error message 10 Symptom 10 Troubleshooting flowchart 10 So...
Page 3: ...31 Troubleshooting flowchart 31 Solution 31 Failure to send packets 33 Symptom 33 Troubleshooting flowchart 33 Solution 33 Related commands 34 Troubleshooting system management 36 High CPU utilization...
Page 4: ...iii Related commands 50...
Page 5: ...utput from the commands executed during the troubleshooting process To ensure safety wear an ESD preventive wrist strap when you replace or maintain a hardware component If hardware replacement is req...
Page 6: ...ollowing items Device status CPU status Memory status Configuration status Software entries Hardware entries Collecting common log messages 1 Save the common log messages from the log buffer to a log...
Page 7: ...tatistics by saving the statistics to a file or displaying the statistics on the screen When you collect operating statistics follow these guidelines Log in to the device through a network port or man...
Page 8: ...flash diag tar gz Done Sysname gunzip diag gz Decompressing file flash diag gz Done Display the content of the operating statistics file Sysname more diag display clock 05 26 01 UTC Tue 01 01 2020 Mo...
Page 9: ...The switch reboots unexpectedly when it is operating Troubleshooting flowchart Figure 1 Troubleshooting unexpected switch reboot Solution To resolve the issue 1 Verify that you can access the CLI afte...
Page 10: ...If the issue persists contact H3C Support Operating power module failure Symptom An operating power module fails Troubleshooting flowchart Figure 2 Troubleshooting operating power module failure Solu...
Page 11: ...r module Execute the display power command to verify that the power module has changed to Normal state If the power module remains in Fault state go to step c c Install the power module into an empty...
Page 12: ...power command to verify that the power module has changed to Normal state in the new slot If the power module remains in Absent state go to step 4 3 Remove and install the power module into an idle po...
Page 13: ...e information If the temperature continues to rise put your hand at the air outlet vents to feel if air is being expelled out of the air outlet b If no air is being expelled out of the air outlet vent...
Page 14: ...resolve the issue 1 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 2...
Page 15: ...trol plane display qos policy control plane slot slot number b If the QoS policy does not contain a class behavior association associate the traffic behavior with the traffic class c If the QoS policy...
Page 16: ...nfigure the packet filter If there is no configuration error go to step 2 2 Verify that the ACL is configured correctly Execute the display acl command to check whether the ACL is configured correctly...
Page 17: ...Sysname classifier count if match acl 3000 Sysname classifier count quit Sysname traffic behavior count Sysname behavior count accounting packet Sysname behavior count quit Sysname qos policy count S...
Page 18: ...roubleshooting ACLs Command Description display acl Displays configuration and match statistics for ACLs display diagnostic information Displays operating statistics for multiple feature modules in th...
Page 19: ...15 Command Description display traffic behavior user defined Displays traffic behavior configuration...
Page 20: ...16 Troubleshooting IRF This section provides troubleshooting information for common issues with IRF IRF fabric establishment failure Symptom An IRF fabric cannot be established...
Page 21: ...solved No Yes Yes No Yes No Yes You cannot add the device to the IRF fabric or complete IRF merge Yes No Member ID unique Modify IRF port bindings or reconnect physical interfaces Number of members fe...
Page 22: ...ends of an IRF link are the same type if you are using SFP or QSFP transceiver modules and fibers If the transceiver modules are not the same type replace them to be the same type Skip this step if y...
Page 23: ...ach IRF port has a minimum of one physical interface in up state display irf Displays IRF fabric information including the member ID role priority bridge MAC address and description of each IRF member...
Page 24: ...ation 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...
Page 25: ...rectly Bring all member ports up No Yes No Yes Operational key attribute configurations same as the reference port Set operational key attribute configurations same as the reference port No Yes Set th...
Page 26: ...in the aggregation group does not exceed the configured maximum number of Selected ports a Execute the link aggregation selected port maximum command to set the maximum number of Selected ports allow...
Page 27: ...o Yes No Yes No Yes Yes No No Yes Yes No No Yes Yes No No Yes Yes No Fiber port remains in down state Contact the support Resolved Speed duplex match on local and peer port Speed duplex match on trans...
Page 28: ...t fails Replace the local port with a new port operating correctly 4 Verify that the transceiver module and cable are operating correctly a Use the display transceiver alarm interface command to displ...
Page 29: ...port match the speed and duplex mode of the peer port a 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...
Page 30: ...hows that the transceiver module is not an H3C transceiver module Sysname display logbuffer Ten GigabitEthernet1 0 49 This transceiver is NOT sold by H3C H3C therefore shall NOT guarantee the normal f...
Page 31: ...abitEthernet1 0 49 transceiver device a0 register information 0000 03 04 07 00 00 00 02 00 0008 00 00 00 03 0d 00 64 00 0010 00 00 00 00 48 69 73 65 0018 6e 73 65 20 20 20 20 20 0020 20 20 20 20 00 00...
Page 32: ...isplay transceiver interface command to save the transceiver module information and contact H3C Support to verify that the transceiver module supports the digital diagnosis function Sysname display tr...
Page 33: ...cs changes more clearly b Use the display interface command to display the incoming packet statistics and outgoing packet statistics of the port c Determine the type of error frames that are accumulat...
Page 34: ...ting correctly 3 Verify that the port configurations are correct a Execute the display interface brief command b Determine whether the speed and duplex mode of the port match the speed and duplex mode...
Page 35: ...ontact 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 Tr...
Page 36: ...e and modify the STP related configurations to resolve the issue As a best practice configure the port as an edge port or disable STP on the port if it is directly connected to a terminal f If the por...
Page 37: ...display interface command to determine whether the number of outgoing packets is accumulating c Determine whether the number of error packets is accumulating 2 Verify that the port configurations do...
Page 38: ...the attribute configurations of the port to make the port become Selected 3 Verify that the port and the link medium are correct a Plug the link medium into another port that is operating correctly an...
Page 39: ...p brief Displays brief spanning tree status and statistics display transceiver alarm interface Displays the current transceiver module alarms display transceiver diagnosis Displays the present measure...
Page 40: ...resolve the issue 1 Execute the display cpu usage command multiple times to display CPU usage information Details not shown 2 Identify the job with a high CPU utilization Sysname display process cpu...
Page 41: ...and 5 minute intervals Typically the average CPU usage of a job is approximately 5 3 Display the job s stack The following example was created for job 14 in probe view Sysname system view Sysname prob...
Page 42: ...lay diagnostic information command to collect diagnostic information 5 Save the information displayed in the previous steps 6 Contact H3C Support High memory utilization Symptom The display memory com...
Page 43: ...4 0 0 656 0 12 2 0 0 MFW_FsCache 0 0 80 0 46 1 0 0 PBR_INSTANCENODE_cachep 0 0 160 4 21 1 0 0 kioctx 0 0 168 0 23 1 0 0 IPCIM_ENTRY_IPV4_cachep More Each value line shows the memory information for a...
Page 44: ...cs for jobs display system internal kernel memory pool Displays memory block usage statistics follow job job id Displays the stack of a job Troubleshooting other issues Layer 2 forwarding failure Symp...
Page 45: ...IP Packet Frame Type PKTFMT_ETHNT_2 Hardware Address 00e0 fc00 5139 Description GigabitEthernet1 0 17 Interface Bandwidth 100000kbps Loopback is not set Incoming error packets No Yes Yes Troubleshoot...
Page 46: ...0 aborts ignored parity errors Output total 0 packets 0 bytes 0 unicasts 0 broadcasts 0 multicasts 0 pauses Output normal 0 packets bytes 0 unicasts 0 broadcasts 0 multicasts 0 pauses Output 0 output...
Page 47: ...GE1 0 13 0 14 ge13 no no 0x4c 3 down GE1 0 14 0 13 ge12 no no 0x4d 3 down GE1 0 15 0 16 ge15 no no 0x4e 3 down GE1 0 16 0 15 ge14 no no 0x4f 3 up GE1 0 17 0 18 ge17 no no 0x50 3 down GE1 0 18 0 17 ge1...
Page 48: ...figured packets of users that fail to pass the portal authentication will be dropped by the port Use the display portal interface command to display the portal configuration information of the specifi...
Page 49: ...mitted information rate cbs committed burst size command Storm suppression Execute the display this command in Ethernet interface view to display the configuration of storm suppression Storm suppressi...
Page 50: ...ed to VLANs display smart link group Displays information about the specified or all smart link groups display stp Displays spanning tree status and statistics display this Displays the running config...
Page 51: ...n learn ARP entries again 3 Verify that route entries are correct a Execute the display ip routing table command to verify that route entries are correct If incorrect route entries exist troubleshoot...
Page 52: ...C 8 2 ESIS 0 0 0 100 S On SMAC 8 3 CLNP 0 0 0 100 S On SMAC 8 4 VRRP 0 0 0 1024 S On SMAC 8 5 UNKNOWN_IPV4MC 0 0 0 100 S On SMAC 8 6 UNKNOWN_IPV6MC 0 0 0 100 S On SMAC 8 7 IPV4_MC_RIP 0 0 0 150 D On S...
Page 53: ...tion To resolve the issue 1 Verify that the airflow direction of the fan tray is as configured a Identify the airflow direction of the fan tray You must install two fan trays of the same model for the...
Page 54: ...1 FAN 1 State Normal Wind Direction Port to Power Prefer Wind Direction Port to Power FAN 2 State Normal Wind Direction Port to Power Prefer Wind Direction Port to Power 2 If the fan tray still canno...
