Table Of Contents
Cisco Nexus 1010 Software Installation and Upgrade Guide, Release 4.2(1) SP1(3)
Information About Software Install and Upgrade
Information About Re-installing the Software
Information About In Service Software Upgrade
Verifying the CIMC Software Version
Upgrading from Software Release 4.2(1)SP1(2)
Upgrading from Software Release 4.0(4)SP1(1)
Feature History for Software Installation and Upgrade
Obtaining Documentation and Submitting a Service Request
Cisco Nexus 1010 Software Installation and Upgrade Guide, Release 4.2(1) SP1(3)
Revised: July 30, 2013
OL-24455-A1This document describes how to reinstall or upgrade the Cisco Nexus 1010 software, and includes the following topics:
•Information About Software Install and Upgrade
•Verifying the CIMC Software Version
•Feature History for Software Installation and Upgrade
•Obtaining Documentation and Submitting a Service Request
Note For information about upgrading Cisco Nexus 1000V software on a VSB, see the Cisco Nexus 1000V Software Upgrade Guide, Release 4.2(1)SV1(4a).
For an overview of the Cisco Nexus 1010 system and procedures for configuring the software after it is installed, see the Cisco Nexus 1010 Software Configuration Guide, Release 4.2(1)SP1(3).
Audience
This document is for network administrators with knowledge of the Cisco Nexus 1000V and experience in the installation, upgrade, and management of Cisco Nexus 1000V VSMs.
Information About Software Install and Upgrade
This section includes the following topics:
•Information About Re-installing the Software
•Information About In Service Software Upgrade
Information About Re-installing the Software
Cisco Nexus 1010 software is pre installed as an ISO image that includes the following components:
•Cisco Nexus 1010 kickstart image
This is the image for the Cisco Nexus 1010 Manager virtual machine which manages shelf and redundancy group configuration.•Hypervisor with a Cisco Nexus 1010 agent
In the event of disk corruption on the Cisco Nexus 1010, the system can be brought up by copying the image from a CD.
Information About In Service Software Upgrade
The Cisco Nexus 1010 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 standby Cisco Nexus 1010 is upgraded first and reloaded by the active. During the upgrade, messages display as the ISO image is extracted, verified, synchronized, and the upgrade summarized. After the standby comes up with the new software version, the system waits for all VSBs to come up before the standby takes over and reloads the active with the new version. Finally, the ISSU is complete when both Cisco Nexus 1010s form an HA pair with the new software version.
Prerequisites
Before installing or upgrading to Cisco Nexus 1010 Release 4.2(1)SP1(3), you must know or do the following:
•You must have CIMC software Version 1.2.1(b) or higher installed. For more information, see the CIMC And BIOS Information.
•Use the "Verifying the CIMC Software Version" procedure to verify you have this CIMC version installed. For more information, see the CIMC Firmware Management on UCS C-Series Servers document.
The upgrade or install fails if an earlier version of CIMC is installed.
•Use N1010 CIMC GUI to update the CIMC, and BIOS firmware individually using the manual procedure. For more information, see the CIMC And BIOS Information.
Guidelines and Limitations
Use the following guidelines and limitations when reinstalling or upgrading software:
Caution When you reinstall the software, all previous configuration is overwritten and lost.
•The only way to upgrade the software is by using the install nexus1010 command
•Boot variables must be set by the system when you use the install command. Never attempt to set the boot variables manually.
CIMC And BIOS Information
Use the following guidelines for installing the latest software version of CIMC and for updating the CIMC and BIOS firmware.
•You must have CIMC software version 1.2.1(b) or higher installed. The latest CIMC software is available in the Unified Computing System (UCS) Server Firmware 1.2(1b) download page.
•Use the "Verifying the CIMC Software Version" procedure to verify you have this CIMC version installed. For more information, see the CIMC Firmware Management on UCS C-Series Servers document.
The upgrade or install fails if an earlier version of CIMC is installed.
•Use N1010 CIMC GUI to update the CIMC, and BIOS firmware individually using the manual procedure.
–Upgrade to the latest CIMC version using the following manual procedure: http://www.cisco.com/en/US/products/ps10493/products_configuration_example09186a0080b07b7c.shtml#gui-firmware-browser
–Upgrade the BIOS firmware using the following manual procedure:
http://www.cisco.com/en/US/docs/unified_computing/ucs/c/sw/bios/b_Upgrading_BIOS_Firmware.html#task_DD83FB75DB8C485FA4E8ED222C77BD3CVerifying the CIMC Software Version
Use this procedure to verify that you have CIMC software Version 1.2.1(b) or higher installed on your Cisco Nexus 1010 or Cisco Nexus 1010-X .
BEFORE YOU BEGIN
Before beginning this procedure, you must know or do the following:
•You must have CIMC software Version 1.2.1(b) or higher installed.
•If CIMC software Version 1.2.1(b) or higher is installed, you will see the product ID N1K-C1010 on Cisco Nexus 1010 or the product ID N1K-C1010-X on Cisco Nexus 1010-X in the output of the show hardware command. This procedure includes steps for this verification.
•You are logged in to the Cisco Nexus 1010 or Cisco Nexus 1010-X from the CLI or a Web browser.
Step 1 From the Cisco Nexus 1010 or Cisco Nexus 1010-X do one of the following to display the product ID (PID):
•From the CLI, view the output of the show hardware command.
Look in the Switch Hardware ID information for the PID.•From a WEB browser, open the Server Summary window and view the server properties. See Figure 1-1 for an example.
Example:DOCS-CPPA# show hardware
Cisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2010, 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 eachsuch license is available at http://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.phpSoftwareloader: version unavailable [last: image booted through mgmt0]kickstart: version 4.0(4)SP1(1)system: version 4.0(4)SP1(1) [gdb]kickstart image file is:kickstart compile time: 4/19/2010 1:00:00system image file is: bootflash:/nexus-1010-mzg.4.0.4.SP1.1.binsystem compile time: 4/19/2010 1:00:00 [04/19/2010 13:07:00]HardwareCisco Nexus 1010 Chassis ("Cisco Nexus1010 Chassis")with 14666752 kB of memory.Device name: DOCS-CPPAbootflash: 3897832 kBDisk Storage capacity for VM virtual disks: 346428 GBNumber of physical 1Gbps ethernet ports: 6Number of CPU Cores: 8CPU Cores details:model name : Intel(R) Xeon(R) CPU E5504 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5504 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5504 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5504 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5504 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5504 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5504 @ 2.00GHzmodel name : Intel(R) Xeon(R) CPU E5504 @ 2.00GHzKernel uptime is 116 day(s), 19 hour(s), 43 minute(s), 7 second(s)pluginCore Plugin, Ethernet Plugin--------------------------------Switch hardware ID information--------------------------------Switch is booted upSwitch type is : Nexus 1010 ChassisModel number is Nexus 1010Manufacture date is 03/29/2010PID-VID-SN: N1K-C1010-A-1383802872129225113UUID is D5A54100-D9A2-11DE-B0C7-6BFCF373D92E--------------------------------Chassis has 2 Module slots--------------------------------Module1 okModule type is : Cisco Nexus1010 Chassis0 submodules are presentModel number is Nexus 1010H/W version is .Manufacture Date is Year 0 Week 3Serial number is T023D7AF101Module2 okModule type is : Cisco Nexus1010 Chassis0 submodules are presentModel number is Nexus 1010H/W version is .Manufacture Date is Year 0 Week 3Serial number is T023D7AF181Figure 1-1 CIMC Window with Product ID (PID)
Step 2 Do one of the following:
•If the PID displayed is N1K-C1010 on Cisco Nexus 1010 or N1K-C1010-X on Cisco Nexus 1010-X, you can proceed with the install or upgrade to Cisco Nexus 1010 Release 4.2(1)SP1(3).
•If the PID displayed is not N1K-C1010 on Cisco Nexus 1010 or N1K-C1010-X on Cisco Nexus 1010-X, do not install or upgrade to Release 4.2(1)SP1(3). Instead you must replace the Cisco Nexus 1010 using the RMA process.
Reinstalling the Software
You can use this procedure to reinstall the software from your software CD in the event that the system disk becomes corrupted.
BEFORE YOU BEGIN
Before beginning this procedure you must know or do the following:
•You have verified that you have the following product ID (PID), using the "Verifying the CIMC Software Version" procedure.
–N1K-C1010 on Cisco Nexus 1010
–N1K-C1010-X on Cisco Nexus 1010-X
Caution You cannot install or upgrade to Release 4.2(1)SP1(3) unless 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.
Caution Potential Loss of Data
When you reinstall the software, all previous configuration is overwritten and lost.
DETAILED STEPS
Step 1 From a terminal server, connect to the serial port of the Cisco Nexus 1010 or Cisco Nexus 1010-X.
Step 2 Insert the installation CD in the DVD-RW drive.
Step 3 On the Cisco Nexus 1010 or Cisco Nexus 1010-X, press the Power button.
The Cisco Nexus 1010 or Cisco Nexus 1010-X reboots and the management software setup process begins.
To configure the software, see the Cisco Nexus 1010 Software Configuration Guide, Release 4.2(1)SP1(3).
Upgrading the Software
You can use the procedures in this section to upgrade the Cisco Nexus 1010 software to a new version.
•Upgrading from Software Release 4.2(1)SP1(2)
•Upgrading from Software Release 4.0(4)SP1(1)
Prerequisites
Before beginning this procedures in this section you must know or do the following:
•You have verified that you have the following product ID (PID), using the "Verifying the CIMC Software Version" procedure.
–N1K-C1010 on Cisco Nexus 1010
–N1K-C1010-X on Cisco Nexus 1010-X
Caution You cannot install or upgrade to Release 4.2(1)SP1(3) unless 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.
•You are logged in to the CLI from the CIMC/Serial over LAN port on the rear of the Cisco Nexus 1010 or Cisco Nexus 1010-X.
Note Do not log in using the management IP for this procedure. This procedure requires you to first upgrade and reload the standby Cisco Nexus 1010 after which the HA pair have incompatible software versions. By logging in using serial over LAN, you prevent the split brain that occurs in this configuration.
•This procedure upgrades both the active and standby Cisco Nexus 1010.
•You have already saved a backup copy of your running configuration on an external server.
•After reloading the new software version during an upgrade, you must save the new upgrade configuration persistently through reboots and restarts by copying it to the startup configuration. These procedures include a step for this.
•You have saved a copy of the new Cisco Nexus 1010 software file from the following Cisco.com software download site to an external server.
•Use N1010 CIMC GUI to update the CIMC, and BIOS firmware individually using the manual procedure. For more information, see the CIMC And BIOS Information.
Upgrading from Software Release 4.2(1)SP1(2)
You can use this procedure for the following Cisco Nexus 1010 upgrade while retaining operational data and persistent information.
Note To upgrade from 4.0(4) SP1(1), see the "Upgrading from Software Release 4.0(4)SP1(1)" procedure.
Note For information about upgrading Cisco Nexus 1000V software on a VSB, see the Cisco Nexus 1000V Software Upgrade Guide, Release 4.2(1)SV1(4a).
DETAILED STEPS
Step 1 From the Cisco Nexus 1010 serial over LAN connection, copy any unsaved configuration from the running configuration to startup so that it is preserved after the reload.
copy running-config startup-config
Example:
switch# copy running-config startup-config
[########################################] 100%switch#Step 2 Copy the new software image from the external server to the following directory.
bootflash: \repository
copy scp://user@path/filename bootflash:filename
Example:
n1010# copy scp://user@linux-box.cisco.com/home/user/nexus-1010.4.2.1.SP1.1.3.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.3.iso 100% 258234 10.3KB/s 00:15n1010#Step 3 Install the new image.
install nexus1010 full_path_to_filename
Example:
switch# install nexus1010 bootflash:repository/nexus-1010.4.2.1.sp1.3.iso
The following things occur on the switch:
•The new software image is copied to bootflash and the standby Cisco Nexus 1010 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 reloads the standby with the new software version.
•The system waits for all VSBs to come up before the standby takes over and reloads the active with the new software version.
Step 4 From the CLI for each module, verify that both modules are in HA mode.
show system redundancy status
Example:
switch# show system redundancy status
Redundancy role---------------administrative: primaryoperational: primaryRedundancy mode---------------administrative: HAoperational: NoneThis supervisor (sup-1)-----------------------Redundancy state: ActiveSupervisor state: ActiveInternal state: Active with HA standbyOther supervisor (sup-2)------------------------Redundancy state: standby Supervisor state: HA standby Internal state: HA standbyswitch#---- ----Step 5 Verify that the new software is loaded.
show module
switch# show module
Mod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------1 0 Cisco Nexus1010 Chassis Nexus1010 active *2 0 Cisco Nexus1010 Chassis Nexus1010 ha-standbyMod Sw Hw--- --------------- ------1 4.2(1)SP1(3) 0.02 4.2(1)SP1(3) 0.0Mod 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 172.23.231.113 NA NA2 172.23.231.113 NA NA* this terminal sessionswitch#Step 6 Save the new upgrade configuration persistently through reboots and restarts by copying it to the startup configuration.
copy running-config startup-config
Example:
switch# copy running-config startup-config
[########################################] 100%
switch#
Upgrading from Software Release 4.0(4)SP1(1)
You can use this procedure for the following Cisco Nexus 1010 upgrade while retaining operational data and persistent information.
Note To upgrade from 4.2(1) SP1(2), see the "Upgrading from Software Release 4.2(1)SP1(2)" procedure.
Note For information about upgrading Cisco Nexus 1000V software on a VSB, see the Cisco Nexus 1000V Software Upgrade Guide, Release 4.2(1)SV1(4a).
BEFORE YOU BEGIN
Before beginning this procedure you must know or do the following:
•To keep VSMs available, reload the redundant VSB modules separately as described in this procedure.
DETAILED STEPS
Step 1 From the Cisco Nexus 1010 serial over LAN connection, copy any unsaved configuration from the running configuration to startup so that it is preserved after the reload.
copy running-config startup-config
Example:
switch# copy running-config startup-config
[########################################] 100%switch#Step 2 Copy the new software image from the external server to the following directory.
bootflash: \repository
copy scp://user@path/filename bootflash:filename
Example:
n1010# copy scp://user@linux-box.cisco.com/home/user/nexus-1010.4.2.1.SP1.1.3.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.1.3.iso 100% 258234 10.3KB/s 00:15n1010#Step 3 Install the new image.
install nexus1010 full_path_to_filename
The following things occur on the switch:
•The new software image is copied to bootflash.
•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 running configuration.
Example:
switch# install nexus1010 bootflash:repository/nexus-1010.4.2.1.SP1.1.3.iso
Step 4 Save the new boot parameters in the startup configuration.
switch# copy running-config startup-config
[########################################] 100%
Caution If you do not copy the running configuration to the startup configuration, the new boot parameters are not saved when you reload the software in Step 5.
Step 5 Reload the software to refresh the software image with the new image file.
reload
The software image is replaced in Cisco Nexus 1010 pair with the version named in bootflash variables. The Cisco Nexus 1010s sync.
Any unsaved configuration is lost.Example:
switch# reloadThis command will reboot the system. (y/n)? [n] y2009 Oct 30 21:51:34 s1 %$ VDC-1 %$ %PLATFORM-2-PFM_SYSTEM_RESET: Manual system restart
from Command Line Interface
switch#
Step 6 From the CLI for each module, verify that both VSBs are in HA mode.
show system redundancy status
Example:
switch# show system redundancy status
Redundancy role---------------administrative: primaryoperational: primaryRedundancy mode---------------administrative: HAoperational: NoneThis supervisor (sup-1)-----------------------Redundancy state: ActiveSupervisor state: ActiveInternal state: Active with HA standbyOther supervisor (sup-2)------------------------Redundancy state: standby Supervisor state: HA standby Internal state: HA standbyswitch#---- ----Step 7 Verify that the new software is loaded.
show module
switch# show module
Mod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------1 0 Cisco Nexus1010 Chassis Nexus1010 active *2 0 Cisco Nexus1010 Chassis Nexus1010 ha-standbyMod Sw Hw--- --------------- ------1 4.2(1)SP1(3) 0.02 4.2(1)SP1(3) 0.0Mod 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 172.23.231.113 NA NA2 172.23.231.113 NA NA* this terminal sessionswitch#Step 8 Save the new upgrade configuration persistently through reboots and restarts by copying it to the startup configuration.
copy running-config startup-config
Example:
n1000v# copy running-config startup-config
[########################################] 100%
n1000v#
Example Configuration
The following is an example upgrade from software version 4.2(1)SP1(2).
cppa-mgr# install nexus1010 bootflash:repository/nexus-1010.4.2.1.SP1.3.isocppa_mgr debug: Using URI: bootflash:/repository/nexus-1010.4.2.1.SP1.3.isoInstalling bootflash:/repository/nexus-1010.4.2.1.SP1.3.iso................................................................................Verifying image bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.3.bin for boot variable "kickstart".[[####################] 100% -- SUCCESSVerifying image bootflash:/nexus-1010-mz.4.2.1.SP1.3.bin for boot variable "system".[[####################] 100% -- SUCCESSVerifying image type.[[[[[####################] 100% -- SUCCESSExtracting "system" version from image bootflash:/nexus-1010-mz.4.2.1.SP1.3.bin.[[####################] 100% -- SUCCESSExtracting "kickstart" version from image bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.3.bin.[####################] 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(2) 4.2(1)SP1(3) yes1 kickstart 4.2(1)SP1(2) 4.2(1)SP1(3) yes2 system 4.2(1)SP1(2) 4.2(1)SP1(3) yes2 kickstart 4.2(1)SP1(2) 4.2(1)SP1(3) yesModule 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.3.bin to standby.[[####################] 100% -- SUCCESSSyncing image bootflash:/nexus-1010-mz.4.2.1.SP1.3.bin to standby.[#[####################] 100% -- SUCCESSSetting boot variables.[# [####################] 100% -- SUCCESSPerforming configuration copy.[[[####################] 100% -- SUCCESS..........................2011 Jul 25 20:12:16 cppa-mgr %PLATFORM-2-MOD_REMOVE: Module 2 removed (Serial number T023D750981)...........................................................................2011 Jul 25 20:14:54 cppa-mgr %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) is forced 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)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.3.bin bootflash:/nexus-1010-mz.4.2.1.SP1.3.bin...Booting kickstart image: bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.3.bin.........................................................Image verificationOKStarting 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.3.binLoad 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. Plugin will be assigned new IDLoading 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/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 existNexus 1010cppa-mgr(standby) login: 2011 Jul 26 04:24:22 cppa-mgr %USER-2-SYSTEM_MSG: CLIS: loading cmd files begin - clis2011 Jul 26 04:24:29 cppa-mgr %USER-2-SYSTEM_MSG: CLIS: loading cmd files end - clis2011 Jul 26 04:24:29 cppa-mgr %USER-2-SYSTEM_MSG: CLIS: init begin - clis2011 Jul 26 04:24:38 cppa-mgr %USER-2-SYSTEM_MSG: Invalid feature name eth-port-sec - clisNexus 1010cppa-mgr(standby) login: adminPassword: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 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 athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.phpcppa-mgr(standby)#Inactive timeout reached, logging out.Nexus 1010cppa-mgr(standby) login:(The upgrade of the standby Cisco Nexus 1010 begins here.)
Auto booting bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.3.bin bootflash:/nexus-1010-mz.4.2.1.SP1.3.bin...Booting kickstart image: bootflash:/nexus-1010-kickstart-mz.4.2.1.SP1.3.bin...............................................................Image verificationOKStarting 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.3.binLoad 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. Plugin will be assigned new IDLoading 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/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 existContinuing with installation, please waitTrying to start the installer...Trying to start the installer...2012 May 26 09:30:15 cppa-mgr %USER-2-SYSTEM_MSG: CLIS: loading cmd files end - clis2012 May 26 09:30:15 cppa-mgr %USER-2-SYSTEM_MSG: CLIS: init begin - clis2012 May 26 09:30:32 cppa-mgr %USER-2-SYSTEM_MSG: Invalid feature name eth-port-sec - clisModule 2: Waiting for module online.-- SUCCESS2011 Jul 25 20:20:41 cppa-mgr %SYSMGR-2-HASWITCHOVER_PRE_START: This supervisor is becoming active (pre-start phase).2011 Jul 25 20:20:41 cppa-mgr %SYSMGR-2-HASWITCHOVER_START: This supervisor is becoming active.2011 Jul 25 20:20:41 cppa-mgr %SYSMGR-2-SWITCHOVER_OVER: Switchover completed.2011 Jul 25 20:20:58 cppa-mgr %PLATFORM-2-MOD_REMOVE: Module 1 removed (Serial number )2011 Jul 25 20:24:21 cppa-mgr %PLATFORM-2-MOD_DETECT: Module 1 detected (Serial number :unavailable) Module-Type Virtual Supervisor Module Model :unavailableInstall has been successful.Nexus 1010cppa-mgr login: adminPassword: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 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 athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.phpcppa-mgr# copy running-config startup-config
[########################################] 100%
cppa-mgr#
Additional References
Feature History for Software Installation and Upgrade
This section provides the software installation and upgrade release history.
Feature Name Releases Feature InformationCisco Nexus 1010-X
4.2(1)SP1(3)
This hardware was introduced.
Software reinstall or upgrade
4.2(1)SP1(2)
This feature was introduced.
Available Documents
This section lists the documents used with the Cisco Nexus 1000V and Cisco Nexus 1010 and available on Cisco.com at the following urls:
http://www.cisco.com/en/US/products/ps9902/tsd_products_support_series_home.html
http://www.cisco.com/en/US/products/ps12752/tsd_products_support_series_home.html
General Information
Cisco Nexus 1000V Documentation Roadmap, Release 4.2(1)SV1(4a)
Cisco Nexus 1000V Release Notes, Release 4.2(1)SV1(4a)
Cisco Nexus 1000V Compatibility Information, Release 4.2(1)SV1(4a)
Cisco Nexus 1010 Management Software Release Notes, Release 4.2(1)SP1(3)
Install and Upgrade
Cisco Nexus 1000V Virtual Supervisor Module Software Installation Guide, Release 4.2(1)SV1(4a)
Cisco Nexus 1000V Software Upgrade Guide, Release 4.2(1)SV1(4a)
Cisco Nexus 1000V VEM Software Installation and Upgrade Guide, Release 4.2(1)SV1(4a)
Cisco Nexus 1010 Virtual Services Appliance Hardware Installation Guide
Cisco Nexus 1010 Software Installation and Upgrade Guide, Release 4.2(1)SP1(3)
Configuration Guides
Cisco Nexus 1000V License Configuration Guide, Release 4.2(1)SV1(4a)
Cisco Nexus 1000V Getting Started Guide, Release 4.2(1)SV1(4a)
Cisco Nexus 1000V High Availability and Redundancy Configuration Guide, Release 4.2(1)SV1(4)
Cisco Nexus 1000V Interface Configuration Guide, Release 4.2(1)SV1(4a)
Cisco Nexus 1000V Layer 2 Switching Configuration Guide, Release 4.2(1)SV1(4)
Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.2(1)SV1(4a)
Cisco Nexus 1000V Quality of Service Configuration Guide, Release 4.2(1)SV1(4)
Cisco Nexus 1000V Security Configuration Guide, Release 4.2(1)SV1(4a)
Cisco Nexus 1000V System Management Configuration Guide, Release 4.2(1)SV1(4a)
Cisco Nexus 1010 Software Configuration Guide, Release 4.2(1)SP1(3)
Programming Guide
Cisco Nexus 1000V XML API User Guide, Release 4.2(1)SV1(4)
Reference Guides
Cisco Nexus 1000V Command Reference, Release 4.2(1)SV1(4)
Cisco Nexus 1000V MIB Quick Reference
Cisco Nexus 1010 Command Reference, Release 4.2(1)SP1(3)
Troubleshooting and Alerts
Cisco Nexus 1000V Troubleshooting Guide, Release 4.2(1)SV1(4a)
Cisco Nexus 1000V Password Recovery Guide
Cisco NX-OS System Messages Reference
Virtual Security Gateway Documentation
Cisco Virtual Security Gateway for Nexus 1000V Series Switch
Virtual Network Management Center
Cisco Virtual Network Management Center
Network Analysis Module Documentation
Cisco Prime Network Analysis Module Software Documentation Guide, 5.1
Cisco Prime Network Analysis Module (NAM) for Nexus 1010 Installation and Configuration Guide, 5.1
Cisco Prime Network Analysis Module Command Reference Guide 5.1
Cisco Prime Network Analysis Module Software 5.1 Release Notes
Cisco Prime Network Analysis Module Software 5.1 User Guide
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
This document is to be used in conjunction with the documents listed in the "Available Documents" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Internet Protocol (IP) addresses used in the examples, command display output, and figures within this document are for illustration only. If an actual IP address appears in this document, it is coincidental.
© 2010-2011 Cisco Systems, Inc. All rights reserved