[atlas] Upgrade existing Anchor to newer hardware
- Previous message (by thread): [atlas] Upgrade existing Anchor to newer hardware
- Next message (by thread): [atlas] New on RIPE Labs: Exploring RIPE Atlas Traceroutes from 2012 to 2019
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Cathal Mooney
cmooney at wikimedia.org
Thu Aug 5 16:14:29 CEST 2021
Ok Anand thank you! regards, Cathal. On Thu, 5 Aug 2021 at 14:43, Anand Buddhdev <anandb at ripe.net> wrote: > > Hello Cathal, > > We can certainly support you with this hardware replacement. We have a > process for this, which triggers various things in our back-end systems. > One of these steps will be to provide you with a new installer image. > > The best approach is to send email to atlas at ripe.net. This will go into > a ticket queue, and one of my colleagues will handle it. In your email, > please provide details of all the anchors that you wish to replace. > > Regards, > Anand Buddhdev > RIPE NCC > > On 05/08/2021 14:50, Cathal Mooney wrote: > > Hi, > > > > I am working for the Wikimedia Foundation, and we have several Atlas > > Anchor's deployed at various locations. > > > > Some time ago the Anchor we had in our location in Dallas, US > > (p6093.probes.atlas.ripe.net) failed due to a hardware failure. We > > are now attempting to replace the Anchor with new hardware which we > > have installed. > > > > The old device was a v2 Anchor (Soekris), however, and the new device > > is v3 (PC Engines APU.2E2). Given the newer hardware I expect we will > > need a different USB image to boot from? Our hope would be to re-use > > the previous IP addressing and other details so that does not need to > > change. > > > > What might be the best way to approach this? > > > > Many thanks, > > > > Cathal. > > > >
- Previous message (by thread): [atlas] Upgrade existing Anchor to newer hardware
- Next message (by thread): [atlas] New on RIPE Labs: Exploring RIPE Atlas Traceroutes from 2012 to 2019
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]