topic WIldFire status: Disabled due to configuration in General Topics

WIldFire status: Disabled due to configuration

Erez — Thu, 25 May 2017 06:03:39 GMT

Hi PA community,

We have two 5060 appliances in active-passive HA mode.

We also have WF-500 as private cloud and "Cloudwildfire.paloaltonetworks.com" as public cloud.

We have a problem in one of the appliances (Whether she is active or passive):

test wildfire registration
This test may take a few minutes to finish. Do you want to continue? (y or n)

Test wildfire Public Cloud

        Testing cloud server wildfire.paloaltonetworks.com ...
        wildfire registration:         failed

Test wildfire Private Cloud

        Testing cloud server ********** ...
        wildfire registration:         failed

*******= Our private ip for WF-500.

show wildfire status

Connection info:
  Signature verification:        enable
  Server selection:              enable
  File cache:                    enable

WildFire Public Cloud:
  Server address:                wildfire.paloaltonetworks.com
  Status:                        Disabled due to configuration
  Best server:
  Device registered:             no
  Through a proxy:               no
  Valid wildfire license:        yes
  Service route IP address:

WildFire Private Cloud:
  Server address:                ************
  Status:                        Disabled due to configuration
  Best server:
  Device registered:             no
  Through a proxy:               no
  Valid wildfire license:        yes
  Service route IP address:

In the second appliance everything is ok.

(We have at least 20 rules with wildfire profile)

Any ideas?

Re: WIldFire status: Disabled due to configuration

TranceforLife — Thu, 25 May 2017 09:00:38 GMT

Not sure if this can help you:

https://live.paloaltonetworks.com/t5/Management-Articles/WildFire-Registration-Failed-With-Error-Disabled-Due-to/ta-p/52641

Re: WIldFire status: Disabled due to configuration

MohamedSharief — Thu, 25 May 2017 10:11:04 GMT

Got the same issue and the same article that @TranceforLife shared solved it but the only difference is that instead of file blocking profile I assigned a wildfire analysis profile to the security policy cause I'm running PANOS 7.1.x.

Regards,

Sharief

Re: WIldFire status: Disabled due to configuration

Erez — Thu, 25 May 2017 10:39:46 GMT

Thank you but we already have a 17 rules in the security policy that assignd to wildfire analysis profiles 😞

And The problem is only in one machine in the cluster. the second machine works fine and they have the same rules (it's active passive mode)

Re: WIldFire status: Disabled due to configuration

MohamedSharief — Thu, 25 May 2017 12:08:09 GMT

By any chance is it the Passive FW that have this issue?

Regards,

Sharief

Re: WIldFire status: Disabled due to configuration

MohamedSharief — Thu, 25 May 2017 12:58:03 GMT

You may get more info by running the below command then try to register again:

>tail follow yes mp-log varrcvr.log

Regards,

Sharief

Re: WIldFire status: Disabled due to configuration

ansharma — Thu, 25 May 2017 16:57:33 GMT

@Erez

Let's check with the service route as well. Make sure that is correct. If the active device is working but passive is not, that'd be it. Passive can only use management interface in this state. Active can use both mgt and data ports.

Regards,

Anurag

Re: WIldFire status: Disabled due to configuration

Erez — Mon, 29 May 2017 05:49:52 GMT

Thank you all guys.

The working appliance working whether it is active or passive.

The other aapliance doesn't work whether it is active or passive.

Re: WIldFire status: Disabled due to configuration

reaper — Mon, 29 May 2017 06:22:38 GMT

have you tried pushing a #commit force ?

if for some reason the config isn't pushed properly on the dataplane, this could happen

Re: WIldFire status: Disabled due to configuration

Erez — Mon, 29 May 2017 06:41:55 GMT

Sure. I've tried commit force and no luck 😞