HP 5830 Switch Series Troubleshooting Guide

HP 5830 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: 5998-4990

Contents General troubleshooting procedures 1 Obtaining diagnostic information 1 Obtaining other information 2 Checklist for deployment 2 Troubleshooting hardware 7 Unexpected switch reboot 7 Symptom 7 Troubleshooting flowchart 7 Solution 8 Operating power supply failure 8 Symptom 8 Solution 8 Newly-installed power supply failure 9 Symptom 9 Solution 9 Fan tray failure 9 Symptom 9 Solution 10 Related commands 10 Troubleshooting system management 11 High CPU usage 11 Symptom 11 Troubleshooting flowchart 11 Solution 11 High memory usage 12 Symptom 12 Troubleshooting flowchart 12 Solution 13 Temperature alarming 14 Symptom 14 Troubleshooting flowchart 14 Solution 14 Related commands 15 Troubleshooting ports 15 10/100/1000Base-T copper port fails to go up 15 Symptom 15 Troubleshooting flowchart 16 Solution 16 100/1000-Mbps SFP fiber port fails to go up 17 Symptom 17 Troubleshooting flowchart 18 Solution 18 10-Gigabit SFP+ fiber port fails to go up 20 Symptom 20 Troubleshooting flowchart 21 Solution 22 Reporting non-hp transceiver modules 23 i

Symptom 23 Troubleshooting flowchart 23 Solution 24 Failure to support digital diagnosis on a transceiver module 25 Symptom 25 Troubleshooting flowchart 25 Solution 26 Error frames (for example, CRC errors) on a port 26 Symptom 26 Troubleshooting flowchart 27 Solution 27 Failure to receive packets 29 Symptom 29 Troubleshooting flowchart 29 Solution 29 Failure to send packets 31 Symptom 31 Troubleshooting flowchart 31 Solution 31 Related commands 32 Troubleshooting IRF 33 IRF fabric establishment failure 33 Symptom 33 Troubleshooting flowchart 34 Solution 34 IRF split 36 Symptom 36 Troubleshooting flowchart 36 Solution 36 BFD MAD failure 37 Symptom 37 Troubleshooting flowchart 38 Solution 38 LACP MAD failure 40 Symptom 40 Troubleshooting flowchart 41 Solution 41 Related commands 42 Troubleshooting QoS and ACL 43 ACL application failure for unsupported ACL rules 43 Symptom 43 Troubleshooting flowchart 44 Solution 44 ACL application failure for insufficient resources 45 Symptom 45 Troubleshooting flowchart 45 Solution 45 ACL application failure without an error message 46 Symptom 46 Troubleshooting flowchart 47 Solution 47 Packet loss or forwarding failure 48 Symptom 48 ii

Troubleshooting flowchart 48 Solution 49 Related commands 50 iii

General troubleshooting procedures This chapter describes how to obtain information for troubleshooting problems. This document is not restricted to specific software or hardware versions. Obtaining diagnostic information Diagnostic information is important for locating and solving problems. You can execute the display diagnostic-information command to obtain diagnostic information. HP recommends that you execute the display diagnostic-information command over Telnet instead of the console port because information collection through the console port (9600 bps) takes a long time. Information collection on an IRF fabric takes more time than on a single device. To obtain diagnostic information: <Sysname> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:y Please input the file name(*.diag)[flash:/default.diag]:aa.diag Diagnostic information is outputting to flash:/aa.diag. Please wait... Save successfully. The following describes the output information above: save or display diagnostic information (Y=save, N=display)? [Y/N]: This prompt asks you whether to save diagnostic information into a.diag file in the flash memory. If the free space of the flash memory is larger than 10 MB, HP recommends that you enter y to save diagnostic information into a.diag file. After you enter y, the following prompt appears: Please input the file name(*.diag)[flash:/default.daig]: Enter a name for the.diag file at the prompt. If you press Enter, the default name default.diag is used. You can enter a name to differentiate between different.diag files. If the name you entered already exists, the following prompt appears: The file already exists, overwrite it? [Y/N] If you enter y, the new file overwrites the old file. If you enter n, the system returns to the view in which you executed the display diagnostic-information command. You need to execute the display diagnostic-information command again and enter a new name for the.diag file. Please wait... The system continues to print dots while saving the diagnostic information. If a fault occurs, the interval between dots will increase, but it will not exceed 2 minutes. After the system saves the diagnostic information, you can execute the dir command in user view to verify whether the diagnostic file exists in the flash memory. <Sysname>dir Directory of flash:/ 0 -rw- 6797 Jun 14 2012 10:37:42 startup.cfg 1 drw- - Sep 03 2010 11:03:06 patch6613 2 -rw- 3395 May 13 2013 13:07:13 system.xml 1

3 -rw- 429516 Aug 19 2010 15:59:51 mpu.btw 4 -rw- 13090 May 13 2013 13:07:03 config.cwmp 5 drw- - Apr 09 2010 13:47:34 seclog 6 -rw- 406528 Dec 11 2012 15:43:37 lsv158308616_v1.06.btw 7 -rw- 22600 Jul 01 2013 11:11:42 5830-cmw520-r1118h01.bin 8 drw- 724660 May 03 2013 14:05:15 default.diag If the diagnostic file is larger than 10000 bytes and the saving time is correct, the saving operation is successful. If the diagnostic file has a size of 0 (-1) or the saving time is incorrect, the saving operation failed. You must configure the system to print the diagnostic information on the console. If the flash memory has no more space during the saving process, the system prints the excess diagnostic information on the console. You can use FTP to download the diagnostic file to a PC and send the file to HP Support. If you enter n at the prompt "save or display diagnostic information (Y=save, N=display)? [Y/N]:", the system prints all diagnostic information on the console. Before you select n, enable information capture on the HyperTerminal or Telnet window. If you are using the console port, the information collection process takes about 20 minutes. If you are using Telnet, the information collection process takes about 3 minutes. After you obtain the diagnostic information, send the file to HP Support. Obtaining other information Besides diagnostic information, the following information is also helpful for troubleshooting: LED state information, such as port LEDs, expansion interface card LEDs, and system status LEDs. Operation information about other relevant devices, configuration information, and log files. Your opinions on this problem. Measures taken on site and the results. Solution to the problem if the problem has been solved. Checklist for deployment The following checklist serves as a deployment guide to help you eliminate potential configuration errors at different deployment sites. Select items according to your deployment environment. Table 1 Checklist Item Sub-item Command or method Result Remarks Environment and device hardware status Environment Fan display environment display fan t related t related The temperature of the device must be lower than 62 C (143.6 F). Make sure the fans are operating correctly. 2

Item Sub-item Command or method Result Remarks Power supply display power t related Make sure the power supplies are operating correctly. Evaluate power backup by referring to the power and system power consumption. LED Examine the status of all the LEDs on the device. t related For more information about the LED description, see HP 5830 Switch Series Installation Guide. Device operating status display device t related The device must be operating correctly. CPU usage Does the CPU usage keep changing between 10% and 60% or stay at a high level (the CPU usage exceeds 60%)? Execute the display cpu-usage command repeatedly. t related Execute the debug ip packet command to view the packets delivered to the CPU and analyze the cause. Memory usage Does the memory usage of the device exceed 60%? display memory slot t related If the memory usage exceeds 60%, execute the display memory command to view memory usage and troubleshoot the module that occupies the most memory. Is the port operating in half-duplex mode? display interface brief t related If a port is operating in half-duplex mode, verify that the configurations on the two ends are consistent. Port Is flow control enabled on the port when not necessary? Check the configuration to see if flow control is enabled. t related Use the undo flow control command to disable flow control on the port. Are large numbers of error packets generated in the outbound/inbound direction of the port? Use the display interface command to verify that a large number of errors are generated and that the number keeps increasing. t related Do the following: 1. Examine link quality and the optical-electrical converter. 2. Verify that the configurations on the two ends are consistent. 3

Item Sub-item Command or method Result Remarks Do the following: Does the port change to up/down frequently? display logbuffer t related 1. Examine the link and the optical-electrical converter. 2. Verify that the optical power of the GE port has reached the threshold value. 3. Verify that the configurations on the two ends are consistent. Are the configurations on the local and peer fiber ports consistent? display current interface t related To connect an HP device to a device of another vendor, HP recommends that you set consistent fiber port rate and duplex mode on the two ends. Fiber port Does CRC error occur on the fiber port? Is the number of CRC errors increasing? display interface t related Verify that the optical power has reached the threshold value. To resolve this issue, replace the transceiver module or pigtail fiber, or clean the connector of the transceiver module. Is the undo port trunk permit vlan 1 command configured on the trunk port? display current interface t related If GVRP is configured for the system and the undo port trunk permit vlan 1 command is configured for the trunk port, configure the PVID of the trunk port as the ID of a VLAN permitted by the trunk port. Trunk port configurations Is the PVID of the trunk port consistent with the peer port? Are the VLANs to which the port is assigned consistent with the peer port? display current interface display current interface t related t related The VLANs permitted by the trunk ports and the PVIDs of the trunk ports connecting the two devices are consistent. The VLANs permitted by the trunk ports connecting the two devices are consistent. Are the ports connecting two devices configured as a trunk port and an access port? display current interface t related Configure the same link type for the ports as needed. 4

Item Sub-item Command or method Result Remarks Does a loop occur in VLAN 1? Use the display interface command to verify that the trunk ports of all devices are assigned to VLAN 1. t related Remove the ports from VLAN 1 as needed. Timeout factor display current-configuration t related Verify that the stp timer-factor command is configured. If not, configure a timeout factor in the range of 5 to 7 to enhance the stability of STP. Is the port on the device connected to the PC configured as an edge port? Use the display current interface command to examine the port configurations. If an edge port is configured, stp edged-port enable is displayed. t related HP recommends configuring the port on the device connected to the PC as an edge port or disabling STP on the port. To prevent state change of the ports from interrupting STP calculation, disable STP on the ports connected to the STP-incapable devices. STP Can the HP device running MSTP/STP/RSTP communicate with the Cisco device running PVST+? Are there too many overlapping paths among the topologies of different MSTIs? Verify that STP calculation on each device is correct. Use the display current interface command to examine port configurations. t related t related To avoid communication between the HP device running MSTP/STP/RSTP and the Cisco device running PVST+, HP recommends that you change the connection mode to Layer 3 connection. Plan VLANs and VLAN-to-instance mappings according to your network environment in order to do the following: Forward traffic of multiple VLANs along different paths. Avoid too many overlapping paths among the topologies of different MSTIs. Does a TC attack exist to cause frequent STP status changes on the port? Use the display stp tc and display stp history commands to examine the statistics of TC/TCN BPDUs received and sent on the port and the historical port role calculation information. t related Make sure the stp edged-port enable command is configured on the port of the device connected to the PC or otherwise STP is disabled. Disable STP on the ports connected to the devices that do not support STP. 5

Item Sub-item Command or method Result Remarks VRRP Is the advertisement timer set to 3 seconds? Is the timer value the same between the two ends? display vrrp t related If fewer than five VRRP groups exist, set the advertisement timer to 3 seconds for all the groups. If five or more VRRP groups exist, set the advertisement timer to different values for every three or five VRRP groups. The timer value can be 3 seconds, 5 seconds, or 7 seconds. Are the router IDs of two devices the same? display ospf peer t related A router ID conflict might result in a route learning error. To restart route learning, you must modify the router ID and execute the reset ospf process command. OSPF Are there a lot of errors from the output of the display ospf error command? Does severe route flapping occur? display ospf error Use the display ip routing-table statistics command to examine the number of added and deleted routes. t related t related If a large amount of OSPF errors exist and the number continues to increase, execute the debugging ospf event command for further analysis. If route flapping occurs, locate the flapping route and the source device to analyze the cause. You can use the display ospf lsdb command multiple times to view the age of routes and locate the flapping route. Is the OSPF status stable? display ospf peer t related View the up time of the OSPF neighbor. ARP Are there a lot of ARP entry conflicts? display logbuffer t related Verify that the IP address of the host does not conflict with other IP addresses. If a conflict occurs, modify the IP address of the host. Route Is the default route correct? Is there any routing loop? Trace the path to a nonexistent network (1.1.1.1, for example) by using the tracert command to check routing loops. Use the debug ip packet command to check if packets with TTL 0 or 1 exist. t related If a routing loop exists, verify the configurations of involved devices. Adjust the route to eliminate the loop. If TTL exceeded packets are received, verify that the corresponding network route is correct. 6

Troubleshooting hardware This section provides troubleshooting information for common hardware problems. NOTE: This section describes how to troubleshoot unexpected switch reboot, power supply failure, and fan tray failure. To troubleshoot transceiver modules, ports, and temperature alarms, see "Troubleshooting system management" and "Troubleshooting ports." Unexpected switch reboot Symptom The switch reboots unexpectedly when it is operating. Troubleshooting flowchart Figure 1 Troubleshooting unexpected switch reboot Switch reboots unexpectedly Can access the CLI? Collect log messages Reload the system software image System software image correct? Is the fault rectified? End Contact HP Support 7

Solution To resolve the problem: 1. Verify that you can access the CLI after the switch reboot. If you can access the CLI, execute the display diagnostic-information command to collect log messages. If you cannot access the CLI, go to step 2. 2. Verify that the system software image on the switch is correct. a. Log in to the switch through the console port and restart the switch. If the system reports that a CRC error occurs or that no system software image is available during the BootWare loading process, reload the system software image. b. Verify that the system software image in the flash memory is the same as the one on the server. If no system software image is available in the flash memory, or if the image is different than the one on the server, reload the system software image. Then set the reloaded system software image to the current system software image. The system software image in the flash memory is automatically set to the current system software image during the BootWare loading process. 3. If the problem persists, contact HP Support. Operating power supply failure Symptom Solution A trap is generated indicating that an operating power supply has failed. To resolve the problem: 1. Execute the display power command to display power supply information. <HP> display power Slot 1 Power 1 State : Absent Power 2 State : rmal Type : AC If the power supply is in Absent state, go to step 2. If the power supply is in Fault state, go to step 3. 2. Remove and reinstall the power supply to make sure the power supply is installed correctly. Then, execute the display power command to verify that the power supply has changed to rmal state. If the power supply remains in Absent state, replace the power supply. 3. A power supply might run into Fault state when it operates continuously at high temperatures or when it is faulty. a. Verify that the power supply surface is clean. If there is dust accumulated on the power supply, remove the dust. Then remove and reinstall the power supply. Execute the display power 8

command to verify that the power supply has changed to rmal state. If the power supply remains in Fault state, go to step b. b. Install the power supply into an empty power supply slot. Then execute the display power command to verify that the power supply has changed to rmal state in the new slot. If the power supply remains in Fault state, replace the power supply. 4. If the problem persists, contact HP Support. Newly-installed power supply failure Symptom Solution A newly-installed power supply fails. To resolve the problem: 1. Execute the display power command to display power supply information. <HP> display power Slot 1 Power 1 State : Absent Power 2 State : rmal Type : AC If the power supply is in Absent state, go to step 2. If the power supply is in Fault state, go to step 3. 2. A newly-installed power supply might run into Absent state when it is not securely installed. a. Remove and reinstall the power supply to make sure the power supply is installed securely. Then execute the display power command to verify that the power supply has changed to rmal state. If the power supply remains in Absent state, go to step b. b. Remove and install the power supply into an empty power supply slot. Then execute the display power command to verify that the power supply has changed to rmal state in the new slot. If the power supply remains in Absent state, go to step 4. 3. Remove and install the power supply into an idle power supply slot. Then execute the display power command to verify that the power supply has changed to rmal state in the new slot. If the power supply remains in Fault state, go to step 4. 4. If the problem persists, contact HP Support. Fan tray failure Symptom An operating fan tray or a newly-installed fan tray fails. 9

Solution To resolve the problem: 1. Execute the display fan command to display the operating states of the fan tray. <HP> display fan Slot 1 Fan 1 State : rmal Direction : Power to port(preferred) Load average : 43% If the fan tray is in Absent state, go to step 2. If the fan tray is in Fault state, go to step 3. 2. Remove and reinstall the fan tray to make sure the fan tray is securely installed. Then execute the display fan command to verify that the fan tray has changed to rmal state. If the fan tray remains in Absent state, replace the fan tray. 3. Execute the display environment command to display temperature information. If the temperature continues to rise, put your hand at the air outlet to verify that air is being exhausted from the air outlet. If there is no air being exhausted from the air outlet, remove and reinstall the fan tray. Then execute the display fan command to verify that the fan tray has changed to rmal state. If the fan tray remains in Fault state, replace the fan tray. If there is no new fan tray, power off the switch to avoid damage caused by high temperatures. If there are cooling measures to maintain the switch operating temperature below 60 C (140 F), the switch can be used temporarily. 4. If the problem persists, contact HP Support. Related commands This section lists the commands that you might use for troubleshooting the hardware. Command _hidecmd dir display boot-loader display environment display fan display logbuffer display power display task slot slot-id Description Enters hidden view. Displays information about files and directories. Displays current configuration files and system software images. Displays temperature information. Displays the operating states of the fan tray. Displays the state of the log buffer and the log information in the log buffer. Displays power supply information. Displays information about tasks. 10

Troubleshooting system management This section provides troubleshooting information for common system management problems. High CPU usage Symptom The CPU usage of the switch is high. Troubleshooting flowchart Figure 2 Troubleshooting high CPU usage Solution To resolve the problem: 1. Use the display cpu-usage task command in hidden view to view the CPU usage of the switch. 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: Use the display interface command to see whether interfaces have received large amounts of broadcast packets. 11

Identify whether a loop exists on the network. If a loop exists, examine the connections between the devices. MSTP Use the display stp bpdu-statistics interface command to view the statistics for received and sent BPDU packets on ports. Identify the counts of TCN/TC packets. If the switch receives a large quantity of TCN/TC packets generated by STP, the switch must delete MAC address entries frequently, which 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 identify route changes. Route flapping might cause high CPU usage. L2X0 or L2X1 MAC address synchronization Identify whether the network topology is stable. If the network topology is not stable, the device must use a large amount of CPU resources to update its MAC address entries frequently. 3. If the problem persists, contact HP Support. High memory usage Symptom The memory usage of the switch is higher than 60% in a certain period of time (typically 30 minutes). Troubleshooting flowchart Figure 3 Troubleshooting high memory usage 12

Solution To resolve the problem: 1. Execute the _display memory command multiple times in hidden view to display memory usage information. [HP-hidecmd]_display memory Slice Memory Usage: Block Size 32 Free 729 Used 25876 Total 26605 Block Size 64 Free 49 Used 30053 Total 30102 Block Size 128 Free 5 Used 9550 Total 9555 Block Size 256 Free 2 Used 2326 Total 2328 Block Size 512 Free 2 Used 1429 Total 1431 Block Size 1024 Free 17 Used 66351 Total 368 Block Size 2048 Free 23 Used 593 Total 616 Block Size 4096 Free 4 Used 156 Total 160 -----------------------------Summary-------------------------------- Used(Byte) 7513792 Free 831 Used 70334 Total 71165 Total Slice Memory(Include Control Data and Free Slice): 15073152 bytes Raw Slice Memory Usage: Total Used Size: 82790994 bytes Num: 423 Total Raw Slice Size (Include Control Data and Free Slice): 93020888 bytes Used Ratio:89 Partition 0 Total Memory(bytes): 196910208 If the memory usage of a memory block is continuously increasing, the memory might be leaked. Verify the situation by calculating the actual memory usage. For example, in the output, the used memory is 66351, so the actual memory that is used is 66351 1024 = 66.35 MB. The result shows that the memory might be leaked because the memory usage is too high. NOTE: Some memory block's leak process is slow, so you might need to observe memory usage for a long period of time (up to several weeks). 2. Execute the _display memory 1024 group command in hidden view to identify the memory block whose memory usage is too high. [HP-hidecmd]_display memory 1024 group (8888, 20) (00a4, 4) (00a8, 1) (00ae, 1) (dd35, 66251) (0150, 149) (0090, 11) (0392, 2) (014d, 1) (0140, 6) (01d0, 1) (0002, 3) (017d, 10) (0050, 105) (001b, 4) (0430, 1) (55aa, 21) (0170, 2) (0000, 0) (0000, 0) The output shows that the dd35 module uses 66251 1024 = 66.35 MB memory. The memory usage is too high. Record the information. 3. If the problem persists, contact HP Support. 13

IMPORTANT: Do not reboot the device after you identify the problems because failure information might be lost after device reboot. Temperature alarming Symptom Temperature alarms occur. Troubleshooting flowchart Figure 4 Troubleshooting temperature alarming Solution To resolve the problem: 1. Identify whether the device temperature or the ambient temperature is too high. If the ambient temperature is too high, lower the temperature by adding air conditioners or taking other heat dissipation measures. If the device temperature is too high, go to step 2. 2. Use the display fan command to verify that the fan tray is operating correctly. If the system displays "Fault," see HP 5830 Switch Series Installation Guide to resolve the problem. 3. Use the temperature-limit command to set the temperature alarm thresholds. 14

You can use the display environment command to identify whether the temperature alarm thresholds are set successfully. If they are not, contact HP Support. If they are but temperature alarms still occur, contact HP Support. Related commands This section lists the commands that you might use for troubleshooting system management. Command _display memory _display memory block-size group _hidecmd display cpu-usage task [ slot slot-id ] display environment display fan display task slot slot-id display task task-id slot slot-id temperature-limit Remarks Displays memory usage information. This command is available in hidden view. Displays memory block information. This command is available in hidden view. Enters hidden view. Displays CPU usage information. This command is available in hidden view. Displays temperature information, including the current temperature and the temperature alarm thresholds. Displays the operating status of all fan trays on the switch. Displays task information. This command is available in hidden view. Displays call stack information about a task. This command is available in hidden view. Sets temperature alarm thresholds. Troubleshooting ports This section provides troubleshooting information for common port problems. 10/100/1000Base-T copper port fails to go up Symptom A 10/100/1000Base-T copper port cannot go up. 15

Troubleshooting flowchart Figure 5 Troubleshooting link up failure on a port Solution To resolve the problem: 1. Verify that the speed and duplex mode of the local port match the speed and duplex mode of the peer port: 16

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 port. b. If they do not match, use the speed command and the duplex command to set the speed and duplex mode for the port. 2. Replace the network cable with a new one to verify that the network cable is in good condition. 3. Replace the local port with a new one to verify that the local port is operating correctly. 4. Replace the peer port with a new one to verify that the peer port is operating correctly. 5. If the problem persists, contact HP Support. 100/1000-Mbps SFP fiber port fails to go up Symptom A 100/1000-Mbps SFP fiber port cannot go up. 17

Troubleshooting flowchart Figure 6 Troubleshooting link up failure on a port A port failed to go up Speed/duplex match on local and peer port? Configure matching speed/duplex Speed/duplex match on transceiver module and port? Configure matching speed/duplex Transceiver module correct? Replace transceiver module Fiber correct? Replace fiber Local port operating correctly? Replace local port Peer port operating correctly? Replace peer port Contact HP Support End Solution To resolve the problem: 18

1. Verify that the speed and duplex mode of the local 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 port. b. If they do not match, use the speed command and the duplex command to set the speed and duplex mode for the port. 2. Verify that the speed and duplex mode of the port match the speed and duplex mode of the transceiver module: 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 transceiver module. b. If they do not match, use the speed command and the duplex command to set the speed and duplex mode for the port. 3. Verify that the transceiver module is operating correctly: a. Execute the display transceiver alarm interface command to examine the alarms present on the transceiver module. The device displays ne if no error occurs. The device displays alarms if the transceiver module fails or the type of the transceiver module does not match the port type. b. Use an optical power meter to verify that the Tx power and Rx power of the transceiver module are stable and are within the correct range. c. Execute the display transceiver interface command to verify that the wavelength and transmission distance of the local transceiver module are consistent with the wavelength and transmission distance of the peer transceiver module. [HP] display transceiver interface gigabitethernet 1/0/15 GigabitEthernet1/0/15 transceiver information: Transceiver Type : 1000_BASE_SX_SFP Connector Type : LC Wavelength(nm) : 850 Transfer Distance(m) : 550(50um),270(62.5um) Digital Diagnostic Monitoring : YES Vendor Name : HP Ordering Name : SFP-GE-SX-MM850-A d. If the transceiver module is not operating correctly, replace it with a new HP transceiver module that matches the fiber port. For more information about transceiver modules, see related installation guides. 4. Replace the fiber with a new one to verify that the fiber is in good condition. 5. Replace the local port with a new one to verify that the local port is operating correctly. 6. Replace the peer port with a new one to verify that the peer port is operating correctly. 7. If the problem persists, contact HP Support. 19

10-Gigabit SFP+ fiber port fails to go up Symptom A 10-Gigabit SFP+ fiber port cannot go up. 20

Troubleshooting flowchart Figure 7 Troubleshooting link up failure on a port 21

Solution To resolve the problem: 1. Verify that the speed and duplex mode of the local 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 port. b. If they do not match, use the speed command and the duplex command to set the speed and duplex mode for the port. 2. Verify that the speed and duplex mode of the port match the speed and duplex mode of the transceiver module: 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 transceiver module. b. If they do not match, use the speed command and the duplex command to set the speed and duplex mode for the port. 3. Verify that the local and peer ports are operating correctly: a. Use a 10-Gigabit SFP+ cable to directly connect the local port and another 10-Gigabit SFP+ fiber port on the device. An SFP+ cable is suitable for short connections. b. If the local port can go up, replace the peer port with a new one to verify that the peer port is operating correctly. c. If the local port cannot go up, replace the local port with a new one to verify that the local port is operating correctly. 4. Verify that the transceiver module is operating correctly: a. Execute the display transceiver alarm interface command to examine the alarms present on the transceiver module. The device displays ne if no error occurs. The device displays alarms if the transceiver module fails or the type of the transceiver module does not match the port type. b. Use an optical power meter to verify that the Tx power and Rx power of the transceiver module are stable and are within the correct range. c. Execute the display transceiver interface command to verify that the wavelength and transmission distance of the local transceiver module are consistent with the wavelength and transmission distance of the peer transceiver module. [HP] display transceiver interface Ten-GigabitEthernet 1/0/15 Ten-GigabitEthernet1/0/15 transceiver information: Transceiver Type : 1000_BASE_SX_SFP Connector Type : LC Wavelength(nm) : 850 Transfer Distance(m) : 550(50um),270(62.5um) Digital Diagnostic Monitoring : YES Vendor Name : HP Ordering Name : SFP-GE-SX-MM850-A d. If the transceiver module is not operating correctly, replace it with a new HP transceiver module that matches the fiber port. For more information about transceiver modules, see related installation guides. 22

5. Verify that the fiber matches the transceiver module. If they do not match, replace the fiber with a new one that matches the transceiver module. 6. If the problem persists, execute the display diagnostic-information command to save the diagnostic information, and contact HP Support. <HP> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y Reporting non-hp transceiver modules Symptom When you use the display logbuffer command to view the system logs, the following reports about non-hp transceiver modules appear in the system logs: <HP> display logbuffer %Jun 19 18:03:24:55 2011 Sysname IC/7/SYS_RESTART: System restarted -- GigabitEthernet1/0/5: This transceiver is NOT sold by HP. HP therefore shall NOT guarantee the normal function of the device or assume the maintenance responsibility thereof! Troubleshooting flowchart Figure 8 Troubleshooting non-hp transceiver module reports 23

Solution To resolve the problem: 1. Identify the vendor of the transceiver module plugged into the port: a. Use the _display transceiver interface command to display the transceiver information. If the Vendor Name field is HP, the transceiver module might be an HP transceiver module without an electrical label or a non-hp transceiver module. b. If the Vendor Name field is not HP, you can determine that this is not an HP transceiver module. Replace it with an HP transceiver module. [HP]_hidecmd w you enter a hidden command view for developer's testing, some commands may affect operation by wrong use, please carefully use it with our engineer's direction. [HP_hidecmd] _display transceiver interface gigabitethernet 1/0/1 GigabitEthernet1/0/1 transceiver information: Transceiver Type : 1000_BASE_LX_SFP Connector Type : LC Wavelength(nm) : 1310 Transfer Distance(km) : 10(9um) Digital Diagnostic Monitoring : YES Vendor Name : HP Ordering Name : SFP-GE-LX-SM1310 Max. TX Power(dBm) : -3.0 Min. TX Power(dBm) : -9.5 Min. RX Power(dBm) : -20.0 Max. RX Power(dBm) : -3.0 Original Manufacturer : AGILENT Part Number : HFCT-5710LP-HP Rev Number : N Serial Number : AA05011023 Product Date : 05-03-01 2. Contact HP Support to determine whether the transceiver module vendor is HP: a. Use the _display transceiver register interface command to collect the transceiver module information. Send the bar code of the transceiver module to HP Support to identify the vendor of the transceiver module. b. If you determine that the transceiver module vendor is not HP, replace it with an HP transceiver module. [HP]_hidecmd w you enter a hidden command view for developer's testing, some commands may affect operation by wrong use, please carefully use it with our engineer's direction. [HP-hidecmd] _ display transceiver register interface gigabitethernet1/0/1 device a0 address 0 length 96 GigabitEthernet1/0/1 transceiver device a0 register information: 0000: 03 04 07 00 00 00 02 00 0008: XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX.. 24

0050: XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX 0058: XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX 3. If the transceiver module vendor is identified as HP but the problem persists, contact HP Support. Failure to support digital diagnosis on a transceiver module Symptom When you use the display transceiver diagnosis interface command to display the diagnostic information of a transceiver module, the system displays a message that the transceiver module does not support digital diagnosis. <HP> display transceiver diagnosis interface gigabitethernet 1/0/1 Error: The transceiver does not support this function. Troubleshooting flowchart Figure 9 Troubleshooting the failure to support digital diagnosis on a transceiver module 25

Solution To resolve the problem: 1. Verify that the vendor of the transceiver module is HP: a. Use the display transceiver interface command to display the transceiver information. b. Determine whether the value of the Vendor Name field is HP. c. Use the _display transceiver register interface command to collect the transceiver module information. Send the bar code of the transceiver module to HP Support to verify that the vendor of the transceiver module is HP. 2. Verify that the transceiver module supports digital diagnosis: a. Use the display transceiver interface command to display transceiver module information. b. Determine whether the value of the Digital Diagnostic Monitoring field is. c. Consult HP Support about whether the transceiver module supports digital diagnosis. <HP> display transceiver interface gigabitethernet1/0/1 GigabitEthernet1/0/1 transceiver information: Transceiver Type : 1000_BASE_LX_SFP Connector Type : LC Wavelength(nm) : 1310 Transfer Distance(km) : 10(9um) Digital Diagnostic Monitoring : YES Vendor Name : HP Ordering Name : SFP-GE-LX-SM1310 3. If the transceiver module vendor is identified as HP and the transceiver module supports digital diagnosis but the problem persists, perform the following tasks: Use the display diagnostic-information command to collect the diagnostic information for the transceiver module. Contact HP Support. <HP> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y Error frames (for example, CRC errors) on a port Symptom In the output from the display interface command, error frames exist (for example, CRC error frames). 26

Troubleshooting flowchart Figure 10 Troubleshooting error frames (for example, CRC errors) on a port Error frames on the port Determine the type of error frames accumulating Optical power of transceiver module normal? Replace it with a transceiver module with normal optical power Speed and duplex match the peer port? Configure the speed and duplex for ports Port and link medium normal? Use normal port and link medium View the number of flow control frames received Contact HP Support End Solution To resolve the problem: 1. Examine the error frame statistics and identify the error frame type: a. (Optional.) Use the reset counter interface command in user view to clear the packet statistics of the port. This command resets the values of each statistical field to 0, so that you can view the statistics changes more clearly. 27

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 accumulating. 2. If the port is a fiber port, verify that the optical power of the transceiver module is operating correctly: a. Use the display transceiver diagnosis interface command to view the present measured values of the digital diagnosis parameters for the transceiver module. b. If the optical power of the transceiver module is not within the correct range, replace the transceiver module with a transceiver module of the same model that is operating correctly. [HP] display transceiver diagnosis interface gigabitethernet1/0/1 GigabitEthernet1/0/1 transceiver diagnostic information: Current diagnostic parameters: Temp.( C) Voltage(V) Bias(mA) RX power(dbm) TX power(dbm) 40 3.34 1.13-20.43 0.20 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 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. Verify that the port and the link medium are operating correctly: a. Plug the link medium into another port that is operating correctly, and determine whether the same problem occurs. b. If the problem still occurs, verify that the following items are operating correctly: Intermediate links and devices, including optical-to-electrical converters, cable terminal racks, and transmission devices. Transmission medium, including network cables, optical fibers, and transceiver modules. c. Examine the port: If the port is a copper port, directly connect the port to a PC. If the port is a fiber port, replace the transceiver module plugged into the port. 5. Determine whether the port has received a large amount of flow control frames: a. Use the display interface command to view the number of pause frames. If the number of pause frames is accumulating, you can determine that the port has sent or received a large amount of flow control frames. b. Verify that the incoming traffic and outgoing traffic have not exceeded the maximum traffic processing capability of the local device and the peer device. 6. If you determine that the configurations, the peer port, and the link are correct but the problem persists, perform the following tasks: Use the display diagnostic-information command to collect the diagnostic information. Contact HP Support. <HP> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y 28

Failure to receive packets Symptom A port is up, but it cannot receive packets. Troubleshooting flowchart Figure 11 Troubleshooting the failure to receive packets A port fails to receive packets View packet statistics of the port Port configurations affect packet receiving? Modify port configurations Port and link medium normal? Use normal port and link medium Contact HP Support End Solution To resolve the problem: 1. Examine the packet statistics of the port: a. (Optional.) Use the reset counter interface command in user view to clear the packet statistics of the port. This command resets the values of each statistical field to 0, so that you can view the statistics changes more clearly. b. Determine whether the ports at both ends are always up, and use the display interface command to determine whether the number of incoming packets is accumulating. At the same time, examine the outgoing packet statistics of the peer port. c. View the values of the error packet fields and determine whether the number of error packets is accumulating. 2. Verify that the port configurations do not affect packet receiving: 29

a. Use the display interface brief command to verify that the port configurations are correct. The port configurations include the duplex mode, speed, port type, and VLAN configurations of the ports at both ends of the link. b. If configuration errors exist, modify the port configurations. If the number of incoming packets in the output from the display interface command is accumulating, you can determine that the port can receive packets. c. If the port fails to receive packets, use the shutdown command and then the undo shutdown command to re-enable the port. If the number of incoming packets in the output from the display interface command is accumulating, you can determine that the port can receive packets. d. If the port is configured with STP, use the display stp brief command to verify that the port is not in the discarding state. e. If a port is set to the discarding state by STP, examine and modify the STP-related 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. f. If the port is assigned to an aggregation group, use the display link-aggregation summary command to verify that the status of the port is Selected. g. If the status of the port is Unselected, the port cannot send or receive data packets. h. Determine why the port becomes Unselected (for example, the attribute configurations of the port are different from the reference port). Modify the attribute configurations of the port to make the port become Selected. 3. Verify that the port and the link medium are operating correctly: a. Plug the link medium into another port that is operating correctly, and determine whether the same problem occurs. b. If the problem still occurs, verify that the following items are operating correctly: Intermediate links and devices, including optical-to-electrical converters, cable terminal racks, and transmission devices. Transmission medium, including network cables, optical fibers, and transceiver modules. c. Examine the port: If the port is a copper port, directly connect the port to a PC. If the port is a fiber port, replace the transceiver module plugged into the port. 4. If you determine that the configurations, the peer port, and the link are correct but the problem persists, perform the following tasks: Use the display diagnostic-information command to collect the diagnostic information. Contact HP Support. <HP> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y 30

Failure to send packets Symptom A port is up, but it cannot send packets. Troubleshooting flowchart Figure 12 Troubleshooting the failure to send packets Solution To resolve the problem: 1. Examine the packet statistics of the port: a. (Optional.) Use the reset counter interface command in user view to clear the packet statistics of the port. This command resets the values of each statistical field to 0, so that you can view the statistics changes more easily. b. Determine whether the ports at both ends are always up, and use the 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 not affect packet sending: 31

a. Use the display interface brief command to verify that the port configurations are correct. The port configurations include the duplex mode, speed, port type, and VLAN configurations of the ports at both ends of the link. b. If configuration errors exist, modify the port configurations. If the number of outgoing packets in the output from the display interface command is accumulating, you can determine that the port can send packets. c. If the port fails to send packets, use the shutdown command and then the undo shutdown command to re-enable the port. If the number of outgoing packets in the output from the display interface command is accumulating, you can determine that the port can send packets. d. If the port is configured with STP, use the display stp brief command to verify that the port is not in the discarding state. e. If a port is set to the discarding state by STP, examine and modify the STP-related 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. f. If the port is assigned to an aggregation group, use the display link-aggregation summary command to verify that the status of the port is Selected. g. If the status of the port is Unselected, the port cannot send or receive data packets. h. Determine why the port becomes Unselected (for example, the attribute configurations of the port are different from the reference port). Modify 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, and determine whether the same problem occurs. If the port is a copper port, replace the peer device with a PC. If the port is a fiber port, replace the transceiver module. b. If the problem still occurs, determine whether intermediate links and devices are operating correctly (for example, optical converters, cable terminal racks, and transmission devices). 4. If you determine that the configurations, the peer port, and the link are correct but the problem persists, perform the following tasks: Use the display diagnostic-information command to collect the diagnostic information. Contact HP Support. <HP> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y Related commands This section lists the commands that you might use for troubleshooting ports. Command _display transceiver register interface _hidecmd Description Displays registration information of transceiver modules. Enters hidden view. 32