“ I understand, and it makes sense, in a way. But wasting a port to achieve this seem like a strange strategy. Must be another way”     The strategy is to connect orphan devices to a partner switch which does have a VPC link back to both partner swtches. MLAG and VLT, though conceptually similar, and existing on two switch platforms owned by the same company, are running different OSes and don’t work the same way. As the white paper I referenced to you originally pointed out (page 23), there are plans to address the “single-home / orphan device connected directly to a primary or secondary peer switch” scenario, by using a secondary, redundant, port-channel between the peer switches to pass traffic for just those single-homed/orphan devices. One critical aspect of this planned implementation is that the VLANs used by single-homed/orphan devices cannot also be passed on the peer-link port-channel (because of the obvious loop that would occur).   --------- Did not work either. It does not ping Po23 is a device on port 1/0/23 on SW2 ME_Core_Switch2 is the Primary peer. The described workaround functions only for devices that are physically connected to the secondary peer. This would let an orphan/single-home device on the secondary peer communicate with either:            A device that is connected to both peers with a vpc port-channel (i.e. a partner switch or partner host); OR            A device connected to that partner switch; OR           A single-home/orphan device connected to the same (i.e. secondary peer) A single-home/orphan device physically connected to the primary peer will never be able to communicate properly. Po46 is my computer on port 1/0/46 on SW1 ME_Core_Switch1(config)#do show vpc bri VPC admin status............................... Enabled Keep-alive admin status........................ Enabled VPC operational status......................... Enabled Self role...................................... Secondary Peer role...................................... Primary Peer detection admin status.................... Peer detected, VPC Operational Peer-Link details   VPC id# 23 ----------- Interface...................................... Po23 Configured VLANs............................... 20 VPC interface state............................ Active Local Members Status ----------------- ------ Gi1/0/23 DOWN << THIS IS WRONG Peer Members Status ---------------- ------ VPC id# 46 ----------- Interface...................................... Po46 Configured VLANs............................... 20 VPC interface state............................ Active Local Members Status ----------------- ------ Gi1/0/46 Up << THIS IS CORRECT Peer Members Status ---------------------------------------------------------------------------------------------------------------- ME_Core_Switch2(config-if-Po46)#do show vpc bri VPC admin status............................... Enabled Keep-alive admin status........................ Enabled VPC operational status......................... Enabled Self role...................................... Primary Peer role...................................... Secondary Peer detection admin status.................... Peer detected, VPC Operational Peer-Link details ----------------- Interface...................................... Po1 Peer-link admin status......................... Enabled Peer-link StP admin status..................... Disabled Configured VLANs............................... 1,10,20,30,40,60,100,170,192 Egress tagged VLANs............................ 10,20,30,40,60,100,170,192 VPC Details ----------- Number of VPCs configured...................... 2 Number of VPCs operational..................... 2 VPC id# 23 ----------- Interface...................................... Po23 Configured VLANs............................... 20 VPC interface state............................ Active Local Members Status ----------------- ------ Gi1/0/23 Up << THIS IS WRONG Peer Members Status ---------------- ------ Gi1/0/23 DOWN VPC id# 46 ----------- Interface...................................... Po46 Configured VLANs............................... 20 VPC interface state............................ Active Local Members Status ----------------- ------ Gi1/0/46 DOWN << THIS IS CORRECT Peer Members Status
Hi there, I'm a little new to the MLAG of the N3000, but not the VLT of the Force10, but somehow, something is not behaving the same way, or I am missing something. I have 2 switchs, connected together by a Port-channel in trunk mode and MLAG Eventhough the MLAG is up and running, and the Port-Channel linking both peers is in trunk mode for all VLANs, I cannot connect to a device on the same vlan that is connected to the other switch. But If i connect a PC to a partner switch, I can connect to any device connected to either one or the other peer switch.  Any ideas why the peer link is behaving that way?  Thanks for your help!
MLAG (VPC) N3000 connectivity issue