On 9/2/21 14:56, Jerry Jones wrote:
I view ISSU as a script to simplify upgrades - not provide for hitless.
Terrible namig on Junipers part. You can perform manually with less
downtime if any.
This is what we do, because you would be scheduling an outage window anyway.
Works, and is
On 9/1/21 18:44, Mike via juniper-nsp wrote:
Hello,
I did an issu upgrade on an MX240 with dual routing engines, going
from 15.1R6 to 17.4R2, and I had reviewed the fine manuals
particularly concerning advance steps to ensure nonstop routing and so
forth. But during the upgrade (near
> Hello,
>
> I did an issu upgrade on an MX240 with dual routing engines, going
> from 15.1R6 to 17.4R2, and I had reviewed the fine manuals particularly
> concerning advance steps to ensure nonstop routing and so forth. But
> during the upgrade (near the very end), the router did
On Wed, 1 Sept 2021 at 20:35, Chuck Anderson via juniper-nsp
wrote:
> Eventually during the ISSU process, the line card software needs to be
> upgraded. During that part, each line card goes offline one at a
> time. If you have multiple line cards, design your network such that
> redundant
On Wed, Sep 01, 2021 at 09:44:08AM -0700, Mike via juniper-nsp wrote:
> "Unified ISSU is supported with Junos OS Release 17.4R1 for MX Series
> routers with MPC-3D-16XGE-SFPP"
>
> my expectations were that the card would stay online and there
> would be little to no operational impact, but
Hello,
I did an issu upgrade on an MX240 with dual routing engines, going
from 15.1R6 to 17.4R2, and I had reviewed the fine manuals particularly
concerning advance steps to ensure nonstop routing and so forth. But
during the upgrade (near the very end), the router did offline my MPC 3D
Richard,
We are running into similar issues with NSR. Are you running with GRES
enabled or have you removed that as well ?
Jasper
On Thu, May 23, 2013 at 12:44 AM, Richard A Steenbergen
r...@e-gerbil.netwrote:
On Tue, May 21, 2013 at 09:01:57PM -0400, Clarke Morledge wrote:
I was curious
-gerbil.net
To: Clarke Morledge chm...@wm.edu
Cc: juniper-nsp@puck.nether.net
Sent: Wednesday, May 22, 2013 5:44:03 PM
Subject: Re: [j-nsp] ISSU timeouts on MX upgrades due to large routing tables?
On Tue, May 21, 2013 at 09:01:57PM -0400, Clarke Morledge wrote:
I was curious to know if anyone
On 05/23/2013 09:25 AM, Mike Azevedo wrote:
I have an MX960, full routes, performed issu. Did not have a timeout
problem.
However, like Ras eluded to, other issues...Once the backup
routing-engine upgrades and takes primary RE position, the used-to-be
primary upgrades itself. You would
On (2013-05-21 21:01 -0400), Clarke Morledge wrote:
I was curious to know if anyone has run into any issues with large
routing tables on an MX causing ISSU upgrades to fail?
We banned ISSU from our network due to poor hit/miss ratio, not uncommonly
something strange would happen after ISSU.
Hello Clarke,
You can use a Linux box with an hexabgp to easely inject as many routes
you want in your lab routers.
Rgds,
Christian
Le 22/05/2013 03:01, Clarke Morledge a écrit :
I was curious to know if anyone has run into any issues with large
routing tables on an MX causing ISSU upgrades
On Wednesday, May 22, 2013 08:38:40 AM Saku Ytti wrote:
We banned ISSU from our network due to poor hit/miss
ratio, not uncommonly something strange would happen
after ISSU.
Like firewall filter was programmed wrong, routes were
blackholing.
But as far as I understand, ISSU on routers
On Tue, May 21, 2013 at 09:01:57PM -0400, Clarke Morledge wrote:
I was curious to know if anyone has run into any issues with large
routing tables on an MX causing ISSU upgrades to fail?
On several occasions, I have been able to successfully do an
In-Software-Service-Upgrade (ISSU) in a
I was curious to know if anyone has run into any issues with large routing
tables on an MX causing ISSU upgrades to fail?
On several occasions, I have been able to successfully do an
In-Software-Service-Upgrade (ISSU) in a lab environment but then it fails
to work in production.
I find it
hi,
how to do iSSU in junos? Can anybody provide me the steps.
--
Thanks with regards
Shekar.B
--
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
On Mon, Mar 29, 2010 at 06:00:35PM +0530, chandrasekaran iyer wrote:
hi,
how to do iSSU in junos? Can anybody provide me the steps.
A unified in-service software upgrade (unified ISSU) enables you to upgrade
between two different JUNOS software releases with no disruption on the control
Hi there,
i just tried ISSU (9.5R3 to 9.5R4) on a MX240 and it FAILED .. but it seems
that it just failed because after rebooting the (upgraded) Backup RE, the NSR
for BGP wasn't syncing fast enough and then the whole ISSU was aborted.
Log shows:
Mar 10 15:25:49 chassisd[1240]:
:26 AM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] ISSU Timeouts too small?
Hi there,
i just tried ISSU (9.5R3 to 9.5R4) on a MX240 and it FAILED .. but it
seems that it just failed because after rebooting the (upgraded) Backup
RE, the NSR for BGP wasn't syncing fast enough
No BFD...
-Originalnachricht-
Von: Stefan Fouant
Gesendet: Mi 10.03.2010 21:21
An: 'Joerg Staedele';juniper-nsp@puck.nether.net
Betreff: RE: [j-nsp] ISSU Timeouts too small?
Are you using BFD by any chance?
Stefan Fouant, CISSP, JNCIE-M/T
www.shortestpathfirst.net
GPG Key ID
: Wednesday, March 10, 2010 9:26 AM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] ISSU Timeouts too small?
Hi there,
i just tried ISSU (9.5R3 to 9.5R4) on a MX240 and it FAILED .. but it
seems that it just failed because after rebooting the (upgraded) Backup
RE, the NSR for BGP wasn't syncing
Fouant; juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] ISSU Timeouts too small?
Prior to ISSU, I don't suppose you noted the uptime of the
replicated BGP sessions on your backup RE? We're about to do a major
code upgrade to fix numerous things, one of which involves the
premature closing
21 matches
Mail list logo
