Cisco Nexus Cloud Services Platform Release Notes, Release 5.2(1)SP1(7.3b)

Upgrading from Release 5.2(1)SP1(7.3), 5.2(1)SP1(7.2), or 4.2(1)SP1(6.2)

The procedure to upgrade from Release 5.2(1)SP1(7.3), 5.2(1)SP1(7.2), or 4.2(1)SP1(6.2) is the same as described in Cisco Nexus Cloud Services Platform Software Installation and Upgrade Guide, Release 5.2(1)SP1(7.1).

Upgrading from Release 5.2(1)SP1(7.1)

To upgrade from Release 5.2(1)SP1(7.1), a manual upgrade procedure is required. Complete the following steps.

Prerequisites

---

Step 1 Copy the new image to the bootflash:repository/ directory.

Step 2 Note the name of the image to use during the upgrade.

Step 3 Use the show system redundancy status command to note the redundancy role of the active module on which the upgrade is being performed. The role should be primary or secondary.

 

Manual Upgrade

To perform the manual upgrade:

---

Step 1 Enter the following command to update to the new image:

---

Note The command and the image name do not auto complete and must be typed in completely.

Step 2 Copy the running configuration to the startup configuration:

---

Note It takes up to 10 seconds to copy the running configuration to the startup configuration. Therefore, you must wait for 10 seconds before proceeding to Step 3.

Step 3 Enter the reload module module command to reload the standby supervisor module and allow it to come back online:

• If the primary module is the active module:

• If the secondary module is the active module:

Step 4 When the standby supervisor module is back online, verify the high availability (HA) synchronization is complete with the active module:

Step 5 After the HA synchronization is complete, switch over to the other module:

Step 6 On the new active supervisor module, wait for the other supervisor module to come back online:

Step 7 Verify that the module is online. When HA is complete, verify that the upgrade procedure is complete:

 

Bug ID	Headline
CSCuj77643	Deploying or removing the Citrix NetScaler 1000V restarts the Cisco Nexus 1000V VSM and the Cisco Virtual Security Gateway VSBs of all 4.2(x) releases.
CSCuo98930	A configuration change does not automatically get copied to the startup configuration for the following commands: (config-if)# channel-group (config-svs-domain)# control uplink uplink int (config-svs-domain)# management uplink uplink int
CSCur20537	The install nexus1010 command returns an “Image not supported” message.

Bug ID	Headline
CSCux51095	VSM keeps on restarting when one of the Cisco Nexus 1110 in an HA pair is powered down.

---

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© 2016 Cisco Systems, Inc. All rights reserved.