Hi,
things have been strangely silent on the topic of "the end of the TTM
boxes" after the last RIPE meeting - so let me try to stir this somewhat.
I've been told that UDMs in Atlas "can do what I need" (use RIPE
measurements to prove to our customers that our Internet reachability
is good). It might, but I find it surprising painful, as I can only
request pings from "10 probes at a time" in the UDM - and for reasonable
accuracy, we'd need something of at least the size of TTM (100+ probes),
or *better*, as we know that individual Atlas probes are not expected
to have the same network stability as a TTM box ("always up. ALWAYS!") -
setting up 30 or more individual UDMs to get 150 clients each to ping our
two TTM boxes is... not the way to go.
Second, I'm a bit confused how to automatedly download the .json-format
UDM results - while I'm logged in, clicking on the link gives me a nice
.json download, but when using the same link with wget, I get a login
page. I'm not overly willing to download 30 UDM result files manually
every day - so there must be some way to use "wget" etc. to get these
data files... any hints on that?
Example link: https://udm01.atlas.ripe.net/atlas/udm_download.json?attach=1&msm_id=100200…
Third, we still need reasonable ping targets in our network, that
are sort of "not under our control" (to meet the goal of "the RIPE NCC
does these measurements, they are neutral, so we're not faking anything
here") - and that are not part of the normal network churn that
www.space.net or one of our routers might have. So far we use the TTM
boxes for that - but they might die of old age some day... Which brings
back the topic of the Atlas Anchor boxes... any news on that?
Gert Doering
-- NetMaster
--
have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279
Dear colleagues,
With the introduction of a new firmware version for RIPE Atlas probes,
the structure of the measurement results will be changing. Anyone making
use of the raw results is advised to read about these upcoming changes
on RIPE Labs:
https://labs.ripe.net/Members/emileaben/ripe-atlas-data-structure-changes
We also suggest to subscribe to our RSS feed to be notified of future
firmware releases.
Kind regards,
Mirjam Kuehne
RIPE NCC
[apologies for duplicates]
Dear colleagues,
Please find an update on RIPE Labs about our effort to help network
operators clean-up redundant settings with respect to 128.0.0.0/16
https://labs.ripe.net/Members/mirjam/de-bogonising-128.0.0.0-16
Kind regards,
Mirjam Kuehne
RIPE NCC
Dear colleagues,
It's been possible to embed RIPEstat widgets for some
time. You can now also include a resource bar so that your
site's visitors can query resources via RIPEstat on your website.
Please find more information on RIPE Labs:
https://labs.ripe.net/Members/becha/adding-interactivity-to-embeded-ripesta…
Kind regards,
Mirjam Kuehne
RIPE NCC
