Cisco UCS Central provides native high-availability (H/A) features primarily for
deployments that do not contain a native hypervisor. In general, use a native
hypervisor, if available. In cases where native hypervisor H/A is not available
or active, you can safely run
Cisco UCS Central in standalone mode without using
Cisco UCS Central’s native H/A clustering.
If your host
hypervisor does not provide H/A support, then it is generally a best practice
to take advantage of
Cisco UCS Central’s H/A capabilities.
Keep in mind that
Cisco UCS Central can incur a temporary outage without disrupting service. This is
Cisco UCS Central only operates on the control-management plane, not the data plane.
Cisco UCS Central, lose visibility to the
Cisco UCS Central server, services within each
continue to operate normally. However, configuration changes to the environment
require you to restore
Cisco UCS Central server.
In general, we do
not recommend running both
Cisco UCS Central H/A and a native hypervisor concurrently.
Cisco UCS Central is down, and you have to make an administrative edit to a global
service profile, you can localize the global service profile such that
Cisco UCS Manager
can then edit it. This is only recommended for the scenario when you have to
edit a service profile when
Cisco UCS Central is down.
Cisco UCS Central in cluster-mode refers to a single logical instance of
Cisco UCS Central, using a primary and a subordinate
Cisco UCS Central VM with a shared clustered third disk.
You can also achieve
H/A by taking advantage of native hypervisor H/A capabilities. In this case, do
Cisco UCS Central’s H/A capabilities. They are not required.
for true DR capabilities are required to leverage any back-end VM DR
capabilities that they may have in place.
Achieve H/A with
Cisco UCS Central using one of two methods:
Refer to the Installation and Upgrade
Guide, before attempting to use either of these methods.