Table of Contents
Advertisement
In the merging process:
– The primary system scans for resources of all merged nodes in the
installed processor packages and memory, and then indicates how much
of it is available.
– The main memory is decreased by 256 MB for each merged system.
After a merge is successful:
– The video window on the primary system is active and contains all
information in POST or in the operating system.
– The video window at all other nodes is active and tells you that you can
watch the window on the primary node.
– The white scalability LED on the front of all systems that merged to a
partition as part of a multinode system becomes solid
on page 231.
– The port link LEDs on the rear of all systems that merged to a partition
becomes solid
on
green. See Figure 4-29 on page 231.
– The scalability LED at the front and the port link LEDs at the rear of the
systems go off again, if the scalability mode is changed after a partition is
started and rebooted to start in stand-alone mode.
If a merge is unsuccessful:
– The node or nodes that could not be merged boot in stand-alone mode.
– All nodes that could be merged boot as multinode system if the
merge
flag is enabled.
– If the scalability LED at the front and the port link LEDs of a system are off,
then this system is not part of a scalability partition or has not merged to a
partition.
– The system event log in the RSA II and Baseboard Management
Controller report the timeout and additional error events, at least on the
particular affected node.
The POST process and the loading of the operating system are shown on the
window only at the primary system, as follows:
– PCIe devices that are integrated or installed in the other systems at this
partition are visible on the window on the primary server.
– The started operating system provides all resources at this partition as
though it is one system.
Chapter 4. Multinode hardware configurations
on
. See Figure 4-29
partial
235
Advertisement
Table of Contents
