Hi Baldur,
You should not give up and just report the bug.
JTAC may ask you to disable feature that is causing an impact, but in the
meantime they will work on resolving it.
Mind that it might take some time to replicate the problem, prepare the fix
and implement it in the next official software
Hi,
File a JTAC problem report, either yourself via a Juniper Partner (where
you should have support for your devices).
Rgds.
Ola Thoresen
On 15.06.2020 08:15, Baldur Norddahl wrote:
Hello
What am I supposed to do with glaring bugs? Are Juniper interested in
knowing those or don't they
On 14/Jun/20 19:16, nikosi...@gmail.com wrote:
> It is true that the official path will tell you that you should follow from
> 15 to 16 then 17 then 18 but I did around 30+ upgrades from 16 to 18 without
> any problems.
> >From 10 to 15 I guess you should go to 14 first but from 16 you can safe
Needless to mention here that if you do an upgrade directly to 18.4 ignoring
Juniper recommendations as someone has suggested if something goes wrong you
are on your own.
So I would never suggest this for a massive deployment.
-Original Message-
From: juniper-nsp On Behalf Of Mark
Tinka
--- Begin Message ---
> On Jun 15, 2020, at 2:15 AM, Baldur Norddahl wrote:
>
>
> What am I supposed to do with glaring bugs? Are Juniper interested in
> knowing those or don't they care?
Treat the following as "I do not speak for official Juniper support policy".
It is to your benefit to
--- Begin Message ---
For 100% sure you should open a JTAC Case, like P3, as you have a current
workaround. JTAC should then reproduce your issue, at which time they will
create a PR for Engg to work on. PR will be scheduled to be fixed in some
future release. JTAC should be able to provide t
--- Begin Message ---
I believe Juniper has at least slightly modified their view on upgrades. The
old "no more than 2 release jumps" was based upon when EEOL type releases
existed; these do not really exist anymore.
AFAIK, the major issue with BIG SW jumps is with the config. New SW may have
On 15/Jun/20 16:20, Richard McGovern via juniper-nsp wrote:
> Better approach to whole subject is to not fall so far behind on Code
> upgrades. I know, easier said then done. I'd say more than 2 or 3 behind
> current is a risk, and I am all for "if it's not broken, why change". So
> today'
8 matches
Mail list logo
