upgrading the cisco nexus cloud services platform software...nexus-1010.4.2.1.sp1.5.1a.iso...

Upgrading the Cisco Nexus Cloud ServicesPlatform Software

This chapter contains the following sections:

• Information About the In Service Software Upgrade, page 1

• Changes in Cisco Nexus Cloud Services Platform After an Upgrade to Release 5.2(1)SP1(7.1), page2

• Prerequisites, page 2

• Guidelines and Limitations, page 3

• Upgrading from earlier Software Releases, page 4

• Reconfiguring SNMP User Accounts After an Upgrade, page 6

• Configuration Examples for Upgrading the Cisco Nexus Cloud Services Platform, page 7

• Feature History for Software Upgrade, page 21

Information About the In Service Software UpgradeThe Cisco Nexus Cloud Services Platform upgrade is a hitless in-service software upgrade (ISSU). When youupgrade the software, the operational data is retained without loss of persistent information. The availabilityof virtual service blades (VSBs ) will not be affected during the upgrade process.

After you enter the command to upgrade the software, from that point on, the whole upgrade process isautomated. The upgrade process is in the following sequence:

• The ISO image components are extracted, verified and synchronized to the standby Cisco Nexus CloudServices Platform.

• The standby Cisco Nexus Cloud Services Platform is upgraded.

• The VSBs on the standby are restarted.

• The upgrade of the active is initiated.

Once the upgrade of the active and standby platform is complete, both form a high-availability (HA) pair byrunning the upgraded software.

Cisco Nexus Cloud Services Platform Software Installation and Upgrade Guide, Release 5.2(1)SP1(7.1) OL-31543-01 1

Changes in Cisco Nexus Cloud Services Platform After anUpgrade to Release 5.2(1)SP1(7.1)

When you upgrade to the Cisco Nexus Cloud Services PlatformRelease 5.2(1)SP1(7.1), the following changesoccur on the Cisco Nexus Cloud Services Platform software:

• All configuration settings and uplink assignments are the same after upgrading the Cisco Nexus CloudServices Platform to a Flexible topology type.

•When you enter the show hardware command after powering on the Cisco Nexus 1110-X, the CiscoUCS VIC 1225 10 Gbps card is listed as an installed hardware component. You should enable the 10Gbps port for a VSB to use it as a shared uplink or form a port channel with two 10 Gbps ports.

• Starting in Release 5.2(1)SP1(7.1), all configured interfaces on the Cisco Nexus Cloud Services Platformare called Ethernet interfaces instead of Gbps Ethernet interfaces.

• The Cavium NITROX Crypto card will not be supported after an upgrade to Release 5.2(1)SP1(7.1).The Crypto card is supported only on a fresh installation of the Cisco Nexus 1110-X. For more informationabout enabling the CaviumNITROX crypto card, see theCisco Nexus Cloud Services Platform SoftwareConfiguration Guide .

PrerequisitesBefore beginning the procedure in this section, you must know or do the following:

• Verify that you have the following product ID (PID), using the instructions in the Verifying the CIMCSoftware Version section.

◦N1K-1110-S on the Cisco Nexus 1110-S

◦N1K-1110-X on the Cisco Nexus 1110-X

◦N1K-C1010 on the Cisco Nexus 1010

◦N1K-C1010-X on the Cisco Nexus 1010-X

You cannot install or upgrade to Release 5.2(1)SP1(7.1) unless your Cisco Nexus 1110-Shas the product ID (PID) N1K-1110-S, your Cisco Nexus 1110-Xhas the product ID(PID) N1K-1110-X, your Cisco Nexus 1010 has the product ID (PID) N1K-C1010, oryour Cisco Nexus 1010-X has the product ID (PID) N1K-C1010-X.

Caution

• Upgrade firmware using the Cisco Host Upgrade Utility (HUU). The HUU is a tool that upgrades thefollowing components:

◦Cisco Integrated Management Controller (CIMC)

◦System BIOS

◦LAN on Motherboard (LOM)

◦Cisco UCS VIC 1225

Cisco Nexus Cloud Services Platform Software Installation and Upgrade Guide, Release 5.2(1)SP1(7.1)2 OL-31543-01

Upgrading the Cisco Nexus Cloud Services Platform SoftwareChanges in Cisco Nexus Cloud Services Platform After an Upgrade to Release 5.2(1)SP1(7.1)

◦Network adapters

◦LSI

Use the following Cisco HUU versions to upgrade the firmware before you upgrade the Cisco NexusCloud Services Platform:

• For the Cisco Nexus 1010 product family, see the Cisco Host Upgrade Utility Release 1.4(3) QuickStart Guide.

• For the Cisco Nexus 1110 product family, see the Cisco Host Upgrade Utility 1.5(1) User Guide.

We recommend that you upgrade the firmware using the Cisco Host Upgrade Utility.Failing to do so might result in a network setup failure and/or system reboots. For moreinformation, see Cisco Host Upgrade Utility Information.

Caution

• Log in to the command-line-interface (CLI) from the CIMC/Serial over LAN (SoL) port on the rear ofthe Cisco Nexus Cloud Services Platform.

Do not log in using the management IP address for this procedure. This procedurerequires that you upgrade and reload the standby Cisco Nexus Cloud Services Platform.After you upgrade, the HA pair will have incompatible software versions. By loggingin using SoL, you prevent the split brain that occurs in this configuration.

Note

• Save a backup copy of your running configuration on an external server.

• Save a copy of the new Cisco Nexus Cloud Services Platform software file to an external server afterdownloading it from www.cisco.com.

• Install Cisco Integrated Management Controller (CIMC) Software Version 1.4(3s) or higher for theCisco Nexus 1010 product family installed and CIMC Software Version 1.5(4e) or higher for the CiscoNexus 1110 product family installed. For more information, see the Verifying the CIMC SoftwareVersion section.

Guidelines and LimitationsThe Cisco Nexus Cloud Services Platform product family has the following configuration guidelines andlimitations:

• This procedure upgrades both the active and standby Cisco Nexus Cloud Services Platforms.

• After reloading the new software release during an upgrade, youmust save the new upgrade configurationpersistently through reboot and then restart the startup configuration.

• The only way to upgrade the software is by using the install nexus1010 command.

• Boot variables will be set by the systemwhen you use the install command. Do not set the boot variablesmanually.


Upgrading the Cisco Nexus Cloud Services Platform SoftwareGuidelines and Limitations

http://www.cisco.com/en/US/docs/unified_computing/ucs/c/sw/lomug/1.4.x/install/b_huu_1_4_3.html

http://www.cisco.com/en/US/docs/unified_computing/ucs/c/sw/lomug/1.4.x/install/b_huu_1_4_3.html

http://www.cisco.com/en/US/docs/unified_computing/ucs/c/sw/lomug/1.5.x/b_huu_1_5_chapter_01.html

b_Cisco_Nexus_CSP_SW_IU_Guide_Rel_5_2_1_SP1_7_1_chapter_011.pdf#unique_22



Upgrading from earlier Software ReleasesYou can use this procedure for the following Cisco Nexus Cloud Services Platform upgrades while retainingoperational data and persistent information:

To Software ReleaseSupported Software Release for Upgrade

4.2(1)SP1(6.2) and later releases4.2(1)SP1(3)—Minimum required version forUpgrade

4.2(1)SP1(4)

4.2(1)SP1(6.2) and later releases4.2(1)SP1(5.1) or 4.2(1)SP1(5.1a)

4.2(1)SP1(6.1)

4.2(1)SP1(6.2a) and later releases4.2(1)SP1(6.2)

5.2(1)SP1(7.1)4.2(1)SP1(6.2a)

Upgrade from Release 4.2(1)SP1(1) or 4.2(1)SP1(2) to 4.2(1)SP1(6.1) or later releases is not supported.Note

For information about upgrading Cisco Nexus 1000V software on a VSB, see the Cisco Nexus 1000VSoftware Installation and Upgrade Guide.

Note

Before You Begin

Procedure

Step 1 From the Cisco Nexus Cloud Services Platform serial over LAN (SoL) connection, copy any unsavedconfiguration from the running configuration to the startup configuration so that it is preserved after the reload.

Example:switch# copy running-config startup-config[########################################] 100%switch#

Step 2 Copy the new software image from the external server to the bootflash: \repository.

Example:switch# copy scp://[email protected]/home/user/nexus-1010.4.2.1.SP1.5.1a.iso bootflash:repositoryEnter vrf (If no input, current vrf 'default' is considered):[email protected]'s password:


Upgrading the Cisco Nexus Cloud Services Platform SoftwareUpgrading from earlier Software Releases

nexus-1010.4.2.1.SP1.5.1a.iso 100% 258234 10.3KB/s 00:15switch#

Step 3 Install the new image.The following things occur on the switch:

• The new software image is copied to bootflash and the standby Cisco Nexus Cloud Services Platformis upgraded.

• Bootflash variables are updated with the names of the new system and kickstart images.

• The new image and bootflash variable information is saved in the startup configuration.

• The active switch reloads the standby switch with the new software release.

• The system waits for all VSBs to come up before the standby switch takes over and reloads the activeswitch with the new software version.

Example:

switch# install nexus1010 bootflash:repository/nexus-1010.4.2.1.sp1.5.1a.iso

Step 4 From the CLI for each module, verify that both modules are in HA mode.

Example:switch# show system redundancy statusRedundancy role---------------

administrative: primaryoperational: primary

Redundancy mode---------------

administrative: HAoperational: None

This supervisor (sup-1)-----------------------

Redundancy state: ActiveSupervisor state: ActiveInternal state: Active with HA standby

Other supervisor (sup-2)------------------------

Redundancy state: standbySupervisor state: HA standbyInternal state: HA standby

switch#---- ----

Step 5 Verify if the new software is loaded.

Example:switch# show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------ ------------1 0 Cisco Virtual Services Appliance VSA active *2 0 Cisco Virtual Services Appliance VSA ha-standby

Mod Sw Hw--- ---------------- ------------------------------------------------1 4.2(1)SP1(5.1a) 0.02 4.2(1)SP1(5.1a) 0.0

Mod MAC-Address(es) Serial-Num--- -------------------------------------- ----------1 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA2 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA


Upgrading the Cisco Nexus Cloud Services Platform SoftwareUpgrading from earlier Software Releases

Mod Server-IP Server-UUID Server-Name--- --------------- ------------ --------------------1 10.78.109.100 NA NA2 10.78.109.100 NA NA

* this terminal session

Step 6 Save the new upgrade configuration persistently through reboots and restarts by copying it to the startupconfiguration.

Example:Example:switch# copy running-config startup-config[########################################] 100%switch#

Reconfiguring SNMP User Accounts After an UpgradeDuring an upgrade, the SNMP engine ID changes internally to a unique engine ID. You must reconfigure allSNMP user accounts to work with the new engine ID. Until the SNMP user accounts are reconfigured, allSNMPv3 queries fail.

After an upgrade, the engine ID is shown as 128:0:0:9:3:2:0:12:0:0:0, as follows:switch# show snmp user______________________________________________________________

SNMP USERS______________________________________________________________

User Auth Priv(enforce) Groups____ ____ _____________ ____________________________________________________________________NOTIFICATION TARGET USERS (configured for sending V3 Inform)______________________________________________________________

User Auth Priv____ ____ ____admin md5 des(EngineID 128:0:0:9:3:2:0:12:0:0:0)Complete the following steps to delete and recreate the username.

Procedure

Step 1 Delete the username.

Example:switch(config)#no snmp user admin auth md5Sfish123 engineID 128:0:0:9:3:2:0:12:0:0:0

Step 2 Use either of the following options to recreate the username:

• Option 1switch(config)# snmp user admin auth md5 Sfish123

• Option 2switch(config)# snmp-server user admin auth md5Sfish123 priv aes-128 Sfish123

Step 3 Confirm that the engine ID has been updated, as follows:


Upgrading the Cisco Nexus Cloud Services Platform SoftwareReconfiguring SNMP User Accounts After an Upgrade

• Option 1switch# show snmp user______________________________________________________________

SNMP USERS______________________________________________________________

User Auth Priv(enforce) Groups____ ____ _____________ ______admin md5 no network-operator

______________________________________________________________NOTIFICATION TARGET USERS (configured for sending V3 Inform)______________________________________________________________

User Auth Priv____ ____ ____

• Option 2switch(config)# show snmp user______________________________________________________________

SNMP USERS______________________________________________________________

User Auth Priv(enforce) Groups____ ____ _____________ ______admin md5 aes-128(no) network-operator

______________________________________________________________NOTIFICATION TARGET USERS (configured for sending V3 Inform)______________________________________________________________

User Auth Priv____ ____ ____

Step 4 Verify that the engine ID is unique.

Example:switch# show snmp engineIDLocal SNMP engineID: [Hex] 8000000903005056A0544E

[Dec] 128:000:000:009:003:000:080:086:160:084:078

Configuration Examples for Upgrading the Cisco Nexus CloudServices Platform

Upgrading Release 4.2(1)SP1(6.2a) to 5.2(1)SP1(7.1)

This example shows how to upgrade from software Release version 4.2(1)SP1(6.2a) to 5.2(1)SP1(7.1):

cppa-mgr(config)# install nexus1010 bootflash:repository/nexus-1010.5.2.1.SP1.7.1.isocppa_mgr

debug: Using URI:bootflash:/repository/nexus-1010.5.2.1.SP1.7.1.isoInstalling bootflash:/repository/nexus-1010.5.2.1.SP1.7.1.iso.2014 May 24 04:07:26 cppa-mgr %CPPA_MGR-5-UPGRADE_START: Upgrade started. Image:nexus-1010.5.2.1.SP1.7.1.iso............................................................2014 May 24 04:09:28 cppa-

mgr %CPPA_MGR-5-UPGRADE_START: Upgrade started. Image:


Upgrading the Cisco Nexus Cloud Services Platform SoftwareConfiguration Examples for Upgrading the Cisco Nexus Cloud Services Platform

nexus-1010.5.2.1.SP1.7.1.iso....................................2014May 24 04:10:48 cppa-mgr %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from

vty by root on vsh.22492.Verifying image bootflash:/nexus-1010-kickstart.5.2.1.SP1.7.1.bin for boot variable"kickstart".[# ] 0%._____________[####################] 100% -- SUCCESS

Verifying image bootflash:/nexus-1010.5.2.1.SP1.7.1.bin for boot variable "system".[# ] 0%._________________[####################] 100% -- SUCCESS

Verifying image type.[# ] 0%.________________[##### ] 20%.._____________[#######

]30%___________[######### ] 40%_____________[########### ]

50%..._____________[########### ] 50%._______________[########### ] 50%.._____________[################### ]90%_____________[####################] 100%_____________

[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/nexus-1010.5.2.1.SP1.7.1.bin.[# ] 0%._____________[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/nexus-1010-kickstart.5.2.1.SP1.7.1.bin.[# ] 0%_____________[####################] 100% -- SUCCESS........Notifying services about system upgrade......_____________[####################] 100% _____________-- SUCCESS

Compatibility check is done:Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------

1 yes non-disruptive reset2 yes non-disruptive reset

Images will be upgraded according to following table:Module Image Running-Version New-Version Upg-Required------ ---------- ---------------------- ---------------------- ------------

1 system 4.2(1)SP1(6.2a) 5.2(1)SP1(7.1) yes1 kickstart 4.2(1)SP1(6.2a) 5.2(1)SP1(7.1) yes2 system 4.2(1)SP1(6.2a) 5.2(1)SP1(7.1) yes2 kickstart 4.2(1)SP1(6.2a) 5.2(1)SP1(7.1) yes

Module Running-Version ESX VersionVSM Compatibility ESX Compatibility------ ---------------------- -------------------------------------------------------------------------- ----------------------

Install is in progress, please wait.

Syncing image bootflash:/nexus-1010-kickstart__________________________[####################]100% -- SUCCESS

Syncing image bootflash:/nexus-1010.5.2.1.SP1.7.1.bin to standby.[# ] 0%...._____________[####################] 100% -- SUCCESS

Setting boot variables.[# ] 0%....._____________[_____________Performing configuration copy.[# ] 0%_____________[## ] 5%_____________[###

]10%_____________[#### ] 15%_____________[######## ]

35%_____________[######### _____________] 40%_____________[##########]



45%_____________[########### ] 50%_____________[############### ]70%_____________

[################ ] 75%_____________[################# ]80%_____________[################## ]85%_____________[####################] 100%2014 May 24 04:12:03 cppa-mgr %SYSMGR-STANDBY-5-

CFGWRITE_STARTED: Configuration copy started (PID 5896).._____________[####################]100%-- SUCCESS.....................2014 May 24 04:12:50 cppa-mgr %REDUN_MGR-4-CTRL_COMM_STATUS_CHANGE:Control Connectivity is DOWN with Secondary VSA..2014 May 24 04:13:00 cppa-mgr %REDUN_MGR-4-HB_STOPPED:

Heartbeats stopped from: Secondary VSA. 2014 May 24 04:13:01 cppa-mgr %PLATFORM-2-MOD_REMOVE:Module 2 removed(Serial number _____________T023D77DE81).............................2014 May 24

04:14:00 cppa-mgr %REDUN_MGR-4-AC_AC_POSSIBLE: Secondary VSA not yet come UP, PossibleActive-Active VSA WARNING!!Check the following things: 1) Secondary VSA is manually powered off? 2) Network

connectivity with Secondary VSA is broken? 3) Secondary VSA is stuck at booting?

................................................................................................................

...................................................................................20

14 May 24 04:20:33 cppa-mgr %REDUN_MGR-4-CTRL_COMM_STATUS_CHANGE: Control Connectivity isUP with Secondary VSA.2014 May 24 04:20:34 cppa-mgr %PLATFORM-2-MOD_DETECT: Module 2 detected (Serial

number :unavailable) Module-Type Virtual Supervisor Module Model :unavailable.........2014May 24 04:20:51 cppa-mgr%BOOTVAR-5-NEIGHBOR_UPDATE_AUTOCOPY: auto-copy supported by neighbor supervisor,

starting... .........2014 May 24 04:21:10 cppa-mgr %SYSMGR-STANDBY-4-READCONF_STARTED:Configuration update started (PID 3600)._____________.2014 May 24 04:21:12 cppa-mgr %SYSMGR-STANDBY-4-

READCONF_STARTED: Configuration update started (PID 3711)..Module 2: Waiting for module online.-- SUCCESS2014 May 24 04:21:15 cppa-mgr %MODULE-5-STANDBY_SUP_OK: Supervisor 2 is standby2014May 24 04:21:15 cppa-mgr %SYSMGR-STANDBY-5-MODULE_ONLINE: System Manager has receivednotification of local

module becoming

online...............................................................................................................................................................................................

............................................................................................

.................Notifying services about the switchover..__________[####################] 100% -- SUCCESS

"Switching over onto standby".

Upgrading Release 4.2(1)SP1(6.1) to 4.2(1)SP1(6.2)

This example shows how to upgrade from software Release version 4.2(1)SP1(6.1) to 4.2(1)SP1(6.2).

login: adminPassword:

Cisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2013, 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 underlicense. Certain components of this software are licensed underthe GNU General Public License (GPL) version 2.0 or the GNULesser General Public License (LGPL) Version 2.1. A copy of eachsuch license is available athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.phpswitch#switch# show module

Mod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------1 0 Cisco Virtual Services Appliance VSA active *2 0 Cisco Virtual Services Appliance VSA ha-standby

Mod Sw Hw--- ---------------- ------------------------------------------------1 4.2(1)SP1(6.1) 0.02 4.2(1)SP1(6.1) 0.0


Mod Server-IP Server-UUID Server-Name--- --------------- ------------------------------------ --------------------1 80.80.80.220 NA NA2 80.80.80.220 NA NA


switch# dir bootflash:repository

939063296 Oct 01 02:39:47 2013 dcnm-installer.6.2.3.iso16384 Oct 01 08:06:29 2013 lost+found/

221212672 Oct 01 02:37:27 2013 nam-app-x86_64.5-1-2.iso162895872 Oct 01 02:35:03 2013 nexus-1000v.4.2.1.SV2.2.1a.iso169783296 Oct 01 02:35:39 2013 nexus-1000v.5.2.1.SM1.5.1.iso159037440 Oct 01 02:36:29 2013 nexus-1000v.5.2.1.VSGM1.4.1.iso674701312 Oct 01 02:42:32 2013 nexus-1010.4.2.1.SP1.6.2.iso

460 Oct 01 03:58:12 2013 vmpresults.txt

Usage for bootflash://sup-local

311828480 bytes used3679551488 bytes free3991379968 bytes total

switch# install nexus1010 bootflash:repository//nexus-1010.4.2.1.SP1.6.2.isoswitch debug: Using URI: bootflash:/repository//nexus-1010.4.2.1.SP1.6.2.isoInstalling bootflash:/repository//nexus-1010.4.2.1.SP1.6.2.iso....................................................................

Verifying image bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.6.2.bin for boot variable"kickstart".[# ] 0%.___________________________[####################] 100% -- SUCCESS

Verifying image bootflash:/nexus-1010-mz.4.2.1.SP1.6.2.bin for boot variable "system".[# ] 0%___________________________[####################] 100% -- SUCCESS

Verifying image type.

[# ] 0%.___________________________[##### ]20%.___________________________[####### ]30%___________________________[######### ]40%___________________________[########### ]50%..___________________________[########### ]50%___________________________[########### ]50%.___________________________[################### ]90%___________________________[####################]100%.___________________________[####################] 100% -- SUCCESS



Extracting "system" version from image bootflash:/nexus-1010-mz.4.2.1.SP1.6.2.bin.[# ] 0%___________________________[####################] 100% -- SUCCESSExtracting "kickstart" version from imagebootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.6.2.bin.[# ] 0%.___________________________[####################] 100% -- SUCCESS.....Notifying services about system upgrade......___________________________[####################] 100% -- SUCCESS

Compatibility check is done:

Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------


Images will be upgraded according to following table:

Module Image Running-Version New-Version Upg-Required------ ---------- ---------------------- ---------------------- ------------

1 system 4.2(1)SP1(6.1) 4.2(1)SP1(6.2) yes1 kickstart 4.2(1)SP1(6.1) 4.2(1)SP1(6.2) yes2 system 4.2(1)SP1(6.1) 4.2(1)SP1(6.2) yes2 kickstart 4.2(1)SP1(6.1) 4.2(1)SP1(6.2) yes



Syncing image bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.6.2.bin to standby.

[# ] 0%..___________________________[####################] 100% --SUCCESS

Syncing image bootflash:/nexus-1010-mz.4.2.1.SP1.6.2.bin to standby.[# ] 0%..___________________________[####################] 100% --SUCCESSSetting boot variables.[# ] 0%....___________________________[####################] 100% --SUCCESSPerforming configuration copy.[# ] 0%___________________________[## ]5%___________________________[### ] 10%___________________________[####

] 15%___________________________[######## ]35%___________________________[######### ]40%___________________________[########## ]45%___________________________[########### ]50%___________________________[############### ]70%___________________________[################ ]75%___________________________[################# ]80%___________________________[################## ]85%___________________________[####################]100%.___________________________[####################] 100% -- SUCCESS....................2013 Oct 1 04:46:18 switch %PLATFORM-2-MOD_REMOVE: Module 2 removed(Serial number T023D781781).............................................................................................................................................................................................................2013Oct 1 04:53:09 switch %PLATFORM-2-MOD_DETECT: Module 2 detected (Serial number :unavailable)Module-Type Virtual Supervisor Module Model :unavailable......................Module 2: Waiting for module online.-- SUCCESS...............................Notifying services about the switchover.___________________________[####################] 100% -- SUCCESS"Switching over onto standby".

Cisco VSA



switch login: adminPassword:

Cisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2013, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained in this software areowned by other third parties and used and distributed underlicense. Certain components of this software are licensed underthe GNU General Public License (GPL) version 2.0 or the GNULesser General Public License (LGPL) Version 2.1. A copy of eachsuch license is available athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.php

switch#switch# show module

Mod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------1 0 Cisco Virtual Services Appliance VSA ha-standby2 0 Cisco Virtual Services Appliance VSA active *

Mod Sw Hw--- ---------------- ------------------------------------------------1 4.2(1)SP1(6.2) 0.02 4.2(1)SP1(6.2) 0.0




Upgrade from software Release version 4.2(1)SP1(5.1a) to 4.2(1)SP1(6.2)

This example shows how to upgrade from Release 4.2(1)SP1(5.1a) to Release 4.2(1)SP1(6.2):login: adminPassword:

Cisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained in this software areowned by other third parties and used and distributed underlicense. Certain components of this software are licensed underthe GNU General Public License (GPL) version 2.0 or the GNULesser General Public License(LGPL) Version 2.1. A copy of eachsuch license is available athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.php

switch# show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------1 0 Cisco Virtual Services Appliance VSA active2 0 Cisco Virtual Services Appliance VSA ha-standbyMod Sw Hw--- ---------------- ------------------------------------------------1 4.2(1)SP1(5.1a) 0.02 4.2(1)SP1(5.1a) 0.0

Mod MAC-Address(es) Serial-Num



--- -------------------------------------- ----------1 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA2 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NAMod Server-IP Server-UUID Server-Name--- --------------- ------------------------------------ --------------------1 80.80.80.220 NA NA2 80.80.80.220 NA NA* this terminal session

switch# dir bootflash:repository

16384 Oct 02 07:51:38 2013 lost+found/674701312 Oct 02 00:08:23 2013 nexus-1010.4.2.1.SP1.6.2.isoUsage for bootflash://sup-local

309125120 bytes used 3682254848 bytes free3991379968 bytes total

switch#

switch# install nexus1010 bootflash:repository//nexus-1010.4.2.1.SP1.6.2.isoswitch debug: Using URI: bootflash:/repository//nexus-1010.4.2.1.SP1.6.2.iso

Installingbootflash:/repository//nexus-1010.4.2.1.SP1.6.2.iso................................................................Verifyingimage bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.6.2.bin for boot variable "kickstart".[#

] 0%.___________________________[####################] 100% -- SUCCESS

Verifying image bootflash:/nexus-1010-mz.4.2.1.SP1.6.2.bin for boot variable "system".[#] 0%___________________________[####################] 100% -- SUCCESS

Verifying image type.[# ] 0%.___________________________[#####] 20%.___________________________[####### ]

30%___________________________[######### ]40%___________________________[########### ]50%..___________________________[########### ]50%___________________________[########### ]50%.___________________________[################### ]90%___________________________[####################]100%.___________________________[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/nexus-1010-mz.4.2.1.SP1.6.2.bin.[#] 0%___________________________[####################] 100% -- SUCCESS

Extracting "kickstart" version from imagebootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.6.2.bin.[# ]0%.___________________________[####################] 100% -- SUCCESS.....

Notifying services about system upgrade......___________________________[####################]100% -- SUCCESS

Compatibility check is done:

Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------1 yes non-disruptive reset2 yes non-disruptive resetImages will be upgraded according to following table:Module Image Running-Version New-Version Upg-Required------ ---------- ---------------------- ---------------------- ------------1 system 4.2(1)SP1(5.1a) 4.2(1)SP1(6.2) yes1 kickstart 4.2(1)SP1(5.1a) 4.2(1)SP1(6.2) yes2 system 4.2(1)SP1(5.1a) 4.2(1)SP1(6.2) yes2 kickstart 4.2(1)SP1(5.1a) 4.2(1)SP1(6.2) yes





Syncing image bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.6.2.bin to standby.[#] 0%.___________________________[####################] 100% -- SUCCESS

Syncing image bootflash:/nexus-1010-mz.4.2.1.SP1.6.2.bin to standby.[# ]0%...___________________________[####################] 100% -- SUCCESS

Setting boot variables.[# ]0%...___________________________[####################] 100% -- SUCCESSPerforming configuration copy.[# ] 0%___________________________[##

] 5%___________________________[### ]10%___________________________[###### ] 25%___________________________[#######

] 30%___________________________[######## ]35%___________________________[########### ]50%___________________________[############ ]55%___________________________[############# ]60%___________________________[################ ]75%___________________________[################# ]80%___________________________[################## ]85%___________________________[####################]100%.___________________________[####################] 100% --SUCCESS.....................2013 Oct 2 00:14:04 switch %PLATFORM-2-MOD_REMOVE: Module 2removed (Serial number T023D781781)........................................................................................................................................................................................................2013Oct 2 00:20:46 switch %PLATFORM-2-MOD_DETECT: Module 2 detected (Serial number :unavailable)Module-Type Virtual Supervisor Module Model :unavailable......................Module 2: Waiting for module online. --SUCCESS...............................Notifying services about theswitchover.___________________________[####################] 100% -- SUCCESS"Switching overonto standby".._login as: adminCisco VSAUsing keyboard-interactive authentication.Password:Cisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2013, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained in this software areowned by other third parties and used and distributed underlicense. Certain components of this software are licensed underthe GNU General Public License (GPL) version 2.0 or the GNULesser General Public License (LGPL) Version 2.1. A copy of eachsuch license is available athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.phpswitch# show moduleMod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------1 0 Cisco Virtual Services Appliance VSA ha-standby2 0 Cisco Virtual Services Appliance VSA active *

Mod Sw Hw--- ---------------- ------------------------------------------------1 4.2(1)SP1(6.2) 0.02 4.2(1)SP1(6.2) 0.0



* this terminal sessionswitch#

Upgrading Release 4.2(1)SP1(3) to 4.2(1)SP1(5.1)

This example shows how to upgrade Release 4.2(1)SP1(3) to Release 4.2(1)SP1(5.1).login as: adminNexus 1010



Using keyboard-interactive authentication.Password:Cisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2011, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained in this software areowned by other third parties and used and distributed underlicense. Certain components of this software are licensed underthe GNU General Public License (GPL) version 2.0 or the GNULesser General Public License (LGPL) Version 2.1. A copy of eachsuch license is available athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.php

switch# show mod[15D[Jswitch# show mod[Jule

Mod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------1 0 Nexus 1010 (Virtual Services App Nexus1010 active *2 0 Nexus 1010 (Virtual Services App Nexus1010 ha-standby

Mod Sw Hw--- ---------------- ------------------------------------------------1 4.2(1)SP1(3) 0.02 4.2(1)SP1(3) 0.0



* this terminal sessionswitch# show[J[J[J[Jd[Jdir boot[15D[Jswitch# dir boot[Jflash:r[22D[Jswitch# dir bootflash:r[Jepository

16384 Jun 11 02:49:38 2014 lost+found/305928192 Jun 12 12:33:09 2014 nexus-1010.4.2.1.SP1.5.0.33.iso

Usage for bootflash://sup-local308862976 bytes used3682516992 bytes free3991379968 bytes total

switch# inst[11D[Jswitch# inst[Jall nexu[19D[Jswitch# install nexu[Js1010 boot[29D[Jswitch# install nexus1010 boot[Jflash:[35D[Jswitch# install nexus1010 bootflash:

bootflash:/// bootflash://sup-1/ bootflash://sup-local/

bootflash://module-1/ bootflash://sup-2/ bootflash://sup-remote/

bootflash://module-2/ bootflash://sup-active/ bootflash://sup-standby/[Jswitch# install nexus1010 bootflash://[J[Jr[36D[Jswitch# install nexus1010 bootflash:r[Jepository/nexu[50D[Jswitch# install nexus1010 bootflash:repository/nexu[Js-1010.4.2.1.SP1.5.0.33.iso

cppa_mgr debug: Using URI: bootflash:/repository/nexus-1010.4.2.1.SP1.5.0.33.isoInstalling bootflash:/repository/nexus-1010.4.2.1.SP1.5.0.33.iso..................Verifying image bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.5.1.bin for boot variable"kickstart".[# ] 0%[####################] 100% -- SUCCESS



Verifying image bootflash:/nexus-1010-mz.4.2.1.SP1.5.1.bin for boot variable "system".[# ] 0%..[####################] 100% -- SUCCESS

Verifying image type.[# ] 0%[##### ] 20%.[####### ] 30%[#########

] 40%[########### ] 50%..[########### ] 50%[###########] 50%.[################### ] 90%[####################] 100%[####################]

100% -- SUCCESS

Extracting "system" version from image bootflash:/nexus-1010-mz.4.2.1.SP1.5.1.bin.[# ] 0%.[####################] 100% -- SUCCESS

Extracting "kickstart" version from imagebootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.5.1.bin.[# ] 0%[####################] 100% -- SUCCESS.....Notifying services about system upgrade.......[####################] 100% -- SUCCESS

Compatibility check is done:Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------



1 system 4.2(1)SP1(3) 4.2(1)SP1(5.1) yes1 kickstart 4.2(1)SP1(3) 4.2(1)SP1(5.1) yes2 system 4.2(1)SP1(3) 4.2(1)SP1(5.1) yes2 kickstart 4.2(1)SP1(3) 4.2(1)SP1(5.1) yes



Syncing image bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.5.1.bin to standby.[# ] 0%.[####################] 100% -- SUCCESS

Syncing image bootflash:/nexus-1010-mz.4.2.1.SP1.5.1.bin to standby.[# ] 0%..[####################] 100% -- SUCCESS

Setting boot variables.[# ] 0%...[####################] 100% -- SUCCESS

Performing configuration copy.[# ] 0%[## ] 5%[### ] 10%[####

] 15%[######## ] 35%[######### ] 40%[##########] 45%[########### ] 50%[############### ] 70%[################ ]

75%[################# ] 80%[################## ] 85%[####################]100%.[####################] 100% -- SUCCESS....................2014 Jun 12 12:37:03 n1010 %PLATFORM-2-MOD_REMOVE: Module 2 removed(Serial number T023D7FFD81)

.............................................................................................................2014Jun 12 12:40:41 n1010 %PLATFORM-2-MOD_DETECT: Module 2 detected (Serial number :unavailable)Module-Type Virtual Supervisor Module Model :unavailable

...................Module 2: Waiting for module online.-- SUCCESS...............................Notifying services about the switchover..[####################] 100% -- SUCCESS

"Switching over onto standby".



login as: adminNexus 1010Using keyboard-interactive authentication.Password:Cisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained in this software areowned by other third parties and used and distributed underlicense. Certain components of this software are licensed underthe GNU General Public License (GPL) version 2.0 or the GNULesser General Public License (LGPL) Version 2.1. A copy of eachsuch license is available athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.php

switch# show mod[15D[Jswitch# show mod[Jule

Mod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------1 0 Cisco Virtual Services Appliance VSA ha-standby2 0 Cisco Virtual Services Appliance VSA active *

Mod Sw Hw--- ---------------- ------------------------------------------------1 4.2(1)SP1(5.1) 0.02 4.2(1)SP1(5.1) 0.0




Upgrading Release 4.2(1)SP1(3) to 4.2(1)SP1(4)

This example shows how to upgrade Release 4.2(1)SP1(3) to Release 4.2(1)SP1(4):switch# install nexus1010 bootflash:repository/nexus-1010.4.2.1.SP1.4.isocppa_mgr debug: Using URI: bootflash:/repository/nexus-1010.4.2.1.SP1.4.isoInstalling bootflash:/repository/nexus-1010.4.2.1.SP1.4.iso................................................................................Verifying image bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.4.bin for boot variable"kickstart".[[####################] 100% -- SUCCESS

Verifying image bootflash:/nexus-1010-mz.4.2.1.SP1.4.bin for boot variable "system".[[####################] 100% -- SUCCESS

Verifying image type.[[[[[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/nexus-1010-mz.4.2.1.SP1.4.bin.[[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.4.bin.[####################] 100% -- SUCCESS......Notifying services about system upgrade. [####################]100% -- SUCCESS.Compatibility check is done:Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------

1 yes non-disruptive reset



2 yes non-disruptive reset


1 system 4.2(1)SP1(3) 4.2(1)SP1(4) yes1 kickstart 4.2(1)SP1(3) 4.2(1)SP1(4) yes2 system 4.2(1)SP1(3) 4.2(1)SP1(4) yes2 kickstart 4.2(1)SP1(3) 4.2(1)SP1(4) yes

Module Running-Version ESX Version VSM Compatibility ESX Compatibility------ ---------------------- -------------------------------------------------------------------------- ----------------------


Syncing image bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.4.bin to standby.[[####################] 100% -- SUCCESS

Syncing image bootflash:/nexus-1010-mz.4.2.1.SP1.4.bin to standby.[#[####################] 100% -- SUCCESS

Setting boot variables.[# [####################] 100% -- SUCCESS

Performing configuration copy.[[[####################] 100% -- SUCCESS..........................2011 Jul 25 20:12:16 switch %PLATFORM-2-MOD_REMOVE: Module 2removed (Serial number T023D750981)...........................................................................2011 Jul 2520:14:54 switch %PLATFORM-2-MOD_DETECT: Module 2 detected (Serial number :unavailable)Module-Type Virtual Supervisor Module Model :unavailable....................Module 2: Waiting for module online.-- SUCCESS........................................................................................................................................................Notifying services about the switchover.[####################] 100% -- SUCCESS

"Switching over onto standby"..Broadcast message from root (console) (Mon Jul 25 20:20:41 2011):

The system is going down for reboot NOW!INIT: Switching to runlevel: 6INIT: Sending processes the TERM signalJul 25 20:20:41 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "sksd" (PID 2487) is forced exit.Jul 25 20:20:41 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Security Daemon" (PID 2499) isforced exit.Jul 25 20:20:41 %TTYD-2-TTYD_ERROR TTYD Error ttyd bad selectJul 25 20:20:41 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "stp" (PID 2765) is forced exit.Jul 25 20:20:41 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service"fs-daemon"(PID2455)is forced exit.Jul 25 20:20:41 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service"Cert_enroll Daemon"(PID 2500)isforced exit.Jul 25 20:20:41 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "netstack"(PID2557)is forced exit.Jul 25 20:20:41 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "vdc_mgr"(PID 2484)is forced exit.Jul 25 20:20:41 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "u6rib" (PID 2507) is forced exit.Jul 25 20:20:41 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "res_mgr"(PID 2489)is forced exit.Jul 25 20:20:41 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "licmgr" (PID 2454)is forced exit.Jul 25 20:20:41 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "igmp" (PID 2771) is forced exit.Jul 25 20:20:41 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "adjmgr" (PID 2537)is forced exit.Jul 25 20:20:41 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Radius Daemon"(PID 2634)is forcedexit.Jul 25 20:20:41 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "AAA Daemon"(PID 2501)is forcedexit.Jul 25 20:20:41 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "urib" (PID 2508) is forced exit.Auto booting bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.4.bin bootflash:/nexus-1010-mz.4.2.1.SP1.3.bin...Booting kickstart image: bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.4.bin.........................................................Image verificationOK

Starting kernel...PCI: PIIX3: Enabling Passiv%H+Y4%



001-Usage: init 0123456SsQqAaBbCcUumkdir: cannot create directory `/new-root/old-root': File existsINIT: version 2.85 bootingBootflash device is /dev/hdaChecking all filesystems..... done.Setting kernel variables: sysctlnet.ipv4.ip_forward = 0net.ipv4.ip_default_ttl = 64net.ipv4.ip_no_pmtu_disc = 1./etc/rc.d/rcS.d/S35iptables: line 41: //iptables: No such file or directory/etc/rc.d/rcS.d/S35iptables: line 44: //ip6tables: No such file or directoryLoading system softwareUncompressing system image: bootflash:/nexus-1010-mz.4.2.1.SP1.4.bin

Load plugins that defined in image conf: /isan/plugin_img/img.confload_plugin: failed read swid map from "/mnt/pss/plugin_swid_map" with rc 0xffffffff. Pluginwill be assigned new IDLoading plugin 0: core_plugin...load_plugin: Can't get exclude list from /isan/plugin/0/boot/etc/plugin_exclude.conf (rc0x40ea0017)plugin_link_to_exec_path: plugin_path = /isan/plugin/0, tar_log = /isan/plugin_extract_log/0num srgs 10: swid-core-sup1sfp, swid-core-sup1sfpnum srgs 10: swid-sup1sfp-ks, swid-sup1sfp-ksINIT: Entering runlevel: 3Starting dhcpd daemon: dhcpdInternet Systems Consortium DHCP Server V3.0.1rc14Copyright 2004 Internet Systems Consortium.All rights reserved.For info, please visit http://www.isc.org/sw/dhcp/Wrote 0 deleted host decls to leases file.Wrote 0 new dynamic host decls to leases file.Wrote 0 leases to leases file.

Not configured to listen on any interfaces!.Exporting directories for NFS kernel daemon...done.Starting NFS kernel daemon:rpc.nfsd.rpc.mountddone.

/bin/mkdir: cannot create directory `/bootflash/repository': File exists/isan/bin/mount_cppa_repository exist

Nexus 1010switch(standby) login: 2011 Jul 26 04:24:22 switch %USER-2-SYSTEM_MSG: CLIS: loading cmdfiles begin - clis2011 Jul 26 04:24:29 switch %USER-2-SYSTEM_MSG: CLIS: loading cmd files end - clis2011 Jul 26 04:24:29 switch %USER-2-SYSTEM_MSG: CLIS: init begin - clis2011 Jul 26 04:24:38 switch %USER-2-SYSTEM_MSG: Invalid feature name eth-port-sec - clisNexus 1010switch(standby) login: adminPassword:Cisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained in this software are owned by other third partiesand used and distributed under license. Certain components of this software are licensedunder the GNU General Public License (GPL) version 2.0 or the GNU Lesser General PublicLicense (LGPL) Version 2.1. A copy of each such license is available athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.phpswitch(standby)#

Inactive timeout reached, logging out.

Nexus 1010switch(standby) login:

(The upgrade of the standby Cisco Nexus 1010 begins here.)Auto booting bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.4.binbootflash:/nexus-1010-mz.4.2.1.SP1.4.bin...Booting kickstart image: bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.4.bin.



..............................................................Image verificationOK

Starting kernel...PCI: PIIX3: Enabling Passive Veh+001-?Usage: init 0123456SsQqAaBbCcUumkdir: cannot create directory `/new-root/old-root': File existsINIT: version 2.85 bootingBootflash device is /dev/hdaChecking all filesystems...r.r.r done.

Setting kernel variables: sysctlnet.ipv4.ip_forward = 0net.ipv4.ip_default_ttl = 64net.ipv4.ip_no_pmtu_disc = 1./etc/rc.d/rcS.d/S35iptables: line 41: //iptables: No such file or directory/etc/rc.d/rcS.d/S35iptables: line 44: //ip6tables: No such file or directoryLoading system softwareUncompressing system image: bootflash:/nexus-1010-mz.4.2.1.SP1.4.bin

Load plugins that defined in image conf: /isan/plugin_img/img.confload_plugin: failed read swid map from "/mnt/pss/plugin_swid_map" with rc 0xffffffff. Pluginwill be assigned new IDLoading plugin 0: core_plugin...load_plugin: Can't get exclude list from /isan/plugin/0/boot/etc/plugin_exclude.conf (rc0x40ea0017)plugin_link_to_exec_path: plugin_path = /isan/plugin/0, tar_log = /isan/plugin_extract_log/0num srgs 10: swid-core-sup1sfp, swid-core-sup1sfpnum srgs 10: swid-sup1sfp-ks, swid-sup1sfp-ksINIT: Entering runlevel: 3Starting dhcpd daemon: dhcpdInternet Systems Consortium DHCP Server V3.0.1rc14Copyright 2004 Internet Systems Consortium.All rights reserved.For info, please visit http://www.isc.org/sw/dhcp/Wrote 0 deleted host decls to leases file.Wrote 0 new dynamic host decls to leases file.Wrote 0 leases to leases file.

Not configured to listen on any interfaces!.Exporting directories for NFS kernel daemon...done.Starting NFS kernel daemon:rpc.nfsd.rpc.mountddone.

/bin/mkdir: cannot create directory `/bootflash/repository': File exists/isan/bin/mount_cppa_repository exist

Continuing with installation, please waitTrying to start the installer...Trying to start the installer...2012 May 26 09:30:15 switch %USER-2-SYSTEM_MSG: CLIS: loading cmd files end - clis2012 May 26 09:30:15 switch %USER-2-SYSTEM_MSG: CLIS: init begin - clis2012 May 26 09:30:32 switch %USER-2-SYSTEM_MSG: Invalid feature name eth-port-sec - clis

Module 2: Waiting for module online.-- SUCCESS2011 Jul 25 20:20:41 switch %SYSMGR-2-HASWITCHOVER_PRE_START: This supervisor is becomingactive (pre-start phase).2011 Jul 25 20:20:41 switch %SYSMGR-2-HASWITCHOVER_START: This supervisor is becoming active.2011 Jul 25 20:20:41 switch %SYSMGR-2-SWITCHOVER_OVER: Switchover completed.2011 Jul 25 20:20:58 switch %PLATFORM-2-MOD_REMOVE: Module 1 removed (Serial number )

2011 Jul 25 20:24:21 switch %PLATFORM-2-MOD_DETECT: Module 1 detected (Serial number:unavailable) Module-Type Virtual Supervisor Module Model :unavailableInstall has been successful.

Nexus 1010switch login: adminPassword:Cisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved.



The copyrights to certain works contained in this software are owned by other third partiesand used and distributed under license. Certain components of this software are licensedunder the GNU General Public License (GPL) version 2.0 or the GNU Lesser General PublicLicense (LGPL) Version 2.1. A copy of each such license is available athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.phpswitch# copy running-config startup-config[########################################] 100%cppa-mgr#

Feature History for Software UpgradeThis section provides the software installation and upgrade release history:

Feature InformationReleasesFeature Name

This feature was introduced.4.2(1)SP1(2)Software upgrade


Upgrading the Cisco Nexus Cloud Services Platform SoftwareFeature History for Software Upgrade


Upgrading the Cisco Nexus Cloud Services Platform SoftwareFeature History for Software Upgrade

upgrading the cisco nexus cloud services platform software...nexus-1010.4.2.1.sp1.5.1a.iso...

Documents