The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Typically, DNS management is defined at a global or corporate level. Therefore, DNS domain names and DNS servers are good candidates for global policy management. Define them as high in the domain group hierarchy’s operational policies as possible.
Policies around power management include two different policies:
Global power allocation policy—Determines whether to apply power capping at the chassis level, or manually override the power caps at the individual blade level.
Power policy—Chassis-level configuration for: Nonredundant, N+1, or Grid for the physical AC power.
The power policy is a strong candidate for Cisco UCS Central policy definition.
Global power allocation policy is one of the most sensitive policies for environmental and location dependencies. Best practices depend on your environment.
For example:
Power budgets, per rack, may vary between different datacenters and locations.
Some sites may have implemented power groups to create power caps that span multiple racks, specific to a data center layout.
Your global power allocation policy depends on local constraints. Definition schemes, such as creating broadly-scoped policies to restrict power on a per-rack basis, are the simplest. However, a definition scheme is site-specific and hard to generalize.
Server
Uplink
Unified Ports
 Note |
You cannot use Cisco UCS Central to manage objects that depend on physical ports, including pin groups and port-channels for both Ethernet and Fibre Channel. |
After you set the time in the NTP server, Cisco UCS Manager may appear to not sync the time immediately.
Note |
Set the hour using 24-hour military time. |
scope system
scope services
set clock month day year hour minute secondThe following example sets the clock to February 22, 2016 at 13:44:00.
scope system
scope services
set clock february 22 2016 13 44 00A message follows, indicating, Clock synchronization successful, with Cisco UCS Manager time reflecting the change. Your next registration attempt should succeed.
Note |
A time difference of a few seconds can cause registration to fail. For a successful registration to occur, the Cisco UCS Manager system time cannot be behind the Cisco UCS Central system time. |
The following CLI commands show how to check the status of the services running on the Cisco UCS Central server.
UCSC-A# connect local-mgmt
UCSC-A (local-mgmt)# show pmon stateNote |
Do not reset PMON (services) without consulting Cisco TAC. |
Many features of the Cisco UCS Central management interface rely on available or imported HTTPS certificates (from each Cisco UCS domain managed by Cisco UCS Central) on the client machine.
The browser uses these certificates to manage Cisco UCS Central for invoking features such as KVM launch, Cisco UCS Manager launch, and to query particular faults or alerts in the Cisco UCS fault summary. If you do not import the certificates properly, or if they have expired, or if certain security settings are enabled, you may encounter errors.
Feedback