Search Imperva Community for
Hope you are fine.Let me try to explain each of the messages, in summary all of them are addressing performance problems, I recommend you to open a support case.
MX fetches GWs' counters every x minutes and calculates status of the gateways at a certain period. Each indicator is scored (OK/Warning/Overloaded/Unknown) per given time period.
There are 5 indicators which impact GW status.
Number of Samples in 15 minutes intervals are taken into consideration. If all of the intervals indicates same status (different than current) a change of status is made in the system events.
You may already have seen it but if not please check below link.
It's likely you are seeing the status of the GW changing when it is unable to communicate correctly with the MX when any of the parties are under heavy load.
The reason for this could be due to
- Connectivity issue- GW is busy and failed to respond the request messages.- MX is busy with other jobs.
In general:* The MX check if the GW is alive or not every 30 seconds and do this 4 times.* After 120 seconds if there were no response from the GW; the MX will change the GW status to Disconnected.
Alert on MX "Gateway Unresponsive" seen mainly when not responding on ssh. There may not be any capacity issue on the gateways even unresponsive alert is received. This might again related to MX busy with other jobs, also could be network issue. Most of the time this message is received when there are "connection timed out" messages for the isAlive packets.
On top of all the explanations when you see these kind of alerts and please feel free to open a case, support will investigate the logs and find the root cause of the alerts.
or Contact Us
Copyright @ 2019 Imperva. All rights reserved