On 14/Jan/16 02:07, Colton Conor wrote:
> Well it would be RE-S-2000-4096 running the JTAC Recommended Junos
> Software Version Junos 13.3R8 plus the standard (not enhanced SCBs).
>
> I know more memory and 64 bit is usually better, but how does this
> help in Junos? From past threads, we have c
Well it would be RE-S-2000-4096 running the JTAC Recommended Junos Software
Version Junos 13.3R8 plus the standard (not enhanced SCBs).
I know more memory and 64 bit is usually better, but how does this help in
Junos? From past threads, we have concluded that Junos is currently single
thread/core
Martin T writes:
>Junos has "banner" XML element under "rpc-reply" and "cli" hierarchy:
This is really only available between cli and mgd. It's internal
and we shouldn't display it at all during "display xml". There's
a PR to stop showing it.
Like Jonathan said, the $junos-context is a better s
Used RE-S-2000 w/SCBE and JunOS 14.2 with JAM for MPC3-NG Cards. No issues.
Mostly running 13.3R6 or R8 on most of our core which is dual RE-S-2000's on
MX480.
- CK.
On 14/01/2016, at 9:11 AM, Tom Storey wrote:
> On 13 January 2016 at 22:32, Mark Tinka wrote:
>> A more current RE means you
On 13 January 2016 at 22:32, Mark Tinka wrote:
> A more current RE means you can run more recent Junos releases. I
> haven't run the RE-S-2000 in a while, so not sure how well it's
> supported by current Junos releases (someone else who has the older RE's
> might want to chime in).
Guess it depen
On 13/Jan/16 20:05, Colton Conor wrote:
>
> Are there any feature limitations I should be aware of using a MX960 with
> the above configuration and older I beleive EOL'd DPC-R-4XGE-XFP
> linecards? For comparison's sake, I am upgrading from a MX80 using the 4
> 10G ports on the front of the MX8
Thanks for the overwhelming wealth of information.
So sounds like the ideal, supported setup would be a MX960 with 3 SBC, 2
RE-S-2000-4096, and redundant power supplies. For a recommended option, we
would have a third RE-S-2000-4096 as a spare (well really we should have a
spare for everything), a
Hi!
Dnia 13 stycznia 2016 18:08:36 CET, Niall Donaghy
>Finally about the REs, you can physically house a spare RE in the dual
>purpose SCB2 / MPC6 slot but I believe it lacks the additional
>backplane connections to enable the RE to work, hence it lies there
>dead.
My knowelage about MXes may be
On Wed, Jan 13, 2016 at 09:06:55AM -0800, joel jaeggli wrote:
> An mx960 has a full fabric with two SCBs.
That depends on the specific MPCs used in the chassis. Some do get
full performance only with all 3 SCBs.
> it is n+1 redundant with 3. e.g. at that point you can swap one
> without cutting t
Sounds correct, only 2 routing engines at a time.
> On Jan 13, 2016, at 11:59 AM, Colton Conor wrote:
>
> Just to confirm though, its the extra RE that is different and not
> supported in this config right? The MX960 can use 3 SCB's at once, but only
> 2 REs? Or do I have the wrong too?
>
>
>
That's correct. On MX960 you can have 3 SCBs running 2+1 redundancy or 3+0
performance mode.
With 2 SCBs you run 2+0, ie: without redundancy. In the case of 1 failing, you
are 1+0 and on reduced capacity, AFAIK I don't think it's terminal -- just very
very suboptimal. :)
With SCBE fabric, here
On 1/13/16 8:59 AM, Colton Conor wrote:
> Just to confirm though, its the extra RE that is different and not
> supported in this config right? The MX960 can use 3 SCB's at once, but only
> 2 REs? Or do I have the wrong too?
An mx960 has a full fabric with two SCBs. it is n+1 redundant with 3.
e.g.
Just to confirm though, its the extra RE that is different and not
supported in this config right? The MX960 can use 3 SCB's at once, but only
2 REs? Or do I have the wrong too?
On Wed, Jan 13, 2016 at 8:16 AM, Mark Tinka wrote:
>
>
> On 13/Jan/16 12:42, Jérôme Nicolle wrote:
>
> > Looks like
Hi Youssef,
here the ctrl/fabric are transported using a vlan over a trunk, not direct
p2p link, I guess it's different.
They run VSTP and not sure what on Extreme network,...
I suspect SRX is not happy to see different packet than HA packet on that
link ;-)
cheers
James
2016-01-13 17:25 GMT+01
While it was not really advisable to run fabric link over a stack of
switches, (and not to have cluster stretched over datacenter) I have
setup many srx cluster in a similar way.
Two points to check :
- obviously a separate single vlan by fabric link (untag on the srx
side, even if it may work
You can get the same information from the node passed in
the document. The node is also stored in
the $junos-context variable.
For example:
root@r0-re0:~ # cat /var/tmp/is-master.slax
version 1.1;
ns junos = "http://xml.juniper.net/junos/*/junos";;
ns xnm = "http://xml.juniper.net/xnm/1.1/x
Dear James,
We have a pretty similar setup with an SRX5600 cluster in two distinct DCs
seperated by dark fibers (18 and 28 kms) that we light ourselves.
Control and fabric link are directly connected and transported via PtP MPLS
services on our core backbone. It's been working great so far.
When
Hi experts,
a customer of mine has implemented an SRX cluster HE(1400) over a L2 (vlan)
infrastructure and is having sometime problems on the dual FAB links, which
trigger basically a split brain.
The cluster is geographically stretched and in one site the customer has
Cisco Nexus 5k and on the
On 13/Jan/16 12:42, Jérôme Nicolle wrote:
> Looks like the broker had a few spare SCB and REs and no functionnal
> chassis to slap them in, so he invented a bundle and didn't fully test it.
If the price is right, I'd take the extra RE and SCB as backup, in case
not including them does not yield
Hi,
Junos has "banner" XML element under "rpc-reply" and "cli" hierarchy:
Is it somehow possible to read the value of "banner" element with SLAX
script? For example I have a router with dual routing-engines, i.e
"banner" element has either value of "{master}" or "{backup}":
{master
Hi,
Le 13/01/2016 05:21, Colton Conor a écrit :
> Then how do they have 3 RE's listed and house in the picture? Is the 3 RE
> in the 3 SBC just in there, but would not be powered on or usable?
Looks like the broker had a few spare SCB and REs and no functionnal
chassis to slap them in, so he inve
21 matches
Mail list logo
