Can't commit in Panorama 8.1.4

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Can't commit in Panorama 8.1.4

L2 Linker

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.

 

 

 

5 REPLIES 5

Cyber Elite
Cyber Elite

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

 

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization

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.

L2 Linker

Hi,

 

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

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

MP

Help the community: Like helpful comments and mark solutions.

L0 Member

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

  • 5850 Views
  • 5 replies
  • 0 Likes
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 LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!