[atlas]Probe flapping

Hi Andreas,
I thought connecting it directly on the distribution network will make  
it The stable one :( well if everything is fine at your end than I'll  
try to change the upstream for this subnet.

Is it possible to change the controller my probe is connected to and  
can you share the controller IPs? If it's not against the policy.

Best Wishes,
Aftab A. Siddiqui

------
Sent from my iPhone *G

On Dec 20, 2010, at 9:21 PM, Andreas Strikos <astrikos at ripe.net> wrote:

> Hi Aftab,
>
> Although your probe is located in Asia, it is still connected to one  
> of our controller in Europe because this part of Asia is closer to  
> Germany than west coast of US :)
> Since Friday our system is fully functional, so I think it's your  
> network that makes your probe flapping. The small gap is normal  
> since after the probe disconnects it takes some time to re-connect.
> From what i can see from our history your probe was disconnected  
> quit often from the beginning :)
>
>
> Regards,
> Andreas Strikos
>
> On Dec 19, 2010, at 9:16 AM, Aftab A. Siddiqui wrote:
>
>> Hi Robert,
>>
>> It seems like a probe (ID: 303) in Asia is still having disconnection
>> problem.
>>
>> Connect at:            Disconnect at:
>> 2010-12-19 06:07:29 UTC    (still connected)
>> 2010-12-18 17:32:11 UTC    2010-12-19 06:06:49 UTC
>> 2010-12-18 17:15:28 UTC    2010-12-18 17:30:54 UTC
>> 2010-12-18 10:26:52 UTC    2010-12-18 17:13:24 UTC
>>
>> Or is this suppose to be normal? But every disconnect - connect  
>> session has
>> 1-2min gap.
>>
>> Best Wishes,
>>
>> Aftab A. Siddiqui
>>
>> -----Original Message-----
>> From: ripe-atlas-admin at ripe.net [mailto:ripe-atlas-admin at ripe.net]  
>> On Behalf
>> Of Robert Kisteleki
>> Sent: Friday, December 17, 2010 4:09 PM
>> To: ripe-atlas at ripe.net
>> Subject: Re: [atlas]Probe flapping
>>
>> Dear All,
>>
>> Here's an update to Daniel's message from yesterday.
>>
>> As Daniel mentioned, on Wednesday evening our system started to  
>> migrate the
>> probes away from a particular controller (ronin, in DE). We have a  
>> strong
>> suspicion on why this happened, but it's not confirmed so I'm not  
>> going to
>> publicly speculate :-) In any case, since we don't yet have enough  
>> spare
>> capacity to handle this situation, another controller was overloaded.
>>
>> We needed to fix the internal databases on these controllers, which  
>> took
>> some time. We were able to bring the system back to a stable state  
>> by the
>> afternoon.
>>
>> This morning we revived some probes (25 or so) which were in a  
>> limbo -- they
>> were not properly connected. We forced them to re-connect, so they  
>> are fine
>> now. There are still some of them, like 10 or so, which are not  
>> connected
>> (down) so we can't really help those from here. If your probe was  
>> working
>> properly before Wednesday, but now is down, then please power cycle  
>> it
>> (using the USB power) and it will very likely come back fine.
>>
>> Probes in the US (and Asia, very likely) were not affected, as they  
>> have a
>> local controller on the west coast, which was not involved. That's  
>> because
>> the system really doesn't like to send European probes to it, it's  
>> too far.
>>
>> Let us know if there's anything else not working properly, so that  
>> we can
>> look into it.
>>
>> Regards,
>> Robert
>>
>>
>> On 2010.12.16. 14:57, Daniel Karrenberg wrote:
>>>
>>> Intermediate update to keep those interested informed.
>>> I am writing this to keep the engineers free to work
>>> the problem. I do not know nitty gritty details, so
>>> this is a general overview.
>>
>> [...]
>>
>