Scott, > -----Original Message----- > Sent: Friday, April 30, 2010 6:36 PM > To: [email protected] > Subject: [c-nsp] nexus 5xx vpc peer keepalives > > Tony, > > Read this as well ( it talks about NOT using the mgmt0 for peer keep alives > ) - we are trying this too > > http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/layer2/Cisco_ > Nexus_5000_Series_NX-OS__chapter8.html > > After figure 6, step 3 there is this text ; > Note > VLAN 900 must not be trunked across the vPC peer-link because it carries the > vPC > peer-keepalive messages. There must be an alternative path between > switches NX-5000-1 and > NX-5000-2 for the vPC peer-keepalive messages. > > The problem we are encountering is that if we drop the peer vlan from > the 5k to 5k link then we get weird errors as well. >
I have mine configured on the management VRF and haven't run into any issues, I believe that is the recommended configuration. Check out the design guides as well, if you're aren't using mgmt0, Cisco suggests using an SVI and a separate port. Are you using a vPC to handle the peer-keepalive traffic? I would imagine that's where the issue is stemming from if you are. This is the document I was looking for on the original thread, but applies to your scenario as well. I thought I had remembered it saying that back to back is okay for testing, but should not be used for production. Look for vPC config best practices: http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/C07-572829-01_Design_N5K_N2K_vPC_DG.pdf HTH, -ryan _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
