cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1638
Views
5
Helpful
2
Replies

Can't ping vPC'd Nexus 3Ks

mt67
Level 1
Level 1

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

1 Accepted Solution

Accepted Solutions

mt67
Level 1
Level 1

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...

View solution in original post

2 Replies 2

Reza Sharifi
Hall of Fame
Hall of Fame

Can you post configs from both 3ks and the 6500?

 

HTH

mt67
Level 1
Level 1

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...