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/[email protected]/
[atlas]trying to collect basic info about the architecture
- Previous message (by thread): [atlas]Probe actually down?
- Next message (by thread): [atlas]trying to collect basic info about the architecture
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Wed Jan 5 11:29:37 CET 2011
Some additional info: On 2010.12.22. 12:09, Emile Aben wrote: > On 21/12/2010 18:23, Wilfried Woeber, UniVie/ACOnet wrote: >> Is the probe capable of bufffering data for a while if connectivity to the >> Net is still there, but not to the controller(s)? > > Yes, the probes have a limited capability to do so. I think it's > currently capable of storing a couple of minutes worth of data. It could store more, but we're cautious for now as in the worst case this could fill up the storage space which could cause serious problems. We'll add more buffering as soon as we're confident it cannot fire back. >> Is there any means to (locally, on the same subnet, or even remotely) >> trigger or "reboot" a probe, other than disconnecting power (which means >> physical access required)? > > Currently there is no way for users to reboot a probe other then > disconnecting power. If this is a capability that people would like to > have, we could look into ways we could make that happen. This makes me wonder: what problem would this solve? You obviously couldn't use this feature if the probe was down, only if it was up; but then why would you want to reboot it? :-) Cheers, Robert
- Previous message (by thread): [atlas]Probe actually down?
- Next message (by thread): [atlas]trying to collect basic info about the architecture
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]