Connecting WildFire Private Cloud to firewall

L2 Linker

Connecting WildFire Private Cloud to firewall

When connecting WildFire Private Cloud to firewall (Device > Setup > Wildfire), It appears that we can only add one (1) appliance IP address. However with a cluster there's more than one appliance.

1) Should this be the management IP address of the Primary cluster member?

2) How does the Firewall know to send traffic to the other appliance(s) if/when the primary cluster member goes down?

3) If possible, how can you add multiple appliance IP addresses to the firewall? 

Community Manager

Re: Connecting WildFire Private Cloud to firewall

the controller node takes care of this, did you follow these steps:

Help the community: Like helpful comments and mark solutions
Reaper out
L2 Linker

Re: Connecting WildFire Private Cloud to firewall

@reaper I've read through the documentation to configure but must've overlooked this note:


WildFire appliance clusters push a registration list that contains all of the nodes in a cluster to every firewall connected to a cluster node. When you register a firewall with an appliance in a cluster, the firewall receives the registration list. When you add a standalone WildFire appliance that already has connected firewalls to a cluster so that it becomes a cluster node, those firewalls receive the registration list.

If a node fails, the connected firewalls use the registration list to register with the next node on the list.


Thanks for your help.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!