Large deployments of
Cisco UCS Central. Cisco has over 300 registered UCS
with 6,000-plus servers. Internal analysis by Cisco IT shows that they save
about 1-person/yr in operations equipment workload by leveraging
Cisco UCS Central. Cisco manages every UCS
Cisco UCS Central.
Cisco tested the
latest release of
Cisco UCS Central to support up to 10,000 servers in a single instance. This type of
scaling drove the complete redesign of the HTML-5 user interface (UI). The
HTML-5 UI is much more suited to managing UCS
and servers when scaling. The older Flash-based UI suffered from performance
issues when used in large environments.
deployments, leveraging an efficient domain group hierarchy is critical. A
large environment can contain UCS
dispersed all around a country, or around the world. A domain group might
encompass different time zones, DNS servers, user authentications, domain
controllers, and remote FTP servers. An efficient domain group hierarchy
permits a more granular approach to firmware upgrades and management.
Trying to separately
manage the backup-job schedules for dozens of UCS domains is tedious and prone
to error. This task is simplified with
Cisco UCS Central. You can define custom schedules for backup (fullstate.bin),
configuration export (allconfig.xml), and specific remote-copy FTP servers to
ensure proper safeguarding of those backups.
When using LDAP
integration for UCS
with internal LDAP servers, replicating those granular settings is also tedious
and prone to error.
Cisco UCS Central makes this task much easier. It sets LDAP configurations as part
of the domain group hierarchical policy. You can define the policy as broadly,
or as granularly, as required.
Cisco UCS Central treats the LDAP Policy as a single policy. You cannot break apart
different components of the policy, such as defining the group mappings at one
level in the hierarchy, and LDAP providers at a lower level.
You can place
policies as high up in the domain group hierarchy as applicable for the UCS
registered in your geographic domain group. You can also place infrastructure
and catalog firmware more granularly, lower in the subdomain group structure.
Ultimately, what works
best for you and your organization will be the best practice. You can always
opt for the simple approach and change or expand your subdomain group
structure. It is easier to change a domain group structure than to change an
organization structure. Changes to organization structure tend to be changes
that result in disruption of the environment.
Figure 1. Large UCS
Central Environment: Configuration Example
policies could reside here.
Cisco UCS Central can push them down to subdomains.
such as infrastructure and catalog firmware, backup and export, user
management, DNS management, time zone, and SEL could reside here.