Hi Santi, upgrade vom 14.2R6.5 to R7.5, also on two different RE types (1800x4, 2000).
Best regards, Theo Von: santiago martinez <santiago.martinez...@gmail.com> Datum: Montag, 7. November 2016 um 15:02 An: Theo Voss <m...@theo-voss.de>, Martin T <m4rtn...@gmail.com> Cc: "juniper-nsp@puck.nether.net" <juniper-nsp@puck.nether.net> Betreff: Re: [j-nsp] MX 14.2R7 / PR1177571 Hi Theo and Martin, Thats weird, was a direct upgrade or you had an interim release? We hit the PR several times but always cleared without any issues. The only diff i can see is that we used 14.2r6s2.2. Cheers. Santi El lun., 7 nov. 2016 a las 13:22, Theo Voss (<m...@theo-voss.de<mailto:m...@theo-voss.de>>) escribió: Hi Martin, same issue here, and I know a third provider with the same problem. We've stopped upgrading until 14.2R8 will be released. Best regards, Theo -----Ursprüngliche Nachricht----- Von: Martin T <m4rtn...@gmail.com<mailto:m4rtn...@gmail.com>> Datum: Montag, 7. November 2016 um 14:19 An: Theo Voss <m...@theo-voss.de<mailto:m...@theo-voss.de>> Cc: "juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net>" <juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net>> Betreff: Re: [j-nsp] MX 14.2R7 / PR1177571 Theo, did you manage to find a solution for this? We were able to replicate this behavior in lab and even system reboot did not clear the alarm message. thanks, Martin On Wed, Oct 26, 2016 at 4:30 PM, Olivier Benghozi <olivier.bengh...@wifirst.fr<mailto:olivier.bengh...@wifirst.fr>> wrote: > Here the alarm (detected on the re0 in older version) disappeared as soon as > re1 (in newer version) took mastership in the chassis (non-GRES switchover, > as specified in JunOS updating documents). > >> Le 26 oct. 2016 à 15:19, Theo Voss >> <m...@theo-voss.de<mailto:m...@theo-voss.de>> a écrit : >> >> Hi Santiago, >> >> did the alarm disappeared after the 2nd RE was detected with the same >> software or after a complete reboot? >> >> Best regards, >> Theo >> >> Von: santiago martinez >> <santiago.martinez...@gmail.com<mailto:santiago.martinez...@gmail.com>> >> Datum: Mittwoch, 26. Oktober 2016 um 15:15 >> An: Theo Voss <m...@theo-voss.de<mailto:m...@theo-voss.de>> >> Cc: "juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net>" >> <juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net>>, Olivier >> Benghozi <olivier.bengh...@wifirst.fr<mailto:olivier.bengh...@wifirst.fr>> >> Betreff: Re: [j-nsp] MX 14.2R7 / PR1177571 >> >> Hi there, yes we did hit the same PR. >> >> the alarm was raised during the upgrade and completely disappear after both >> RE. were running the same code version (14.2R6). >> >> Regards >> >> santiago >> >> >> On 26 Oct 2016 12:00, "Theo Voss" >> <m...@theo-voss.de<mailto:m...@theo-voss.de> >> <mailto:m...@theo-voss.de<mailto:m...@theo-voss.de>>> wrote: >> Hi Olivier, >> >> thanks for your reply. Yes, /var is correctly mounted. >> >> Best regards, >> Theo >> >> -----Ursprüngliche Nachricht----- >> Von: juniper-nsp >> <juniper-nsp-boun...@puck.nether.net<mailto:juniper-nsp-boun...@puck.nether.net> >> >> <mailto:juniper-nsp-boun...@puck.nether.net<mailto:juniper-nsp-boun...@puck.nether.net>>> >> im Auftrag von Olivier Benghozi >> <olivier.bengh...@wifirst.fr<mailto:olivier.bengh...@wifirst.fr> >> <mailto:olivier.bengh...@wifirst.fr<mailto:olivier.bengh...@wifirst.fr>>> >> Datum: Mittwoch, 26. Oktober 2016 um 10:59 >> An: "juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net> >> <mailto:juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net>>" >> <juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net> >> <mailto:juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net>>> >> Betreff: Re: [j-nsp] MX 14.2R7 / PR1177571 >> >> Yes but with 14.2R6 on re0 and 15.1R4 on re1 (so, during the update). >> >> Did you check that /var was properly mounted on re1? :) >> >> > Le 26 oct. 2016 à 10:53, Theo Voss >> > <m...@theo-voss.de<mailto:m...@theo-voss.de> >> > <mailto:m...@theo-voss.de<mailto:m...@theo-voss.de>>> a écrit : >> > >> > we've upgraded two of our MXs (MX960, 1800x4-32) to 14.2R7 and ran into >> > PR1177571 which should already be fixed in R7. >> > >> > router> show version invoke-on all-routing-engines | match boot >> > JUNOS Base OS boot [14.2R7.5] >> > JUNOS Base OS boot [14.2R7.5] >> > >> > router> show system alarms >> > 1 alarms currently active >> > Alarm time Class Description >> > 2016-10-25 23:36:53 UTC Major Host 1 failed to mount /var off HDD, >> > emergency /var created >> > >> > Workaround according to Juniper: Upgrade backup RE to the same release >> > with master RE. << see "show version". >> > Resolved In: 13.3R9-S4 13.3R10 14.1R8 >> 14.2R7 << 15.1R4 15.1R5 15.1F5-S3 >> > 15.1F6-S1 16.1X70-D10 16.1R2 << see "show version". >> > >> > Has anybody encountered the same problem? >> >> _______________________________________________ >> juniper-nsp mailing list >> juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net> >> <mailto:juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net>> >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> <https://puck.nether.net/mailman/listinfo/juniper-nsp> >> >> _______________________________________________ >> juniper-nsp mailing list >> juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net> >> <mailto:juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net>> >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> <https://puck.nether.net/mailman/listinfo/juniper-nsp> > _______________________________________________ > juniper-nsp mailing list > juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net> > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net> https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
