Status: Verify Failure Error(s): Following commands failed mutual-exclusion checks: interface port-channel10 switchport mode trunk interface port-channel10 vpc 10 interface port-channel10 switchport trunk allowed vlan 10, 20, 30, 40 Chapter 18: Cisco Nexus Here it says that it verified locally, but failed remotely. Let's cut to the chase-this simple configuration won't verify, because it's been imported and we have a peer configured. When working with config-sync, if you want to import existing config- uration from the running config, you must disable the sync-peer. If you do not, the config will never verify, and you will not be able to commit it. I'll remove the sync-peers command: (config-sync-sp-import)# no sync-peers dest 10.0.0.2 And watch the magic happen: NX-5K-1(config-sync-sp-import)# verify Verification Successful I have decided not to comment on this issue at this time, since I have nothing nice to say and my mother warned me to keep my mouth shut in such instances. There are two verification checks that can fail. A mutual-exclusion (mutex) verification checks to make sure that the configuration you've entered in sync mode does not exist in the running config. Both switches are checked unless the peer is down or is not configured, in which case the mutex is done locally. Merge checks are done with the switch profile of the other switch to ensure that there are no conflicts. If either check results in a failure, the problem must be fixed manually. Once we've got our interface configuration verified, we can commit it to the switch profile: NX-5K-1(config-sync-sp-import)# commit Verification successful After I jump through similar hoops on MX-5K-2, I've got the switches almost ready for syncing. Remember, I need to reestablish those sync-peer destination commands before I can sync between switches. I'll go ahead and do that on both switches. First, switch 1: NX-5K-1(config-sync)# switch-profile GAD Switch-Profile started, Profile ID is 1 NX-5K-1(config-sync-sp)# sync-peers destination 10.0.0.2 And then s