Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
FK
Participant

Mgmt_cli limitation when publishing a large number of newly created objects?

Jump to solution

Hi CheckMates,

 

I have a question regarding mgmt_cli and limitation.

Is there a limit when publishing a large amount of newly created objects?

Let´s say you have a script which creates a network group for azure IPs with thousands of network objects.

Updatable objects is not an option -> 1400 appliances.

 

Thank you.

 

Greetings from Austria.

0 Kudos
1 Solution

Accepted Solutions
_Val_
Admin
Admin

You need to mind API time out error, which is 10 min by default. If you push a long list of objects, and the command takes more than 10 minutes to post, API will return an error. The best practice is to push in smaller portions, multiple times. If each POST is short enough, you should be okay.

View solution in original post

10 Replies
_Val_
Admin
Admin

You need to mind API time out error, which is 10 min by default. If you push a long list of objects, and the command takes more than 10 minutes to post, API will return an error. The best practice is to push in smaller portions, multiple times. If each POST is short enough, you should be okay.

View solution in original post

FK
Participant

Hi Guys,

 

thank you for inputs.

I will try to seperate it into smaller groups per publish.

 

Greetings.

Fabian

0 Kudos
Henrik_Noerr1
Contributor

This complicates rollbacks and revision control however. Not sure there is a great solution with the time it takes in general to communitate with the API on larger installations / changes

0 Kudos
Robert_Decker1
Participant

One solution is to increase the timeout on Apache server from default 10 minutes.

0 Kudos
PhoneBoy
Admin
Admin

The more changes you try to publish at the same time, the longer the process will take.
If you’re making a bunch of changes at once, it’s generally recommended to publish every few hundred changes or so.

0 Kudos
JozkoMrkvicka
Leader
Leader

Is there some easy way how to force publish to be done once number of XY changes were done in one session ?

For example, I want to automatically publish 50 changes if performed in the same session.

If I did 160 changes in the same session, the first publish will be done after first 50 changes, next publish after next 50 changes (100 changes already done). The last 10 changes will be handled by "manual" publish.

Kind regards,
Jozko Mrkvicka
0 Kudos
PhoneBoy
Admin
Admin

On the API side of things? No.
You would have to handle that in the logic of your script.
You can commit with each mgmt_cli invocation by using -r true, however that incurs a lot of extra overhead (login/do/commit/logout with each command).

0 Kudos
Tomer_Noy
Employee
Employee

I would seriously consider upgrading the gateways to newer hardware (1500 appliances) in order to use the Azure Updatable Objects.

For anyone that is coming across this thread, it's a simple as choosing it in the Access policy:

 

Azure Updatable Objects.png

Filling your management with thousands of network objects and huge network groups isn't good practice and might introduce future slowness in some scenarios beyond the challenge of the initial publish via API.

0 Kudos
Robert_Decker1
Participant

100 changes per publish is recommended.

Same goes for group members.

FK
Participant

Thanks for this info.

0 Kudos