Cisco Cisco Nexus 5010 Switch Guida All'Installazione

  kickstart compile time:  1/23/2014 4:00:00 [01/23/2014 05:38:54]

  system image file is:    bootflash:///n5000-uk9.7.2.0.N1.1.bin

  system compile time:     1/23/2014 4:00:00 [01/23/2014 08:56:30]

Hardware

  cisco Nexus5548 Chassis ("O2 32X10GE/Modular Supervisor")

  Intel(R) Xeon(R) CPU         with 8253860 kB of memory.

  Processor Board ID JAF1429AMFB

  Device name: switch-1

  bootflash:    2007040 kB

Kernel uptime is 0 day(s), 0 hour(s), 5 minute(s), 31 second(s)

Last reset at 82850 usecs after  Fri Jan 24 17:06:14 2014

  Reason: Reset due to upgrade

  System version: 7.0(3)N1(1)

  Service:

plugin

  Core Plugin, Ethernet Plugin, Fc Plugin

The following list summarizes the upgrade process on a primary switch in a vPC topology. 

In vPC topologies, the two peer switches must be upgraded individually. An upgrade on one peer switch 
does not automatically update the vPC peer switch.

The install all command issued on the vPC primary switch triggers the installation upgrade.

The compatibility checks display the impact of the upgrade.

The installation proceeds or not based on the upgrade impact.

The configuration is locked on both vPC peer switches.

The current state is saved.

The system unloads and runs the new image.

The stateful restart of the system software and application occurs.

The installer resumes with the new image.

The FEXs are upgraded sequentially.

The installation is complete.

When the installation is complete, the vPC primary switch and the FEXs that are connected to the 
primary switch are upgraded. The single-homed FEXs and the dual-homed FEXs are now running the 
upgraded software.

The dual-homed FEXs are now connected to the primary and secondary switches that are running two 
different versions of the Cisco NX-OS software. The vPC primary switch is running the upgraded 
version and the vPC secondary switch is running the original software version. The Cisco NX-OS