We are running the latest software on ours and stopped using them as ntp servers and everything is copacetic now. No more lock-ups :)
-sean On Friday, April 3, 2015, Josh Baird <joshba...@gmail.com> wrote: > Even if devices are not using the CTM as a NTP server, they tend to lock > up.. in my experience anyways. We have several CTM's (not CTM2) in the > field that have experienced this. > > On Fri, Apr 3, 2015 at 7:06 PM, Sean Heskett <af...@zirkel.us > <javascript:_e(%7B%7D,'cvml','af...@zirkel.us');>> wrote: > >> If devices are set up to use the ctm2 as their ntp server then the ctm2 >> interface tends to lock up. >> >> Make sure nothing upset to use the ctm2 as its ntp server. >> >> -sean >> >> On Friday, April 3, 2015, Dan Petermann <d...@wyoming.com >> <javascript:_e(%7B%7D,'cvml','d...@wyoming.com');>> wrote: >> >>> We had lost management access to the CTM2. Rebooted it and all is good >>> now. >>> >>> No idea of how that could happen. >>> >>> >>> On Apr 3, 2015, at 2:35 PM, David Sovereen <david.sover...@mercury.net> >>> wrote: >>> >>> > This seems to ring a bell as an old firmware issue… perhaps circa >>> Version 9 or 10, maybe 11? >>> > >>> > Dave >>> > >>> >> On Apr 3, 2015, at 1:42 PM, Dan Petermann <d...@wyoming.com> wrote: >>> >> >>> >> Does anybody know what would cause every 6th ping to be in the >>> 400-600mS range? >>> >> >>> >> This is on 5.7 PMP100 gear. >>> > >>> > >>> >>> >
