Here you can find a Cluster Gateway manual: https://docs.imperva.com/bundle/v14.7-database-activity-monitoring-user-guide/page/6516.htm
The best configuration is Dual Network Topology - Separate Agent.
- Gateway management interfaces should be in the same VLAN.
- The listeners' interface of gateways should be in a different VLAN than the management gateway interfaces.
- DB Servers can be in any different VLAN, but you must remember to add agent routing.
I suppose that GW's management interfaces could be in various VLANs, but I have never done a configuration like that.
------------------------------
Karol Gruszczynski
IT Security Expert
Trafford IT Sp. z o.o.
Warsaw
------------------------------
Original Message:
Sent: 11-28-2023 05:31
From: Charles Eapen
Subject: agent cross connection to Gateway
can the cluster be done between GW servers in DC and DR. Both are in different IP subnets.
------------------------------
Charles
Original Message:
Sent: 11-26-2023 08:37
From: Karol Gruszczynski
Subject: agent cross connection to Gateway
Hi,
During the agent registration, you have additional options to register the agent to the second gateway. But I read somewhere that this option will be unsupported or is no longer unsupported.
The best way is to configure Cluster Gateway or Large Cluster Gateway depending on the performance of your SQL server. You can decide/move the agents between the gateways.
------------------------------
Karol Gruszczynski
IT Security Expert
Trafford IT Sp. z o.o.
Warsaw
Original Message:
Sent: 11-24-2023 01:57
From: Charles Eapen
Subject: agent cross connection to Gateway
Is it possible to connect the agents in Datacenter DC to DR gateways also. Currently agents in DC are connected to Gateway servers in DC.
Agents in DR are connected to Gateway servers id DR. Both DC and Dr have S2S VPN network connectivity.
#DatabaseActivityMonitoring
------------------------------
------------------------------