[j-nsp] Upgrading from RE-S-2000-4096-S/SCB-MX960-S to RE-S-1800X4-32G-S/SCBE2-MX-S

[Sebastian Becker]

As already mentioned: SBE exchange requires a power down. But the REs can easily upgraded by replacing first the backup RE, install correct software there and sync config to it and then do a switch over.

Juniper does not support a longer period of mixed REs but the upgrading is supported. We have done that many times and it works quite well. Doing staging in a lab is from the logistic point for a bigger network not a good option.

One thing: We had issues if you boot up with one empty RE (no config and newer software). This might override the configured RE.

So maybe one approach will be:

1. Swap backup RE with the new one.
2. Upgrade new backup RE with software and config.
3. Power down the system
4. Replace all SBE with SCBE2 and insert only the new configured RE (was the new backup RE in 2.)
5. After boot insert second new RE and upgrade / configure it.

Done.

The good thing is that you have the old SBE and RE for any fallback almost untouched at the side.

— 
Sebastian Becker
sb at lab.dtag.de

> Am 17.01.2018 um 11:15 schrieb James Bensley <jwbensley at gmail.com>:
> 
> On 17 January 2018 at 09:32, Niall Donaghy <niall.donaghy at geant.org> wrote:
>> Hi Craig,
>> 
>> Indeed Misak's recommendation is the one I would follow.
>> 
>> We are in the process of upgrading SCBEs to SCBE2s and indeed you must power off for this.
>> 
>> As for the RE upgrades, JNPR states here https://www.juniper.net/documentation/en_US/release-independent/junos/topics/reference/specifications/routing-engine-m-mx-t-series-specifications-by-model.html that: "On routers that accept two Routing Engines, you cannot mix Routing Engine types except for a brief period (one minute or so) during an upgrade or downgrade to two Routing Engines of the same type." I suggest that if you try to sync in-chassis rather than use flash, it might work, but is technically unsupported.
>> 
>> Br,
>> Niall
>> 
>> Niall Donaghy
>> Senior Network Engineer
>> GÉANT
>> T: +44 (0)1223 371393
>> M: +44 (0) 7557770303
>> Skype: niall.donaghy-dante
>> PGP Key ID: 0x77680027
>> nic-hdl: NGD-RIPE
>> 
>> Networks • Services • People
>> Learn more at www.geant.org
>> GÉANT is the collective trading name of the GÉANT Association and GEANT Limited.
>> 
>> GÉANT Vereniging (Association) is registered in the Netherlands with the Chamber of Commerce in Amsterdam. Registration number: 40535155. Registered office: Hoekenrode 3, 1102BR Amsterdam, The Netherlands.
>> GEANT Limited  is registered in England & Wales. Registration number: 2806796. Registered office: City House, 126-130 Hills Road, Cambridge CB2 1PQ, UK.
>> 
>> 
>> 
>> -----Original Message-----
>> From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Misak Khachatryan
>> Sent: 16 January 2018 18:30
>> To: craig washington <craigwashington01 at hotmail.com>
>> Cc: juniper-nsp at puck.nether.net
>> Subject: Re: [j-nsp] Upgrading from RE-S-2000-4096-S/SCB-MX960-S to RE-S-1800X4-32G-S/SCBE2-MX-S
>> 
>> Hi,
>> 
>> As i remember, you can't mix REs and/or SCBs. Better to save your configuration to flash, replace all cards and power it up. It's relatively easy to predict port number changes from DPCE to MPC, so you can edit configuration accordingly before loading it to updated router.
>> 
>> Best regards,
>> Misak Khachatryan,
>> Network Administration and
>> Monitoring Department Manager,
>> 
>> GNC- ALFA CJSC
>> 1 Khaghaghutyan str., Abovyan, 2201 Armenia
>> Tel: +374 60 46 99 70 (9670),
>> Mob.: +374 55 19 98 40
>> URL:    www.rtarmenia.am
>> 
>> 
>> On Tue, Jan 16, 2018 at 5:52 PM, craig washington <craigwashington01 at hotmail.com> wrote:
>>> Hello smart people.
>>> 
>>> 
>>> We are in the process of upgrading from the aforementioned in the title.
>>> 
>>> My question is does anyone have a procedure they have used in the past for doing this or any type of gotchas.
>>> 
>>> We are also replacing the old DPC's for MPC's.
>>> 
>>> I know the port numbers will change and that the MPC's aren't compatible with SCB.
>>> 
>>> So I am looking for something like what's the best process to follow, for instance should I:
>>> 
>>> 
>>>  1.  Swap out RE-2000 for RE-1800 one at a time (leaving SCB in place) to get the configuration over and sync and then once that's up swap out the SCB for SCBE2 and also swap out the DPC's at the same time?
>>> 
>>> 
>>> Juniper documentation suggest powering off the entire router when going from SCB to SCBE2 so figured I would make sure the RE's are good and code is up to date before powering off and swapping out SCBE2 and DPCs for MPC's.
>>> 
>>> 
>>> Thanks again and all feedback is welcome.
>>> _______________________________________________
>>> 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
> 
> We are going through a similar process, upgrading to SCBE2 and RE-NGs.
> 
> Seeing as the chassis have to be powered down I think one of the two
> approaches is best;
> 
> - Use a lab chassis (or get a vendor loan) and insert all the same
> hardware you have in productions, load up the same config, then
> upgrade the Junos and the SCBs. You can then remove those REs which
> will have the correct Junos code and working config on them, and the
> SBEs, take them to the DC and the upgrade process on the live network
> is "only" a case of shutting down the chassis, swapping RE/SCB cards
> and booting up.
> 
> - Again, seeing as you are doing a power down, build the finally
> chassis / config / software in the lab and take a pre-built chassis to
> the DC and replace the chassis. If this is a P with only a few
> connections this is easy and clean. If it's a fully PE loaded with
> every port (pre)patched then this isn't viable and opt 1 is possibly
> better.
> 
> Cheers,
> James.
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp