Table of Contents
Advertisement
Note: Bear in mind this expects a local response if you do not have access
to an uninterruptible power supply that can manage the power connections
to shut off/ or turn on the power to the outlets.
3. After powering off all boxes:
– Delete the partition, as described in 4.8, "Working with partitions" on
page 228. Create a new partition and try to merge.
– Clear all Complex information as described in 4.8, "Working with
partitions" on page 228. Create a new partition and try to merge.
4.9.2 Problems with merging if prerequisites were not met
This section describes situations where the merge process fails, particularly if the
prerequisites listed in 4.4, "Prerequisites to create a multinode complex" on
page 201 are not met.
Problem 1: CPU mismatch
The merging of nodes fails with information about the window, as shown in
Example 4-6.
Example 4-6 x3950 M2: merging process unsuccessful, Primary server
Chassis Number
1
2
Partition merge failed: No secondary chasiss to merge successful
64 GB Memory: Installed
512 MB Memory: Consumed by Scalability
How to identify the problem
To identify the issue:
Check that all systems in this complex have two or four CPUs installed.
Check that all servers you added to this complex have the same type of CPU
regarding speed, cache size, and number of cores. This is especially
important if you ordered your servers on different dates or added a new one to
an existing complex.
Partition Merge Status
Primary
Failed: CPU Mismatch
Chapter 4. Multinode hardware configurations
Installed Memory
32GB
239
Advertisement
Table of Contents
