I/O module will not power on
If an I/O module will not power on, the problem may be caused by the blade itself, power supplies, or by configuration settings within the advanced management module.
Problem
You attempted to power on an I/O module, but it will not power on. All other components in the BladeCenter S chassis appear to be functioning normally.
Investigation
Perform these steps to resolve the problem:
- Verify that all power supplies are operating normally and that the wattage requirements for this configuration meet the overall wattage guidelines for this BladeCenter S chassis.
To view power consumption from the advanced management module Web interface, click .
- Check all LEDs.
- Check the LEDs on the I/O module to ensure that the OK LED is lit and that the Error LED is not lit.
- If the OK LED is not lit, reseat the module and wait 60 seconds for the OK LED to light.
- Check the advanced management module event log for I/O module power errors.
- Check all LEDs for the BladeCenter S chassis. Verify that the power LED is lit and that the over-temperature, information, and system-error LEDs are not lit.
- Check the LEDs on the advanced management module to ensure there are no error conditions.
- Check the LEDs on the I/O module to ensure that the OK LED is lit and that the Error LED is not lit.
- Log in to the advanced management module and check any problems.
- Check the System Status page for any messages.
- Check the advanced management module hardware Vital Product Data (VPD) to validate the VPD for the I/O module. If the I/O module is a switch module and it is located in bay 3 or 4, the type of expansion card option installed on the blade server must match the I/O module type. For example, if the I/O module is an SAS connectivity module, a SAS expansion card option in each blade server that will access the integrated shared storage.
- Check the advanced management module firmware VPD to ensure that it is compatible with the I/O module firmware. Update the firmware if needed.
- Check the advanced management module event log to determine whether there are power recovery event or service processor communications errors. If there are errors for multiple BladeCenter S chassis components, the problem may be related to the chassis. See Isolating component failures.
- Use the advanced management module to restart the I/O module.
- Verify that the module bay is functioning
- If you have another functioning I/O module, replace the I/O module that will not power on with the functioning I/O module. If the replacement module works in the bay, the original I/O module needs to be replaced.NoteThe module that you use as a replacement must be the same type of I/O module as the original. For example, you can only replace an Ethernet switch module with another Ethernet switch module.
- If you do not have another functioning I/O module, move the I/O module to another I/O bay in a different chassis (in the same bay).
- If the I/O module powers up, the problem may be related to the chassis. See Isolating component failures.
- If the I/O module does not power up, replace it.
- If you have neither a functioning I/O module nor another chassis:
- See Isolating component failures. Keep in mind that this will require bringing down all components in the chassis.
- Replace the I/O module. However, if the problem is related to the chassis, it will persist even if you replace the I/O module.
- If you have another functioning I/O module, replace the I/O module that will not power on with the functioning I/O module. If the replacement module works in the bay, the original I/O module needs to be replaced.
- Check the I/O module settings. In most cases, unless you are very familiar with the setup of your company's internal server network, you will want to set up the I/O module so that it is managed on the advanced management module management network with the setting External Management over all ports disabled.
Give documentation feedback