Profile

Yes, can someone walk me through this resolution, I am currently facing the same issue too. How can i resolve this? ------------------------------ Thomas Lim IT Consultant NCS Pte. Ltd. Singapore ------------------------------

Hi Jaired, Single MX deployment works without issue. Yes wondering if community have experience any issues deploying MXHA in AWS too. The CFT didnt ask for the DNS name of the ELB. The CFT will create the ELB. I think the statement is for gateway registering to MX ------------------------------ ...

Hi Jaired, No, currently only testing on the MX. During the selection of DAM products, I only select DAM MXHA (BYOL) Yes I have created a internet gateways for the vpc that hold the Imperva MX. While I look at the "impctl show logs" on the MX, it said Secure password not sync ...

Hi Jaired, Yes, but I am using Imperva DAM 14.10.1.10 Cloud Formation Tool And I noticed everytime the stacks will stop at MxWaitCondition. Causing the CFT deploy MX to not running and the ha status is not running. Below is the "impctl show log" right after the ...

Hi, We deployed 2 AVM150 Imperva MX in AWS and require to install high availability. When i input the command (impctl server ha install), it require mandatory parameters --elb-name. And after i input a network load balancer (listener TCP1234, Healthcheck TCP 50007, Target on the ...