I'm gonna go ahead and say nope.
SRX supports reth with active/passive nodes.
It doesn't support a lag that uses both nodes active/active as part of the same
ae.
You can build a reth with multiple ports that uses LACP to build a lag on each
node however.
I recommend not using AE at all on SRX. It will bring you pain. Just build them
as reth. You can configure LACP on the reth to bundle the links.
On Jan 19, 2014, at 10:22 PM, Samol <molas...@gmail.com>
wrote:
> Dear list,
>
> i'm trying to configure MC-LAG on clustering SRX and got below
> message. it does say we need the member links to be on the same node.
> Is there anything that can be used to accomplish this so that
> redundancy is in place.
>
>
> [edit interfaces ge-9/0/5 gigether-options]
> '802.3ad'
> In Clustering mode, child links ge-9/0/5, ge-0/0/5 of bundle ae1
> must be from same chassis
> error: configuration check-out failed
>
>
> Below is the configuration:
>
> [edit interfaces ge-0/0/5 gigether-options]
> + 802.3ad ae1;
> [edit interfaces ge-9/0/5 gigether-options]
> + 802.3ad ae1;
> [edit interfaces]
> + ae1 {
> + aggregated-ether-options {
> + lacp {
> + passive;
> + }
> + }
> + }
>
>
> Regards,
> --
> Samol Khoeurn
> (855) 077 55 64 02 / (855) 067 41 88 66
> Network Engineer
> Cisco: CCNA/CCNP SP/CCIP/
> Juniper: JNCIA/JNCIS-ENT,SP,SEC/JNCIP-ENT
> www.linkedin.com/in/samolkhoeurn
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
