probes do not register
on a SOHO LAN that used gto have a good running v3 probe (25867 but it went where so many v3 probes go, dead for a few months now. yes i did usb recovery, to no avail. you gotta love v3 probes.) i unpack an unused v3 (25909) i had in my back pocket for a few years. plug it into the LAN. wait a few hours. it does not register. power LED on, LED to right of it blinks about every two seconds. web page for it, https://atlas.ripe.net/probes/25909/ shows it has been down for 1 year 11 months while, in fact, it has never been up. oddly that web page shows the correct AS, comcast, 7922, but no IP addressing. tcpdump is my friend. pcap can be found at https://archive.psg.com/240907.atlas-25909.pcap it gets dhcp etc. then twice successfully pings to nl-ams-as3333-3.anchors.atlas.ripe.net (193.0.0.164) then it does successful DNS AAAA queries for woolsey.atlas.ripe.net and reg02.atlas.ripe.net. but it never reaches out to them that i can see. then it does a successful ARP for the default gateway, 192.168.0.1 then silence and much more silence unpack another unused antique from its envelope, 25918. dns queries for different controllers, but otherwise the same story. pcap avaliable as https://archive.psg.com/240907.atlas-25918.pcap. how to further debug? randy
25909 just managed to call home and is up! thanks whomever. randy
Hello Randy, I believe your probe (25909) eventually decided to connect to the infra after all :-) But then it got into an upgrade loop - it asked for a new firmware that it didn't like. We saw this at our end, and turned some knobs to help - which ultimately made it upgrade to a newer firmware. Eventually it is expected to upgrade to the newest firmware (you can nudge it to make this happen sooner by rebooting, but this not critical). I'd like to thank you for reporting this, since as a consequence we saw that other probes may experience similar issues and applied the same solution to those. As for the other two probes you mention: - 25918: same, this is also happy now - 25867: this one consistently reports "USB-READONLY" meaning it doesn't like the USB stick now, perhaps you can take another look Regards, Robert On Mon, Sep 9, 2024 at 5:50 PM Randy Bush <randy@psg.com> wrote:
25909 just managed to call home and is up! thanks whomever.
randy ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
hi robert thanks for following up, much appreciated
I believe your probe (25909) eventually decided to connect to the infra after all :-) But then it got into an upgrade loop - it asked for a new firmware that it didn't like. We saw this at our end, and turned some knobs to help - which ultimately made it upgrade to a newer firmware. Eventually it is expected to upgrade to the newest firmware (you can nudge it to make this happen sooner by rebooting, but this not critical).
how do i know what is latest? it claims to be at 5080, as is 25918 .
I'd like to thank you for reporting this, since as a consequence we saw that other probes may experience similar issues and applied the same solution to those.
even though i realize i am being a pita, i always report problems because others might have them.
As for the other two probes you mention: - 25918: same, this is also happy now
yep
- 25867: this one consistently reports "USB-READONLY" meaning it doesn't like the USB stick now, perhaps you can take another look
unfortunately, it's 325km away. again, thanks. randy
Hello Randy,
how do i know what is latest? it claims to be at 5080, as is 25918 .
As of now, 5080 is the latest for hardware probes (v3 and up). For software (RPM, specifically) 5090 is available but it's only internally different from 5080. There are some indirect sources that can tell you this, but it's certainly easiest if we indicate (in the UI) if the probe is using the latest firmware. This is of course more meaningful for software probes, where the host has full control over this. We have that on our todo list, but we can give the same indication to hardware probe hosts as well.
I'd like to thank you for reporting this, since as a consequence we saw that other probes may experience similar issues and applied the same solution to those.
even though i realize i am being a pita, i always report problems because others might have them.
This mailing list (and the RIPE Forum, Twitter, ...) are not really the best venues for individual support; we have the ticketed atlas@ripe for that. However, in most cases it's hard to know in advance if something is an isolated case or not. While we *prefer* tickets, such a public ask for assistance is also ok. Robert
Hello, On 9/10/24 8:24 PM, Robert Kisteleki wrote:
I'd like to thank you for reporting this, since as a consequence we saw that other probes may experience similar issues and applied the same solution to those. even though i realize i am being a pita, i always report problems because others might have them. This mailing list (and the RIPE Forum, Twitter, ...) are not really the best venues for individual support; we have the ticketed atlas@ripe for that. However, in most cases it's hard to know in advance if something is an isolated case or not. While we*prefer* tickets, such a public ask for assistance is also ok.
But it is necessary to admit that many current problems have a global basis... this will of course be hidden in your tickets... The information on the mailing list is better, one does not have to panic and open individual tickets because of a global problem... which are quite recurring... if I read here that others have the same problem, I have no reason to open an individual ticket. Answering dozens of the same tickets also takes time, doesn't it? - Daniel
participants (3)
-
Daniel Suchy -
Randy Bush -
Robert Kisteleki