Cluster
For High Availability
Last updated
Was this helpful?
For High Availability
Last updated
Was this helpful?
DDOS Protection support high availability, for two compatible DDoS Protector devices to operate in Active – Active, Active – Passive, Cluster mode.
Stack > Instance > Instance Name > HA
User can configure as per requirement
Click on Save Settings
Primary Instance
String
--
HA Mode
Drop down
None
HA Port
Integer
11211
Peer check Interval
Integer
2
Peer failure threshold
Integer
2
Peer recovery threshold
Integer
1
Max Allowed Flaps
Integer
6
Enable Bandwidth Monitoring
Boolean
False
Minimum Bandwidth
Integer
1024/10
Link Monitoring Interval
Integer
100
Minimum Active links
Integer
0
Specify the default instance from the drop-down that will have an active mode on start-up
Specify the high availability mode between multiple mitigation instances
Specify port over which mitigation instances communicate with each other
Specify the time (in sec) after which one mitigation instance checks the health of its peer
Specify the number of failed peer health checks after which a mitigation instance considers its peer unhealthy
In some situations, two mitigation instances may Allowed keep changing their state from active to inactive. A Flaps flap is counted when the instance leaves the active state. This can result in poor network performance and can disrupt normal traffic flows. Specify allowed number of flaps after which the primary instance goes into hardware bypass
Specify if bandwidth monitoring should be used to trigger fail over in the HA cluster
Specify minimum bandwidth (in bps) for a specified interval (in sec) below which fail-over is triggered
Specify the interval in milliseconds (ms) for periodic link monitoring between multiple mitigation instance
Specify the minimum allowed active link pairs below which the solution will mark itself down
