witch 2: NX-5K-2(config-sync)# switch-profile GAD Switch-Profile started, Profile ID is 1 NX-5K-2(config-sync-sp)# sync-peers destination 10.0.0.1 Nexus Design Features Now I can do what I came here to do in the first place. Remember the spanning-tree port type problem? I'll configure that, but this time I'll use config-sync. I'll need to be in config-sync mode, and within the switch profile: NX-5K-2 (config-sync)# switch-profile GAD Switch-Profile started, Profile ID is 1 Once there, I just need to enter the commands that I'd like to sync. Remember, the commands must be for a vPC-related interface or FEX that has been either imported or input directly into config-sync mode. I only enter this on one of the switches: NX-5K-1 (config-sync-sp)# int po 10 X-5K-1(config-sync-sp-if)# spanning-tree port type edge trunk Now I'll see if I can verify: NX-5K-1(config-sync-sp-if)# verify Failed: Session Database already locked, Verify/Commit in Progress. If you've been banging on this in a lab and have been dropping/adding the sync-peer like I have, you may see this message. You will also see this message if you telnet to the switch and try to verify or commit while someone else is verifying or committing. Wait a bit, make sure you're the only one making changes, and try again: IX-5K-1(config-sync-sp)# verify Verification Successful Now that we're all verified, let's commit the change. This will commit it locally, and will also commit the configuration to the remote switch. It can take a few seconds, SO don't worry if it seems hung for a bit: NX-5K-1(config-sync-sp)# commit Verification successful Proceeding to apply configuration. This might take a while depending on amount of configuration in buffer. Please avoid other configuration changes during this time. Commit Successful I made the change on NX-5K-1, SO let's take a look at the port channel 10 interface NX-5K-2 and see if my change has propagated. Hopefully, the other switch will have the spanning-tree port type edge trunk command: NX-5K-1(config-sync)# sho run int po