c mode are saved within a switch profile. You must configure the same switch profile on both switches that will be synced. Here, I've created a switch profile with the clever name GAD: NX-5K-1(config-sync)# switch-profile GAD Switch-Profile started, Profile ID is 1 X-5K-1(config-sync-sp)# You can only have one profile, and it must match on the other switch in the sync pair. So let's configure it on the other switch: NX-5K-2# configure sync Enter configuration commands, one per line. End with CNTL/Z. NX-5K-2(config-sync): switch-profile GAD Switch-Profile started, Profile ID is 1 NX-5K-2(config-sync-sp)# We still haven't told each switch how to find its partner, SO let's do SO. First on NX-5K-1: NX-5K-1 (config-sync-sp)# sync-peers destination 10.0.0.2 And then on NX-5K-2: Chapter 18: Cisco Nexus NX-5K-2(config-sync-sp)# sync-peers destination 10.0.0.1 Those IP addresses correspond to the management interfaces on the Nexus 5000s. Now here it gets a little weird for me. For commands to sync, they cannot exist in the running config. If you want to edit an existing switch config, you can import the running config, or parts thereof, into your switch profile. I recommend only doing this for the interfaces or FEXs for which you will be syncing, because otherwise you'll spend hours trying to figure out why it's not working. There are many commands that are not sup- ported within config-sync and, as of now, the list is not well documented. Keep it simple, and stick to port channels and FEXs. So I've decided that I'd like to sync port channel 10, which is already configured. Great-all I have to do is import it, and then I can use config-sync. The caveat here is that I cannot import a configuration after I've configured the config-sync peer. The good news is that I should only need to import once, since from that point on, I'll have config-sync managing my relevant interfaces and FEXs, assuming I was smart enough to import everything I needed up front. I'm showing you this specifically because it's wrong, and because it too