[j-nsp] Automation of EX code upgrade

[Ben Dale]

If you're talking green fields (out-of-the-box) then there are a couple of ways depending on the current Junos release the switch is running:

<12.2 - Automatic Software Download

http://www.juniper.net/techpubs/en_US/junos/topics/task/configuration/ex-series-software-automatic-download-upgrading.html

>=12.2 - Zero Touch Provisioning

http://www.juniper.net/techpubs/en_US/junos12.2/topics/concept/software-image-and-configuration-automatic-provisioning-understanding.html

Try to stagger upgrades if you can, or learn the effects of having a hundred switches hitting a TFTP server for a ~110MB image file.  Neither of these methods will display the success of the upgrades though.

If your switches are already deployed, then a better way to do it is with Junos Space.  

The nice thing about the Space method is that you can upgrade smaller groups of switches at a time, pre-stage the images up to each switch and schedule the entire process.  Each upgrade is given a Job ID and that Job ID will return success or failure depending on the outcome, even in the pre-staging if you don't have room on your flash for the image..

This functionality is built into the base Space platform too, which you can download and install with a 60(?)-day trial license.

Cheers,

Ben

On 20/09/2013, at 8:04 AM, Mick Burns <bmx1955 at gmail.com> wrote:

> Hey all,
> 
> I am looking for ideas/previous experience in the best way to automate the
> upgrade of multiple (let's say about a hundred units) EX switches in large
> datacenters.  Let's assume here they are a mix of 3200 and 4200 and all of
> them runs the same JunOS release.  Any failure must be quickly identified
> for a manual upgrade.
> 
> Any help or advice is much appreciated.
> Mick B.
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>