This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] RIPE Atlas V1 Probe Issue
- Previous message (by thread): [atlas] RIPE Atlas V1 Probe Issue
- Next message (by thread): [atlas] RIPE Atlas V1 Probe Issue
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michael Hayler
ripe-atlas-probe-2010 at hayler.de
Wed May 17 13:04:23 CEST 2017
Hi, my Probe was reported offline one week ago and of course that happened while I was on vacation :) >From a tcpdump on my gateway it seemed that the probe itself was doing nothing anymore (no active checks etc.) but it was still responding to my Nagios Ping Checks. After a switchport shut/no shut it did not even respond to arp/nd anymore. So I powercycled the probe after I was home again and since then it is online without any issues for 11 hours now. Am 17.05.2017 um 12:40 schrieb Alun Davies: > A few points of clarification are warranted following the previous mail. > > The firmware alluded to in the previous email was released in February > 2017. Since then, approximately 100 RIPE Atlas V1 probes have > disconnected - about 15% of the total number of V1 probes on the network. > > The fix that is currently in the making is expected to be released in a > month or so. If at that time you have still been unable to reconnect > your V1 probe, you can then return your probe to be fixed. > Alternatively, you may apply for a V3 probe by following the usual > process as described > here: https://atlas.ripe.net/get-involved/become-a-host/ > -- Best Regards Michael Hayler
- Previous message (by thread): [atlas] RIPE Atlas V1 Probe Issue
- Next message (by thread): [atlas] RIPE Atlas V1 Probe Issue
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]