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 ]
Randy Bush
randy at psg.com
Mon Dec 13 20:38:13 CET 2021
>>> 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. > > 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. so what is the convention for marking the removed v1 as deceased? randy
- 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 ]