upgraded according to following table: Module Image Running-Version New-Version Upg-Required system 4.2 (1) N2 (1) 5.0 (2) N2 (1) 1 kickstart 4.2 (1)N2(1) 5.0(2)N2(1) 2.0(06/19/08) v1.3.0(09/08/09) 1 power-seq At this point, if your Nexus switch needs to be rebooted (disruptive upgrade), you will get the following message: Switch will be reloaded for disruptive upgrade. Do you want to continue with the installation (y/n)? [n] Ours does not, SO we get this instead: Do you want to continue with the installation (y/n)? [n] y We're then treated to a pile of descriptive process updates: Chapter 18: Cisco Nexus Install is in progress, please wait. Notifying services about the upgrade. 100% -- SUCCESS Setting boot variables. 100% -- SUCCESS Performing configuration copy. ] 100% -- SUCCESS Module 1: Refreshing compact flash and upgrading bios/loader/bootrom/power-seq. Warning: please do not remove or power off the module at this time. Note: Power-seq upgrade needs a power-cycle to take into effect. On success of power-seq upgrade, SWITCH OFF THE POWER to the system and then, power it up. 100% -- SUCCESS Upgrade can no longer be aborted, any failure will result in a disruptive upgrade. Requesting Line Cards to stop communication. ] 100% -- SUCCESS Requesting Sup Apps to stop communication. 100% -- SUCCESS Freeing memory in the file system. 100% -- SUCCESS Loading images into memory. 100% -- SUCCESS Saving supervisor runtime state. 100% -- SUCCESS Saving mts state. writing reset reason 88, <NULL> 100% -- SUCCESS Rebooting the switch to proceed with the upgrade. This looks scary, but it's only informing us that the CPU-based processes are restarting. While we'll be kicked out of the switch, traffic will continue to flow during this process: All telnet and ssh connections will now be terminated. Starting new kernel Calling kexec callback Moving to new kernel Calling into reboot_code_buffer code Starting kernel Usage: init 0123456SsQqAaBbCcUu INIT: version 2.85 booting platform_type cmdline parameter not found. Asssuming Oreg