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] some thoughts and question regrding probe "stability"
- Previous message (by thread): [atlas] some thoughts and question regrding probe "stability"
- Next message (by thread): [atlas] some thoughts and question regrding probe "stability"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Fri Jul 18 00:27:05 CEST 2014
On 2014/07/17 19:01 , Mike. wrote: > On 7/17/2014 at 6:03 PM Philip Homburg wrote: > > |Hi Wilfried, > | [major snip] > | > | In contrast, the connection between a probe and the > | controller is already terminated if the network is > | down for one minute. > ============= > > > > Pulling that one sentence out of a long-ish reply. > > If I read that correctly... > > If a probe loses contact with its controller for > 60 seconds, then the controller considers the probe > offline and starts a disconnected timer. More like, the controller 'pings' the probe every 20 seconds and after 3 missed responses the connection is terminated. And for the Atlas system as a whole, that works. But the goal of the Atlas system is not to have a probe connected as long as possible. Philip
- Previous message (by thread): [atlas] some thoughts and question regrding probe "stability"
- Next message (by thread): [atlas] some thoughts and question regrding probe "stability"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]