age: "Running-config contains configuration that is incompatible with the new image (strict incompatibility). Please run 'show incompatibility system <image>' command to find out which feature needs to be disabled.' Now that I'm happy that I won't break the network, I can go ahead and install the images using the install command: NX-5K-1# install all kickstart n5000-uk9-kickstart.5.0.2.N2. system n5000-uk9.5.0.2.N2.1.bin Verifying image bootflash:/n5000-uk9-kickstart.5.0.2.N2.1.bin for boot variable "kickstart". [####################] 100% -- SUCCESS Verifying image bootflash:/n5000-uk9.5.0.2.N2.1.bin for boot variable "system". [####################] 100% SUCCESS Verifying image type. [####################] 100% SUCCESS Extracting "system" version from image bootflash:/n5000-uk9.5.0.2.N2.1.bin Nexus Design Features [####################] 100% -- SUCCESS Extracting "kickstart" version from image botflash:/n5000-uk9-kickstart. 5.0.2.N2.1.bin. [####################] 100% SUCCESS Extracting "bios" version from image bootflash:/n5000-uk9.5.0.2.N2.1.bin. [####################] 100% -- SUCCESS Notifying services about system upgrade. ] 100% - - SUCCESS If you cannot do a hitless upgrade, you will get this paragraph (or one similar, depending on the reason: Compatibility check is done: Module bootable Impact Install-type Reason disruptive reset Current running-config is not supported by new image Luckily, we're in good shape, and got the following instead: Compatibility check is done: Module bootable Impact Install-type Reason yes non-disruptive reset A disruptive upgrade means that the entire switch will reboot, ceasing all network traffic traversing the switch. A nondisruptive, or hitless, upgrade will reload the kernel, but packets will continue to flow during the process. This is possible because Nexus sep- arates packet flow from CPU processing, or as the marketing docs say, the data plane is separate from the control plane. Finally, we get the following chart, which tells us what's about to happen: Images will be 