Address mappings #
Address mappings specify how different Connect iT core appliances connect to each other.
Address mappings are configured under ⚙ Settings → Address mappings
Region and Private address #
An address mapping belongs to a region and a private address. This means that if the region of an appliance changes or if the address of an interface changes, a new address mapping will need to be created. The old one will still exist for the old private address but will not have any effect, and it will be displayed in the list without an appliance or interface.
This also means it is not possible to change the region or private address once they are created.
Because of this, it is also possible to create address mappings for addresses which currently have no appliance or interface associated with them. This could, for example, be useful when planning for new appliances that have not yet been configured.
Public address #
These addresses need to be public in the sense that all appliances (Nimbra VAs, Edge Connects etc) that connect to the cluster need to be able to reach them.
Each video node needs to have one ip address configured as the public address. These addresses can be NATed if needed, but the public address needs to be unique for each video node.
Example 1: The cluster contains 2 video nodes that have private ip addresses reachable by the connecting appliances through a NAT.
| Video node | Private address | (NATed) Public address |
|---|---|---|
| video-1 | 10.10.10.10 | 216.58.207.227 |
| video-2 | 10.10.10.11 | 216.58.207.228 |
Example 2: The cluster contains 2 video nodes that have private ip addresses reachable without a NAT.
| Video node | Private address | Public address |
|---|---|---|
| video-1 | 10.10.10.10 | 10.10.10.10 |
| video-2 | 10.10.10.11 | 10.10.10.11 |
Finding the public address
If you do not know the public address of an appliance you can easily get it by running this command on the machine:
$ curl icanhazip.com
198.51.100.45
Internal address #
For each video node you can configure the address used when thumb nodes in the same region need to communicate with it. This is called the internal address mapping. If you do not specify any such mapping, the private address for the node will be used also for the connections from the thumb nodes.
Example 1: The cluster contains 2 video nodes that have internal addresses reachable by the thumb nodes.
| Video node | Private address | Internal address |
|---|---|---|
| video-1 | 10.10.10.10 | 20.20.20.20 |
| video-2 | 10.10.10.11 | 20.20.20.21 |
With this configuration in place, when the thumb nodes establish RIST tunnels to video-1 or video-2, the video nodes will listen on 20.20.20.20 and 20.20.20.21 respectively.
Inter region address #
For each video node you can configure the address mapping used when video nodes in other regions need to communicate with it. This is called the region address mapping. You can only specify one such mapping per video node. If you do not specify any such mapping, the public address mapping for the node will be used also for inter-region traffic.
Example 1: The system consists of two regions: Shanghai and Singapore. Each region has 1 video node.
| Video node | Private address | (NATed) region address |
|---|---|---|
| shanghai-1 | 10.10.1.10 | 216.58.207.227 |
| singapore-1 | 192.168.2.11 | 216.58.207.228 |
With this configuration in place, when a RIST tunnel need to be established from shanghai-1 to singapore-1, the shanghai-1 node will bind on 10.10.1.10 and send the UDP packets towards 216.58.207.228 where they will reach the singapore-1 node listening on its local address 192.168.2.11.