Address on loopback interface as a peer ip in FGSP protocol and speed of sync session
I have two FGCP clusters and FGSP beetwen it.
I have some questions:
1) Is it possible to use loopback interface and address on it as a peer ip on FGSP? When I use address on loopback interface as a peer ip session syncronization doesn't work, but when I change peer ip and use address on some connected interface session syncronization begin to work. For loopback I have created firewall policy, but it doesn't help.
2) Are there ways to speed up session sync process? I have 9k session and it's can take for 3-5 minutes.
Sure, I have connectivity, but it doesn't work. I have seen session sync it tcpdump, but when I use "diag test application sessionsync 6" it shows that peer is dead. On connected interface I haven't observed this.
I tested this in my lab and I dont think it will work since the session sync will be sourced from the outgoing interface, not the loopback interface. I received errors on the remote fortigate that the peer ip was not configured. The peer ip in question was the outgoing interface IP, not the loopback IP.
Yes, sync is sourced from the outgoing interface, not from loopback. I thought about it, but I haven't found logs with errors. I have connectivity exactly between loopback interfaces, but how use it as a source in the session sync I haven't found.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.