[j-nsp] RE-S-X6-64G & ISSU?

[Luis Balbinot]

Depending on your arrangement with Juniper the price for a backup RE
is negligible compared to the rest of the chassis (we got them for
free several times). There's really no reason to leave a blank RE slot
considering you have redundant SCBs.

Luis

On Tue, Nov 22, 2016 at 2:19 PM, Michael Hare <michael.hare at wisc.edu> wrote:
> Agree with Mark, if you count loss of redundancy as a high priority issue find the funds to purchase dual RE even on dual chassis designs.
>
> We made this engineering mistake; initially saved money with a single RE design with dual PE MX104s.  We've had some NAND corruption RE failures that are undetectable until the fan gets hit.  The MX104 recovery process requires physical access (would love to be proven wrong).  Some of these chassis are distant and/or not convenient to access physically.  We are walking back and installing dual RE everywhere.
>
> -Michael
>
>> -----Original Message-----
>> From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of
>> Mark Tinka
>> Sent: Tuesday, November 22, 2016 12:00 AM
>> To: Aaron <aaron1 at gvtc.com>; 'Sebastian Becker' <sb at lab.dtag.de>
>> Cc: juniper-nsp at puck.nether.net; 'Clarke Morledge' <chmorl at wm.edu>
>> Subject: Re: [j-nsp] RE-S-X6-64G & ISSU?
>>
>>
>>
>> On 14/Nov/16 17:04, Aaron wrote:
>>
>> > Have y'all ever thought through the benefits of having dual RE in one
>> > chassis compared to 2 chassis with 1 RE in each ?
>> >
>> > Like if I'm thinking about getting a MX480 with dual RE... what about
>> > instead, getting dual MX240 with 1 RE in each ?  ...and possibly Virtual
>> > Chassis'ing the dual MX240's as one virtual router
>> >
>> > Chassis diversity seems nice...then whatever would connect in that location,
>> > can be redundantly connected to both MX240's.
>>
>> Firstly, unless you're tight for space, I'd not spend money on an MX240.
>> MX480 should be the bare minimum. Line cards are hungry for space.
>>
>> We used to run single control planes in core switches, and have 2 core
>> switches per PoP. This was because those switches only handled Ethernet
>> traffic, no IP/MPLS.
>>
>> I'd be hesitant to run any kind of routing device on a single control
>> plane unless it was designed as such. Then again, control planes are not
>> that much more expensive in current-generation core switches, so we are
>> now kitting them fully out from that perspective as well.
>>
>> Mark.
>> _______________________________________________
>> 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