Table of Contents
Troubleshooting
Related Manuals for HPE FlexNetwork 5130 Series
Summary of Contents for HPE FlexNetwork 5130 Series
-
Page 1: Troubleshooting Guide
HPE FlexNetwork 5130 EI Switch Series Troubleshooting Guide Part number: 5200-1218 Document version: 6W102-20160429 The information in this document is subject to change without notice. © Copyright 2016 Hewlett Packard Enterprise Development LP... -
Page 2: Table Of Contents
Symptom ···················································································································································· 4 Troubleshooting flowchart ·························································································································· 5 Solution ······················································································································································ 5 Operating power supply failure on the HPE FlexNetwork 5130 24G SFP 4SFP+ EI Switch (JG933A) ············· 6 Symptom ···················································································································································· 6 Solution ······················································································································································ 6 Newly-installed power supply failure on the HPE FlexNetwork 5130 24G SFP 4SFP+ EI Switch (JG933A) ···· 6 ... - Page 3 Related commands ·········································································································································· 21 Troubleshooting other problems ··································································· 22 Layer 2 forwarding failure ································································································································ 22 Symptom ·················································································································································· 22 Troubleshooting flowchart ························································································································ 22 Solution ···················································································································································· 22 Related commands ·································································································································· 26 Layer 3 forwarding failure ································································································································ 27 ...
-
Page 4: Introduction
For configuration recovery, regularly back up the configuration to a remote server. When you troubleshoot HPE FlexNetwork 5130 EI switches, follow these general guidelines: • To help identify the cause of the problem, collect system and configuration information, including: Symptom, time of failure, and configuration. -
Page 5: Collecting Common Log Messages
Category File name format Content Diagnostic log messages about device operation, including the following items: • Parameter settings used when an error occurs. Diagnostic log diagfile.log • Information about a card startup error. • Handshaking information between member devices when a communication error occurs. -
Page 6: Collecting Operating Statistics
# Display the diagnostic log file on the master device. <Sysname> dir flash:/diagfile/ Directory of flash:/diagfile 0 -rw- 161321 Jul 11 2013 16:16:00 diagfile.log 524288 KB total (36944 KB free) # Display the diagnostic log file on each subordinate device: <Sysname>... -
Page 7: Contacting Technical Support
Technical support registration numbers (if applicable). This information will help the support engineer assist you as quickly as possible. The following is the contact of Hewlett Packard Enterprise Support for networking products: www.hpe.com/support/hpesc Troubleshooting hardware This section provides troubleshooting information for common hardware problems. -
Page 8: Troubleshooting Flowchart
Troubleshooting flowchart Figure 1 Troubleshooting an unexpected switch reboot The switch reboots unexpectedly Can the CLI be accessed? Collect diagnostic Is the system software messages image correct? Reload the system software image Contact the Problem resolved? support Solution To resolve the problem: Verify that you can access the CLI after the switch reboots. -
Page 9: Operating Power Supply Failure On The Hpe Flexnetwork 5130 24G Sfp 4Sfp+ Ei Switch (Jg933A)
Operating power supply failure on the HPE FlexNetwork 5130 24G SFP 4SFP+ EI Switch (JG933A) Symptom A trap or log is generated indicating that an operating power supply is faulty. Solution To resolve the problem: Execute the display power command to display power supply information. -
Page 10: Solution
Solution To resolve the problem: Execute the display power command to display power supply information. <Sysname> display power Slot 1: PowerID State Mode Current(A) Voltage(V) Power(W) Normal Fault If the power supply is in Absent state, go to step 2. If the power supply is in Fault state, go to step 3. -
Page 11: Related Commands
Related commands This section lists the commands that you might use for troubleshooting the hardware. Command Description Displays information about files and directories. Displays current configuration files and system software display boot-loader images. display environment Displays temperature information. display fan Displays the operating states of the fixed fan. -
Page 12: Troubleshooting Acl
Troubleshooting ACL This section provides troubleshooting information for common problems with ACLs. ACL application failure with an error message Symptom The system fails to apply a packet filter or an ACL-based QoS policy to the hardware. It also displays the "Reason: Not enough hardware resource" message. Solution To resolve the problem: Execute the display qos-acl resource command, and then check the Remaining field for ACL... -
Page 13: Solution
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: a. Use one of the following commands to check the QoS policy for configuration errors, depending on the policy application destination: Destination Command... - Page 14 Command Description Displays whether an ACL has been successfully applied to display packet-filter an interface for packet filtering. display qos-acl resource Displays QoS and ACL resource usage. Displays information about the QoS policies applied to the display qos policy control-plane specified control plane.
-
Page 15: 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. Troubleshooting flowchart Figure 3 Troubleshooting an IRF fabric establishment failure... -
Page 16: Solution
Solution To resolve the problem: Verify that the number of member devices does not exceed the upper limit (varies by software version). 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 17: Related Commands
save the configuration before you execute the irf-port-configuration active command. Verify that all member devices use the same software version: a. Execute the display version command to identify the software version of each member device. b. Upgrade the software of all member devices to the same version. NOTE: Typically, the irf auto-update enable command can automatically synchronize a member device with the software version of the master device. -
Page 18: 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 19: Troubleshooting Flowchart
Troubleshooting flowchart Figure 4 Troubleshooting a link aggregation failure Aggregation failed Are all physical connections correct? Connect physical links correctly Resolved? Are all member ports up? Bring all member ports up Resolved? Set operational key/attributes Operational key/attributes same as the Resolved? same as the reference port reference port? -
Page 20: Related Commands
a. Execute the display link-aggregation verbose command to display the Selected state of the member ports. b. Execute the display current-configuration interface command to display the configurations of the aggregate interface and the Unselected ports. c. Configure the Unselected ports to make sure they have the same operational key and attribute configurations as the reference port. -
Page 21: Troubleshooting Ports
Troubleshooting ports This section provides troubleshooting information for common port problems. A 10-GE SFP+ fiber port or GE SFP fiber port fails to come up Symptom A 10-GE SFP+ fiber port or GE SFP fiber port fails to come up. Troubleshooting flowchart Figure 5 Troubleshooting a link up failure on a fiber port A fiber port failed to come up... -
Page 22: Solution
If the transceiver module is not operating correctly, replace it with an HPE transceiver module that matches the fiber port. -
Page 23: A 10/100/1000Base-T Ge Copper Port Fails To Come Up
A 10/100/1000Base-T GE copper port fails to come up Symptom A 10/100/1000Base-T GE copper port fails to come up. Troubleshooting flowchart Figure 6 Troubleshooting a link up failure on a copper port A copper port failed to come up Speed/duplex match Configure matching Resolved? on local and peer port? -
Page 24: Related Commands
Related commands This section lists the commands that you might use for troubleshooting ports. Command Remarks Displays or saves running status data for display diagnostic-information multiple feature modules. display interface brief Displays brief interface information. Displays alarms present on transceiver display transceiver alarm interface modules. -
Page 25: 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 7 Troubleshooting a Layer 2 packet loss failure Layer 2 packet loss Troubleshoot the Incoming error packets? - Page 26 Verify that no error packets have been received on the local port: a. Execute the display interface command and check for error packets. <Sysname> display interface Ten-GigabitEthernet1/0/36 GigabitEthernet1/0/25 Current state: UP Line protocol state: UP IP Packet Frame Type: PKTFMT_ETHNT_2, Hardware Address: 5cdd-70b1-81a8 ……...
- Page 27 GE1/0/5 ge20 down GE1/0/6 ge21 down GE1/0/7 ge22 down GE1/0/8 ge23 down GE1/0/9 down GE1/0/10 down GE1/0/11 down GE1/0/12 down GE1/0/13 down GE1/0/14 down GE1/0/15 down GE1/0/16 0x10 down GE1/0/17 0x11 down GE1/0/18 0x12 down GE1/0/19 ge10 0x13 down The output shows that GigabitEthernet 1/0/1 is associated with chip port ge16. # Execute the bcm slot 1 0 chip show/c/ge16 command to check the RDBGC and TDBGC fields for Rx and Tx dropped packet statistics, respectively.
- Page 28 − The IP source guard feature creates ACLs automatically. Execute the display this command in Ethernet interface view to verify that the ip source binding or ip verify source command is configured on the port. To display source guard binding entries, execute the display ip source binding or display ipv6 source binding command.
-
Page 29: Related Commands
suppression, multicast suppression, and unknown unicast suppression. To adjust the suppression thresholds, execute the broadcast-suppression, multicast-suppression, and unicast-suppression commands. Verify that no congestion occurs by using the display qos queue interface command. If congestion occurs, locate and resolve the problem by referencing related congestion management documents. -
Page 30: Layer 3 Forwarding Failure
Layer 3 forwarding failure Symptom Packet loss occurs when the switch forwards packets to a different network. Troubleshooting flowchart Figure 8 Troubleshooting a Layer 3 forwarding failure Layer 3 packet loss Troubleshoot the Resolved? The port is faulty? port Troubleshoot ARP Resolved? ARP entries are correct? entries... -
Page 31: Related Commands
a. Execute the display ip routing-table command to verify that route entries are correct. If incorrect route entries exist, troubleshoot the protocol that learns the route entries. b. Execute the display fib command to verify that the output interfaces in the FIB entries and route entries are the same. -
Page 32: Troubleshooting Flowchart
Troubleshooting flowchart Figure 9 Troubleshooting protocol flapping Layer 3 protocol flapping Troubleshoot the Layer 2 packet loss occurs? Resolved? problem Troubleshoot the Layer 3 packet loss occurs? Resolved? problem Collect diagnostic Software-related information packet loss occurs? Contact the support Solution To resolve the problem: Verify that Layer 2 is operating correctly, as described in "Layer 2 forwarding... - Page 33 When you contact Hewlett Packard Enterprise Support, provide diagnostic information if software-related packet loss occurred.
Need help?
Do you have a question about the FlexNetwork 5130 Series and is the answer not in the manual?
Questions and answers