HP 5800 & 5820X Switch Series Troubleshooting Guide

Transcription

1 HP 5800 & 5820X Switch Series Troubleshooting Guide Copyright 2013 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. thing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Part number:

2 Contents Introduction 1 Troubleshooting ACL 1 ACL application failure with an error message 1 Symptom 1 Solution 1 ACL application failure without an error message 1 Symptom 1 Troubleshooting flowchart 2 Solution 2 Related commands 3 Troubleshooting IRF 4 IRF fabric establishment failure 4 Symptom 4 Troubleshooting flowchart 5 Solution 6 Related commands 7 Troubleshooting Ethernet link aggregation 8 Link aggregation failure 8 Symptom 8 Troubleshooting flowchart 9 Solution 9 Related commands 10 Troubleshooting ports 13 Link up failure on a port 13 Symptom 13 Troubleshooting flowchart 13 Solution 13 Related commands 15 Troubleshooting other problems 16 High CPU usage 16 Symptom 16 Troubleshooting flowchart 16 Solution 16 Related commands 17 Layer 2 forwarding failure 17 Symptom 17 Troubleshooting flowchart 18 Solution 18 Related commands 21 Layer 3 forwarding failure 22 Symptom 22 Troubleshooting flowchart 22 Solution 22 Related commands 23 SFP+ port not coming up 23 Symptom 23 i

3 Troubleshooting flowchart 23 Solution 24 Related commands 24 PoE power supply anomaly 24 Symptom 24 Troubleshooting flowchart 25 Solution 25 Related commands 27 ii

4 Introduction This document is not specific to any software version or device model. Troubleshooting ACL This section provides troubleshooting information for common problems with ACLs. ACL application failure with an error message Symptom Solution The system fails to apply a packet filter or ACL-based classifiers in a QoS policy to the hardware. It also displays the "Reason: t enough hardware resource" message. To resolve this problem: 1. Execute the display 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. To free hardware resources, remove unused packet filters or ACL-based classifiers from QoS policies. 3. If the problem persists, contact HP Support. ACL application failure without an error message Symptom The system applies a packet filter or a QoS policy that contains ACLs to the hardware. However, the ACL does not take effect. 1

5 Troubleshooting flowchart Figure 1 Troubleshooting an ACL application failure Failed to apply an ACL QoS policy/packet filter configured correctly? Reconfigure QoS policy/packet filter Problem resolved? ACL rule configured correctly? Reconfigure ACL rule Problem resolved? Contact HP Support Problem is resolved 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: 1. 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 Interface VLAN Global Control plane Command display qos policy interface display qos vlan-policy display qos policy global 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 contains a class-behavior association, execute the display traffic classifier user-defined command and the display traffic behavior user-defined command to check for traffic class and behavior configuration errors, respectively. If they are configured incorrectly, reconfigure them. If they are configured correctly, go to Step 2. 2

6 2. Verify that the ACL is configured correctly. Execute the display acl command to check whether the ACL is configured correctly. If the ACL is configured incorrectly, reconfigure it. If the ACL is configured correctly but the problem persists, contact HP Support. 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: 1. Verify that the packet filter configuration is correct: a. Execute the display packet-filter command. b. If there are any configuration errors, reconfigure the packet filter. 2. Verify that the ACL configuration is correct: a. Execute the display acl command. b. If there are any configuration errors, reconfigure the ACL. 3. If the problem persists, contact HP Support. Related commands This section lists the commands that you might use for troubleshooting ACLs. Command display acl resource display qos policy interface display qos vlan-policy display qos policy global display qos policy control-plane display traffic classifier user-defined display traffic behavior user-defined display packet-filter Description Displays information about hardware resources for ACL applications. Displays information about the QoS policies applied to an interface or to all interfaces. Displays information about QoS policies applied to VLANs. Displays information about global QoS policies. Displays information about the QoS policies applied to the specified control plane. Displays traffic class configurations. Displays traffic behavior configurations. Displays whether an ACL has been successfully applied to an interface for packet filtering. 3

7 Troubleshooting IRF This section provides troubleshooting information for common problems with IRF. IRF fabric establishment failure Symptom An IRF fabric cannot be established. 4

8 Troubleshooting flowchart Figure 2 Troubleshooting IRF fabric establishment failure IRF fabric setup failed (1) IRF fabric size allowed? Remove excess member chassis Resolved (2) t resolved All member IDs are unique? Change member IDs Resolved (3) t resolved Physical IRF connections consistent with IRF port bindings? Modify bindings or reconnect physical ports Resolved (4) t resolved 10-Gbps IRF links used? Replace with 10 Gbps or SFP+ transceiver modules/cables Resolved (5) t resolved IRF links up? Bring up physical ports/activate IRF port configuration Resolved (6) t resolved All chassis use same software version? Upgrade software version to be the same Resolved t resolved (7) Software versions compatible? Upgrade software Resolved (8) t resolved Contact HP Support End 5

9 Solution To resolve the problem: 1. Verify that the number of member chassis does not exceed the upper limit (nine). If you are adding new chassis to an existing IRF fabric, use the display irf command to identify the number of member chassis already in the chassis. 2. Verify that the member ID of each member chassis is unique: a. Execute the display irf configuration command to view the member ID of each chassis. b. If two member chassis use duplicate IDs, assign a unique member ID to each member. 3. Verify that the physical IRF links are connected correctly: IMPORTANT: When you connect two neighboring IRF members, you must connect the physical ports of IRF-port 1 on one member to the physical ports of IRF-port 2 on the other. a. Execute the display irf configuration command on each member chassis, and check the IRF-Port1 and IRF-Port2 fields for IRF port bindings. b. Verify that the physical IRF connections are consistent with the IRF port bindings. c. If there are inconsistencies, reconfigure the IRF port bindings or reconnect the physical IRF ports. 4. Verify that IRF links are 10 Gbps: a. Verify that the transceiver modules or cables for IRF connection are labeled with 10Gbps or SFP+. b. Replace a transceiver module or cable if it is not for 10 Gbps connection. 5. Verify that all IRF links are up: a. Execute the display irf topology command, and then check the Link field. b. If the Link field for an IRF port displays DOWN, execute the display interface command, and then check the current state field. If all physical ports bound to the IRF port are down, bring them up. If the IRF port has at least one physical port in up state, proceed to the next step. c. Save the configuration, and then execute the irf-port-configuration active command in system view to activate the IRF port configuration. IMPORTANT: Activating IRF port configuration requires a reboot. To prevent configuration loss, you must save the configuration before you execute the irf-port-configuration active command. 6. Verify that all member chassis 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 chassis to the same version. 6

10 NOTE: Typically the irf auto-update enable command can automatically synchronize a member chassis with the software version of the master chassis. However, the synchronization might fail when the gap between the software versions is large. 7. If the problem persists, contact HP Support. Related commands This section lists the commands that you might use for troubleshooting IRF. Command display interface display irf display irf configuration display irf topology display version irf-port-configuration active Description Displays interface information. Use this command to verify that each IRF port has at least one physical port in up state. Displays IRF fabric information, including the member ID, role, priority, bridge MAC address, and description of each IRF member. Displays basic IRF settings, including the current member ID, new member ID, and physical ports bound to the IRF ports on each IRF member device. The new member IDs take effect at reboot. Displays the IRF fabric topology, including the member IDs, IRF port state, and adjacencies of IRF ports. Displays system version information. Activates IRF configuration on IRF ports. 7

11 Troubleshooting Ethernet link aggregation This section provides troubleshooting information for common problems with Ethernet link aggregation. Link aggregation failure Symptom Link aggregation does not operate correctly. 8

12 Troubleshooting flowchart Figure 3 Troubleshooting link aggregation failure Link aggregation failed Are all physical connections correct? Connect physical links correctly Are all member ports up? Bring all member ports up Attribute configurations/class-two configurations same as the reference port? Set attribute configurations/class-two configurations same as the reference port Link aggregation in dynamic mode? Attribute configurations/class-two configurations of the peer ports same as the peer port of the reference port? Set attribute configurations/class-two configurations of the peer ports same as the peer port of the reference port More than 8 member ports? Set no more than 8 member ports Contact HP Support End Solution To resolve the problem: 1. Verify that all physical connections are correct. You can verify the physical connections against your network plan. 2. Verify that all member ports are up: 9

13 a. Execute the display interface command to display the status of the member ports. b. If the member ports are down, follow the solution in "Link up failure on a port" to troubleshoot the problem. 3. Verify that the member ports have the same attribute configurations and class-two configurations as the reference port: a. Execute the display current-configuration interface command to display the configurations of the aggregate interface and the member ports. b. Configure the member ports to make sure they have the same attribute configurations and class-two configurations as the reference port. 4. Identify the aggregation mode of the aggregation group. If the aggregation mode is static, proceed to step 6. If the aggregation mode is dynamic, proceed to step Verify that the peer member ports have the same attribute configurations and class-two configurations as the peer port of the reference port: a. Execute the display current-configuration interface command on the peer device to display the configurations of the peer member ports. b. Configure the peer member ports to make sure the peer ports have the same attribute configurations and class-two configurations as the peer port of the reference port. 6. Verify that the number of member ports in the aggregation group does not exceed eight. a. Execute the display link-aggregation verbose command to verify that the number of member ports does not exceed eight. If the number of member ports exceeds eight, the ports with higher port numbers are in Unselected state. b. Use the undo port link-aggregation group command to remove undesired member ports from the aggregation group. This makes sure all member ports you assign to the aggregation group can become Selected. 7. If the problem persists, contact HP Support. Related commands This section lists the commands that you might use for troubleshooting Ethernet link aggregation. Commands display current-configuration interface display interface display link-aggregation verbose Description Displays interface configuration. Displays Ethernet interface information. Display detailed information about the aggregation groups that correspond to the Layer 2 or Layer 3 aggregate interfaces. 10

14 Troubleshooting ports This section provides troubleshooting information for common problems with ports. Link up failure on a port Symptom A port cannot go up when the port is connected to another port. Troubleshooting flowchart Figure 4 Troubleshooting link up failure on a port A port failed to go up Physically connected? Check the port connection Shut down? undo shutdown Cable is correct or transceiver module matches wavelength? Replace the cable or fiber Subcard is operating correctly if the interface is on a subcard? Install the subcard again or replace a subcard Enable internal loopback testing to examine the physical port Contact HP Support Resolved Solution To resolve the problem: 13

15 1. Verify that the physical connection of the port is correct: a. Unplug and then plug in the network cable of the port. b. Verify that the port is up. 2. Verify that the port is not shut down: a. Execute the display interface brief command. b. Check whether ADM appears in the second column of the output for the port. c. If ADM appears, use the undo shutdown command to bring up the port. 3. Verify that the speed and duplex mode of the port match those of the peer port: a. Execute the display interface brief command. b. Check whether the speed and duplex mode of the port match those of the peer port. c. If they do not match, use the speed command and the duplex command to set the speed and duplex mode for the port. 4. Examine the network cable quality or verify that the transceiver module type of the fiber port matches the wavelength: a. Replace the network cable with a new one, and verify that the port is up. b. If the port is a fiber port, verify that the transceiver module type of the fiber port matches the wavelength. If the transceiver module information is not on the label, use the display transceiver interface command to display the transceiver module information. <Sysname>display transceiver interface ten-gigabitethernet 1/1/1 Ten-GigabitEthernet1/1/1 transceiver information: Transceiver Type Connector Type : 10G_BASE_SR_SFP : LC Wavelength(nm) : 850 Transfer Distance(m) Digital Diagnostic Monitoring : YES Vendor Name Ordering Name : 80(50um),30(62.5um) : FINISAR CORP. : SFP_XGE_SX-MM If the port is on a subcard, verify that the subcard is operating correctly: a. Execute the display device command. b. Check whether rmal appears in the last column of the output for the subcard. c. If rmal does not appear in the last column, re-plug in the subcard or replace the subcard with a subcard of the same model. [Sysname-GigabitEthernet1/0/2]display device Slot 1 SubS PortNum PCBVer FPGAVer CPLDVer BootRomVer AddrLM Type State 0 52 Ver.B NULL IVL MAIN rmal 1 4 Ver.A NULL 002 NULL IVL LSW1SP4P0 rmal 2 16 Ver.A NULL 001 NULL IVL LSW1GP16P0 rmal 3 1 Ver.A NULL 000 NULL IVL LSWM1IPS10 rmal 6. Enable internal loopback testing on the port to verify that the physical port is operating correctly. [Sysname-GigabitEthernet1/0/2]loopback internal %Apr 26 12:40:25: CPWR IFNET/4/LINK UPDOWN: GigabitEthernet1/0/2: link status is UP 14

16 %Apr 26 12:40:25: CPWR IFNET/4/LINK UPDOWN: GigabitEthernet1/0/2: link status is DOWN Loop internal succeeded! 7. If the problem persists, contact HP Support. Related commands This section lists the commands that you might use for troubleshooting ports. Command display device display interface brief display transceiver interface loopback internal Description Displays device information. Displays brief interface information. Displays key parameters of the transceiver module installed in an interface. Enables loopback testing on an Ethernet interface. 15

17 Troubleshooting other problems High CPU usage Symptom The display cpu command shows that the CPU usage is high. Troubleshooting flowchart Figure 5 Troubleshooting high CPU usage High CPU usage Locate the tasks that are using CPU resources Analyze the tasks that are using CPU resources Problem solved? Y End N Contact HP Support Solution To resolve the problem: 1. Locate the tasks that are using CPU resources. Use the display cpu-usage task [ slot slot id ] command in hidden view to display CPU usage information on cards. Locate the tasks that are using CPU resources. 2. Analyze the tasks that are using CPU resources. The following are common tasks that use CPU resources: brx1 and brx2 If these tasks are using CPU resources, the switch might be receiving large amounts of packets that need to be forwarded to the CPU. Do the following: 16

18 MSTP Use the display interface command to see whether interfaces have received large amounts of broadcast packets. Check whether a loop exists on the network. If a loop exists, examine the connections between the devices. Use the display stp bpdu-statistics interface command to view the statistics for received and sent BPDU packets on ports. Examine the counts of TCN/TC packets. If the switch receives a large quantity of TCN/TC packets generated by STP, the switch has to delete MAC address entries frequently. This results in high CPU usage. AGNT Examine the network management software. Frequent MIB information browsing might result in high CPU usage. ROUT Use the display ip routing-table command to examine route changes. Route flapping might cause high CPU usage. L2X0 or L2X1 MAC address synchronization Examine whether the network topology is stable. If the network topology is not stable, the device has to use a lot of CPU resources to update its MAC address entries frequently. 3. If the problem persists, contact HP Support. Related commands This section lists the commands that you might use for troubleshooting high CPU usage. Command _hidecmd display cpu-usage task [ slot slot id ] display interface display ip routing-table display stp bpdu-statistics interface Description Enters hidden view. Displays CPU usage information. This command is available in hidden view. Displays Ethernet interface information. Displays brief information about active routes in the routing table. Displays the BPDU statistics for a port. Layer 2 forwarding failure Symptom Layer 2 packet loss occurs between two devices on the same network segment and in the same VLAN. 17

19 Troubleshooting flowchart Figure 6 Troubleshooting Layer 2 packet loss failure Layer 2 packet loss Incoming error packets? Locate the reasons of the failure Packets filtered by ACLs or QoS policies? Locate the reasons and solve the failure Port blocked? Locate the reasons and solve the failure Port misconfigurations? Locate and modify misconfigurations Port congestion? Locate and solve congestion Contact HP Support End Solution To solve the problem: 1. Verify that no error packets have been received on the local port: a. Execute the display interface command and check for error packets. <HP>display interface GigabitEthernet1/0/36 GigabitEthernet1/0/36 current state: UP IP Packet Frame Type: PKTFMT_ETHNT_2, Hardware Address: 000f-e b Last 300 seconds output: 0 packets/sec 10 bytes/sec 0% Input (total): 57 packets, 7838 bytes 0 unicasts, 50 broadcasts, 2 multicasts, 0 pauses Input (normal): 52 packets, - bytes 18

20 0 unicasts, 50 broadcasts, 2 multicasts, 0 pauses Input: 5 input errors, 0 runts, 0 giants, 0 throttles 5 CRC, 0 frame, - overruns, 0 aborts - ignored, - parity errors b. If the statistics are not zero, the following failures might occur: Interface hardware failure To test such a failure, connect the cable that is connected to the local port to a correctly operating port (for example, Port A) with the same configurations as the local port. If Port A forwards traffic correctly, you can determine that the hardware of the local port fails. In this event, you must replace the local port with a correctly operating port. Transceiver module, fiber, or twisted pair failure To test and solve such a failure, replace the transceiver module, fiber, or twisted pair with a good one. Inconsistent configurations Verify that the configurations (such as speed and duplex mode) of the peer are consistent with the local port. If they are inconsistent, modify the configurations of the local port. c. If the problem persists, contact HP Support. 2. Verify that packets are not mistakenly filtered out by ACLs: a. Examine the ACL and QoS policy configuration for packet filtering on the port, on the VLAN of the port, or globally. If packets are mistakenly filtered out, modify the ACL or QoS policy configuration. To display the ACL configuration on the port for packet filtering, execute the display packet-filter command. To display the QoS policy configuration on the port, execute the display qos policy command. To display the QoS policy configuration on the VLANs of the port, execute the display qos vlan-policy command. To display the global QoS policy configuration, execute the display qos policy global command. b. Examine whether packets are filtered out by automatically created ACLs. The following features automatically create ACLs: IP source guard Configured by using the ip source binding or ip verify source command. To display source guard binding entries, execute the display ip source binding or display ipv6 source binding command. If IP source guard is configured but the packets match no entry, further troubleshoot the problem based on the way the binding entries are created. Portal authentication When portal authentication is configured, the port discards the packets of unauthenticated users. To display the portal configuration of the port or the VLANs of the port, execute the display portal interface command. To cancel the portal configuration on the port, execute the undo portal command in Layer 2 Ethernet interface view. To cancel the portal configuration on the VLAN of the port, execute the undo portal server server-name command on the corresponding VLAN interface. EAD fast deployment When EAD fast deployment is enabled, the port discards packets of unauthenticated users except when the users only access a free IP. To display whether EAD fast deployment is enabled on the port, execute the display dot1x command. MFF To display the MFF configuration information of the VLAN to which the port belongs, execute the display mac-forced-forwarding vlan command. If the output does 19

21 not contain the gateway information, examine whether the ARP snooping or DHCP snooping configuration is correct. 3. Verify that the port is not blocked: Execute the display stp brief command to determine whether STP sets 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. If the port belongs to an aggregation group, execute the display link-aggregation verbose command to identify the port status. When the port is an Unselected port, it cannot forward traffic. Locate the reasons why the port is in Unselected state. For example, the attribute configurations of the port are different from the configurations of the reference port. Execute the display rrpp verbose command to determine whether the port is down or RRPP sets the state of the port to blocked. When the port is in down or blocked state, it cannot forward traffic. If the port is in down state, examine whether the port is physically or administratively shut down. If the port is in blocked state, find the reasons. For example, the roles of the primary and secondary port on the master node are reversed, or the broadcast storm suppression mechanism blocks the port because SRPT failure occurs in a multi-homed subring. Execute the display smart-link group command to determine whether Smart Link sets the state of the port to standby or down. When the port is in standby or down state, it cannot forward traffic. If the port is in standby state, set the port as the primary port. If the port is in down state, the follow reasons might apply, and further troubleshooting is required: The uplink device is configured with Monitor link, and its uplink is down. The link between the local port and its peer fails. The local port is administratively shut down. 4. Examine the following configurations that might cause packet loss: VLAN configuration Execute the display this command in Ethernet interface view to display whether the port is in the VLAN of the packets. If not, add the port to the VLAN. Blackhole MAC address entries Execute the display mac-address blackhole command to display blackhole MAC address entries. If the packets are discarded because they match a blackhole MAC address entry, delete the entry. To delete the blackhole MAC address entry, execute the undo mac-address blackhole mac-address vlan vlan-id command. Rate limit Execute the display qos lr interface command to display the rate limit configuration on the port. If rate limit is configured on the port, make sure the committed information rate (CIR) and the committed burst size (CBS) are appropriate. To adjust the CIR and CBS values, execute the qos lr { inbound outbound } cir committed-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 suppression includes broadcast suppression, multicast suppression, and unknown unicast suppression. To adjust the suppression thresholds, execute the broadcast-suppression, multicast-suppression, and unicast-suppression commands, respectively. 5. Verify that no congestion occurs by using the display qos queue-statistics interface command. 20

22 If congestion occurs, locate and solve the problem by referencing related congestion management documents. 6. If the problem persists, contact HP Support. Related commands This section lists the commands that you might use for troubleshooting Layer 2 packet loss failure. Command display interface display packet-filter display qos policy display qos policy interface display qos vlan-policy display qos policy global display this display ip source binding/display ipv6 source binding display portal interface display dot1x display mac-forced-forwarding vlan display link-aggregation verbose display rrpp verbose display smart-link group display mac-address blackhole display qos lr interface display qos queue-statistics interface Description Displays Ethernet interface information. Displays whether an ACL has been successfully applied to an interface for packet filtering. Displays user-defined QoS policy configuration information. Displays information about the QoS policies applied to an interface or all interfaces. Displays information about QoS policies applied to VLANs. Displays information about global QoS policies. Displays the running configuration in the current view. Displays source guard binding entries. Displays the portal configuration of an interface. Displays information about 802.1X. Displays the MFF configuration information of a VLAN. Displays detailed information about the aggregation groups that correspond to the aggregate interfaces. Displays detailed RRPP information. Displays information about the specified or all smart link groups. Displays blackhole MAC address entries. Displays the rate limit configuration and statistics on a specified interface or all the interfaces. Displays traffic statistics collected for an interface on a per-queue basis. 21

23 Layer 3 forwarding failure Symptom Packet loss occurs when the switch forwards packets to a different network. Troubleshooting flowchart Figure 7 Troubleshooting Layer 3 forwarding failure Layer 3 packet loss The port is faulty? Troubleshoot the port Problem resolved? ARP entries are correct? Troubleshoot ARP entries Problem resolved? Route entries are correct? Troubleshoot route entries Problem resolved? Contact HP Support End Solution To resolve the problem: 1. 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. If the port is not faulty, go to step Verify that ARP entries are correct by using the display arp command: If incorrect ARP entries exist, execute the debugging arp packet command to locate the problem. If the switch learns no ARP entries, you can execute the arp static command to configure static ARP entries. If ARP entries are correct, go to step Verify that the route entries are correct by using the display ip routing-table command: If incorrect route entries exist, troubleshoot the protocol that learns the route entries. If route entries are correct but the problem persists, contact HP Support. 22

24 Related commands This section lists the commands that you might use for troubleshooting Layer 3 forwarding failure. Command debugging arp packet display arp display ip routing-table Description Enables ARP packet debugging. Displays ARP entries. Displays brief information about active routes in the routing table. SFP+ port not coming up Symptom An SFP+ port that has a 1000 Mbps SFP transceiver module installed fails to come up on an HP 5800/5820X switch. Troubleshooting flowchart Figure 8 Troubleshooting SFP+ port failure SFP+ port not coming up Transceiver modules and optical fibers match? Connect the two ends using matching optical fibers and transceiver modules SFP+ port bound to an IRF port? Unbind the SFP+ port from the IRF port and re-plug in the SFP transceiver module Collect diagnostic information End Contact HP support 23

25 Solution To resolve the problem: 1. Verify that the optical fibers and transceiver modules on the two ends match and are not faulty by replacing them with correct and matching optical fibers and transceiver modules. 2. Execute the display irf configuration command to verify that the port is not bound to an IRF port. If the SFP+ port is bound to an IRF port, it supports only 10 Gbps transceiver modules. Therefore, it does not come up when a 1000 Mbps SFP module is plugged. If the SFP+ port is bound to an IRF port, use the undo port group interface interface-name command to remove the binding between the SFP+ port and the IRF port and re-plug in the SFP module to the SFP+ port. If the SFP+ port is not bound to an IRF port, perform step If the problem persists, run the display diagnostic-information command to collect diagnostic information, and contact HP Support. Related commands This section lists the commands that you might use for troubleshooting an SFP+ port. Commands display diagnostic-information display irf configuration Description Displays the operating statistics for multiple feature modules in the system Displays basic IRF settings, including the current member ID, new member ID, and physical ports bound to the IRF ports on each IRF member device. The new member IDs take effect at reboot. PoE power supply anomaly Symptom The PoE device cannot supply power correctly. 24

26 Troubleshooting flowchart Figure 9 Troubleshooting PoE power supply anomaly PoE power supply anomaly PoE power used correctly? Use correct PoE power PSE software operates correctly? Upgrade PSE software PSE supplies power correctly? Configure PSE correctly Power supplied correctly by PoE interfaces? Configure PoE interfaces correctly Contact HP Support End Solution To resolve the problem: 1. Verify that the PoE power is correctly used. For the G-PoE+ (2 slots) and G-PoE+ TAA (2 slot), use the PoE power according to the PoE power supply scheme. For information about the power supply compatibility, see Hot Swappable Power Supply Ordering Guide for HP A G-PoE+ Switch with 2 Interface Slots. 2. Execute the following commands to display power supply information: a. Execute the display poe device command in any view to display PSE information, and check the faulty field to identify PSE problems. <Sysname> display poe device PSE ID Slot SubS PortNum MaxPower(W) State Model faulty LSW124POED-M The output shows that the PSE has problems. b. Execute the poe update command to upgrade the PSE processing software in service. <Sysname> system-view [Sysname] poe update full ver_3_9_0_release.bin pse 4 This command will fully update firmware on the specific PSE(s), Continue? [Y/N]:y 25

27 System is downloading firmware into the hardware. Please wait Update firmware on the specific PSE(s) successfully! The output shows that the PSE processing software has been upgraded. c. Execute the display poe device command again to display PSE information, and check the on or off field for the PSE state. [Sysname] display poe device PSE ID Slot SubS PortNum MaxPower(W) State Model off LSW124POED-M The output shows that the PSE problem has been resolved. d. Execute the display poe pse command in any view to display detailed PSE information. Verify the following: The current power, average power, and peak power of the PSE are correct. nstandard PD detection by the PSE is enabled. [Sysname] display poe pse PSE ID : 4 PSE Slot : 1 PSE SubSlot : 0 PSE Model PSE Power Enabled PSE Power Priority : - : LSW124POED-M : enabled PSE Current Power : 0 W PSE Average Power : 0 W PSE Peak Power : 0 W PSE Max Power : 370 W PSE Remaining Guaranteed : 370 W PSE CPLD Version : - PSE Software Version : 390 PSE Hardware Version : PSE Legacy Detection PSE Utilization-threshold : 80 PSE Pd-policy Mode PSE PD Disconnect Detect Mode : disabled : disable : AC If the current power, average power, and peak power of the PSE are close to or reach the maximum power of the PSE, use PoE power with higher-wattage supply. If the PSE Pd-policy Mode field displays disable, execute the poe legacy enable pse command to enable nonstandard PD detection by the PSE. e. Execute the display poe interface gigabitethernet 1/0/1 command in any view to display power supply information for GigabitEthernet 1/0/1. Verify the following: The current power, average power, and peak power of the PoE interface are correct. The PoE interface current and voltage are correct. <Sysname> display poe interface gigabitethernet 1/0/1 Port Power Enabled Port Power Priority Port Operating Status : disabled : low : off Port IEEE Class : 0 Port Detection Status : disabled 26

28 Port Power Mode : signal Port Current Power : 0 mw Port Average Power : 0 mw Port Peak Power : 0 mw Port Max Power : mw Port Current : 0 ma Port Voltage : 0.0 V Port PD Description : If the current power, average power, and peak power of the PoE interface are close to or reach the maximum power of the PoE interface, execute the poe max-power command to configure the maximum power with higher-wattage supply. 3. If the problem persists, contact HP Support. Related commands This section lists the commands that you might use for troubleshooting PoE. Command display poe device display poe pse display poe interface interface-type interface-number poe legacy enable pse poe max-power Description Displays PSE information. Displays detailed PSE information. Displays power supply information for PoE interfaces. Enables the PSE to detect nonstandard PDs. Configures the maximum power for a PoE interface. 27