Create a Post
Showing results for 
Search instead for 
Did you mean: 

Maestro SG Missing OS route

We are having some problems with our VSX gateway in a Maestro setup. One of the VS's is setup as a VPN concentrator on a dedicated customer network and the other interface has a connection to some backend servers.

On a customer site there is a box that runs a Cloudguard IAAS version of a gateway that is connected to the smae dedicated customer network and will initiate the tunnel.

Hardware: MHO140, thsi SG has 1 x 5800 gateway

R80.20SP with JHF 258

VS VPN-concentrator has IP

Cloadguard GW has IP but has link selection set to static nat to IP

Packets arriving at the VS are dropped with the message in the log: Missing OS route

fw ctl zdebug drop shows this message:

fw_first_packet_outbound_init Reason: failed to get outbound interface;

Packet trace from the vs0 shows packets :

Inbound packet:

BPEth0[in ]: vlan 3620, p 0, ethertype IPv4, > isakmp: phase 1 I #34[]
bond1.614[in ]: > isakmp: phase 1 I #34[]

Outbound packet:

wrp321[out]: > isakmp: phase 1 I #34[]
wrpj321[in ]: > isakmp: phase 1 I #34[]
bond1.614[out]: > isakmp: phase 1 I #34[]
bond1[out]: > isakmp: phase 1 I #34[]
eth1-10[out]: > isakmp: phase 1 I #34[]
BPEth0[out]: vlan 1033, p 0, ethertype IPv4, > isakmp: phase 1 I #34[]
ethsBP1-01[out]: vlan 1033, p 0, ethertype IPv4, > isakmp: phase 1 I #34[]

All I can find with the failed to get outbound interface message was a SK about a bridged interface and a normal interface communication that was not properly working after an upgrade.

Regards, Maarten
0 Kudos
2 Replies

Hi Maarten,

Usually this kind of message is a result of interface being down. Because this is a VS there could be some corruption in the VS itself. As the first step verify that the interfaces are up. Push configuration to the VS again (open the VS and hit ok) and install policy. If the problem persists, I would open an SR (try rebooting the gateway as well).


0 Kudos

I had restarted the VS separately and I also restarted the complete VSX gateway, but it did not help.

One of my colleagues was seeing a strange address in the route cache, after searching through the smartconsole for this address, he found there was a NAT for this address and the IP of the VS VPN Concentrator, as there was no default route, this address that was not in the routing table, could not be reached, hence the Missing OS route.

The NAT rule came from a policy that was imported a couple of months ago and overseen.


Regards, Maarten
0 Kudos