Re: [j-nsp] Automation of EX code upgrade

2013-09-20 Thread Mick Burns
Thanks to all who answered, your contribution is welcome. This is exactly
the kind of hints that I was looking for.

Cheers,
Mick


On Fri, Sep 20, 2013 at 7:12 AM, Frank Sweetser  wrote:

>
> Jeremy Schulman has put together some ansible playbooks that will let you
> do exactly that, as well as various config pushing bits:
>
> https://github.com/**jeremyschulman/ansible-junos-**demo
>
> Frank Sweetser fs at wpi.edu|  For every problem, there is a solution
> that
> Manager of Network Operations   |  is simple, elegant, and wrong.
> Worcester Polytechnic Institute |   - HL Mencken
>
> On 9/19/2013 6:04 PM, Mick Burns 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@puck.nether.net
>> https://puck.nether.net/**mailman/listinfo/juniper-nsp
>>
>>  __**_
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/**mailman/listinfo/juniper-nsp
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Automation of EX code upgrade

2013-09-20 Thread Frank Sweetser


Jeremy Schulman has put together some ansible playbooks that will let you do 
exactly that, as well as various config pushing bits:


https://github.com/jeremyschulman/ansible-junos-demo

Frank Sweetser fs at wpi.edu|  For every problem, there is a solution that
Manager of Network Operations   |  is simple, elegant, and wrong.
Worcester Polytechnic Institute |   - HL Mencken

On 9/19/2013 6:04 PM, Mick Burns 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@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Automation of EX code upgrade

2013-09-19 Thread Georgios Vlachos

Junos Space (VM version) is pretty inexpensive as well for required
functionality using the built in application "Network Management Platform". 

Thanks,
George

-Original Message-
From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of
Ben Dale
Sent: Friday, September 20, 2013 1:33 AM
To: Mick Burns
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] Automation of EX code upgrade

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-ser
ies-software-automatic-download-upgrading.html

>=12.2 - Zero Touch Provisioning

http://www.juniper.net/techpubs/en_US/junos12.2/topics/concept/software-imag
e-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  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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
> 


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


[j-nsp] Automation of EX code upgrade

2013-09-19 Thread Mick Burns
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@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Automation of EX code upgrade

2013-09-19 Thread 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  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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
> 


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Automation of EX code upgrade

2013-09-19 Thread Morgan McLean
Unix expect script? SSH keys can make scp'ing files and logging in to run
commands pretty painless.

Good luck!

Morgan


On Thu, Sep 19, 2013 at 3:04 PM, Mick Burns  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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>



-- 
Thanks,
Morgan
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp