Mikrotik hEX lite (RB750r2) and satellite updates

RouterOS General
1

Hi!
Mikrotik hEX lite (RB750r2, It is now installed at 6.35.4) an error is returned when updating packages through the satellite “ERROR: connection timed out”.
RTT = ~700 ms, can this affect updates?
[admin@MikroTik] > ping upgrade.mikrotik.com
SEQ HOST SIZE TTL TIME STATUS
0 8.8.8.8 56 49 564ms
1 8.8.8.8 56 49 599ms
2 8.8.8.8 56 49 590ms
3 8.8.8.8 56 49 586ms
sent=4 received=4 packet-loss=0% min-rtt=564ms avg-rtt=584ms max-rtt=599ms

[admin@MikroTik] > ping update.mikrotik.com
SEQ HOST SIZE TTL TIME STATUS
0 8.8.8.8 56 49 591ms
1 8.8.8.8 56 49 610ms
2 8.8.8.8 56 49 603ms
3 8.8.8.8 56 49 592ms
sent=4 received=4 packet-loss=0% min-rtt=591ms avg-rtt=599ms max-rtt=610ms

2

No RTT 700+ does not affect. Check DNS resolution.

3

For me both fqdns resolve properly, so check your own DNS setup. 8.8.8.8 is an IP of Google DNS server, so something is really wrong in your DNS chain.

You may resolve the fqdns to IPs somewhere else and then create static DNS items in the configuration of the device you’re trying to upgrade.

[me@myTik] > put [resolve update.mikrotik.com]
159.148.147.205
[me@myTik] > put [resolve upgrade.mikrotik.com]
159.148.172.226

Also, upgrading from 6.35.4 directly to current long-term (6.47.9 as of writing this) is a voucher for a headache. So if the device is still running 6.35.4., I’d start from upgrading to the last 6.40.x release, then to the last 6.41x one, and then further, but I’m still not sure whether a jump to 6.47.9 will be safe. The level of risk depends on the configuration - some parts of it haven’t changed at all, some (e.g. IPsec) have seriously. So you may want to post the export for a check; definitely make an export and download it somewhere else before the upgrade, so that you could eventually reconstruct the configuration if the upgrade fails.