1. I did a direct USB recovery format boot from 17.4r2-S11, and afterwards
recovered configs from FTP. The reason for this was because 15.1x54D51 screws
up your /tmp directory and you wont have enough free space no matter what you
try. - at least, this was the case for my installs
2. One
I'll preface this by saying I don't have anything constructive to add...
On Fri, 28 Aug 2020, Nathan Ward wrote:
I’ve tried JTAC on this, twice. First on 16.1, and again now on 19.4. Both
times JTAC have either not understood and stalled for months and refused to
escalate to someone who does
Thanks Kody, 2 questions sir... I recently began moving towards that same
version (17.4R2-S11) as I was hitting PR1419761 high cpu.
1 - did you upgrade straight from 15.1x54D51 to 17.4R2-S11 , or did you take
an intermediate step? Asking since JTAC recently told me that this was too
far of a
Recently upgraded all my edges from 15.1x54D51 to 17.4R2-S11.
The upgrade was forced by strange transit ARP packet digestion in vpls
instances...
Thoroughly tested in my lab prior to deployment.
It is finally nice to gain a dedicated oob mgmt routing-instance How long
have we been
Amen to that. I recall a few years back, going with 15.1X54-D51.7 for the
ACX5048 and having complete outage on irb's in L3VPN's with no dhcp relay
(ip helper) capability. ...and being baffled as I recall that the D51
version was on the JTAC recommended list. (D61 fixed it) So yeah, I agree
5 matches
Mail list logo