config (that aren't actually there): NX-5K-1(config-sync-sp)# sho run int po 10 !Command: show running-config interface port-channel10 !Time: Mon Jan 17 23:05:25 2011 version 5.0(2)N2(1) interface port-channel10 description BladeServer switchport mode trunk vpc 10 switchport trunk allowed vlan 10,20,30,40 spanning-tree port type edge trunk speed 1000 And here we can see the lines back in the local switch's database: NX (config-sync-sp)# sho run switch-profile switch-profile GAD sync-peers destination 10.0.0.2 interface port-channel10 spanning-tree port type edge trunk There is one more thing to watch out for with config-sync, and that is the fact that once you've configured an interface or FEX using the feature, you may no longer configure it in config term mode: NX-5K-1# conf t Enter configuration commands, one per line. End with CNTL/Z. NX-5K-1 (config)# int po 10 NX-5K-1 (config-if)# no spanning-tree port type edge trunk Error: Command is not mutually exclusive Config-sync is a very useful tool. It is a bit cumbersome, though, especially when you're first getting used to it. I strongly recommend that you play with this in a lab setting first, or at least test it out on gear before it goes into production. Configuration Rollback One of the cool new features in Nexus is the ability to roll back configs with ease. As you probably know, IOS employs an additive CLI. That means commands are always added on top of what's there. There's no easy way to wipe out the entire config and load another without rebooting. This is especially a pain when you're in a lab Nexus Design Features environment, since the only way to clear the config is to use the write-erase command, reload, and then somehow enter the new configuration. This is time-consuming and clumsy, to use nice words. Rollback is supported on Nexus 5000s using NX-OS version 5.0(2)N1(1) and later. Nexus allows us to roll back the entire box-VDCs and all-to a previously saved point. I've saved some configuration checkpoints, but before we list them, let's create a n