Upgrading the Cisco Nexus Cloud Services Platform Software

This chapter contains the following sections:

Information About the In Service Software Upgrade

The Cisco Nexus Cloud Services Platform upgrade is a hitless in-service software upgrade (ISSU). When you upgrade the software, the operational data is retained without loss of persistent information. The availability of 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 is automated. The upgrade process is in the following sequence:

  • The ISO image components are extracted, verified and synchronized to the standby Cisco Nexus Cloud Services 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 by running the upgraded software.

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

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

  • All configuration settings and uplink assignments are the same after upgrading the Cisco Nexus Cloud Services Platform to a Flexible topology type.
  • When you enter the show hardware command after powering on the Cisco Nexus 1110-X, the Cisco UCS VIC 1225 10 Gbps card is listed as an installed hardware component. You should enable the 10 Gbps 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 Platform are 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 information about enabling the Cavium NITROX crypto card, see theCisco Nexus Cloud Services Platform Software Configuration Guide .

Prerequisites

Before 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 CIMC Software 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

    Caution

    You cannot install or upgrade to Release 5.2(1)SP1(7.1) unless your Cisco Nexus 1110-S has 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, or your Cisco Nexus 1010-X has the product ID (PID) N1K-C1010-X.

  • Upgrade firmware using the Cisco Host Upgrade Utility (HUU). The HUU is a tool that upgrades the following components:
    • Cisco Integrated Management Controller (CIMC)
    • System BIOS
    • LAN on Motherboard (LOM)
    • Cisco UCS VIC 1225
    • Network adapters
    • LSI
    Use the following Cisco HUU versions to upgrade the firmware before you upgrade the Cisco Nexus Cloud Services Platform:

    Caution

    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 more information, see Cisco Host Upgrade Utility Information.

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

    Note

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

  • 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 after downloading it from www.cisco.com.
  • Install Cisco Integrated Management Controller (CIMC) Software Version 1.4(3s) or higher for the Cisco Nexus 1010 product family installed and CIMC Software Version 1.5(4e) or higher for the Cisco Nexus 1110 product family installed. For more information, see the Verifying the CIMC Software Version section.

Guidelines and Limitations

The Cisco Nexus Cloud Services Platform product family has the following configuration guidelines and limitations:

  • This procedure upgrades both the active and standby Cisco Nexus Cloud Services Platforms.
  • After reloading the new software release during an upgrade, you must save the new upgrade configuration persistently 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 system when you use the install command. Do not set the boot variables manually.

Upgrading from earlier Software Releases

You can use this procedure for the following Cisco Nexus Cloud Services Platform upgrades while retaining operational data and persistent information:

Supported Software Release for Upgrade

To Software Release

4.2(1)SP1(3)—Minimum required version for Upgrade

4.2(1)SP1(6.2) and later releases

4.2(1)SP1(4)

4.2(1)SP1(5.1) or 4.2(1)SP1(5.1a)

4.2(1)SP1(6.2) and later releases

4.2(1)SP1(6.1)

4.2(1)SP1(6.2)

4.2(1)SP1(6.2a) and later releases

4.2(1)SP1(6.2a)

5.2(1)SP1(7.1)


Note

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 1000V Software Installation and Upgrade Guide.

Before You Begin
Procedure
    Step 1   From the Cisco Nexus Cloud Services Platform serial over LAN (SoL) connection, copy any unsaved configuration 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://user@linux-box.cisco.com/home/user/
nexus-1010.4.2.1.SP1.5.1a.iso bootflash:repository 
Enter vrf (If no input, current vrf 'default' is considered):
user@linux-box.cisco.com's password:
nexus-1010.4.2.1.SP1.5.1a.iso       100%  258234  10.3KB/s   00:15
switch#
    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 Platform is 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 active switch 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 status 
Redundancy role
---------------
      administrative:   primary
         operational:   primary
Redundancy mode
---------------
      administrative:   HA
         operational:   None
This supervisor (sup-1)
-----------------------
    Redundancy state:   Active
    Supervisor state:   Active
      Internal state:   Active with HA standby 
Other supervisor (sup-2)
------------------------
    Redundancy state: standby
    Supervisor state: HA standby
      Internal state: HA standby
switch#
---- ----
    Step 5   Verify if the new software is loaded.

    Example: 
    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(5.1a)   0.0
2   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  NA
2    00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8  NA

Mod  Server-IP       Server-UUID  Server-Name
---  --------------- ------------ --------------------
1    10.78.109.100   NA           NA
2    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 startup configuration.

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

    Reconfiguring SNMP User Accounts After an Upgrade

    During an upgrade, the SNMP engine ID changes internally to a unique engine ID. You must reconfigure all SNMP user accounts to work with the new engine ID. Until the SNMP user accounts are reconfigured, all SNMPv3 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 md5 
Sfish123 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 1 
        switch(config)# snmp user admin auth md5 Sfish123
      • Option 2 
        switch(config)# snmp-server user admin auth md5 
Sfish123 priv aes-128 Sfish123
      Step 3   Confirm that the engine ID has been updated, as follows:
      • Option 1 
        switch# 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 2 
        switch(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 engineID 
Local SNMP engineID: [Hex] 8000000903005056A0544E
                     [Dec] 128:000:000:009:003:000:080:086:160:084:078

      Configuration Examples for Upgrading the Cisco Nexus Cloud Services 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.iso
Installing 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: nexus-1010.5.2.1.SP1.7.1.iso....................................2014 
May 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         reset  
     2       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)           yes
     1   kickstart         4.2(1)SP1(6.2a)          5.2(1)SP1(7.1)           yes
     2      system         4.2(1)SP1(6.2a)          5.2(1)SP1(7.1)           yes
     2   kickstart         4.2(1)SP1(6.2a)          5.2(1)SP1(7.1)           yes


Module         Running-Version                                         ESX Version       
VSM 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, Possible Active-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 is UP 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.........2014 May 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.
 -- SUCCESS
2014 May 24 04:21:15 cppa-mgr %MODULE-5-STANDBY_SUP_OK: Supervisor 2 is standby2014 
May 24 04:21:15 cppa-mgr %SYSMGR-STANDBY-5-MODULE_ONLINE: System Manager has received notification of local 

module becoming 

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

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


"Switching over onto standby".
      This example shows how to upgrade from software Release version 4.2(1)SP1(6.1) to 4.2(1)SP1(6.2). 
      login: admin
Password: 

Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (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 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
switch# 
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.0                                              
2    4.2(1)SP1(6.1)    0.0                                              


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

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

* this terminal session 

switch# dir bootflash:repository

  939063296     Oct 01 02:39:47 2013  dcnm-installer.6.2.3.iso
      16384     Oct 01 08:06:29 2013  lost+found/
  221212672     Oct 01 02:37:27 2013  nam-app-x86_64.5-1-2.iso
  162895872     Oct 01 02:35:03 2013  nexus-1000v.4.2.1.SV2.2.1a.iso
  169783296     Oct 01 02:35:39 2013  nexus-1000v.5.2.1.SM1.5.1.iso
  159037440     Oct 01 02:36:29 2013  nexus-1000v.5.2.1.VSGM1.4.1.iso
  674701312     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 used
 3679551488 bytes free
 3991379968 bytes total

switch# install nexus1010 bootflash:repository//nexus-1010.4.2.1.SP1.6.2.iso
switch debug: Using URI: bootflash:/repository//nexus-1010.4.2.1.SP1.6.2.iso
Installing 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% -- SUCCESS
Extracting "kickstart" version from image bootflash:/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         reset  
     2       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.1)          4.2(1)SP1(6.2)           yes
     1   kickstart          4.2(1)SP1(6.1)          4.2(1)SP1(6.2)           yes
     2      system          4.2(1)SP1(6.1)          4.2(1)SP1(6.2)           yes
     2   kickstart          4.2(1)SP1(6.1)          4.2(1)SP1(6.2)           yes

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

Install is in progress, please wait.

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% -- SUCCESS
Performing 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)
.............................................................................................................................................................................................................2013 Oct  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: admin
Password: 

Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (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 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


switch# 
switch# show module

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

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

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

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


* this terminal session
      This example shows how to upgrade from Release 4.2(1)SP1(5.1a) to Release 4.2(1)SP1(6.2): 
      login: admin
Password: 

Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2012, 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 GNULesser 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


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(5.1a)   0.0                                              
2    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  NA
2    00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8  NA
Mod  Server-IP        Server-UUID                           Server-Name
---  ---------------  ------------------------------------  --------------------
1    80.80.80.220     NA                                    NA
2    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.iso
Usage for bootflash://sup-local  

309125120 bytes used 3682254848 bytes free 
3991379968 bytes total


switch# 

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

Installing 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% -- SUCCESS

Extracting "kickstart" version from image bootflash:/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         reset       
2       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(5.1a)          4.2(1)SP1(6.2)           yes    
1   kickstart         4.2(1)SP1(5.1a)          4.2(1)SP1(6.2)           yes     
2      system         4.2(1)SP1(5.1a)          4.2(1)SP1(6.2)           yes     
2   kickstart         4.2(1)SP1(5.1a)          4.2(1)SP1(6.2)           yes

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

Install is in progress, please wait.
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% -- SUCCESS
Performing 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 2 removed (Serial number T023D781781)
........................................................................................................................................................................................................2013 Oct  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 the switchover.___________________________[####################] 100% -- SUCCESS"Switching over onto standby".._
login as: admin
Cisco VSA
Using keyboard-interactive authentication.
Password:
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (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 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
switch# show module
Mod  Ports  Module-Type                       Model               Status
---  -----  --------------------------------  ------------------  ------------
1    0      Cisco Virtual Services Appliance  VSA                 ha-standby
2    0      Cisco Virtual Services Appliance  VSA                 active *

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

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

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

* this terminal session
switch#

      This example shows how to upgrade Release 4.2(1)SP1(3) to Release 4.2(1)SP1(5.1). 

      login as: admin
Nexus 1010
Using keyboard-interactive authentication.
Password: 
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2011, 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

switch# show mod[15D[J
switch# 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.0                                              
2    4.2(1)SP1(3)      0.0                                              

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

Mod  Server-IP        Server-UUID                           Server-Name
---  ---------------  ------------------------------------  --------------------
1    10.78.109.59     NA                                    NA
2    10.78.109.59     NA                                    NA

* this terminal session 
switch# show[J[J[J[Jd[Jdir boot[15D[J
switch# dir boot[Jflash:r[22D[J
switch# 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-local
  308862976 bytes used
 3682516992 bytes free
 3991379968 bytes total

switch# inst[11D[J
switch# inst[Jall nexu[19D[J
switch# install nexu[Js1010 boot[29D[J
switch# install nexus1010 boot[Jflash:[35D[J
switch# 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/
[J
switch# install nexus1010 bootflash://[J[Jr[36D[J
switch# install nexus1010 bootflash:r[Jepository/nexu[50D[J
switch# 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.iso
Installing 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 image bootflash:/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       yes  non-disruptive         reset  
     2       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(3)          4.2(1)SP1(5.1)           yes
     1   kickstart            4.2(1)SP1(3)          4.2(1)SP1(5.1)           yes
     2      system            4.2(1)SP1(3)          4.2(1)SP1(5.1)           yes
     2   kickstart            4.2(1)SP1(3)          4.2(1)SP1(5.1)           yes


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


Install is in progress, please wait.

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)

.............................................................................................................2014 Jun 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: admin
Nexus 1010
Using keyboard-interactive authentication.
Password: 
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2012, 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

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

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

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

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

Mod  Server-IP        Server-UUID                           Server-Name
---  ---------------  ------------------------------------  --------------------
1    10.78.109.59     NA                                    NA
2    10.78.109.59     NA                                    NA

* this terminal session

      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.iso	
cppa_mgr debug: Using URI: bootflash:/repository/nexus-1010.4.2.1.SP1.4.iso
Installing 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 

Images will be upgraded according to following table:
Module       Image         Running-Version             New-Version  Upg-Required
------  ----------  ----------------------  ----------------------  ------------
     1      system            4.2(1)SP1(3)            4.2(1)SP1(4)           yes
     1   kickstart            4.2(1)SP1(3)            4.2(1)SP1(4)           yes
     2      system            4.2(1)SP1(3)            4.2(1)SP1(4)           yes
     2   kickstart            4.2(1)SP1(3)            4.2(1)SP1(4)           yes
Module         Running-Version ESX Version       VSM Compatibility       ESX Compatibility
------  ----------------------  ----------------------------------------------------  ----------------------  ----------------------

Install is in progress, please wait.

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 2 removed (Serial number T023D750981)
...........................................................................2011 Jul 25 20: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: 6
INIT: Sending processes the TERM signal
Jul 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) is forced exit.
Jul 25 20:20:41 %TTYD-2-TTYD_ERROR TTYD Error ttyd bad select
Jul 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)is forced 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 forced exit.
Jul 25 20:20:41 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "AAA Daemon"(PID 2501)is forced exit.
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:/n
exus-1010-mz.4.2.1.SP1.3.bin...
Booting kickstart image: bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.4.bin.
........................................................Image verification 
OK

Starting kernel...
PCI: PIIX3: Enabling Passiv%H+Y4% 
                                     001-Usage: init 0123456SsQqAaBbCcUu
mkdir: cannot create directory `/new-root/old-root': File exists
INIT: version 2.85 booting
Bootflash device is /dev/hda
Checking all filesystems..... done.
Setting kernel variables: sysctlnet.ipv4.ip_forward = 0
net.ipv4.ip_default_ttl = 64
net.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 directory
Loading system software
Uncompressing system image: bootflash:/nexus-1010-mz.4.2.1.SP1.4.bin

Load plugins that defined in image conf: /isan/plugin_img/img.conf
load_plugin: failed read swid map from "/mnt/pss/plugin_swid_map" with rc 0xffffffff. Plugin will be assigned new ID
Loading plugin 0: core_plugin...
load_plugin: Can't get exclude list from /isan/plugin/0/boot/etc/plugin_exclude.conf (rc 0x40ea0017)
plugin_link_to_exec_path: plugin_path = /isan/plugin/0, tar_log = /isan/plugin_extract_log/0
num srgs 1
0: swid-core-sup1sfp, swid-core-sup1sfp
num srgs 1
0: swid-sup1sfp-ks, swid-sup1sfp-ks
INIT: Entering runlevel: 3
Starting dhcpd daemon: dhcpdInternet Systems Consortium DHCP Server V3.0.1rc14
Copyright 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 1010
switch(standby) login: 2011 Jul 26 04:24:22 switch %USER-2-SYSTEM_MSG: CLIS: loading cmd files begin  - clis
2011 Jul 26 04:24:29 switch %USER-2-SYSTEM_MSG: CLIS: loading cmd files end  - clis
2011 Jul 26 04:24:29 switch %USER-2-SYSTEM_MSG: CLIS: init begin  - clis
2011 Jul 26 04:24:38 switch %USER-2-SYSTEM_MSG: Invalid feature name eth-port-sec - clis
Nexus 1010
switch(standby) login: admin
Password: 
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2012, 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
switch(standby)# 

Inactive timeout reached, logging out.

Nexus 1010
switch(standby) login:

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

Starting kernel...
PCI: PIIX3: Enabling Passive Veh+001-?Usage: init 0123456SsQqAaBbCcUu
mkdir: cannot create directory `/new-root/old-root': File exists
INIT: version 2.85 booting
Bootflash device is /dev/hda
Checking all filesystems...r.r.r done.

Setting kernel variables: sysctlnet.ipv4.ip_forward = 0
net.ipv4.ip_default_ttl = 64
net.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 directory
Loading system software
Uncompressing system image: bootflash:/nexus-1010-mz.4.2.1.SP1.4.bin

Load plugins that defined in image conf: /isan/plugin_img/img.conf
load_plugin: failed read swid map from "/mnt/pss/plugin_swid_map" with rc 0xffffffff. Plugin will be assigned new ID
Loading plugin 0: core_plugin...
load_plugin: Can't get exclude list from /isan/plugin/0/boot/etc/plugin_exclude.conf (rc 0x40ea0017)
plugin_link_to_exec_path: plugin_path = /isan/plugin/0, tar_log = /isan/plugin_extract_log/0
num srgs 1
0: swid-core-sup1sfp, swid-core-sup1sfp
num srgs 1
0: swid-sup1sfp-ks, swid-sup1sfp-ks
INIT: Entering runlevel: 3
Starting dhcpd daemon: dhcpdInternet Systems Consortium DHCP Server V3.0.1rc14
Copyright 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 wait
Trying 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  - clis
2012 May 26 09:30:15 switch %USER-2-SYSTEM_MSG: CLIS: init begin  - clis
2012 May 26 09:30:32 switch %USER-2-SYSTEM_MSG: Invalid feature name eth-port-sec - clis

Module 2: Waiting for module online.
 -- SUCCESS
2011 Jul 25 20:20:41 switch %SYSMGR-2-HASWITCHOVER_PRE_START: This supervisor is becoming active (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 :unavailable
Install has been successful.

Nexus 1010
switch login: admin
Password: 
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2012, 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
switch# copy running-config startup-config
[########################################] 100%
cppa-mgr#

      Feature History for Software Upgrade

      This section provides the software installation and upgrade release history:

      Feature Name

      Releases

      Feature Information

      Software upgrade

      4.2(1)SP1(2)

      This feature was introduced.