The multi-node setup
is supported for
on a 64-bit operating system only. With a multi-node setup, you can scale
to support a larger number of VMs than is supported by a single installation of
This setup includes the following nodes:
Figure 1. Multi-Node Topology
For a multi-node
setup, you have to install the license on the primary node only.
A multi-node setup
improves scalability by offloading the processing of system tasks, such as
inventory data collection, from the primary node to one or more service nodes.
You can assign certain system tasks to one or more service nodes. The number of
nodes determines how the processing of system tasks are scaled.
Node pools combine
service nodes into groups and enable you to assign system tasks to more than
one service node. This provides you with control over which system task is
executed by which service node or group of service nodes. If you have multiple
service nodes in a node pool and one of the service nodes is busy when a system
task needs to be run,
uses a round-robin assignment to determine which service node should process
that system task. if all service nodes are busy, you can have the primary node
run the system task.
However, if you do
not need that level of control over the system tasks, you can use the default
task policy and add all of the service nodes to the default node pool. All
system tasks are already associated with the default task policy, and the
round-robin assignment will be used to determine which service node should
process a system task.
If you want to have
some critical tasks processed only by the primary node, you can assign those
tasks to a local-run policy.
For more information
about how to configure the primary node and service nodes, and how to assign
system tasks, see the
Cisco UCS Director