Virtual Standby member cannot reach internal DNS or Internet

[Jan_Kleinhans]

Hello,

after upgrade to R80.40 HFA 48 we encounter the following problem.

If the standby member of a VS (VS2 for example) tries to reach a system, for example the internal DNS, it doesn't work.

In the log we can see, that the package doesn't get send from the interface of the virtual machine but gets send out from an interface of the VS0 (in this example the Mgmt interface).

So the standby member has a Threat Emulation Error because it cannot reach the DNS or something else.

When we change the standby member to active state we get "Firewall - Domain resolving error. Check DNS configuration on the gateway (0)" errors in the log and have distorted internet access. The new standby member has now the same issue as the old standby member and cannot reach any address. If the new standby member will work as expected after some time we did not test as is was in production.

Has anybody else such a problem?

Best regards,

Jan