topic HA Clustering session synchronization in General Topics

HA Clustering session synchronization

mateuszga — Thu, 21 Oct 2021 10:59:16 GMT

Hello!

I have some question about session synchronization in HA Clustering (geographic cluster). All firewalls in HA clustering use the first rule for traffic that should not match it, this only happens on geoclustered firewalls. Later, the rules are processed correctly, but the first one is always used, so I see incorrect traffic in the logs.
Example:
Policy "First": From TRUST zone and 192.168.1.1 src.address to UNTRUST zone 8.8.8.8 dst.address application any action DROP.
Log: From GUEST zone and 10.100.100.1 src.address to DMZ zone 1.1.1.1 dst.address action ALLOW used policy "First".

It doesn't make sense, but I did the configuration in the lab and it works the same there, I think it is related to session synchronization and flooding information about these sessions to the neighbors. However, I cannot find an explanation for this behaviour in the documentation. Can anyone explain it?

Regards!

Re: HA Clustering session synchronization

S.Cantwell — Sat, 23 Oct 2021 12:09:39 GMT

The only thing that comes to mind is that perhaps "First" is a negate rule.

So, if traffic is NOT coming from 192.168.1.1. to 8.8.8.8 then allow... policy log would show First.

Re: HA Clustering session synchronization

mateuszga — Mon, 25 Oct 2021 10:42:56 GMT

Hello.

Thank you for your answer.

Can you explain it more precisely? Yes, action for "First" rule is drop, rule log only on session end.

I can see this behaviour only in HA clustering members so it can be indication.