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:
For information on the migration of Cisco Nexus 1000V with VSG to Cisco Nexus 1000VE with VSG, see the Cisco Nexus 1000VE Installation Guide, Release 5.2(1)SV5(1.1)
When you upgrade the Cisco PNSC software, all current command-line interface (CLI) and graphical user interface (GUI) sessions are interrupted, which means that you must restart any CLI or GUI sessions.
Migration of Nexus 1000V to Nexus 1000VE includes upgrading PNSC to version 3.5.1a. The following table lists the compatibility information for the PNSC upgrade.
|
Initial Version |
Intermediate State(s) |
Final Version |
|
3.4.2c |
NA |
3.5.1a |
|
3.4.2d |
NA |
3.5.1a |
 Note |
For detailed information about Upgrading PNSC, see Upgrading Prime Network Services Controller. |
Upgrade Procedure for Cisco PNSC Release 3.4.2d to Release 3.5.1
You are logged in to the CLI in EXEC mode.
You have backed up the new software files to a remote server and have verified that the backup file was created on the remote server.
You must have the Cisco PNSC Release 3.5.1 downloaded.
| Command or Action | Purpose | |||||
|---|---|---|---|---|---|---|
| Step 1 |
nsc# connect local-mgmt |
Places you in local management mode. |
||||
| Step 2 |
(Optional) nsc (local-mgmt)# show version |
(Optional)
Displays the version information for the Cisco PNSC software. |
||||
| Step 3 |
(Optional) nsc (local-mgmt)# copy scp://user@ example-server-ip/example-dir/filename bootflash:/ |
(Optional)
Copies the Cisco PNSC software file to the VM. |
||||
| Step 4 |
nsc (local-mgmt)# dir bootflash:/ |
Verifies that the desired file is copied in the directory. |
||||
| Step 5 |
nsc (local-mgmt)# update bootflash:/ filename |
Begins the update of the Cisco PNSC software. |
||||
| Step 6 |
(Optional) nsc (local-mgmt)# service status |
(Optional)
Allows you to verify that the server is operating as desired. |
||||
| Step 7 |
(Optional) nsc (local-mgmt)# show version |
(Optional)
Allows you to verify that the Cisco PNSC software version is updated.
|
The following example shows how to connect to the local-mgmt mode:
nsc# connect local-mgmt
Cisco Prime Network Services Controller
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2018, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
The following example shows how to display version information for the Cisco PNSC:
nsc(local-mgmt)# show version
Name Package Version GUI
---- ------- ------- ----
core Base System 3.4(2b) 3.4(2b) service-reg
Service Registry 3.4(2b) 3.4(2b) policy-mgr
Policy Manager 3.4(2b) 3.4(2b) resource-mgr
Resource Manager 3.4(2b) 3.4(2b) vm-mgr
VM manager 3.4(2b) none vsm-service
VSM Service 3.4(2d) none cloudprovider-mgr
Cloud Provider Mgr 3.4(2d) none
localhost(local-mgmt)#The following example shows how to copy the Cisco PNSC software to the VM:
nsc(local-mgmt)# copy scp://<user@example-server-ip>/example1-dir/nsc.3.5.1.bin bootflash:/
Enter password:
100% 143MB 11.9MB/s 00:12The following example shows how to see the directory information for Cisco PNSC:
nsc(local-mgmt)# dir bootflash:/
1.1G Dec 05 00:57 nsc.3.5.1.bin
Usage for bootflash://
6359716 KB used
10889320 KB free
18187836 KB totalThe following example shows how to start the update for the Cisco PNSC:
nsc(local-mgmt)# update bootflash:/nsc.3.5.1.bin
It is recommended that you perform a full-state backup before updating any VNMC component. Press enter to continue or Ctrl-c to exit.The following example shows how to display the updated version for the Cisco PNSC:
nsc(local-mgmt)# show version
Name Package Version GUI
---- ------- ------- ----
core Base System 3.5.1 3.5.1
service-reg Service Registry 3.5.1 3.5.1
policy-mgr Policy Manager 3.5.1 3.5.1
resource-mgr Resource Manager 3.5.1 3.5.1
vm-mgr VM manager 3.5.1 none
cloudprovider-mgr Cloud Provider Mgr 3.5.1 noneUpgrade from existing PNSC 3.4.2c/d with PNSC 3.5.1a VSM and VSG.
Register Policy Agent (PA) of PNSC 3.5.1a VSM and VSG to PNSC 3.4.2c/d.
Create Firewall object for PNSC 3.5.1a VSG with different data IP (to be later configured on PNSC 3.5.1a VSM) on PNSC 3.4.2c/d.
Migrate to PNSC 3.5.1a VSG with data IP (to be provided in the migration config text field).
After migration is complete, PNSC 3.4.2c/d is now attached to PNSC 3.5.1a VSM and VSG. This leads to VM Info loss in PNSC.
Upgrade PNSC 3.4.2 c/d to PNSC 3.5.1a . The VM Info gets populated on PNSC.
Re-register PNSC 3.5.1a VSM and VSG Policy Agent (PA) and the traffic is restored.
Feedback