Cisco Prime Network Services Controller 3.4.2b Installation Guide
Bias-Free Language
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.
- Updated:
- March 31, 2017
Chapter: Upgrading Prime Network Services Controller
Upgrading
Prime Network Services Controller
This section includes the following topics:
Upgrading Overview
The following tables show the supported upgrade paths for Prime Network Services Controller. Upgrading to Prime Network Services Controller is supported only in VMware environments.
| Hypervisor | Supported Upgrade Versions | |
|---|---|---|
| Standalone Mode | Orchestrator Mode | |
|
VMware |
3.2, 3.2.2a, 3.2.2b, 3.4.1c, 3.4.1d, 3.4.2a, 3.4.2b |
Not applicable |
| Initial Version | Intermediate State(s) |
Final Version |
|---|---|---|
|
2.0.3 |
2.1 to 3.0.2g to 3.2.2a to 3.4.1d |
3.4.2b |
|
2.1 |
3.0.2 to 3.2.2a to 3.4.1d |
3.4.2b |
|
3.0.2 |
3.2.2a to 3.4.1d |
3.4.2b |
|
3.2.1d |
3.4.1d |
3.4.2b |
|
3.2.2b |
3.4.1d |
3.4.2b |
|
3.4.1b |
3.4.1d |
3.4.2b |
|
3.4.1c |
3.4.1d |
3.4.2b |
|
3.4.1d |
N/A |
3.4.2b |
|
3.4.2a |
N/A |
3.4.2b |
To upgrade from VNMC 2.x to Prime Network Services Controller , you must first upgrade to one of the supported upgrade versions.
-
If you are upgrading from VNMC 2.1, ensure that the VNMC 2.1 is deployed in a single disk. The upgrade will fail if the VNMC 2.1 deployment spans more than one disk.
 Note | For more information on PNSC upgrade matrix, see the Cisco Prime Network Services Controller Release Notes at http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/network_services_controller/3-4-2b/release-notes/b_CiscoPrimeNetworkServicesController-3-4-2-ReleaseNotes.html. |
Upgrade Workflow
The following table identifies the tasks in sequence for a smooth upgrade.
| Task | Notes |
|---|---|
|
1. Perform a full-state backup of Prime Network Services Controller using the Secure Copy (SCP) protocol. |
See Backing Up Data. |
|
2. Stop the Prime Network Services Controller Device Adapter VM. |
Do not delete this VM yet. You can delete it after you verify that the upgrade is successful and that you do not need to restore the previous version. |
|
3. Upgrade Prime Network Services Controller by using the CLI update bootflash command. |
|
|
4. Using the new Prime Network Services Controller Device Adapter version, deploy a new Prime Network Services Controller Device Adapter VM and power it up. |
When configuring the new Prime Network Services Controller Device Adapter VM, use the same host information (hostname, access credentials, and management IP address) as the previous version. |
|
5. Verify that Prime Network Services Controller has been successfully upgraded. |
|
|
6. Delete the previous Prime Network Services Controller Device Adapter VM. |
After verifying that the service nodes are registered, you can delete this VM. |
- Allow the system to synchronize and stabilize for at least 15 minutes. Do not add or modify policies or service devices during this time.
- Allow approximately five minutes for each service node to register with Prime Network Services Controller.
- If you see the previous version of Prime Network Services Controller in your browser, clear the browser cache and history, and restart the browser. This applies to all supported browsers: Internet Explorer, Mozilla Firefox, and Chrome.
Backing Up Data
Back up Prime Network Services Controller before upgrading to a new version.
Adhere to the following conventions when backing up Prime Network Services Controller:
-
Temporarily disable the Cisco Security Agent (CSA) on the remote file server.
-
Do not use TFTP to back up data.
-
Do not perform a backup while the system is importing images.
-
Access the CLI through the console instead of using SSH. If the SSH session should disconnect, you will not be able to access the VM.
Upgrading to Prime Network Services Controller
After you back up the data for your existing Prime Network Services Controller installation, you can upgrade to Prime Network Services Controller .
Adhere to the following guidelines when upgrading Prime Network Services Controller:
-
Do not use TFTP to update data.
-
Do not access the GUI during the upgrade process.
-
Use the console to access the CLI instead of SSH. If the SSH session should disconnect, you will not be able to access the VM.
Note | For more information on PNSC upgrade matrix, see the Cisco Prime Network Services Controller Release Notes at http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/network_services_controller/3-4-2b/release-notes/b_CiscoPrimeNetworkServicesController-3-4-2-ReleaseNotes.html. |
Confirm the following:
-
You have backed up your current system for recovery purposes, if needed. For more information, see Backing Up Data.
-
Prime Network Services Controller has two virtual disks with the following configuration:
If you do not have two disks configured, you will not be able to upgrade to .
Feedback