08.02.2015 Views

Table of Contents

Table of Contents

Table of Contents

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

NX-5K-2(config-sync-sp)# sync-peers destination 10.0.0.1<br />

Those IP addresses correspond to the management interfaces on the Nexus 5000s.<br />

Now here it gets a little weird for me. For commands to sync, they cannot exist in the<br />

running config. If you want to edit an existing switch config, you can import the running<br />

config, or parts there<strong>of</strong>, into your switch pr<strong>of</strong>ile. I recommend only doing this for the<br />

interfaces or FEXs for which you will be syncing, because otherwise you’ll spend hours<br />

trying to figure out why it’s not working. There are many commands that are not supported<br />

within config-sync and, as <strong>of</strong> now, the list is not well documented. Keep it<br />

simple, and stick to port channels and FEXs.<br />

So I’ve decided that I’d like to sync port channel 10, which is already configured.<br />

Great—all I have to do is import it, and then I can use config-sync. The caveat here is<br />

that I cannot import a configuration after I’ve configured the config-sync peer. The<br />

good news is that I should only need to import once, since from that point on, I’ll have<br />

config-sync managing my relevant interfaces and FEXs, assuming I was smart enough<br />

to import everything I needed up front. I’m showing you this specifically because it’s<br />

wrong, and because it took me days <strong>of</strong> lab time and calls to Cisco TAC to figure it out.<br />

Let’s go ahead and import the configuration for port channel 10. Here, I’m importing<br />

on NX-5K-2, but I’ll need to do it on both switches anyway:<br />

NX-5K-2(config-sync-sp)# import interface po10<br />

NX-5K-2(config-sync-sp-import)#<br />

Seems simple enough. Anytime there are changes in the config-sync buffer, we should<br />

verify them. If the commands won’t verify, they won’t sync:<br />

NX-5K-1(config-sync-sp-import)# verify<br />

Failed: Verify Failed<br />

I hate when that happens. That’s not a very helpful message, either. How can we figure<br />

out what the problem is The first step is to see what’s in the buffer with the show<br />

switch-pr<strong>of</strong>ile pr<strong>of</strong>ile-name buffer command:<br />

NX-5K-1(config-sync-sp-import)# sho switch-pr<strong>of</strong>ile GAD buffer<br />

switch-pr<strong>of</strong>ile : GAD<br />

----------------------------------------------------------<br />

Seq-no Command<br />

----------------------------------------------------------<br />

1 interface port-channel10<br />

1.1 switchport mode trunk<br />

1.2 vpc 10<br />

1.3 switchport trunk allowed vlan 10, 20, 30, 40<br />

1.4 speed 1000<br />

That all looks pretty good, but there’s still no indication <strong>of</strong> why it’s failing. Here’s the<br />

output <strong>of</strong> the same command from NX-5K-1:<br />

NX-5K-1(config-sync-sp-import)# sho switch-pr<strong>of</strong>ile GAD buffer<br />

switch-pr<strong>of</strong>ile : GAD<br />

Nexus Design Features | 303

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!