[PANORAMA][ERROR] Can't use export or push device config bundle feature

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

[PANORAMA][ERROR] Can't use export or push device config bundle feature

L2 Linker

Hello,

 

I got issues using the feature : Panorama > Setup > Operations > Export or push device config bundle.

I try to erase the local configuration of a PA-850 and push the Panorama configuration on it.

 

I got this error message when I click on push & commit :

 

 Capture.PNG

 

I would appreciate some help on this, does anyone already saw this error message before ?

 

Thanks for reading my post.

 

Best regards,

 

 

5 REPLIES 5

Cyber Elite
Cyber Elite

@SERMA-NES,

I mean it's kind of telling you what the issue is; the config bundle that Panorama is building is to large to push to a PA-850. It also appears as though you are leaving the default config for a smaller device which doesn't always work that wel.. 

 

Perform these actions. 

  • Panorama > Setup > Management, and go into Panorama Settings. 
  • Make sure that your 'SHare Unused Address and Service Objects with Devices' check box is not checked so that you only push the objects the config actually needs. 
  • Then perform a Panorama Commit.

you should then be able to push and commit to the pa-850 without issues. 

Thanks for your answer, but I already unchecked that checkbox.

I also unchecked the "Import devices' shared objects into Panorama's shared context" when you Import the device configuration to Panorama.

 

The PA-850 is a physical appliance so there should not be any storage issues I guess.

The Panorama is a VM with 4 CPU / 4GO RAM / 80GO Storage which seems enough to me.

 

I find really few informations on internet and I don't really know where to investigate at this point.

Panorama running on 4GB of memory ...

This could be completely unrelated, but there are a plethora of issues with underspecked installastions of VM Panorma.

 

Ajaz

@SERMA-NES,

How many firewalls are you managing? 4GBs of RAM is fine if you are managing a relatively low number of firewalls and your configs aren't that large. Palo Alto says that you can get away with up to 10 with 4GBs, in practice I would put that number closer to 5 before I tell people to bump it up simply because I don't know the size of the configs that people are working with. 

It looks like I solved the issue.

I had to upgrade my Panorama in 8.0.4 because I needed to add a FW which is in 8.0.3.

I still had the same issue with this new FW but I had a new error message refering to Device Groups.

So, When I imported the configuration, I modified the name of the Template and the Device Group which is the Firewall name by default.

 

With that custom name, It works.

 

I'm not sure of what happened but now it is working.

 

Thank you for your help !

 

 

  • 5437 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!