Features Not Supported for a FireCluster

There are some Fireware configuration and management features that you cannot use with FireCluster.

FireCluster Network Configuration Limitations

For an active/active cluster, you cannot configure the network in bridge mode or drop-in mode.
For an active/passive cluster, you cannot configure the network in bridge mode.
For an active/active cluster, you cannot configure the external interface to use PPPoE or DHCP.
For an active/passive cluster, you cannot configure the external interface to use PPPoE in Fireware v11.8.x or earlier, or DHCP in Fireware v11.11.4 or earlier.
You cannot configure IPv6 address autoconfiguration or enable the DHCPv6 server on an interface.
You cannot configure IPv6 dynamic routing protocols (RIPng, OSPFv3, and BGP for IPv6).
The FireCluster for a wireless device can be configured only in active/passive mode when wireless is enabled.
For an active/active cluster, you cannot configure link aggregation interfaces.
Hotspot user lock out after a user session times out is not supported.
Mobile VPN with SSL connections to a BOVPN that terminates on an active/active cluster are not supported.
Access Portal is supported for Active/Passive FireCluster only.

In Fireware v11.8.x and lower, you cannot use Fireware Web UI to connect to a Firebox that is a member of a FireCluster.
In Fireware v11.9.x and higher, you can use Fireware Web UI to connect to a FireCluster, but you cannot use the Web UI to configure a cluster, or change the FireCluster settings.
You cannot use the Management Server to schedule an OS update for any managed device that is a member of a FireCluster.