new AP is on order, if I recall I think that this unit showing problems was
purchased on EBAY so I am wondering if there was a reason this unit was on
Ebay in the first place.

On Mon, Dec 19, 2016 at 10:59 AM, That One Guy /sarcasm <
[email protected]> wrote:

> wrap the whole radio and antenna in aluminum foil to keep the heat in.
>
> seriously though, do you give subscribers any access to the units? If so,
> I wonder if having them run a bunch of link speedtests could generate
> enough processing to warm the unit
>
> On Mon, Dec 19, 2016 at 9:54 AM, Kurt Fankhauser <[email protected]
> > wrote:
>
>> Seems that the colder it is the more frequent the flapping is. I doubt
>> its the RJ45 ends since I tried a different cable run on the tower and
>> still showing the same issue.
>>
>> On Mon, Dec 19, 2016 at 10:42 AM, George Skorup <[email protected]>
>> wrote:
>>
>>> I would try new RJ45s on both ends. If that's not it, then swap it and
>>> RMA if it's still under warranty.
>>>
>>>
>>> On 12/19/2016 9:35 AM, Kurt Fankhauser wrote:
>>>
>>>> I have a 3.65ghz 450 AP that was running flawless for over 6 months
>>>> until we got our first really cold spell last week, temps dropped to near 0
>>>> degrees a couple nights back to back and when I woke up one morning the AP
>>>> was dropping offline. Logged into the Mikrotik 2011 and it showed Ethernet
>>>> was flapping. (was originally going through a Sync Injector). I had an old
>>>> FSK AP going through the same sync injector and wasn't showing any
>>>> problems. I tried switching the ports on the sync injector, changed ports
>>>> on RB2011, eliminated sync injector and used a standard Canopy SM power
>>>> supply. Finally I even switched the known good Ethernet cable from the FSK
>>>> AP to the 450 and the port is still flapping. Won't lock to 10-baseT
>>>> either. I am thinking at this point that I am going to have to replace the
>>>> AP.
>>>>
>>>
>>>
>>
>
>
> --
> If you only see yourself as part of the team but you don't see your team
> as part of yourself you have already failed as part of the team.
>

Reply via email to