ASA logging problem - not able to send logs to a remote server

[TheBelphegor]

Hi team, 

Hopefully someone help with the problem that I am facing for quite some time... So I have three ASA devices in three different locations (different parts of the world), also I have a logging server on Azure. The goal is to make all three ASA FWs send their logs to that logging server on Azure. 

I configured the same configuration on all three devices, and only one of the devices is sending logs to the remote logging server. 

Other FWs are not able to send logs, and when I do "show log" I get an output that the logging server is not connected?

Anyway I guarantee that everything is configured the same way on all devices, also everything is allowed, there is nothing that could stop the traffic from going to a remote logging server. 

Also, in the logs I can see the following: 

Routing failed to locate the next hop for TCP from identity: x.x.x.x

If anyone can help with this I would really appricate that. 

[balaji.bandi]

Make sure you have a route available to reach the Azure IP address from ASA source IP.

[TheBelphegor]

Hi BB, 

Thank you for your reply, I have a route to Azure, I can even reach that server on Azure from the server that is connected to inside interface on ASA... 

Any other suggestion?

[balaji.bandi]

Azzure is outside right? you should have a route outside?

until I am getting wrong, do you have inside extended to Azzure.

[TheBelphegor]

Hi BB, 

Yes, Azure is outside so this is how it looks like:

Azure - (VTI VPN) - DC ASA - (IPsec IKEv1) - onsite ASA 

Again the same configuration works for other ASA with the same setup. 

Output of the show logg command on the ASA where logging works:

Logging to inside 172.16.5.5 tcp/5514 Connected TX:3144701

Output of the show logg command on the ASA where logging is not working:

Logging to inside_data 172.16.5.5 tcp/5514 Not connected since Fri, 19 Feb 2021 17:50:37 CET

What do you mean inside extended to Azure?