[atlas] Reconnecting probe 3508 - troubleshooting

On 23.08.16 10:52 , Philip Homburg wrote:
> On 2016/08/22 22:14 , Michael-John Turner wrote:
>> The reason why the probe was offline originally was that it stopped
>> accepting DHCPOFFERs for some reason, with the result that it would
>> continually send DHCPDISCOVERs every few seconds but never ACK an OFFER and
>> never connect properly to the network. That seemed to be fixed when I
>> powered it on again yesterday but now I see the problem is occurring again
>> (it started again as soon as the initial lease it received yesterday
>> expired):
>>
>> ...
>> Aug 22 21:10:18 dreamland dhcpd: DHCPOFFER on 192.168.1.247 to 00:80:a3:91:38:ac via br0
>> Aug 22 21:10:21 dreamland dhcpd: DHCPDISCOVER from 00:80:a3:91:38:ac via br0
>> Aug 22 21:10:21 dreamland dhcpd: DHCPOFFER on 192.168.1.247 to 00:80:a3:91:38:ac via br0
>> ...
>>
>> This poor probe seems cursed :( Is there any way to reset it (it's a v1
>> probe, according to the Atlas website on firmware 4480)?
> 
> One possible explanation is that the probe doesn't actually receive any
> packets (i.e. the receive circuitry at the ethernet level is broken).
> The only way to know for sure is to open up the probe and attach a
> serial console. But I'm not aware of any software failure mode that
> leads to this behavior.

Try a different ethernet cable and/or switch port.

Daniel