[j-nsp] Juniper MX Upgrade / Configuration question

Julien Goodwin jgoodwin at studio442.com.au
Thu Oct 16 07:48:05 EDT 2014

On 16/10/14 21:07, Saku Ytti wrote:
> On (2014-10-16 09:52 +0200), Sebastian Wiesinger wrote:
> Hi Sebastian,
>>> I was wondering if anyone knows where a MX router stores the boot
>>> configuration its going to use after you load a new version of code
>>> on the router.
>> a software upgrade does not change the configuration. It will use
>> /config/juniper.conf.gz as always. I never saw anything else during SW
>> upgrades.
> If I understood Matt correctly his problem is, he has already done 'request
> system software add', which stores the config somewhere to be used after
> upgrade and further commits will not be included in that.
> He'd like to make changes to the configs before reloading the boxes and ensure
> the config changes are included.

In this case you can simply follow the useful advice given by the
command to cancel the scheduled upgrade and reapply it once the config
changes have been made.

> I've been quite annoyed by this, since it means you have to be awake in
> maintenance window 30min-1h longer than you should, because you can't pre-load
> the new software then in maintenace window just boot.

I'm obviously missing something here, "request system software add"
takes less than five minutes on anything I've ever used (from SRX100
through the bigger T & MX kit).

Copying the image to the box may take more, but if that's true and you
don't pre-stage images you deserve what comes to you.

It's the reboot into the new image that's horribly slow.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20141016/66e3fdd5/attachment-0001.sig>

More information about the juniper-nsp mailing list