EUMETCast Terrestrial over AMT can serve any user hosted on the EUMETSAT side of the EWC, regardless of native multicast connectivity. The encapsulated data can travel via GEANT network or the commercial internet.

Pre-requisite

  1. You need to register to the EO Portal
  2. Subscribe to data for EUMETCast Terrestrial
  3. Request EUMETCast Terrestrial credentials for access from the EWC. You have to write to ops@eumetsat.int (Helpdesk) with you username from EO Portal.


Once you have the following parameters, you can proceed to the next steps.

parametervalue or where to take it
usernamefrom EO portal
userkey

provided by the helpdesk in the pilot phase. (opening a ticket and request  EUMETCast Terrestrial credentials for access from the EWC



Create security group

Once you enter your tenancy:

  1. Go to Infrastructure → Network

2. Go to Security Group tab and click the add button:


3. Assign eumetcast-ssh name to the security group and hit save:

In the scoped cloud select your tenancy from the list. If you leave All, the security group cannot be assigned to VMs.


4. Click on the new security group to access it


5. Click on the 'Add rule' button to create a new rule


6. Add the following rules and hit save

2268-udpingressCustom RuleUDP2268Network0.0.0.0/0Instance
22-ssh-tcpingressCustom RuleTCP22Network10.0.0.0/24Instance
8500-tcpingressCustom RuleTCP8500Network0.0.0.0/0Instance

Now you are ready to provision the client!

Provision the client VM

  1. Go to Provisioning → Instances and click 'Add' button


2. Use the search bar to find the 'EUMETCAST TERRESTRIAL ON AMT' (type eumetcast or terrestrial for example):

3. Select name for your VM:(e.g. eumetcast-client)

4. Use the following specifications for the provisioning of the client:

CPU

8 cores 

RAM

64 GB

OS

Ubuntu v 22.04

Storage

1.2TB

EWC Plan

hm.xlarge

5. Insert your Eumetcast terrestrial credentials

6. Select the following security group: 

  •        eumetcast-ssh

The login to this machine is allowed only from the internal network (10.0.0.0/24) even if there is a public IP! This is for security reasons after public IP was required for the eumetcast machine. (See point 7 below)

In other words, if you want to login to the machine you need to first login to a machine in the EWC (for example a proxy or one machine with the security group that allow ssh 22 from external network) and then login using the internal IP of the eumetcast machine, not the public IP, because it won't work otherwise.

You can find the internal IP of the machine going to Morpheus → eumetcast instance/VM → select Tab Network for the machine and look at Interfaces, as shown below:

 7. Select the floating ip as external

 8. Hit Next and Complete to create the VM


Once the service is provisioned, the user will start to receive their subscribed data on their VM (stored by default in /root/data/eumetcast/ but can be changed in the /etc/cast-client-channels_ter-1.ini file).

A crontab is automatically activated in order to prevent the build-up of data on the machine

All data is deleted 5 mins after retrieval by default and this can be changed by the user. (See How to modify the time to live of the data to modify that)

9. Enable NAKs How to enable NAKs

10. Enable ACKs How to enable ACKs

User Notification Service

To access the User Notification Service (UNS), go to uns.eumetsat.int. You can find information on service alerts, scheduled maintenance and service enhancements. You can subscribe to UNS email notifications via the Earth Observation Portal. In addition, users can receive regular updates on scheduled maintenance and service enhancements through our EUMETSAT Users Twitter feed.


Advanced topics

Full documentation related to EUMETCast Terrestrial can be found here.