chore: migrate HIGHDEF peering from ATL1 to MIA1

[yzguy]

Noticed earlier that some of the highdef peerings don't go to where they originally went, eg ATL1 to ATL.

The ATL1 peering now goes to their Tampa (TPA) node

-> dig atl.peer.highdef.network +short
tpa.peer.highdef.network.
158.51.125.4

Looking at the latency between ATL1 and TPA, and MIA1 and TPA it's much better going to MIA1 (16ms vs 8ms)

ATL1 <> TPA

[email protected]:~$ ping tpa.peer.highdef.network count 1
PING tpa.peer.highdef.network(2606:65c0:20:97:ae8:3d00:92c9:abdf.hostodo.com (2606:65c0:20:97:ae8:3d00:92c9:abdf)) 56 data bytes
64 bytes from 2606:65c0:20:97:ae8:3d00:92c9:abdf.hostodo.com (2606:65c0:20:97:ae8:3d00:92c9:abdf): icmp_seq=1 ttl=53 time=16.0 ms

--- tpa.peer.highdef.network ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 15.963/15.963/15.963/0.000 ms

MIA1 <> TPA

[email protected]:~$ ping tpa.peer.highdef.network count 1
PING tpa.peer.highdef.network(2606:65c0:20:97:ae8:3d00:92c9:abdf.hostodo.com (2606:65c0:20:97:ae8:3d00:92c9:abdf)) 56 data bytes
64 bytes from 2606:65c0:20:97:ae8:3d00:92c9:abdf.hostodo.com (2606:65c0:20:97:ae8:3d00:92c9:abdf): icmp_seq=1 ttl=49 time=7.69 ms

--- tpa.peer.highdef.network ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 7.693/7.693/7.693/0.000 ms

Therefore we will migrate the peering from ATL1 to MIA1

Opened a commit to update it on their side as well jlu5/ansible-dn42#29

[github-actions]

Hello,

We have started the deployment of new configuration on our side for the peering at our ATL1 PoP.
It is ready for the configuration on your side.

You can use our Nodes page for PoP information to be used: https://dn42.routedbits.com/nodes/#atl1

We manage configuration via our dn42-peers repository, you can submit pull requests to add/remove/change your own peerings. Once accepted and merged, the changes are pushed to our routers within a few minutes.

Pull Request: routedbits/dn42-peers#100

Let us know if you have any questions or issues.

Thanks,
NOC, RoutedBits

[github-actions]

Hello,

We have started the deployment of new configuration on our side for the peering at our MIA1 PoP.
It is ready for the configuration on your side.

You can use our Nodes page for PoP information to be used: https://dn42.routedbits.com/nodes/#mia1

We manage configuration via our dn42-peers repository, you can submit pull requests to add/remove/change your own peerings. Once accepted and merged, the changes are pushed to our routers within a few minutes.

Pull Request: routedbits/dn42-peers#100

Let us know if you have any questions or issues.

Thanks,
NOC, RoutedBits