topic Re: Failed to find any routes on the machine in Firewall and Security Management

Failed to find any routes on the machine

pandersson — Mon, 23 Sep 2019 08:39:14 GMT

Hello.

I get this message when trying to create a VSX cluster "Error: Failed to find any routes on the machine".
The information in sk144832 does not help, as there are no aliases.
Neither does sk92556, which happens if I just try to add one single
node(Failed to resolve Management Virtual System NIC).
Boxes are new out of the box, and have almost no configuration at all.
Mainly ip-address and default route, and one additionas I added for testing.
I had a couple of bonds, but removed them to see if it made a difference.

Does anybody know what to do with this ?

(I will ask CheckPoint as soon as support contract is activated)

/Per

Re: Failed to find any routes on the machine

_Val_ — Mon, 23 Sep 2019 08:56:34 GMT

Version, installation and config details, appliance models? do those machines have DG defined?

Re: Failed to find any routes on the machine

pandersson — Mon, 23 Sep 2019 09:01:01 GMT

Ah, yes, R80.10 on both gates and mgmt, and DG is there, as is a specific hostroute to mgmt-station.
192.168.x.135 172.16.y.193 255.255.255.255 UGHD 0 0 0 Mgmt
172.16.y.192 0.0.0.0 255.255.255.240 U 0 0 0 Mgmt
0.0.0.0 172.26.y.193 0.0.0.0 UGD 0 0 0 Mgmt

Re: Failed to find any routes on the machine

_Val_ — Mon, 23 Sep 2019 09:53:21 GMT

should work out of the box. try rebooting VSX GWs and start again

Re: Failed to find any routes on the machine

pandersson — Mon, 23 Sep 2019 09:56:40 GMT

Thanks, but done multiple times. And mgmt. No difference.

Re: Failed to find any routes on the machine

Maarten_Sjouw — Tue, 24 Sep 2019 05:51:08 GMT

In clish can you do a 'show configuration static-routes'
And obfuscating rfc1918 addresses is not really needed.
The host route for the 192.168 address is not needed and can better be left out, the default route is all you need as the nexthop on both is the same.