Table of Contents
Advertisement
4.9 Observations with scalability configurations
This section highlights the experiences we gained when we tested and worked
with the servers in our lab. You should regularly check the IBM Support Web
page for tips, newly released documentation, and system firmware updates at:
http://www.ibm.com/systems/support/x
4.9.1 Problem with merging if prerequisites were met
If you have problems forming a multinode complex but you have met all
prerequisites as described in 4.4, "Prerequisites to create a multinode complex"
on page 201, check the error indicators in the Scalable Complex Management
health page as shown in Figure 4-24 on page 224. This section provides
additional guidance.
Problem: Members of partition not found
During the process of merging, a successful merge is not completed. The
members in this partition do not find each other and cannot find a member to
merge.
The systems cannot be bypassed for merging to boot in stand-alone mode. This
cannot be done remotely if the merge process is not completed.
If the RSA II scalability management menu does not enable you to manage any
partition, restart or power off the systems; the system can be recovered only by
an AC power cycle.
Note: You can bypass the boot to stand-alone remote if the scalability
management interface is unresponsive only by a support person who is
on-site, who must push the blue REMIND button.
No function in the remote control interface simulates the REMIND button.
How to identify the problem
The RSA Log can contain the following events:
Primary node:
E Merge Failure-No secondary servers found to merge.
E Merge Failure-Timed out waiting for secondary server.
I System Complex Powered Up
Chapter 4. Multinode hardware configurations
237
Advertisement
Table of Contents
