g config parallelly (not a real word) is a result of me rolling back the config while in config mode. The system is warning me that I really shouldn't do that. I'm stubborn (read: stupid), SO I'm trudging on. Wait a minute, though-the hostname has changed. What else has changed? Annie (config)# sho vdc vdc id vdc name state Goober active 00:26:98:1b:f0:41 Goober? What happened to the Annie and Guinness VDCs? They were wiped out when I did the config rollback. If you're going to play with configuration rollback and you're going to restore a previous configuration, always make a new checkpoint before you do anything else! Nexus Design Features Holy panic attack-I need my VDCs back! Luckily, I made a checkpoint before I started all this. What was the name of that checkpoint again? NX-7K-2# rollback running-config checkpoint ? 100526-1 Checkpoint name Checkpoint name Clean Checkpoint name Restoring my configuration is as simple as rolling back to that checkpoint: Annie(config)# rollback running-config checkpoint 100526-1 Note: Applying config parallelly may fail Rollback verification Collecting Running-Config Generating Rollback Patch Executing Rollback Patch Generating Running-config for verification Generating Patch for verification NX-7K-2(config)# My hostname is back, but what about my VDCs? NX-7K-2# sho vdc vdc id vdc name state NX-7K-2 active 00:26:98:1b:f0:41 Annie active 00:26:98:1b:f0:42 Guinness active 00:26:98:1b:f0:43 All present and accounted for. Configuration rollback is a fabulous tool. I strongly recommend that you create a new checkpoint before making any major change. It might just save your job. Upgrading NX-OS You can upgrade a Nexus switch similarly to IOS, but there is a much better way. With NX-OS, the image files are very large. Version 4.2.1 for the 5000 was around 182 MB. Not only are the images large, but you must also install the proper kickstart image along with it. The kickstart images are usually around 20 MB. Here I'll walk through the steps of upgrading the code on a Nexus 5020 from 