Note the following deployment limitations in this release.
To maintain high availability and data consistency, create clusters with three broker nodes.
Clusters with two broker nodes are not recommended.
DHCP is not supported on the submission or cluster interface.
IPv6 is not supported on the management interface, cluster interface, or submission interface.
On an Email Security — Server Edition sensor, ether2 cannot be used as both the submission interface and the URL Dynamic Analysis interface.
A node must be removed from the cluster before you change its cluster interface or hostname.
In the Create New Cluster or Edit Cluster wizard in the Central Management Web UI, it is recommended that you perform the "move node to cluster" and "remove node from cluster" actions on no more than three nodes at a time.
Do not upgrade an individual node if it is currently part of a cluster. Use the upgrade orchestration procedure described in Upgrades to ensure that at least one broker and one compute node are running during the upgrade.
Transcontinental deployments are not recommended due to throughput, reliability, and latency issues.
Physical or virtual Network Security sensor limitations:
Jumbo frames are not supported.
Network Security High Availability is not supported.
The Essentials edition is not supported.
Virtual sensor limitations: See the Trellix Device Deployment Guide.