Add layer 3 physical interfaces to Firewall Clusters
To route traffic through the Firewall Cluster, you must define at least two layer 3 physical interfaces.
- An interface used for communications between the Management Server and the Firewall.
- An interface for the heartbeat communications between the cluster nodes. The heartbeat traffic is critical to the functioning of the cluster, so it is highly recommended to have a dedicated heartbeat interface.
Although you can configure more interfaces at any later time, it is simplest to add more interfaces right away. This action allows traffic to be routed through the Firewall. You can use the Cluster installation worksheet to document the interfaces.
- An interface that corresponds to a single network interface on each node in the Firewall Cluster. In the Management Client, the interface type is None.
- An aggregated link in high availability mode represents two interfaces on each node. Only the first interface in
the aggregated link is actively used. The second interface becomes active only if the first interface fails.
Connect the first interface in the link to one external switch and the second interface to another external switch.
- An aggregated link in load balancing mode represents two or more interfaces (up to eight interfaces) on each
node. All interfaces in the aggregated link are actively used and connections are automatically balanced between the
interfaces.
Link aggregation in load-balancing mode is implemented based on the IEEE 802.3ad Link Aggregation standard. Connect all interfaces to a single external switch. Make sure that the switch supports the Link Aggregation Control Protocol (LACP) and that LACP is configured on the switch.
For more details about the product and how to configure features, click Help or press F1.