02-13-2018 06:34 AM - edited 03-08-2019 01:49 PM
Hello and thanks for any help with this!
I have 2 Nexus 3Ks (N3K01/N3K02) that I have just figured out how to vPC together (vPC keepalive using 2x10gb per switch LACP port-channeled/vPC peer link using 2x40gb per switch LACP port-channeled). All type-1 and 2 compatibility issues have been cleared up; show vpc looks good. I configured an LACP port-channeled trunk link (2x1gb) to a 6509. All ports are participating, link is up. The vPC peer link and the trunk link are currently allowing all vlans.
For remote management purposes, I have IP'd each N3K's int vlan1 with 192.168.10.1/24 and 192.168.10.2/24 (not really, just illustration here...) The 6509's vlan1 IP is 192.168.10.3/24 and there is a PC connected to the 6509 whose IP is 192.168.10.4/24.
It seems like I'm missing something very simple here, but I can't even ping either N3K switch from the PC (let alone remotely manage them...)
Thanks again for any assistance with this!
MT
Solved! Go to Solution.
02-13-2018 11:23 AM
I figured it out. STP was blocking on the 6509 side. I had 'spanning-tree portfast network' set on the trunk link which was causing bridge assurance inconsistencies. Removing that command from the trunk port channel fixed the problem.
I really need to get up to speed on STP...
02-13-2018 09:22 AM
Can you post configs from both 3ks and the 6500?
HTH
02-13-2018 11:23 AM
I figured it out. STP was blocking on the 6509 side. I had 'spanning-tree portfast network' set on the trunk link which was causing bridge assurance inconsistencies. Removing that command from the trunk port channel fixed the problem.
I really need to get up to speed on STP...
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide