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.
This chapter includes the following sections:
Cisco UCS Central provides centralized management capabilities to multiple Cisco UCS domains across one or more data centers. Cisco UCS Central works with Cisco UCS Manager to provide a scalable management solution for a growing Cisco UCS environment.
Cisco UCS Central does not reduce or change any local management capabilities of Cisco UCS Manager, such as its API. This allows you to continue using Cisco UCS Manager the same way you did before Cisco UCS Central. This also allows all existing third party integrations to continue to operate without change.
To manage Cisco UCS Manager through Cisco UCS Central, you must register the Cisco UCS domains in Cisco UCS Central. You can register a Cisco UCS domain as a part of a domain group or as an ungrouped domain. When you have a domain group, all registered domains in the domain group can share common policies and other configurations.
You can use a Fully Qualified Domain Name (FQDN) or IP address to register Cisco UCS domains in Cisco UCS Central.
Note | During the initial registration process with Cisco UCS Central, all of the active Cisco UCS Manager GUI sessions are terminated. |
Before registering a domain in Cisco UCS Central, do the following:
Configure an NTP server and the correct time zone in both Cisco UCS Manager and Cisco UCS Central to ensure that they are in sync. If the time and date in the Cisco UCS domain and Cisco UCS Central are out of sync, the registration might fail.
Obtain the hostname or IP address of Cisco UCS Central. You cannot use the same hostname for both Cisco UCS Central and Cisco UCS Manager. For standalone mode, use individual VM IP address. If you plan to setup in cluster mode, use virtual IP address.
Obtain the shared secret that you configured when you deployed Cisco UCS Central.
Note |
|
Warning | You must upgrade to Cisco UCS Manager Release 2.1(2) or greater before registering with Cisco UCS Central. If you try to register earlier versions of Cisco UCS Manager, the registration will fail. |
Caution | If you want to unregister any registered Cisco UCS Domain in a production system, contact Cisco Technical Support. |
When you unregister a Cisco UCS Domain from Cisco UCS Central:
You can no longer manage the service profiles, policies and other configuration for the Cisco UCS Domain from Cisco UCS Central.
All global service profiles and policies become local and continues to operate as local entities. When you re-register the domain, the service profiles and polices still remain local.
The following example registers a Cisco UCS Domain with a Cisco UCS Central system with a FQDN, and commits the transaction:
UCS-A# scope system UCS-A /system # create control-ep policy UCSCentral.MyCompany.com Shared Secret for Registration: S3cretW0rd! UCS-A /system/control-ep* # commit-buffer UCS-A /system/control-ep #
Caution | If you want to unregister any registered Cisco UCS Domain in a production system, contact Cisco Technical Support. |
When you unregister a Cisco UCS Domain from Cisco UCS Central:
You can no longer manage the service profiles, policies and other configuration for the Cisco UCS Domain from Cisco UCS Central.
All global service profiles and policies become local and continues to operate as local entities. When you re-register the domain, the service profiles and polices still remain local.
Command or Action | Purpose |
---|
The following example unregisters a Cisco UCS Domain from Cisco UCS Central and commits the transaction:
UCS-A# scope system UCS-A /system # delete control-ep policy UCS-A /system* # commit-buffer UCS-A /system #
Cisco recommends that you always register Cisco UCS domains using Cisco UCS Central's Fully Qualified Domain Name (FQDN). If domains are registered with FQDN, any change in the Cisco UCS Central IP address is transparent to the domain. Changing Cisco UCS Central's IP address is supported only when Cisco UCS Central has a Fully Qualified Domain Name (FQDN), and when the Cisco UCS domain is registered using a Cisco UCS Central domain name.
Note | Changing Cisco UCS Central's IP address is not supported if Cisco UCS domains are registered using Cisco UCS Central's IP address. |
Step 1 | Delete the existing Cisco UCS Central IP address from the DNS server for the hostname and enter the new IP address and the Cisco UCS Central hostname. |
Step 2 | On the virtual infrastructure management platform (for example, VMware vCenter), change the virtual network interface (VIF) to point to the new subnet. |
Step 3 | From the Cisco UCS Central VM console, change the IP address of the network interface. |
Step 4 | Launch Cisco UCS Central from the GUI using the hostname. If the Cisco UCS Central GUI is inaccessible, then restart pmon command from the Cisco UCS Central CLI. |
Step 5 | Verify the Cisco UCS Central registration status on the Cisco UCS Manager GUI. |
Step 6 | For a High Availability setup, IP addresses of both the nodes and the virtual IP can be changed only at the primary node as shown in the example below. |
Changing IP for a UCS Central system in Standalone mode: UCSC # scope network-interface a UCSC/network-interface # set net ip 10.10.10.2 gw 10.10.10.1 netmask 255.255.255.0 Warning: When committed, this change may disconnect the current CLI session UCSC/network-interface* # commit-buffer UCSC/(local-mgmt)# pmon restart Shutting down pmon: [ OK ] Starting pmon: [ OK ] ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Changing node IP for a UCS Central system in High-Availability mode: UCSC # scope network-interface a UCSC/network-interface # set net ip 10.10.10.2 gw 10.10.10.1 netmask 255.255.255.0 Warning: When committed, this change may disconnect the current CLI session UCSC/network-interface* # commit-buffer UCSC # scope network-interface b UCSC/network-interface # set net ip 10.10.10.2 gw 10.10.10.1 netmask 255.255.255.0 Warning: When committed, this change may disconnect the current CLI session UCSC/network-interface* # commit-buffer UCSC/(local-mgmt)# pmon restart Shutting down pmon: [ OK ] Starting pmon: [ OK ] –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––-- Changing virtual IP for a UCS Central system in High-Availability mode UCSC# scope system UCSC/system # set virtual-ip a.b.c.d System IP Address ipv6 System IPv6 Address UCSC/system # set virtual-ip 10.106.227.206 UCSC/system*# commit buffer
You can change the Cisco UCS Manager IP address if Cisco UCS domains are registered to Cisco UCS Central through an IP address. Use the following steps to change the Cisco UCS Manager IP address:
Step 1 | Delete the existing Cisco UCS Manager IP address from the DNS server for the hostname, and enter the new IP address and the same Cisco UCS Manager hostname. |
Step 2 | From the primary FI console, run the following commands: Example: UCS-A# scope fabric-interconnect a UCS-A /fabric-interconnect # set out-of-band ip 10.193.190.61 netmask 255.255.255.0 gw 10.193.190.1 UCS-A /fabric-interconnect* # scope fabric-interconnect b UCS-A /fabric-interconnect* # set out-of-band ip 10.193.190.62 netmask 255.255.255.0 gw 10.193.190.1 UCS-A /fabric-interconnect* # scope system UCS-A /system* # set virtual-ip 10.193.190.60 UCS-A /system* # commit-buffer |
Step 3 | After running the commands shown above, launch Cisco UCS Manager using the hostname and verify that the registration status is not changed. |
Step 4 | Under service-reg in the Cisco Cisco UCS Central CLI, verify that the show clients commands point to the new IP address for the UCS Domain. |
Step 5 | (Optional) To check if the IP address is changed, launch Cisco UCS Manager GUI from Cisco UCS Central, and verify that the new IP address is updated in the UI.
You can perform an additional check by updating one of the global service profile labels from the Cisco UCS Central GUI and ensure that the updated label is pushed down to Cisco UCS Manager. You can also create new global service profiles or policies and push them down to Cisco UCS Manager to verify that the new IP address is updated in the UI. |
You can migrate a Cisco UCS Central instance to support Data Center migration or Disaster Recovery use cases. The following are required to successfully migrate a Cisco UCS Central instance:
Cisco UCS Central has a Fully Qualified Domain Name (FQDN). In order to migrate a Cisco UCS Central instance, the FQDN (hostname) of the instance must remain the same.
Note | Cisco UCS Central supports changing of the Cisco UCS Central IP address during migration. |