Switching

Hi,

Does EX2200 and EX4300 support MultiChassis Link Aggregation?

I want to make MC-LAG between EX2200 VC and EX4200 VC.

The physical connection will be like this:

port 1(EX2200 VC member 0) ---- port1 (EX4300 VC member 0)

port 2(EX2200 VC member 1) ---- port2 (EX4300 VC member 1)

Thank you.

Jerry Fan

Hello

Just ex9200 supports  MC-LAG(Junos13.2R3). You see the supported platforms at the following link.

http://pathfinder.juniper.net/feature-explorer/feature-info.html?fKey=4070&fn=Multichassis+link+aggregation+(MC-LAG)

Many thanks.

What you're describing is technically regular link aggregation, not multi-chassis link aggregation.

MC-LAG is a LAG between a given switch (or cluster) and multiple other separate (i.e. un-clustered) switch chassis. Bear in mind that switches in a VC collectively behave as a single chassis, so building a LAG involving ports on separate physical switches in the same VC is done exactly the same way as building a regular LAG (add your aggregate interface, add the physical interfaces to the aggregate interface, configure LACP etc).

So yes, you can easily build a LAG between an EX2200 VC and an EX4300 VC, even split across physical switches. Just think of each VC as one big switch.

Old thread, but since I got here by googling, I figured I'd update this question.

Spud is correct, you can do ordinary LAG between the two, no need for MC-LAG (and those switches don't support it). New EX switches do support MC-LAG:

EX4300 Junos OS 13.2X51-D20
EX4600 Junos OS 13.2X51-D25
EX9200 Junos OS 12.3R2

I might suggest that outside of EX9200, which no longer provides VC support, that MC-LAG deployment with any other EX products is limited at best, and maybe no one is doing this.  Everyone would be much safer (via number of deployments) using standard LAG with EX VC instead.

Just word to the wise.