Table of Contents
Advertisement
Chapter 6. Troubleshooting and support
This topic covers known problems and workarounds, limitations, and error
messages related to OFM. It also contains information to get support and
troubleshoot problems.
Problems when you create or apply a standby blade pool
When creating a standby blade pool or applying the standby blade pool, you may
run into a number of error conditions. This section describes typical problems and
how to resolve these issues.
© Copyright IBM Corp. 2007, 2008
Table 9. Blade address configuration creation and application problems
Problem
Profile failed to be applied.
No chassis show up in the Available chassis
box
Table 10. Standby blade pool creation and application problems
Problem
No blades show up in the available blades
section.
Only the blades from one chassis appear in
the available blades section.
Standby Blade Pool failed after manually
applying to a blade.
Solution
v Check that blades are not powered on.
v Check that you have discovered all of the
chassis in the domain.
v Check that you do not have address
duplications in the domain.
Make sure that the chassis have been
completely discovered.
Solution
Make sure that the blades and the
BladeCenter chassis have been completely
detected.
When creating a standby pool through a
targeted action (such as dragging
BladeCenter Configuration Manager onto a
BladeCenter chassis) only the blades from
that chassis will appear in the available
blades section. To see all of the blades that
have been detected, start BladeCenter
Configuration Manager through an
un-targeted action, such as double clicking
on the task.
v Check that the blades in the standby pool
have the same model and type as the
source blade.
v Check that the standby blade pool does
not contain only the source blade (a
failover attempt to the same blade will
always fail).
Check that the blades in the standby
v
blade are powered off.
v Make sure that the Director plug-in for
your network switches has been installed.
31
Advertisement
Table of Contents
