HP 5920 series Troubleshooting Manual
Hide thumbs
Also See for 5920 series:
- Command reference manual (607 pages) ,
- Configuration manual (424 pages) ,
- Fc and fcoe configuration manual (257 pages)
Table of Contents
Advertisement
Quick Links
HP 5920 & 5900 Switch Series
Troubleshooting Guide
© Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained
herein is subject to change without notice. The only warranties for HP products and services are
set forth in the express warranty statements accompanying such products and services. Nothing
herein should be construed as constituting an additional warranty. HP shall not be liable for
technical or editorial errors or omissions contained herein.
Advertisement
Table of Contents
Troubleshooting
Related Manuals for HP 5920 series
Summary of Contents for HP 5920 series
-
Page 1: Troubleshooting Guide
Troubleshooting Guide © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. -
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 ... - Page 3 A 10/100/1000Base-T GE copper port or 1/10GBase-T 10-GE copper port fails to come up ························ 23 Symptom ································································································································································· 23 Troubleshooting flowchart ···································································································································· 23 Solution ··································································································································································· 23 Non-HP transceiver module error message ················································································································· 24 Symptom ································································································································································· 24 Troubleshooting flowchart ···································································································································· 24 Solution ··································································································································································· 24 ...
- Page 4 Symptom ································································································································································· 46 Troubleshooting flowchart ···································································································································· 47 Solution ··································································································································································· 47 Related commands ················································································································································ 48 ...
-
Page 5: Introduction
Introduction This document provides information about troubleshooting common software and hardware problems with the HP 5920 & 5900 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
Network and management ports are faster than the console port. Do not execute commands during operating statistics collection. • HP recommends saving operating statistics to a file to retain the information. • NOTE: The amount of time to collect statistics increases along with the number of IRF member devices. -
Page 8: Contacting Technical Support
===============display version=============== …… Contacting technical support If you cannot resolve a problem after using the troubleshooting procedures in this document, contact HP Support. When you contact an authorized HP support representative, be prepared to provide the following information: Information described in "General... -
Page 9: 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 HP Support. -
Page 10: Operating Power Supply Failure
Normal state in the new slot. If the power supply remains in Fault state, replace the power supply. If the problem persists, contact HP Support. Newly installed power supply failure Symptom A trap or log is generated indicating that a newly installed power supply is faulty. -
Page 11: Fan Tray Failure
Normal state in the new slot. If the power supply remains in Fault state, go to step 4. If the problem persists, contact HP Support. Fan tray failure Symptom A trap or log is generated indicating that an operating fan tray or a newly installed fan tray is faulty. -
Page 12: 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 HP Support. Related commands This section lists the commands that you might use for troubleshooting the hardware. -
Page 13: Troubleshooting Acl
If this field displays 0, the ACL hardware resources are exhausted. To free hardware resources, delete unnecessary ACLs. If the problem persists, contact HP 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 14: Troubleshooting Flowchart
Troubleshooting flowchart Figure 2 Troubleshooting ACL application failure Failure to apply an ACL QoS policy/packet filter Reconfigure QoS Resolved? configured correctly? policy/packet filter Reconfigure ACL Resolved? configured correctly? Contact the support 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 15: 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 HP 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 16: 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 17: Troubleshooting Flowchart
Troubleshooting flowchart Figure 3 Troubleshooting IRF fabric setup failure Solution To resolve the problem: Verify that the number of member devices does not exceed the upper limit. 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 18 Release 2307 and later versions—Nine. 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 a member ID that is not being used in the IRF fabric.
-
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 problem persists, contact HP Support. Related commands This section lists the commands that you might use for troubleshooting IRF. -
Page 20: 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 21: Troubleshooting Flowchart
More member ports than allowed max. number than or equal to allowed max. number of Resolved? of Selected ports? Selected ports Contact HP Support Solution To resolve the problem: Verify that all physical connections are correct. You can verify the physical connections against your network plan. -
Page 22: Related Commands
This makes sure all member ports you assign to the aggregation group can become Selected ports. If the problem persists, contact HP Support. Related commands This section lists the commands that you might use for troubleshooting Ethernet link aggregation. - Page 23 Commands Description Configure the maximum number of Selected ports link-aggregation selected-port maximum allowed in an aggregation group.
-
Page 24: 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. -
Page 25: Troubleshooting Flowchart
Troubleshooting flowchart Figure 5 Troubleshooting link up failure on a copper port A port failed to come up Speed/duplex match Configure matching Resolved? on local and peer port? speed/duplex Speed/duplex Configure matching match on transceiver module and Resolved? speed/duplex port? Local/peer port Replace local/peer port Resolved? - Page 26 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 HP transceiver module that matches the fiber port.
-
Page 27: A 10/100/1000Base-T Ge Copper Port Or 1/10Gbase-T 10-Ge Copper Port Fails To Come Up
A 10/100/1000Base-T GE copper port or 1/10GBase-T 10-GE copper port fails to come up Symptom A 10/100/1000Base-T GE copper port or 1/10GBase-T 10-GE copper port fails to come up. Troubleshooting flowchart Figure 6 Troubleshooting link up failure on a copper port Solution To resolve the problem: Verify that the speed and duplex mode of the local port match the speed and duplex mode of the... -
Page 28: Non-Hp Transceiver Module Error Message
If the problem persists, contact HP Support. Non-HP transceiver module error message Symptom The output from the display logbuffer command shows that the transceiver module is not an HP transceiver module. <Sysname> display logbuffer Ten-GigabitEthernet1/0/5: This transceiver is NOT sold by HP. HP therefore shall NOT... -
Page 29: Transceiver Module Does Not Support Digital Diagnosis
Digital Diagnostic Monitoring : YES Vendor Name : HP If the vendor name field does not display HP, replace the transceiver module with an HP transceiver module. If the vendor name field displays HP, perform the following tasks: Execute the display transceiver register interface command for Release 22xx and execute −... -
Page 30: Troubleshooting Flowchart
Execute the display transceiver interface command to view the vendor name of the transceiver module. If the vendor name field does not display HP, replace the transceiver module with an HP transceiver module. If the vendor name field displays HP, perform the following tasks: Execute the display transceiver manuinfo interface command to save the transceiver −... -
Page 31: 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 9 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 32 (Optional.) Use the reset counter interface command in user view 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. Use the display interface command to display the incoming packet statistics and outgoing packet statistics of the port.
-
Page 33: 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 HP Support. Failure to receive packets Symptom A port is up, but it cannot receive packets. -
Page 34: Solution
If the port is set to the discarding state by the spanning tree feature, examine and modify the spanning tree feature configurations to resolve the problem. HP 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 35: Failure To Send Packets
Failure to send packets Symptom A port is up, but it cannot send packets. Troubleshooting flowchart Figure 11 Troubleshooting failure to send 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. -
Page 36: Related Commands
If the port is set to the discarding state by the spanning tree feature, examine and modify the spanning tree feature configurations to resolve the problem. HP recommends that you configure the port as an edge port or disable the spanning tree feature on the port if it is directly connected to a terminal. - Page 37 Command Description Displays the key parameters of transceiver display transceiver interface modules. Displays electronic label information for the display transceiver manuinfo interface transceiver module in an interface.
-
Page 38: 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 12 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 39 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 40: High Memory Utilization
[<80379b24>] schedule+0x954/0x1270 [<80199e5c>] watchdog+0xac/0x440 [<8016fd88>] kthread+0xe8/0x120 [<801221f0>] kernel_thread_helper+0x10/0x20 Save the information displayed in the previous steps. Contact HP Support. High memory utilization Symptom The memory utilization of the device is higher than 60% for more than 30 minutes. Troubleshooting flowchart... -
Page 41: Related Commands
Save the information displayed in the previous step. Contact HP Support. IMPORTANT: HP recommends not rebooting the device before you contact HP 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 42: Troubleshooting Other Problems
Command Description Displays memory block usage statistics. This command is available in one of the following views: display system internal kernel memory pool • Hide view—For Release 22xx. • Probe view—For Release 2307 or later. Displays the stack of a job. This command is available in one of the following views: follow job job-id •... -
Page 43: Troubleshooting Flowchart
Troubleshooting flowchart Figure 14 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> display interface Ten-GigabitEthernet1/0/36 Ten-GigabitEthernet1/0/36 current state: UP Line protocol state: UP IP Packet Frame Type: PKTFMT_ETHNT_2, Hardware Address: 000f-e200-002b... - Page 44 If the problem persists, contact HP Support. When you contact HP Support, provide the following diagnostic information if packet loss occurs on the chip port with which the interface is associated: # In Release 22xx, use the en_diag command to enter en_diag view. In Release 2307 and later versions, use the probe command to enter probe view.
- Page 45 XGE1/0/14 xe13 down XGE1/0/15 xe14 down The output shows that Ten-GigabitEthernet 1/0/1 is associated with chip port xe0. # Execute the bcm 1 0 show/c/xe0 command to check the RDBGC and TDBGC fields for Rx and Tx dropped packet statistics, respectively. The statistics displayed were generated between the last and the current execution of the command.
-
Page 46: Related Commands
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. HP recommends disabling STP on the port, or configuring the port as an edge port if the port is connected to a terminal device. -
Page 47: Layer 3 Forwarding 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. Displays user-defined QoS policy configuration display qos policy information. Displays information about the QoS policies applied display qos policy interface to an interface or all interfaces. -
Page 48: Troubleshooting Flowchart
Troubleshoot route Route entries are correct? Resolved? entries Contact HP Support 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"... -
Page 49: 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 HP Support. Related commands This section lists the commands that you might use for troubleshooting Layer 3 forwarding failure. -
Page 50: Solution
SMAC 8 UNKNOWN_IPV6MC SMAC 8 IPV4_MC_RIP SMAC 8 IPV4_BC_RIP SMAC 8 If the problem persists, contact HP Support. When you contact HP Support, provide diagnostic information if software-related packet loss occurred. Fan failure Symptom The fans do not operate correctly. -
Page 51: Troubleshooting Flowchart
Troubleshooting flowchart Figure 17 Flowchart for troubleshooting fan failure Fan failure Display fan operating status Preferred airflow direction Change the preferred Resolved? is the fan airflow direction? airflow direction Fans are damaged? Replace the fan tray Resolved? Contact the support Solution To resolve the problem: Verify that the preferred airflow direction specified for the fans is the same as the airflow direction... -
Page 52: 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 HP Support. Related commands This section lists the commands that you might use for troubleshooting fans.