Features Not Supported for a FireCluster

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

FireCluster Network Configuration Limitations

  • Spanning Tree Protocol is not supported for FireCluster.
  • 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.
  • 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.
  • Modem interfaces are not supported for FireCluster.

FireCluster Management Limitations

  • 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.

Virtual Machine (VM) Limitations

VMware does not send traffic from clients on the same ESXi host as a cluster member to the other cluster member on a different ESXi host. For more information, go to Configure a FireCluster on VMware ESXi.

Related Topics

About FireCluster

Supported Models for FireCluster

FireCluster Diagnostics