NX-5K-1(config-sync)# no switch-profile GAD local-config Verification successful Proceeding to delete switch-profile. This might take a while depending on amount of configuration under a switch-profile. Nexus Design Features Please avoid other configuration changes during this time. Delete Successful Uh oh. Let's take a look at the damage, shall we? First let's look at the port channel 10 interface that we synchronized earlier: NX-5K-1(config-sync)# sho run int po10 interface port-channel10 description BladeServer switchport mode trunk vpc 10 switchport trunk allowed vlan 10,20,30,40 speed 1000 Notice anything missing? That's right-the spanning- tree port type edge trunk com- mand is gone. Since it was only deleted locally, that means the vPC is probably broken now. Sure enough: NX-5K-1 1 (config-sync)# sho vpc Legend: (*) - local vPC is down, forwarding via vPC peer-link vPC domain id Peer status : peer adjacency formed ok vPC keep-alive status peer is alive Configuration consistency status: success Per-vlan consistency status : success Type-2 consistency status : success vPC role : primary Number of vPCs configured Peer Gateway : Disabled Dual-active excluded VLANs Graceful Consistency Check : Enabled vPC Peer-link status Status Active vlans vPC status Status Consistency Reason Active vlans failed vPC type-1 configuration incompatible - STP interface port type inconsistent Yeah, that's bad, but let's take this opportunity to examine one of the benefits of config- sync. Because we had synced the config to the other switch, and because all of the lines executed through config-sync are stored in a database on the other switch, we can get them all back with lease. All we have to do is configure the switch profile, configure the destination peer, and wait: Chapter 18: Cisco Nexus NX-5K-1# config sync 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 After a few seconds, it all comes back. Here we can see the lines in the running 