UTM 9 Firmware 9.406-3 "Last check" never.

I think it's fairly generic.  Here's what one contains in our lab in Oklahoma:

utm:/root # cat /etc/up2date/servers.sorted.rpmsave
$VAR1 = [
          {
            'name' => 'v8up2date1',
            'Port' => '443',
            'Ip' => '79.125.21.244',
            'Host' => 'v8up2date1.astaro.com',
            'Fallback_Ip' => '79.125.21.244'
          },
          {
            'name' => 'v8up2date3',
            'Port' => '443',
            'Ip' => '175.41.132.12',
            'Host' => 'v8up2date3.astaro.com',
            'Fallback_Ip' => '175.41.132.12'
          },
          {
            'name' => 'v8up2date2',
            'Port' => '443',
            'Ip' => '184.72.238.199',
            'Host' => 'v8up2date2.astaro.com',
            'Fallback_Ip' => '184.72.238.199'
          }
        ];

I guess you could try creating that file, but it looks like when you imaged that device in January that something went wrong.  If you've gotten no updates since then, I'd be tempted to offload some config backups, re-image with a new DVD burned at 4x and restore.

Cheers - Bob

The system is a new install in October because of a hardware crash of my old server. I installed with the ISO of 9.406-3 as VM, restored my configuration (9.406-3) and then made an Up2Date to 9.407-3 which was showed by Up2Date automatically. And because of having two new machines I decided to install a second UTM as VM and configured a HA cluster.

I will try with the file but after my further investigations yesterday I don't think that it will help - the tries with the IP address you posted yesterday weren't successful. Now after testing with the file I can say that this doesn't solve the issue.

I also have an UTM Manager, Release 4.303-9 running. This system isn't able to get pattern updates, too. There are the same error messages as on the UTM. I don't know if this is an issue of the UTM installation...

I can't believe that my two UTMs and the UTM Manager have a corrupt installation. So I don't see a need to reinstall all these systems.

Today I updated the two UTMs to 9.408-4 by manually uploading the U2D package. But Up2Date isn't still working.

MTU size is 1500 on all interfaces. There was a post to solve this issue by adding the interface to the allowed networks of the proxy. This isn't possible because you can only add network objects and I have all network objects added (Internal, External and DMZ). In the past I hadn't added External because it makes no sense but for troubleshooting of this issue...

I also put all IP addresses of the UTM into a network group and added this group to the list of hosts for skipping the transparent proxy. This didn't help.

I even checked my license which is valid until August 2017.

I don't understand what is meant by "status=500 proxy connect failed: Alarm" in the Up2Date log. Which proxy is meant? I thought it's the proxy of the UTM because the UTM Manager has the same error message. But if all exception rules in the Web Protection section don't help it seems to be another proxy.

Any other ideas of what could be the reason or this issue?

I found a very interesting post: https://community.sophos.com/products/unified-threat-management/f/hardware-installation-up2date-licensing/77242/utm-9-402-7-failing-to-connect-to-up2date-servers#pi2132219853filter=all&pi2132219853scroll=false

And after disabling the Up2Date cache of the UTM Manager the UTM can connect to the authentication servers and download the Up2Date files. You find the setting here: Management | Central Management | SUM Settings | Use SUM server as Up2Date cache.

Thanks to IanMorehouse [:)]

But what about SUM? Here are still error messages.

And I could solve the issue by

1. Installing a new license: My old license did expire for some features.
2. Checking the network access: When I installed the SUM as VM I connected the external NIC to the DMZ vSwitch. Now after connecting to the Internet vSwitch everything is working fine again. [:$]

I got a new firmware by Up2Date and updated SUM successfully to 4.304-5 now.