hierarchy design is one of your more important architectural design decisions.
There is no right or wrong method. The goal is to best reflect your specific
environment and management design requirements. You must understand the
following attributes of domain groups:
is an arbitrary grouping of individual
Cisco UCS domains. The
Cisco UCS Central administrator designs the grouping. A
is purely a
Cisco UCS Central global construct. A domain is not aware that it is a member of a
can only reside in one domain group at a time, unlike server
where one server can reside in multiple server
Cisco UCS Central places all
at registration. Domains in the ungrouped
resolve to any
even if the local
Cisco UCS administrator has opted-in for
policy resolution control.
policies in effect for all domains in the
They resolve and apply in a domain group.
You can move
However, any domain group-to-domain move can be disruptive, depending on the
policies in the destination
resolve their own policies from domain groups in which they reside. If a new
domain joins a
then it applies the new
which may impact service.
global firmware management, evaluate the impact. Realize that more than one
Cisco UCS domain might be subject to the policy definitions for that firmware.
It might also be subject, simultaneously, to any changes or upgrades to that
domains can automatically join a
based on qualification policies at registration time. Domain-group policy
qualifications work in a similar manner to server-pool policy qualifications.
You can place
anywhere in the domain-group hierarchy, and override policies set at a higher
level by setting a policy in a lower domain group.
administrator moves a domain to a new
the policies for the old
are not necessarily removed. Instead, the old policies remain in place, until
the new policies overwrite the previous ones.
For example: Let's say
that you have a UCS domain backup policy. The old policy defines the backup
schedule and the new policy omits this policy. The UCS backups still occur
based on the old schedule. They change if you create a new policy for the new
are resolved through references are removed if they are not present in the new
Weigh the degree
to which you employ the subdomains against the amount of administration and
management required for managing the different subdomains.
You can nest
subdomain groups up to five levels deep, hierarchically, for finer granularity
of policy control.