Complete Upgrade Procedure
You are Upgrading From | Follow The Sequential Steps in the Following Section: |
---|---|
Cisco VSG Release 5.2(1)VSG2(1.1b) to Release 5.2(1)VSG2(1.2b) and Cisco PNSC Release 3.2 to Cisco PNSC Release 3.4. |
Upgrade Procedures for Cisco VSG Release 5.2(1)VSG2(1.1b) to Release 5.2(1)VSG2(1.2b) and Cisco PNSC Release 3.2 to Cisco PNSC Release 3.4. This includes upgrade procedures for Cisco Nexus 1000V Release 5.2(1)SM1(5.2b) to Release 5.2(1)SM3(1.1). |
-
Stage 1: Upgrading Cisco PNSC
-
Stage 2: Upgrading a Cisco VSG Pair
-
Stage 3: Upgrading the VSM pair and the VEMs
![]() Note |
We highly recommend that you upgrade the Cisco VSG and the Cisco PNSC in the sequence listed. Any deviation from the ordered steps could cause disruption of your connectivity and data communication. The Cisco PNSC must be upgraded with the corresponding policy agent (PA). |
Information About Cisco Prime NSC Upgrades
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.
Information About Cisco VSG Upgrades
The upgrade procedure for Cisco VSG in standalone or HA mode is hitful, which means that you must manually reload the Cisco VSG for the new image to become effective.
Because license information is not stored with the Cisco VSG but is maintained between the Virtual Supervisor Module (VSM) and Virtual Ethernet Module (VEM), if packets are received at the Cisco VSG, that means that the license is valid and the packets are processed.
An upgrade affects two bin files: the kickstart file and the system file.
An upgrade does not erase any of the existing information, when the Cisco VSG comes online. Because the Cisco VSG is stateless, it gets all this information from the Cisco PNSC at bootup.