Yep, build 17 is working pretty good for me too across a couple sectors.
On 6/15/2016 10:10 PM, Sean Heskett wrote:
14.1.2(beta 17) is extremely stable. They should be releasing the
final 14.1.2 any day now.
-Sean
On Wednesday, June 15, 2016, David Milholen <[email protected]
<mailto:[email protected]>> wrote:
At least move to 13.4 it has been really stable for us but have
been doing beta on our 3.65 gear.
On 6/15/2016 11:27 AM, George Skorup wrote:
Mine was 13.2.1
On 6/15/2016 11:23 AM, David wrote:
Which Firmware was this?
On 06/15/2016 11:18 AM, TJ Burbank wrote:
I have had 3 radios do this exact same thing but could never
bring them back to life.
Working 1 days the next not registering. AP Eval showed
nothing, SA showed energy on AP frequency, factory defaults,
firmware upgrades, etc... Still nothing.
How long did you let SA run before switching it off?
-TJ
On Mon, Jun 6, 2016 at 5:44 PM, George Skorup
<[email protected]
<javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:
One of the guys brought me in a 5GHz 450 SM today. Said it
saw no APs in the eval list. Sure enough, power it up on my
desk and it can't see the AP at the top of our NOC SSV.
Factory default, still nothing. But the spectrum analyzer
shows that the AP's RF energy is there. After stopping the
SA and letting it scan, bam... there's the AP in the eval
list now. Coincidence?
The event log does show a couple 'XO trim at min diff'
messages. Maybe this thing stored a bad frequency offset
and the SA fixed it? Question is now, do I assume it's
fixed and try to redeploy it?
--
