Right. Growing pains I guess. Is anything every bug free? I think the more features you put into something the more possibility there is for bugs.
Actually I feel this is why when I get comfortable with a version of code and the platform I tend to camp out there for quite some time and have to be really convinced to load any new software on it. I remember hitting a IPv4 forwarding bug in IOS XR 4.something on my ASR9k around 10:00 a.m. Some years as back.... Dang I actually remember the time of day... Traumatized I guess , LOL , I remember my boss and everyone standing over me in my office while we worked frantically with the XR TAC about loading a fix Aaron On Jul 11, 2018, at 8:14 AM, <[email protected]> <[email protected]> wrote: >> Of Jackson, William >> Sent: Wednesday, July 11, 2018 1:28 PM >> To: 'Colton Conor'; Nick Ryce >> Cc: Juniper List >> Subject: Re: [j-nsp] QFX5100 vs ACX5048 >> >>> [email protected]> >>> wrote: >>> >>> Gustavo, >>> >>> We you say " Another problem was upgrading to the lastest Junos JTAC >>> recommended that made the ACX5048 unusable... ( Junos was unable >>> to find >>> the physical ports..) We had to downgrade to get it back working >>> again.." >> >> How the hell does that type of problem even get past QA? >> >> I had the same issue with a qfx5100, upgraded to 17.x version and when >> booted didn’t detect the ports. After a 30 minute wait we downgraded. > We had the same exact fun with the good old ME3600, makes you wonder whether > vendors have time to do any testing when in pressure to release a new code. > > adam > > netconsultings.com > ::carrier-class solutions for the telecommunications industry:: > > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
