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:
You can upgrade Cisco UCS Central release 1.1(2a) or 1.2 to 1.3 in either standalone or cluster mode. If you are already in a standalone mode installation, when you upgrade to release 1.3, you can also configure your environment in cluster mode. For upgrading a cluster setup, see Upgrading Cisco UCS Central in Cluster Mode
Make sure your system meets the system requirements for Cisco UCS Central, release 1.3. See System Requirements.
Cisco UCS Central, release 1.3 requires a minimum of 12GB RAM and 40 GB storage space. Make sure that the VM RAM meets this requirement and disk1 size is upgraded to 40 GB. Otherwise, the upgrade will fail.
Use the ISO image for an upgrade Cisco UCS Central.
After the upgrade, make sure to clear browser cache before logging into the Cisco UCS Central GUI.
Caution | Cisco UCS Central, release 1.3 supports Cisco UCS Manager, release 2.1(2), 2.1(3), 2.2(x), 2.5(x)MS, and 3.0(x). You must first upgrade Cisco UCS Manager to one of the supported release versions before upgrading Cisco UCS Central. If you do not upgrade Cisco UCS Manager first, Cisco UCS Central generates version mismatch errors and any registered Cisco UCS domains stop receiving updates from Cisco UCS Central. |
You can only upgrade Cisco UCS Central to release 1.3(1a) from any of the following two releases:
Before upgrading Cisco UCS Central to 1.3 you must do the following:
Make sure you have Cisco UCS Manager to 2.1(2) or newer. It is recommended to upgrade Cisco UCS Manager to the latest version to ensure complete feature support.
Upgrade Cisco UCS Central 1.0 to one of supported Cisco UCS Central 1.1 patch release.
Make sure to take a full state backup before starting the upgrade process.
Only ISO upgrade is supported for upgrade from release 1.0 to 1.1. The ISO upgrade is preferred upgrade method for upgrade from release 1.1 to any newer releases.
You can use backup and restore option to ensure that you can recreate the environment in case of any failure. Backup and restore is not recommended for upgrades. The following is the recommended best practice for back up and restore:
Use full state backup for disaster recovery scenario, where the Cisco UCS Central VM is lost.
Use configuration import for importing configuration from a backup file on an existing Cisco UCS Central VM.
Full State backup does not backup firmware images downloaded in Cisco UCS Central. When deploying new Cisco UCS Central VM and restoring from a full state backup, make sure to download the firmware images again in Cisco UCS Central. After a full state restore, you must download the firmware images before acknowledging the Cisco UCS domains from suspend mode.
The following options are NOT supported in 1.3(1a):
Erase samdb config import.
Upgrade from Cisco UCS Central releases 1.0 and 1.1(1a)
Taking a full state back up from Cisco UCS Central release 1.0 or 1.1(1a) to restore Cisco UCS Central release 1.3.
Taking a config export from Cisco UCS Central release 1.0 or 1.1(1a) to config import from Cisco UCS Central release 1.3.
Downgrade from Cisco UCS Central release 1.3 to and Cisco UCS Central releases 1.0 or 1.1.
This procedure upgrades the current running version of the RHEL kernel and all Cisco UCS Central components. It also retains all Cisco UCS Central data.
You must have obtained the Cisco UCS Central, release 1.3 ISO image. See Obtaining the Cisco UCS Central Software from Cisco.com. We recommend that you backup your Cisco UCS Central data before you perform this procedure.
You must complete ISO upgrade on both the nodes in the cluster. You can perform the upgrade in any order on both nodes. The cluster setup is available only after both the nodes are running same release versions of Cisco UCS Central.
Make sure to perform the following Step 1 through Step 5 on both Node A and Node B in the cluster.
You must have obtained the Cisco UCS Central ISO image for this release. See Obtaining the Cisco UCS Central Software from Cisco.com. We recommend that you backup your Cisco UCS Central data before you perform this procedure. Make sure to retain the Shared storage connectivity.
Depending on the registration status and availability of Cisco UCS domains, the HA status would be remain similar to the state before the upgrade.
Note | In a cluster set up, when the RDM link goes down on the primary node, DMEs cannot write to the database. This causes a crash on the primary node and failover to the subordinate node. The subordinate node takes over as the primary node. The database is then mounted in read-write mode on the new primary node. Because the RDM link is down, umount fails on the old primary node. When the RDM link comes up, the database is mounted on the old primary (current subordinate) node in read-only mode. As a workaround, you can restart pmon services on the current subordinate node or restart the node itself. Either of these processes will unmount the read-only partition and enable proper cleanup. |
We recommend that you backup your Cisco UCS Central data before you perform this procedure.
Upgrade Cisco UCS Central from 1.0 to 1.1 using the ISO image. See Upgrading Cisco UCS Central in Standalone Mode
Step 1 | Shutdown the VM. | ||
Step 2 | Add shared storage device to the VM. See Adding and Setting up an RDM Shared Storage on Hyper-V or Adding and Setting up an RDM Shared Storage on VMware. | ||
Step 3 | Start the VM and wait for the VM to come up. | ||
Step 4 | Run the local
management command to connect to local management.
| ||
Step 5 | At the enable cluster mode prompt, enter yes and press Enter to continue. | ||
Step 6 | When prompted to
enter the Shared Storage Device, enter the number of the shared storage device
and press
Enter.
This VM becomes Node A of the cluster is made Forced Primary by default. The system now transfers all data from the local disk to the shared disk, converting the system from standalone mode to cluster mode. | ||
Step 7 | Check cluster
state. The node should display as elected primary.
You can add the Node B to the cluster. See Installing Cisco UCS Central on Node B
|