topic Re: Can't commit in Panorama 8.1.4 in General Topics

Can't commit in Panorama 8.1.4

jmarchant — Wed, 20 Mar 2019 19:17:36 GMT

Trying to add a new firewall into panorama, Im simply adding the serial number to the manageded devices and when I try to commit I get the following:

Validation Error:
deviceconfig -> system -> panorama-server constraints failed : Panorama server address cannot be the same as own management IP address
deviceconfig -> system -> panorama-server is invalid

I'm looking and I see no IP address that are the same.

Re: Can't commit in Panorama 8.1.4

reaper — Thu, 21 Mar 2019 10:47:08 GMT

the panorama's IP and the firewall's IP are not identical, right?

have you run a config audit to see the difference between running and candidate config?

can you try running a 'revert to running', then add the panorama IP and commit

Re: Can't commit in Panorama 8.1.4

jmarchant — Thu, 21 Mar 2019 13:03:16 GMT

Thank you for the response.

the panorama's IP and the firewall's IP are not identical, right? Correct, I think.... Can the Panorama MGMT interface be used for mgmt and log collection, device deployment and collector group information?

have you run a config audit to see the difference between running and candidate config? Shows in the running config panorama-server 10.1.X.X; in the Canidiate config it's deleted.

can you try running a 'revert to running', then add the panorama IP and commit. I have reverted to the running config, tried chaning something minmial like the hostname and commit and still get the same error.

Re: Can't commit in Panorama 8.1.4

RicardoNeira — Mon, 16 Sep 2019 14:48:03 GMT

Hi,

I´m have the same problem. Did you find any solution?

Re: Can't commit in Panorama 8.1.4

MP18 — Mon, 16 Sep 2019 15:00:48 GMT

I think.... Can the Panorama MGMT interface be used for mgmt and log collection, device deployment and collector group information?

YEs

which mode panorama is ?

if on panorama you do show systm info you will see that

Re: Can't commit in Panorama 8.1.4

RamonH — Mon, 23 Sep 2019 16:38:51 GMT

This issue is related to the Panorama configuration believing there is a secondary Panorama in the mix. Basically, the primary Panorama and the secondary Panorama devices can not have the same IP address. There are two ways to correct this issue in the CLI:

If you *DO* have a secondary Panorama in the mix:

> configure
# set deviceconfig system panorama-server <Secondary Panorama IP Address>

If you DON'T have a secondary Panorama in the mix, you can just delete the element altogether:

> configure

# delete deviceconfig system panorama-server

Proceed to commit after that and you are ready to roll.

-RH