HP ProCurve 2 Port 10-GbE CX4 al Module (J9149A) (3)
HP ProCurve 2-Port 10-GbE SFP+ al Module (J9008A) (2,3)
HP ProCurve 10-GbE al Interconnect Kit (J9165A) (3)For transceivers other than the direct attach cables, you should disconnect the network cables from transceiver before hot-swapping them.
The SFP+ slots in J9008A 2-Port 10-GbE SFP+ al Module only supports the following SFP+ Transceivers and direct attached cable products.
It also provides a new mechanism for communicating power capability and requirements using the 802.1ab Link Layer Discovery Protocol (LLDP). This new protocol addition allows PoE+ switches to deliver power more efficiently and thereby provide power to more devices for a given power supply capacity.
After discovery, a PD must draw a minimum current for the power flow to remain active. If, for example, the PD is unplugged; the PSE will discontinue power supply over the cable. The discovery process will be repeated until the PD is returned to service.
ProCurveSwitch2910al(config)# spanning-tree force-version < stp-compatible | rstp-operation | mstp-operation >
Because the switch behaves in this way (in compliance with the IEEE 802.3 standard), if a device connected to the switch has a fixed configuration at full duplex, the device will not connect correctly to the switch. The result will be high error rates and very inefficient communications between the switch and the device. Make sure that all devices connected to the switch are configured to auto negotiate, or are configured to connect at half duplex (all hubs are configured this way, for example).
| LED Pattern Indicating Problems | Diag Tips | |||||||
| Power | Fault | Module (Mdl) Status** | RPS Status | EPS Status | Test | Fan Status | Port LED (in link view mode) |
|
| Off with power cord plugged in | * | * | * | * | * | * | 1 | |
| On | Prolonged On | * | * | Prolonged On | * | * | 2 | |
| On | Blinking+ | * | * | Blinking+ | * | * | 3 | |
| On | Blinking+ | * | * | Off | Blinking+ | * | 4 | |
| On | Blinking+ | See tip 5 | Blinking+ | * | Blinking+ | 5 | ||
| On | Off | * | * | Off | * | Off with cable connected | 6 | |
| On | Off | * | * | Off | * | On, but the port is not communicating | 7 | |
| On | Blinking+ | * | Blinking+ | * | * | * | 8 | |
| On | Blinking+ | * | * | Blinking+ | * | * | 9 | |
| On | Blinking+ | (F) Blinking+ (B) Blinking+ |
* | * | * | 10 | ||
| Tip | Problem | Solution |
| 1 | The switch is not plugged into an active AC power source, or the switch’s power supply may have failed. The switch will not power up if the top is off. |
|
| 2 | A switch hard-ware failure has occurred. All the LEDs will stay on indefinitely. | Try power cycling the switch. If the fault indication reoccurs, the switch may have failed. Call your ProCurve authorized LAN dealer, or use the electronic support services from HP to get assistance. See the Customer Support/Warranty booklet for more information. |
| 3 | The switch has experienced a software failure during self test. |
|
| 4 | One or both of the switch cooling fans may have failed. | Try disconnecting power from the switch and wait a few moments. Then reconnect the power to the switch and check the LEDs again. If the error indication reoccurs, one or both of the fans has failed. The switch has two fans and may continue to operate under this condition if the ambient temperature does not exceed normal room temperature, but for best operation, the switch should be replaced. Contact your ProCurve authorized LAN dealer, or use the electronic support services from ProCurve to get assistance. See the Customer Support/Warranty booklet for more information. |
| 5 | The network port for which the LED is flashing has experienced a self test or initialization failure. If the Mdl Status LED is flashing, the affected port is on the al Module. | Try power cycling the switch. If the fault indication reoccurs, the switch port may have failed. Call your ProCurve authorized LAN dealer, or use the electronic support services from ProCurve to get assistance. See the Customer Support/Warranty booklet for more information. If the port is a pluggable, verify it is one of the pluggables supported by the switch. The Transceivers are also tested when they are “hot-swapped”—installed or changed while the switch is powered on. To verify the port has failed, try removing and reinstalling the Transceiver without having to power off the switch. Next try installing Transceiver into another port. If the port fault indication reoccurs, you will have to replace the Transceiver. |
| 6 | The network connection is not working properly. | Try the following procedures:
|
| 7 | The port may be improperly configured, or the port may be in a “blocking” state by the normal operation of the Spanning Tree, LACP, or IGMP features. | Use the switch console to see if the port is part of a dynamic trunk (through the LACP feature) or to see if Spanning Tree is enabled on the switch, and to see if the port may have been put into a “blocking” state by those features. The show lacp command displays the port status for the LACP feature; the show spanning-tree command displays the port status for Spanning Tree. Also check the Port Status screen using the show interfaces command to see if the port has been configured as “disabled”. Other switch features that may affect the port operation include VLANs and IGMP. Use the switch console to see how the port is configured for these features. For software troubleshooting tips, see the chapter “Troubleshooting” in the Management and Configuration Guide, which is on the ProCurve Website at www.procurve.com/manuals. Make sure also, the device at the other end of the connection is indicating a good link to the switch. If it is not, the problem may be with the cabling between the devices or the connectors on the cable. |
| 8 | An RPS is connected but the switch has experienced a fault. | Check the RPS unit to make sure it is plugged in to an active power source. If this is ok but the LEDs are still blinking, the power supply in the RPS unit may have failed. Try reversing R1 and R2 power cords. Also check the log files of the connected switch for more information. This condition can also be caused by an RPS unit fan failure or an over temperature condition. If necessary to resolve the problem, contact your ProCurve authorized LAN dealer, or use the electronic support services from ProCurve to get assistance. See the Customer Support/Warranty booklet for more information. |
| 9 | An EPS is connected but the switch has experienced a fault. | Check the EPS unit to make sure it is plugged in to an active power source. If this is ok but the LEDs are still blinking, the power supply in the EPS unit may have failed. Try reversing EPS1 and EPS2 power cords. Also check the log files of the connected switch for more information. This condition can also be caused by an RPS unit fan failure or an over temperature condition. If necessary to resolve the problem, contact your ProCurve authorized LAN dealer, or use the electronic support services from ProCurve to get assistance. See the Customer Support/Warranty booklet for more information. |
| Expansion al module is plugged in but has experienced a fault. | Check the rear of the switch. Check the module LEDs for indications. This will only occur during an initialization self test. |
For your switch, if you wish to build redundant paths between important nodes in your network to provide some fault tolerance, you should enable Spanning Tree Protocol support on the switch. This ensures only one of the redundant paths is active at any time, thus avoiding data path loops. Spanning Tree can be enabled through the switch console, the web browser interface, or ProCurve Manager. For more information refer to the Advance Traffic Management Guide.
NOTE: This form is used to collect required data at the request of an
HP ProCurve Support Engineer for an open support call. Do NOT use it
to open a new call. If you need to open a new call please visit our
web site at http://www.procurve.com and select "Contact ProCurve".
ProCurve Switch Support Form - Required Data
If you are using an unmanaged product or you cannot access the CLI
(command-line interface) of a managed product please provide the
following information:
Product Number: ___________________
(This can be found in the blue box on the front of your switch.
It will be in the format Jxxxxx).
Part Number: ______________________
(This can be found in the blue box on the front of your switch
and will be in the format JxxxxX)
Serial Number: ___________________
(This can be found on the rear of the switch on a white label)
Precise problem statement: __________________________________________
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
What symptoms lead you to believe that the switch is not operating
correctly? __________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
Total number of switches affected? __________________________________
Did the problem begin at installation? ______________________________
How long has the switch been in operation? __________________________
What changes were made to the switch configuration prior to the
problem episode? ____________________________________________________
_____________________________________________________________________
What changes were made to the network topology/conditions prior to
the problem episode? ________________________________________________
_____________________________________________________________________
How often does the problem occur? ___________________________________
What is the current workaround, if any? _____________________________
_____________________________________________________________________
What troubleshooting steps have you performed to isolate the problem
to this switch? _____________________________________________________
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
If you have network management (e.g. ProCurve Manager) that can
monitor the device, what is the network management product and what
pertinent information does it report? ______________________________
_____________________________________________________________________
_____________________________________________________________________
What if any Genuine ProCurve accessories are you using
(mini-GBICs, transceivers, RPS/EPS)? ________________________________
_____________________________________________________________________
_____________________________________________________________________
*********************************************************************
Please attach the following information:
1. Network topology map:
a) All IP addresses and subnet masks of devices that are relevant
to the problem.
b) Port mapping of connected network devices.
c) Port mapping of connected clients/servers relevant to the
problem.
Please attach the following for managed products with CLI:
2. TECHNICAL SUPPORT DATA:
This output will help HP gather valuable information about your
switch.
The data should be captured while the problem is occurring.
i) From a console connection or TELNET session, use the following
CLI command:
show tech all [*ENTER*]
and capture/log the output; or
ii) You will need a TFTP server. Use the following CLI command:
copy command 'show tech all' tftp
[*ENTER*]
3. CRASH LOG: You will need a TFTP server to get this binary file.
Use the following CLI command:
copy crash-log tftp [*ENTER*]