Hello, I got IPv6 connectivity for my probe 4365 a few days ago (2016-09-26) when I first noticed the system tag "IPv6 Doesn't Work". As the system tags aren't updated more often than every four hours I started some successful IPv6 measurements on that probe and settled back for four days. Now the probe is still flagged as IPv6 not working. In the meantime I noticed the tag "v2" but the general information tab tells me the system architecture is probev1… Actually I don't know if it's a v1 or v2, but it's still an old Lantronix one, so it's not completely wrong :-) Is there a possibility to re-trigger the assignment of the system tags for this probe or some other solution? Thanks! jomat
Johannes, On 2016-09-30 14:18, Johannes Matheis wrote:
Hello,
I got IPv6 connectivity for my probe 4365 a few days ago (2016-09-26) when I first noticed the system tag "IPv6 Doesn't Work". As the system tags aren't updated more often than every four hours I started some successful IPv6 measurements on that probe and settled back for four days. Now the probe is still flagged as IPv6 not working. In the
There is evidence of v6 failing around 26 September, but the successes after don't seem to be recognised. We'll check why that is.
meantime I noticed the tag "v2" but the general information tab tells me the system architecture is probev1… Actually I don't know if it's a v1 or v2, but it's still an old Lantronix one, so it's not completely wrong :-)
All lantronix probes have the "probev1" architecture; even though the v2 probes have more memory, they run the same code and have the same architecture. So this is correct :-)
Is there a possibility to re-trigger the assignment of the system tags for this probe or some other solution?
This will happen automatically, once we understand (and possibly fix) the reason. Please bear with us. Thank you for reporting this! Robert
Thanks! jomat
participants (2)
-
Johannes Matheis
-
Robert Kisteleki