Dear All,
Thanks for the responses.
1. Arista mlag configuration is OK, as w tested on 3750 and also on stacked 3750
It started giving error when connected to 6500 VSS
2. to even simplify the things, I tried to use two links from a pair
of arista to one node of VSS only.
Kindly check below ....xxx arista , yyy cisco
xxx-swi20#sh lacp sys-id detailed
System Identifier used by LACP:
System priority: 32768
Switch MAC Address: 00:1c:73:18:ba:32
802.11.43 representation: 8000,00-1c-73-18-ba-32
MLAG System-identifier: 02:1c:73:18:b7:e0
802.11.43 representation: 8000,02-1c-73-18-b7-e0
xxx-swi20#sh lldp nei
Last table change time : 0:02:13 ago
Number of table inserts : 446
Number of table deletes : 429
Number of table drops : 0
Number of table age-outs : 0
Port Neighbor Device ID Neighbor Port ID TTL
Et3 xxx-swi03 Ethernet50 120
Et4 xxx-swi04 Ethernet50 120
Et5 xxx-swi05 Ethernet50 120
Et6 xxx-swi06 Ethernet50 120
Et7 xxx-swi07 Ethernet20 120
Et8 xxx-swi08 Ethernet20 120
Et13 xxx-swi13 Ethernet20 120
Et14 xxx-swi14 Ethernet20 120
Et15 xxx-swi15 Ethernet50 120
Et16 xxx-swi16 Ethernet50 120
Et17 xxx-swi17 Ethernet50 120
Et18 xxx-swi18 Ethernet50 120
Et42 yyy-rou01 Te2/1/8 120
Et43 testing Te2/1/1 120
Et44 yyy-rou01 Te1/1/7 120
Et47 xxx-swi01 Ethernet47 120
Et48 xxx-swi01 Ethernet48 120
xxx-swi20#sh lacp neighbor brief
State: A = Active, P = Passive; S=ShortTimeout, L=LongTimeout;
G = Aggregable, I = Individual; s+=InSync, s-=OutOfSync;
C = Collecting, X = state machine expired,
D = Distributing, d = default neighbor state
| Partner
Port Status | Sys-id Port# State OperKey PortPri
------ ----------|------------------------- ------- --------- --------- -------
Port Channel Port-Channel1*:
Et42 Bundled | 8000,02-00-00-00-00-c8 8457 ALGs+CD 0x0001 32768
Et44 Bundled | 8000,02-00-00-00-00-c8 4360 ALGs+CD 0x0001 32768
Port Channel Port-Channel13*:
Et3 Bundled | 8000,02-1c-73-2f-4c-6c 32818 ALGs+CD 0x0003 32768
Et4 Bundled | 8000,02-1c-73-2f-4c-6c 50 ALGs+CD 0x0003 32768
Port Channel Port-Channel15*:
Et5 Bundled | 8000,02-1c-73-1c-27-b6 32818 ALGs+CD 0x0005 32768
Et6 Bundled | 8000,02-1c-73-1c-27-b6 50 ALGs+CD 0x0005 32768
Port Channel Port-Channel17*:
Et7 Bundled | 8000,02-1c-73-18-62-cc 32788 ALGs+CD 0x0007 32768
Et8 Bundled | 8000,02-1c-73-18-62-cc 20 ALGs+CD 0x0007 32768
Port Channel Port-Channel20:
Et47 Bundled | 8000,00-1c-73-18-b7-e0 47 ALGs+CD 0x0014 32768
Et48 Bundled | 8000,00-1c-73-18-b7-e0 48 ALGs+CD 0x0014 32768
Port Channel Port-Channel43*:
Et43 Bundled | 8000,a4-4c-11-53-0d-00 566 ALGs+CD 0x002b 32768
Port Channel Port-Channel113*:
Et13 Bundled | 8000,02-1c-73-17-4d-64 20 ALGs+CD 0x000d 32768
Et14 Bundled | 8000,02-1c-73-17-4d-64 32788 ALGs+CD 0x000d 32768
Port Channel Port-Channel115*:
Et15 Bundled | 8000,02-1c-73-1c-31-c4 50 ALGs+CD 0x000f 32768
Et16 Bundled | 8000,02-1c-73-1c-31-c4 32818 ALGs+CD 0x000f 32768
Port Channel Port-Channel117*:
Et17 Bundled | 8000,02-1c-73-2f-4c-2a 50 ALGs+CD 0x0011 32768
Et18 Bundled | 8000,02-1c-73-2f-4c-2a 32818 ALGs+CD 0x0011 32768
* - Only local interfaces for MLAGs are displayed. Connect to the peer to
see the state for peer interfaces.
xxx-swi20#sh lacp sys-id
LACP System-identifier: 8000,00-1c-73-18-ba-32
MLAG System-identifier: 8000,02-1c-73-18-b7-e0
xxx-swi20#sh run int po1
interface Port-Channel1
description connect to yyy-rou01_01 and yyy-rou01_02
mlag 1
yyy-rou01#sh lacp sys-id
32768,0200.0000.00c8
Mar 6 15:32:47.596: %LACP-SW1-4-MULTIPLE_NEIGHBORS: Multiple
neighbors detected on Te2/1/8: new neighbor(sys-mac-id:
001c.7318.ba32, port: 0x802A), old neighbo
r(sys-mac-id: 021c.7318.b7e0, port: 0x802A)
Mar 6 15:32:47.600: %LACP-SW1-4-MULTIPLE_NEIGHBORS: Multiple
neighbors detected on Te1/1/7: new neighbor(sys-mac-id:
001c.7318.ba32, port: 0x802C), old neighbo
r(sys-mac-id: 021c.7318.b7e0, port: 0x802C)
yyy-rou01#sh run int t1/1/7
Building configuration...
Current configuration : 173 bytes
!
interface TenGigabitEthernet1/1/7
description connect to xxx-swi01
switchport
switchport mode access
mtu 9216
channel-protocol lacp
channel-group 1 mode active
end
yyy-rou01#sh run int t2/1/8
Building configuration...
Current configuration : 173 bytes
!
interface TenGigabitEthernet2/1/8
description connect to xxx-swi20
switchport
switchport mode access
mtu 9216
channel-protocol lacp
channel-group 1 mode active
end
On 06/03/2014, Tony Singh <mothafungla_at_gmail.com> wrote:
>
> Agree that's what I've been suggesting too in below, not much on google
> about whether the Arista will MLAG with a Cisco, have you seen it working
> Brian?
>
> Here's a snippet from Ethan Banks post on packet pushers
>
> Multichassis etherchannel. Spreading an LACP link across two switches does
> allow for forwarding on all interswitch links, but it's not a topological
> "any-any". In addition, vendors' MEC solutions are not interoperable. You
> can't take an Arista switch, mate it to a Cisco switch, and present a
> unified MEC uplink to an adjacent node. Examples of MEC include Cisco's
> Nexus virtual port channel (vPC) and Arista's multichassis link aggregation
> (MLAG).
> Not an RFC but if you've got this working then all good
> --
> BR
>
> Tony
>
> Sent from my iPad
>
>> On 6 Mar 2014, at 00:36, Brian McGahan <bmcgahan_at_ine.com> wrote:
>>
>> 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
>>
>> Internetwork Expert, Inc.
>> http://www.INE.com
>>
>>> On Mar 5, 2014, at 5:44 PM, "Tony Singh" <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> 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> 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> 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.net
>>>>>>
>>>>>> _______________________________________________________________________
>>>>>> Subscription information may be found at:
>>>>>> http://www.groupstudy.com/list/CCIELab.html
>>>>>
>>>>>
>>>>> Blogs and organic groups at http://www.ccie.net
>>>>>
>>>>> _______________________________________________________________________
>>>>> Subscription information may be found at:
>>>>> http://www.groupstudy.com/list/CCIELab.html
>>>
>>>
>>> Blogs and organic groups at http://www.ccie.net
>>>
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Thu Mar 06 2014 - 15:57:13 ART
This archive was generated by hypermail 2.2.0 : Thu Apr 03 2014 - 17:12:31 ART