You are here: Home > Analyse > Internet Measurements > RIPE Atlas

VM anchor Installation

Installation instructions

You can create a Virtual Machine to be used as a RIPE Atlas anchor, provided it meets certain requirements.

The following requirements ensure a consistent environment for the operation of RIPE Atlas VM anchors across different virtualisation technologies that may be used by anchor hosts.

Network requirements

Network-wise, RIPE Atlas VM anchors have the following requirements:

  • The anchor must have native IPv4 and IPv6 (if IPv6 is announced in the host ASN)
  • Static IPv4 and IPv6 addresses need to be unfiltered (not firewalled)
  • The VM anchor may require up to 10 Mbit bandwidth (it currently requires much less)

Hardware requirements

Create a VM with the following virtual hardware specifications:

  • 2 vCPUs, amd64 (x86_64) platform
  • 2GB of RAM
  • 50GB of storage
  • 1 virtual NIC

OS requirements (for installing Linux on VM)

  • A minimal CentOS 7 installation
  • The storage to be presented as a single block device, with the following partition layout:
  • partition 1: 1 GB for /boot, ext4
  • partition 2: remaining space, LVM Physical Volume
    • a single / (root file system), ext4

Set up your RIPE Atlas VM anchor

Application Confirmation

Once your anchor application has been confirmed, you will be able to see your anchor hostname on the anchors page under My Atlas. Your anchor hostname is automatically generated and will have the form country code-city code-asxxxxx. If you are not the ASN holder, the hostname will include the suffix -client.

Complete the details on the "Anchors" page

It is important that all the mandatory information is filled in on your anchors page: https://atlas.ripe.net/anchors/manage/. This page can only be accessed if you are logged in to your RIPE NCC Access account.

Install Linux on the VM anchor

Below is an example CentOS 7 Anaconda kickstart installation config, that will install the operating system:

cmdline
install
lang en_US.UTF-8
keyboard us
rootpw --iscrypted !! --lock
firewall --service=ssh
timezone --utc UTC
bootloader --location=mbr --append="crashkernel=auto"
clearpart --drives=/dev/sda --all --initlabel
zerombr
part /boot --fstype=ext4 --size=1024 --ondisk=/dev/sda
part pv.01 --size=1 --grow --ondisk=/dev/sda
volgroup vg01 --pesize=4096 pv.01
logvol / --fstype=ext4 --name=lv_root --vgname=vg01 --size=1 --grow --fsoptions="noatime,nodiratime,discard"
network --bootproto=static --hostname=nl-ams-as3333.anchors.atlas.ripe.net --ip=192.0.2.2 --netmask=255.255.255.248 --gateway=192.0.2.1 --ipv6=2001:db8:0:0::2/64 --ipv6gateway=2001:db8:0:0::1 --nameserver=8.8.8.8,2001:4860:4860::8888 --onboot=yes
shutdown

%packages
%end

%post
# Bootstrap SSH key
mkdir -m 0700 -p /root/.ssh
cat <<EOF > /root/.ssh/authorized_keys
<< snip authorized key >>
EOF
restorecon -R /root/.ssh
%end

This kickstart file should be changed as follows:

  • the network line should be updated with the network settings for your Anchors
  • the snip authorized key line should be replaced with the SSH key that you will be sent by email after your Anchor registration has been accepted

Below is an example virt-install command to create the VM:

virt-install \  
   --name=nl-ams-as3333.anchors.atlas.ripe.net \  
   --file=/VMs/nl-ams-as3333.anchors.atlas.ripe.net.qcow2,size=50 \  
   --vcpus=2 \  
   --ram=2048 \  
   --os-type=linux \  
   --os-variant=rhel6 \  
   --graphics none \  
   --console pty,target_type=serial  \  
   --network type=direct,source=p4p1,source_mode=bridge,model=virtio \  
   -x 'console=ttyS0 ks=https://x.x.x.x/ks/anchor.ks ip=a.b.c.d netmask=255.255.255.192 gateway=a.b.c.d' \  
   --location /path/to/CentOS-7-x86_64-Minimal-1708.iso

You should modify the arguments as needed for your installation.

Start the virtual Machine

It is important that once you have installed the Anchor, you log in to your RIPE Atlas account, go to the My Atlas menu and then Anchors, and check the boxes “Software is installed” and Anchor is connected to the network so the RIPE NCC gets notified and can begin these tests.

Pass internal tests to verify measurements are possible

The RIPE NCC will perform some internal tests to check that the anchor is properly set up. If it isn't, we will contact you to troubleshoot.

NOTE: Your anchor will not be fully activated until we have finished these internal tests. We will notify you when they are complete.

Your RIPE Atlas VM anchor has been successfully setup!

Once all verifications are complete, the anchor will be fully activated and will become public:

  • You will be able to locate it on the map of anchors
  • It will appear on the list of anchors
  • You can use it as a probe for your own measurements
  • You will be able to select the anchor as a target under My Measurements
  • It will be added to the anchoring measurements that the RIPE NCC runs for you
  • You will start earning credits you can use to perform your own customised measurements

We develop RIPE Atlas in cooperation with the Internet community, and we want to know what you think. Find out how to get in touch.