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/ripe-atlas@ripe.net/
[atlas] swapping a v1 for a v3
- Previous message (by thread): [atlas] swapping a v1 for a v3
- Next message (by thread): [atlas] swapping a v1 for a v3
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Mon Dec 13 10:09:23 CET 2021
On 2021-12-10 18:31, Randy Bush wrote: >> The solution suggested by the Atlas team was simply >> to register the new instance with the ID number I >> had been using before. This worked. >> >> IIUC, each hardware probe is pre-registered. This >> may be an obstacle; I don’t know. > > i suspect the probe or actually the back end would have an identity > crisis. > > randy Indeed! For hardware probes, where the probe's key is virtually unchangeable, we don't do such ID/key juggling. For software probes the host can update (re-register) the probe's key meaning the ID remains the same; this is intended to solve the problem Niall faced. Hope this helps, Robert
- Previous message (by thread): [atlas] swapping a v1 for a v3
- Next message (by thread): [atlas] swapping a v1 for a v3
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]