Try a different power brick.
On Jun 20, 2016 9:47 PM, "Chadwick Wachs" <[email protected]> wrote:

> One end is brick (the end that is having issues) and the other end is off
> a Netonix.
>
> On Mon, Jun 20, 2016 at 9:37 PM, Chris Ruschmann <[email protected]>
> wrote:
>
>> How are you powering them? Power brick or switch?
>> On Jun 20, 2016 7:35 PM, "Faisal Imtiaz" <[email protected]>
>> wrote:
>>
>> Are there the only two radios you have ? maybe there is a physical
>> hardware issue with one of the radios..
>>
>> we have seen something similar with on another link we were working on
>> for another WISP.  No conclusions yet, but one radio is definitely doing
>> hokey stuff...They have spares, will be trying another pair (the radios
>> linked up on the bench, but would not link nor go thru the alignment
>> process on a 400m link).
>>
>> Regards.
>>
>> Faisal Imtiaz
>> Snappy Internet & Telecom
>> 7266 SW 48 Street
>> Miami, FL 33155
>> Tel: 305 663 5518 x 232
>>
>> Help-desk: (305)663-5518 Option 2 or Email: [email protected]
>>
>> ------------------------------
>>
>> *From: *"Chadwick Wachs" <[email protected]>
>> *To: *"WISPA General List" <[email protected]>
>> *Sent: *Monday, June 20, 2016 12:47:43 PM
>> *Subject: *Re: [WISPA] Any IgniteNet MetroLinq customers out there
>>
>> Update to all on this.  We are running MCS1, the latest public firmware
>> and contacted Ignite support. They are responsive.  We did get the 60 GHz
>> radios to link up once - for about 30 minutes. Then, the 60 GHz radio on
>> the client end died. Can't open the 60 GHz aiming tool and the dashboard
>> acts like the radio is off.
>> We have been through a number of reboots to get the 60 GHz radio to wake
>> back up. No dice. Ignite is aware of the issue, acknowledges I am not the
>> only one who has seen this but so far no solutions.  Last night, the 5 GHz
>> link between these two radios died at 3am (not a production link).  We lost
>> all wireless and ethernet access to the client radio until a reboot.
>>
>> After rebooting, the 5 GHz would not pass any traffic until the 60 GHz
>> radios were turned off in the interface on both ends.  Both ends are on big
>> UPSs so I don't think power is the issue, I think there is buggy firmware.
>> While I have *some* time to deal with testing firmware and trouble
>> shooting, I don't have unlimited time to do this.
>>
>> It is back running on 5 GHz. It is aimed well - we did get a solid 60 GHz
>> signal but we never got the 60's to link back up after one mysteriously
>> stopped.
>>
>>
>>
>> On Sun, Jun 19, 2016 at 12:37 AM, Rob Genovesi <[email protected]>
>> wrote:
>>
>>> Aiming takes patience, the scopes aren't perfect but a huge help.  We
>>> found that turning off auto MCS and using fixed lower rate helped a
>>> lot.  Make sure you have the newest firmware, I believe there are more
>>> updates coming out soon as well.  IgniteNet support was responsive and
>>> very helpful when we had questions.
>>>
>>>
>>> Rob Genovesi • Coastside.Net • Owner
>>> 650-712-5900 • 525B Obispo Rd • Half Moon Bay CA
>>>
>>> On Wed, Jun 15, 2016 at 4:55 PM, Chadwick Wachs <[email protected]>
>>> wrote:
>>> > I have been trying for a couple days to get a new PTP60-35 60 GHz link
>>> up
>>> > and running with no luck. Looking for some help / suggestions from
>>> anyone
>>> > who has been successful getting links up. The 5 GHz link is working
>>> but 60
>>> > never trains up. I bought the spotting scopes and each end is dead
>>> center.
>>> > Good old fashioned up/down/left/right aiming methods do not seem to
>>> work
>>> > either and IgniteNet is lacking in the support department.
>>> >
>>> > Anyone want to contact me off list if you have any suggestions on what
>>> > worked for you?
>>> >
>>> > Thanks,
>>> > Chad
>>> >
>>> > _______________________________________________
>>> > Wireless mailing list
>>> > [email protected]
>>> > http://lists.wispa.org/mailman/listinfo/wireless
>>> >
>>> _______________________________________________
>>> Wireless mailing list
>>> [email protected]
>>> http://lists.wispa.org/mailman/listinfo/wireless
>>>
>>
>>
>>
>> --
>>
>> ____________________________
>>
>> AU Wireless (Golden Wireless)
>>
>> www.AUwireless.net <http://www.auwireless.net/>
>>
>> Facebook <https://www.facebook.com/AU-Wireless-1630781100539377/> |
>> @auwirelessnet <https://twitter.com/AUWirelessNet>
>>
>> _______________________________________________
>> Wireless mailing list
>> [email protected]
>> http://lists.wispa.org/mailman/listinfo/wireless
>>
>>
>> _______________________________________________
>> Wireless mailing list
>> [email protected]
>> http://lists.wispa.org/mailman/listinfo/wireless
>>
>>
>> _______________________________________________
>> Wireless mailing list
>> [email protected]
>> http://lists.wispa.org/mailman/listinfo/wireless
>>
>>
>
>
> --
>
> ____________________________
>
> AU Wireless (Golden Wireless)
>
> www.AUwireless.net <http://www.auwireless.net/>
>
> *Facebook <https://www.facebook.com/AU-Wireless-1630781100539377/>* |
> @auwirelessnet <https://twitter.com/AUWirelessNet>
>
> _______________________________________________
> Wireless mailing list
> [email protected]
> http://lists.wispa.org/mailman/listinfo/wireless
>
>
_______________________________________________
Wireless mailing list
[email protected]
http://lists.wispa.org/mailman/listinfo/wireless

Reply via email to