The Arista side must be misconfigured. It's behaving as a regular LAG not an MLAG.
Arista MLAG is like Nexus vPC, where there are two control planes & management planes that sync over a control plane peer-link. To allow for this they have to spoof a shared LACP system-ID.
The log on the Catalyst side means that the Aristas have 2 LACP IDs, which means its MLAG is broken for some reason.
Brian McGahan, 4 x CCIE #8593 (R&S/SP/SC/DC), CCDE #2013::13
bmcgahan_at_INE.com<mailto:bmcgahan_at_INE.com>
Internetwork Expert, Inc.
http://www.INE.com<http://www.ine.com/>
On Mar 5, 2014, at 5:44 PM, "Tony Singh" <mothafungla_at_gmail.com<mailto:mothafungla_at_gmail.com>> wrote:
to add
When regular port-channel config is added on the 6500 and you have different ports added on both chassis the VSS will pick this up as a MEC (multi ether-channel chassis)
It's seems it's seeing multiple macs or system-id's via the MLAG ports on the Arista
Depends on how Arista encode the frames, I don't think MLAG or MEC are RFC compliant even if LACP is
Where you could get Arista nodes communicating using MLAG
-- BR Tony Sent from my iPad On 5 Mar 2014, at 21:32, Cristian Matei <cmatei_at_ine.com<mailto:cmatei_at_ine.com>> wrote: I say it should work, is MLAG correctly configured on Arista; if so, all ports in the ether channel towards VSS should use the same system-id? What does B3show ether channel summaryB2 show on VSS? Regards, Cristian. On 05/03/14 23:15, "Tony Singh" <mothafungla_at_gmail.com<mailto:mothafungla_at_gmail.com>> wrote: In the system-id negotiated in your LACP frames your multi chassis lag has a different base mac-address per unit Hence no LACP Had the same issue between a Cisco ASA pair going to a stackable switch, it can't be done from what I've seen Maybe someone will override me -- BR Tony Sent from my iPad On 5 Mar 2014, at 12:53, Taufik Kurniawan <ktaufik_at_gmail.com<mailto:ktaufik_at_gmail.com>> wrote: Dear All, Does anyone here has an experience to connect an arista pair (MLAG) with a pair of 6500 (VSS). We are trying this, but a pair of 6500 (VSS) complaining below messages : Feb 27 20:05:13.351: %LACP-SW1-4-MULTIPLE_NEIGHBORS: Multiple neighbors detected on Te1/1/1: new neighbor(sys-mac-id: 001c.7318.b7e0, port: 0x29), old neighbor(sys-mac-id: 021c.7318.b7e0, port: 0x29) Feb 27 20:05:14.211: %LACP-SW1-4-MULTIPLE_NEIGHBORS: Multiple neighbors detected on Te2/1/8: new neighbor(sys-mac-id: 001c.7318.ba32, port: 0x802A), old neighbor(sys-mac-id: 021c.7318.b7e0, port: 0x802A) Blogs and organic groups at http://www.ccie.netReceived on Wed Mar 05 2014 - 18:36:44 ART
This archive was generated by hypermail 2.2.0 : Thu Apr 03 2014 - 17:12:31 ART