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] Firmware versions (anchors)
- Previous message (by thread): [atlas] Firmware versions (anchors)
- Next message (by thread): [atlas] Fwd: [service] Technical Outage Resolved
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Wed Jan 15 16:05:04 CET 2014
On 2014.01.15. 15:46, Wilfried Woeber wrote: > Robert Kisteleki wrote: > > [...] > > given the "lazy" approach :-) > >> 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. > > I just noticed that our (old tech) anchor is still more than one version behind. > > Is there some sort of schedule to make them load the update eventually, in > case they do not disconnect "regularly". Which is sort of expected behaviour > for Anchors, imho :-) > > Wilfried. Yes, good point, we'll be a bit more aggressive with Anchors :-) (And the morhogenetic field seems to be strong today, I hear our engineers have discussed this just this afternoon...) Robert
- Previous message (by thread): [atlas] Firmware versions (anchors)
- Next message (by thread): [atlas] Fwd: [service] Technical Outage Resolved
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]