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.
Review the following sections in this chapter for information about upgrading to the latest Cisco APIC-EM version and verification.
The GUI upgrade procedure requires that you perform the following tasks:
Download the release upgrade pack from the secure Cisco website at the Download Software link.
Run a checksum against the release upgrade pack.
Upload the release upgrade pack to the controller using the GUI.
Update the controller's software with the release upgrade pack using the GUI.
You must have successfully deployed the Cisco APIC-EM and it must be operational.
You must have received notification from Cisco that the Cisco APIC-EM software upgrade is available to download from the secure Cisco website.
You must have administrator (ROLE_ADMIN) permissions and access to all devices (RBAC Scope set to ALL) to perform this procedure.
For information about the user permissions required to perform tasks using the Cisco APIC-EM, see the chapter, Managing Users and Roles in the Cisco Application Policy Infrastructure Controller Enterprise Module Administrator Guide.
This procedure should be read with the latest version of the Cisco APIC-EM release notes, as there may be specific additional requirements for that release's upgrade.
Note | In a multi-host cluster, you only need to update a single host. After updating that single host, the other two hosts are automatically updated with the release upgrade pack. |
Step 1 | Review the
information in the Cisco notification about the
Cisco APIC-EM
upgrade.
The Cisco notification specifies the location of the release upgrade pack and verification values for either a Message Digest 5 (MD5) or Secure Hash Algorithm (SHA) 512 bits (SHA512) checksum.
| ||
Step 2 | Download the
Cisco APIC-EM
upgrade package from the Cisco website at the
Download Software link.
The release upgrade pack is available for download as a tar file that is also compressed, so the release upgrade pack has a .tar.gz extension. The release upgrade pack itself may consist of any or all of the following update files:
| ||
Step 3 | Run a checksum against the file using your own checksum verification tool or utility (either MD5 or SHA512). | ||
Step 4 | Review the
displayed checksum verification value from your checksum verification tool or
utility.
If the output from your checksum verification tool or utility matches the appropriate checksum value in the Cisco notification or from the Cisco secure website, then proceed to the next step. If the output does not match the checksum value, then download the release upgrade pack and perform another checksum. If checksum verification issues persist, contact Cisco support. | ||
Step 5 | Upload the
upgrade package to the controller using the
Update functionality of the GUI.
For additional information about this step, see the Cisco Application Policy Infrastructure Controller Enterprise Module Administrator Guide. | ||
Step 6 | Update the
controller's software with the upgrade package using the
Update functionality of the GUI.
For additional information about this step, see the Cisco Application Policy Infrastructure Controller Enterprise Module Administrator Guide.
| ||
Step 7 | After updating the controller's software with the upgrade package in the previous step, proceed to clear your web browser's cache. | ||
Step 8 | Check the
controller’s software version number in the GUI
SYSTEM
INFO tab, located in the
Home window. The
SYSTEM
INFO tab should display the new software version.
|
Verify the upgrade process, see Verifying the Upgrade Process.
The CLI upgrade procedure requires that you perform the following tasks:
Download the release upgrade pack (.tar.gz file) from the secure Cisco website at the Download Software link.
Run a checksum against the file.
Save the file to a location on your appliance, server, or virtual machine.
Run the Grapevine upgrade command on the file.
You must have successfully deployed the Cisco APIC-EM and it must be operational.
You must have received notification from Cisco that the Cisco APIC-EM software upgrade is available to download from the secure Cisco website.
You must have Grapevine SSH access privileges to perform this procedure.
This procedure should be read with the latest version of the Cisco APIC-EM release notes, as there may be specific additional requirements for that release's upgrade.
Step 1 | Review the
information in the Cisco notification about the
Cisco APIC-EM
upgrade.
The Cisco notification specifies the location of the release upgrade pack and verification values for either a Message Digest 5 (MD5) or Secure Hash Algorithm (SHA) 512 bits (SHA512) checksum.
| ||||
Step 2 | Download the
Cisco APIC-EM
upgrade package from the Cisco website at the
Download Software link.
The release upgrade pack is available for download as a tar file that is also compressed, so the release upgrade pack has a .tar.gz extension. The release upgrade pack itself may consist of any or all of the following update files:
| ||||
Step 3 | Run a checksum against the file using your own checksum verification tool or utility (either MD5 or SHA512). | ||||
Step 4 | Review the
displayed checksum verification value from your checksum verification tool or
utility.
If the output from your checksum verification tool or utility matches the appropriate checksum value in the Cisco notification or from the Cisco secure website, then proceed to the next step. If the output does not match the checksum value, then download the release upgrade pack and perform another checksum. If checksum verification issues persist, contact Cisco support. | ||||
Step 5 | Copy or move the file from your laptop or secure network location to the appliance, server, or virtual machine with the controller. | ||||
Step 6 | Using a Secure Shell (SSH) client, log into the host (appliance, server or virtual machine) with the IP address that you specified using the configuration wizard. | ||||
Step 7 | When prompted, enter your Linux username ('grapevine') and password for SSH access. | ||||
Step 8 | Navigate to the
folder where the file is located and run the following command:
$ grape update upload [path-to-upgrade-package] The grape update upload command will proceed to upgrade (upload and then update) the controller with the file. You should refrain from working with the controller during the entire upgrade process. During the upgrade process, the controller may shut down and restart. The shut down process may last for several minutes. A percentage bar will appear to show the upload progress. Once the upload process completes, you will receive notification of its completion and of the beginning of the update process. Release upgrade package uploaded successfully, Update process started. task_id: 8507f3f6-1de2-11e6-bf7e-00505695af10
| ||||
Step 9 | Once the
upgrade process finishes (upload and update), you will receive a success or
failure notification.
If the upgrade was successful, you will receive a successful upgrade notification and can then proceed working with the controller. If the upgrade was unsuccessful, you will receive an unsuccessful upgrade notification with suggested remedial actions to take. |
Verify the upgrade process, see Verifying the Upgrade Process.
To verify if an upgrade is successful, do one of the following:
Check the controller's GUI.
After the update, information about it will also appear in the Update History field of the Update window. The following update data is displayed in this field:
Date—Local date and time of the update
User—Username of the person initiating the update
Update Version—Update path of release upgrade pack version represented with an arrow.
Update Status—Success or failure status of the update.
Note | If you place your cursor over (mouseover) a failure status in this field, then additional details about the failure is displayed. |
Using a Secure Shell (SSH) client, log into the host (physical or virtual) with the IP address that you specified using the configuration wizard and run the following CLI commands:
grape update history—Displays update history of the controller, including individual task IDs.
grape release display current—Displays the Cisco APIC-EM software release currently running, with services and versions
grape instance display—Displays service instances and versions
grape instance status—Displays service instance status and versions
We also recommend that you run some network tests (for example, discoveries and/or path traces) to ensure that the controller functions as expected and that users are able to authenticate and access the resources on your network.