[atlas] Firmware versions (was: Re: (no subject))

On 02 Jan 2014, at 11:44, Robert Kisteleki <robert at ripe.net> wrote:

> [...]
> 
> As a general rule, we keep the firmware versions in sync across hardware
> revisions in order to have the same capabilities available. The current
> situation is a bit of an exception, but that's only because we needed to
> deploy a new firmware for one hardware version only; functionally there's
> no difference.
> 
>> Due to a) and b) would it make sense to also attach the hardware
>> version (v1, v2, v3) of the probe as a tag in each UDM result as well?
>> We don’t know if different hardwares have effects on the measurement
>> results. We can cross-confirm this if the UDMs attach a hardware
>> version in addition to the firmware revision.
> 
> This would be possible, though (with some more documentation from our end
> [*]) one could also easily determine the hardware version from the probe ID.
> 
> Regards,
> Robert
> 
> [*] the quick version:
> - ID < 1500: v1
> - 2000 < ID < 5000: v2
> - 6000 < ID < 7000: anchor
> - ID > 10000: v3

Aha! This is useful. Thanks for sharing.

Best, Vaibhav

-----------------------------------------------------
Vaibhav Bajpai

Research I, Room 86
Computer Networks and Distributed Systems  (CNDS) Lab
School of Engineering and Sciences
Jacobs University Bremen, Germany

www.vaibhavbajpai.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: </ripe/mail/archives/ripe-atlas/attachments/20140103/a8001a0e/attachment.sig>