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 contains the following sections:
Before attempting to migrate to any software image version, follow these guidelines:
Upgrading to the latest version of the Cisco Nexus 1000V InterCloud consists of the following steps. After completing each procedure, return to this section to make sure that you have completed all required procedures in the correct sequence.
The upgrade process is irrevocable. Downgrade of the software is not supported.
Step 1 | Upgrading the Cisco Prime Network Services Controller . |
Step 2 | Upgrading the Cisco Nexus 1000V Virtual Supervisor Module (VSM) for InterCloud. |
Step 3 | Uploading the latest version of the InterCloud Extender and InterCloud Switch images to Cisco Prime Network Services Controller. |
Step 4 |
Updating the InterCloud links to the latest InterCloud Extender and InterCloudSwitch images. See Updating an InterCloud Link and Updating an InterCloud Link in High Availability Mode |
Upgrading the Cisco Prime Network Services Controller
After you back up the data for your existing Prime Network Services Controller 3.0 installation, you can upgrade to Prime Network Services Controller 3.0.2.
Caution |
To save a state for recovery purposes, perform a backup before beginning the upgrade. For more information, see Backing Up Data. |
Note |
Do not use TFTP to update data. |
Step 1 |
Using the CLI, log into Prime Network Services Controller as admin:
ssh admin@server-ip-address |
||
Step 2 |
Connect to local-mgmt:
connect local-mgmt |
||
Step 3 |
(Optional) Check the current version of the Prime Network Services Controller software:
show version |
||
Step 4 |
Download the Prime Network Services Controller 3.0.2 image from a remote file server:
copy scp://imageURLtoBinFile bootflash:/ |
||
Step 5 |
Upgrade to Prime Network Services Controller 3.0.2:
update bootflash:/nsc.3.0.2.XXXX.binwhere nsc.3.0.2.XXXX.bin is the image name. |
||
Step 6 |
Restart the server:
service restart |
||
Step 7 |
(Optional) Confirm that the Prime Network Services Controller server is operating as desired:
service status |
||
Step 8 |
(Optional) Verify that the Prime Network Services Controller software version has been updated:
show version |
||
Step 9 |
To confirm that Prime Network Services Controller is fully accessible after the upgrade, log in via the GUI. If your browser displays the previous version instead of the upgraded version, clear the browser cache and browsing history, and restart the browser. |
||
Step 10 |
If you have changed the server hostname or fully qualified domain name (FQDN), reconfigure Prime Network Services Controller connectivity with vCenter. For more information, see Task 2—Configuring Prime Network Services Controller Connectivity with vCenter.
|
Note |
Temporarily disable the Cisco Security Agent (CSA) on the remote file server. |
Note |
Do not use TFTP to back up data. |
Step 1 | Log in to the active Cisco Nexus 1000V VSM for InterCloud. | ||
Step 2 |
Log in to Cisco.com to access the links provided in this document. To log in to Cisco.com, go to the URL http://www.cisco.com/ and click Log In at the top of the page. Enter your Cisco username and password.
|
||
Step 3 | Access the Software Download Center by using this URL: | ||
Step 4 |
Navigate to the download site for your system. You see links to the download images for your switch. |
||
Step 5 | Choose and download the Cisco Nexus 1000V InterCloud zip file and extract the kickstart , system, and Policy Agent software files to a server. | ||
Step 6 |
Ensure that the required space is available for the image file(s) to be copied by entering the dir bootflash: command.
|
||
Step 7 | Verify that there is space available on the standby Cisco Nexus 1000V VSM for InterCloud by entering the dir bootflash://sup-standby/ command . | ||
Step 8 | Delete any unnecessary files to make space available if you need more space on the standby VSM. | ||
Step 9 |
If you plan to install the images from the bootflash:, copy the Cisco Nexus 1000V InterCloud kickstart , system and Policy Agent images image to the active VSM by using a transfer protocol. You can use ftp:, tftp:, scp:, or sftp:. The examples in this procedure copies a kickstart and system image using scp:.
|
||
Step 10 | Read the release notes for the related image file. See the Cisco Nexus 1000V InterCloud Release Notes. | ||
Step 11 | Save the running configuration to the startup configuration by using the copy running-config startup-config command. | ||
Step 12 |
Save the running configuration on the bootflash and externally.
|
||
Step 13 | Perform the upgrade on the active VSM using the kickstart , system, and Policy Agent images by using the install all kickstart bootflash:kickstart_filename system bootflash:system_filenamevnmpa bootflash: pa_filename command. The example in this procedure shows the kickstart ,system, and Policy Agent images. | ||
Step 14 |
Continue with the installation by pressing Y. If you press N, the installation exits gracefully.
|
||
Step 15 | After the installation operation completes, log in and verify that the switch is running the required software version by using the switch# show version command | ||
Step 16 | Copy the running configuration to the startup configuration by using the switch# copy running-config startup-config command | ||
Step 17 | Check the install log for the last installation by entering the following commands. | ||
Step 18 | In case of an upgrade failure check the logs by entering the following commands. | ||
Step 19 | Review information about reserving memory and CPU on the VSM VM to accommodate the new scalability limits. |
After the zipped file is imported, Prime Network Services Controller automatically places the zipped files in the correct locations and populates the Add InterCloud Link Wizard with the images.
Note |
|
This feature helps ensure that you always have appropriate, compatible images available for creating InterCloud links and instantiating cloud VMs.
Step 1 | Choose InterCloud Management > InterCloud Link > Images. |
Step 2 | Click Import Bundled Image. |
Step 3 |
In the Import Bundled Image dialog box:
|
Updating an InterCloud Link
Prime Network Services Controller enables you to update the images for an InterCloud Extender and Switch for a deployed link.
Note |
Prime Network Services Controller does not support Amazon Marketplace functionality. |
Note |
If you undeploy an InterCloud link while the InterCloud link is being upgraded, the InterCloud Switch might not be terminated on the cloud. If this occurs, you will need to manually remove the InterCloud Switch from the cloud when the link is undeployed. |
Ensure that a VM Manager is configured in Prime Network Services Controller.
Ensure that you have imported the new platform images.
Use this procedure to update both the primary and secondary devices in an InterCloud link that is configured for high availability.
Note |
When you update an InterCloud link in a HA mode, only the standby InterCloud link in updated. |
Step 1 | Update the InterCloud link as described in Updating an InterCloud Link. |
Step 2 | Verify that the InterCloud link is updated on the Cisco Nexus 1000V InterCloud VSM as follows: |
Step 3 |
Trigger a switchover as follows:
|
Step 4 | Update the InterCloud link again. |
Step 5 | Verify that the upgrade is successful by entering the following commands: |