version 4.1 to 5.0. I use a TFTP server running on my MacBook Pro connected to the 5020 via the mgmt0 interface on the switch. First I'll start with the similar copy tftp: boot flash: statement: NX-5K-1# copy tftp: bootflash: The switch then prompts me for the new filename, which I give as follows: Enter source filename: n5000-uk9-kickstart.5.0.2.N2.1.bi This next prompt trips up people new to Nexus. It's asking for the VRF you want to use. The switch will default to the VRF named default, which is incorrect. We need to Chapter 18: Cisco Nexus tell it that we're using the management VRF. Remember, the Nexus likes to keep control and data planes separate, and the mgmt0 interface is a part of the management VRF: Enter vrf (If no input, current vrf 'default' is considered) management From here on, it should seem pretty familiar: Enter hostname for the tftp server: 10.1.1.1 Trying to connect to tftp server Connection to Server Established. The switch will then transfer the file. The same process must be completed for the main image file as well. If you're using TFTP as I've done, expect it to take a long time. Of course, you can also use FTP or even SCP directly from Cisco's website if you have an Internet connection to the switch. Once the transfer is complete, the proper way to upgrade a Nexus is with the install all command. Not only can we install the kickstart and system images at once, but if the system conditions are right, we can do it without interrupting traffic flow. This will also update the BIOS and module images as needed. Let's walk through the process on a Nexus 5020. The first thing we should do is make sure that our configuration won't be compromised when we upgrade. This nifty command will examine your config and report if anything will break upon upgrade (or downgrade, as the case may be): NX-5K-1# sho incompatibility system 15000-uk9.5.0.2.N2.1.bin No incompatible configurations If you forget to do this, the system will do it for you during the install process and warn you with the following mess