[j-nsp] Anybody use dual RE in srx3k? SCM only?

[Nicholas Oas]

I manage two SRX-3k chassis clusters with CRMs. The main reason we chose
CRMs in our deployment is to have a secondary control link (EM1) to avoid
split-brain scenario should we lose the link for EM0. We did the same thing
with the data plane (FAB0, FAB1) which of course does not require any
special hardware.

While the CRM is *not *a fully fledged RE, you can console into the RJ45
serial for RE1 and talk to it with a limited set of commands. JTAC directed
me to do this.

In that TAC case, EM1 was refusing to link up. The root cause was not
determined, however our use of non-Juniper optics had something to do with
it. Switching them out with the genuine OEM part (e.g. SRX-SFP-1GE-LX ,
SRX-SFP-1GE-SX) resolved our issue. So my advice when selecting parts for
the EM0/EM1 ports is to use the real deal.

Sidebar, of particular annoyance is the fact that at least as of 12.1,
there is absolutely no diagnostic information whatsoever for optics in
ports EM0/EM1. Normally you can 'show interface diagnostics optics', but
not for these two ports. They also do not show up in 'show chassis
hardware'. I sent our SE an enhancement request to get this added, but if
anyone else finds this annoying I encourage them to do the same. :)

That said we are happy with both clusters. Desirable things like ISSU and
session failover work as intended.




On Tue, Dec 17, 2013 at 4:33 PM, Bill Pfeifer <billp at juniper.net> wrote:

> SCM will also keep a chassis alive in case of RE failure (assuming it's in
> a cluster and there's an active RE on the other chassis). I don't believe
> that a second RE is supported in 3k, but that's primarily because the SCM
> does everything that a backup RE would be able to do for less $$$ (so even
> if a second RE were supported, there would be no benefit to paying the
> extra cost of using an RE rather than SCM).
> -Bill
>
> On 12/16/13 6:12 PM, "Santiago Martinez" <santiago.martinez.uk at gmail.com>
> wrote:
>
> Hi, the SCM will only allow you to use a secondary control link on the
> srx3600. Juniper sales ing said that they are not planning to add support
> for a second RE on the srx3000 family. if you don't have the SCM the
> second control port will be/stay disable.
> Hope it helps
> Santiago.
>
> > On 16 Dec 2013, at 21:26, "OBrien, Will" <ObrienH at missouri.edu> wrote:
> >
> > Second REs don't really do anything on SRX... yet.
> >
> > On the 5800s, I had to add them in order to bring up a secondary control
> >link. The only thing they do is init the control plane on the chassis for
> >that link to come up.
> > I believe it's an artifact from stealing the MX chassis.  I don't think
> >it does anything for you on the 3600, since that's a different chassis
> >architecture altogether.
> >
> > Will
> >
> >
> >> On Dec 16, 2013, at 3:07 PM, Morgan McLean wrote:
> >>
> >> Hi all,
> >>
> >> Looking into installing the SCM module into a couple of SRX3600's I
> >>have in
> >> production. Notice the diagram from juniper says slot RE1 for SCM. Do
> >>they
> >> support running another RE? Just curious if anybody does this, if its
> >>worth
> >> it or if its even possible.
> >>
> >> --
> >> Thanks,
> >> Morgan
> >> _______________________________________________
> >> juniper-nsp mailing list juniper-nsp at puck.nether.net
> >> https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
> >
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
>
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>