History for Threat Defense Virtual Clustering in a Private Cloud
Feature |
Minimum Firewall Management Center |
Minimum Firewall Threat Defense |
Details |
||
---|---|---|---|---|---|
MTU ping test on cluster node join |
20241030 |
7.6.0 |
When a node joins the cluster, it checks MTU compatibility by sending a ping to the control node with a packet size matching the cluster control link MTU. If the ping fails, a notification is generated so you can fix the MTU mismatch on connecting switches and try again. See: Clustering for the Secure Firewall 3100/4200, Clustering for Threat Defense Virtual in a Private Cloud, Clustering for Threat Defense Virtual in a Public Cloud, Clustering for the Firepower 4100/9300 |
||
Cluster health monitor settings |
20221213 |
Any |
You can now edit cluster health monitor settings. New/Modified screens:
|
||
Cluster health monitor dashboard |
20221213 |
Any |
You can now view cluster health on the cluster health monitor dashboard. New/Modified screens: |
||
Clustering for the Firewall Threat Defense Virtual on VMware and KVM |
Any |
7.2.0 |
The Firewall Threat Defense Virtual supports Individual interface clustering for up to 4 nodes on VMware and KVM. New/Modified screens:
Supported platforms: Firewall Threat Defense Virtual on VMware and KVM |