Imperva Cyber Community

Hi there,

A customer has 1 MX and 3 GW (Clustered).  They wanted to install DB Agent to another 8 Database servers on another location.  They had been advised to make sure that connectivity between the gateway to the DB servers with port 5555 and 443 to be open.

They mentioned that they are able to test the connectivity from the DB to GW and it end at GW with no response back from GW to DB servers.  What can be the cause of this ? anybody had come across this before and how you are able to resolve this.

#DatabaseActivityMonitoring

------------------------------
Edwin Ng

------------------------------

Hi Edwin,

Your cluster network is Dual or not? If it is Dual network cluster, your problem is similar to that topic https://community.imperva.com/discussion/dam-agent-interface-not-reachable. I think you need to add back-route to DB networks on all gateways.

Hi there,

A customer has 1 MX and 3 GW (Clustered).  They wanted to install DB Agent to another 8 Database servers on another location.  They had been advised to make sure that connectivity between the gateway to the DB servers with port 5555 and 443 to be open.

They mentioned that they are able to test the connectivity from the DB to GW and it end at GW with no response back from GW to DB servers.  What can be the cause of this ? anybody had come across this before and how you are able to resolve this.

Hi Cezmi Cal,

What do you mean by dual network cluster?  btw the "https://community.imperva.com/discussion/dam-agent-interface-not-reachable" not accessible.

Can advise me how to to add back-route to DB networks on all gateways..

Thank you.

B. Regards

Hi Edwin,

Your cluster network is Dual or not? If it is Dual network cluster, your problem is similar to that topic https://community.imperva.com/discussion/dam-agent-interface-not-reachable. I think you need to add back-route to DB networks on all gateways.

Hi there,

A customer has 1 MX and 3 GW (Clustered).  They wanted to install DB Agent to another 8 Database servers on another location.  They had been advised to make sure that connectivity between the gateway to the DB servers with port 5555 and 443 to be open.

They mentioned that they are able to test the connectivity from the DB to GW and it end at GW with no response back from GW to DB servers.  What can be the cause of this ? anybody had come across this before and how you are able to resolve this.

Hi Edwin,

you could not reach the page because of the dot (.) located at the end of link. I edited the post and corrected the link, you should reach now. I described adding back-route at that discussion post.

info about dual network cluster -> https://docs.imperva.com/bundle/v14.17-database-activity-monitoring-user-guide/page/6536.htm

Hi Cezmi Cal,

What do you mean by dual network cluster?  btw the "https://community.imperva.com/discussion/dam-agent-interface-not-reachable" not accessible.

Can advise me how to to add back-route to DB networks on all gateways..

Thank you.

B. Regards

Hi Edwin,

Your cluster network is Dual or not? If it is Dual network cluster, your problem is similar to that topic https://community.imperva.com/discussion/dam-agent-interface-not-reachable. I think you need to add back-route to DB networks on all gateways.

Hi there,

A customer has 1 MX and 3 GW (Clustered).  They wanted to install DB Agent to another 8 Database servers on another location.  They had been advised to make sure that connectivity between the gateway to the DB servers with port 5555 and 443 to be open.

They mentioned that they are able to test the connectivity from the DB to GW and it end at GW with no response back from GW to DB servers.  What can be the cause of this ? anybody had come across this before and how you are able to resolve this.

Hi Cezmi Cal,

Not sure where in the discussion post where you described how to add back-route to DB networks on all gateways.

Possible to show me the steps.

Thank you

Hi Edwin,

you could not reach the page because of the dot (.) located at the end of link. I edited the post and corrected the link, you should reach now. I described adding back-route at that discussion post.

info about dual network cluster -> https://docs.imperva.com/bundle/v14.17-database-activity-monitoring-user-guide/page/6536.htm

Hi Cezmi Cal,

What do you mean by dual network cluster?  btw the "https://community.imperva.com/discussion/dam-agent-interface-not-reachable" not accessible.

Can advise me how to to add back-route to DB networks on all gateways..

Thank you.

B. Regards

Hi Edwin,

Your cluster network is Dual or not? If it is Dual network cluster, your problem is similar to that topic https://community.imperva.com/discussion/dam-agent-interface-not-reachable. I think you need to add back-route to DB networks on all gateways.

Hi there,

A customer has 1 MX and 3 GW (Clustered).  They wanted to install DB Agent to another 8 Database servers on another location.  They had been advised to make sure that connectivity between the gateway to the DB servers with port 5555 and 443 to be open.

They mentioned that they are able to test the connectivity from the DB to GW and it end at GW with no response back from GW to DB servers.  What can be the cause of this ? anybody had come across this before and how you are able to resolve this.