[181038] in North American Network Operators' Group
Re: Question about EX - SRX redundancy
daemon@ATHENA.MIT.EDU (Anurag Bhatia)
Sun Jun 14 16:38:36 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <33C0B3C9-AB2D-4AB1-AA94-010E97FA432F@gmail.com>
From: Anurag Bhatia <me@anuragbhatia.com>
Date: Mon, 15 Jun 2015 02:07:53 +0530
To: Rob Greenwood <bilco105@gmail.com>
Cc: NANOG Mailing List <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Hi Rob
I couldn't get the ports working on SRX with low priority on the cluster.
They always showed as down by protocol and never picked traffic. Can you
put some light on the reason for that?
Thanks
On Sun, Jun 14, 2015 at 3:42 AM, Rob Greenwood <bilco105@gmail.com> wrote:
> > 3. In case of SRX only one device runs at a time and ports of other S=
RX
> > (slave) do not access traffic at all as long as it see the master is
> up via
> > heartbeat.
> Not entirely accurate. The control plane (routing engine) is only active
> on one SRX at a time, however, the data plane is active on both. This mea=
ns
> in your configuration, both ae1 and ae2 on the EX will be passing traffic
> to both SRXs.
>
> It=E2=80=99s also worth noting you can create multiple redundancy groups =
and split
> them between both SRXs. If a device fails, all redundancy groups on the
> failed device will be migrated to the remaining one.
>
> -Rob
>
--=20
Anurag Bhatia
anuragbhatia.com
Linkedin <http://in.linkedin.com/in/anuragbhatia21> | Twitter
<https://twitter.com/anurag_bhatia>
Skype: anuragbhatia.com
PGP Key Fingerprint: 3115 677D 2E94 B696 651B 870C C06D D524 245E 58E2
