[atlas]Probe actually down?
- Previous message (by thread): [atlas]Probe actually down?
- Next message (by thread): [atlas]Probe actually down?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Wed Jan 5 11:22:39 CET 2011
Replying to various mails in the thread: On 2010.12.30. 20:00, Richard L. Barnes wrote: > Probe #394 is reported as being down in the web GUI, but I can ping6 to it without a problem. I'm not near the probe right now, so I can't look at it or its traffic. Are there known cases where probes are alive but not reporting to their controllers? > > --Richard There are a few scenarios when this is possible: * the probe is powered on, but it's not connected to the infrastructure (for example the connection went down for some reason, or after a reboot). In this case you can still ping it as the network stack is running, but it's reported as "down". * Every now and then we have issues with the controllers' network connections. They do reconnect themselves reliably, but if a probe connects to such a controller in the meantime, then the controller cannot report the probe status change to our database. A fix is in the making for this. On 2011.01.04. 10:38, Egor Zimin wrote: > I see the same situation with probe #163. This probe seems to be up now. There are days when it fluctuates, but also periods when it's up for days. On 2011.01.04. 10:46, Piotr Strzyzewski wrote: > Maybe this is the right time to implement optional mail notifications > about such events? So you'd like to subscribe to notifications when your probe comes up or goes down? It's certainly possible to do this, but -- since probe reconnects are not really that serious events -- I think I'd rather want be notified if a probe was down for a non-trivial time. Cheers, Robert
- Previous message (by thread): [atlas]Probe actually down?
- Next message (by thread): [atlas]Probe actually down?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]