MX L3Firewall Push Method ?

[Abdul-USA]

Hello Community,

I am novice API + Python user. My objective was to update an existing Layer 3 Firewall rule for an Organization that has over 100 sites(MXs), we ended up doing it manually. I tried to test the API Python script but it has only "Put method". It was not updating my existing rule, instead it was over-writing it. Is there away that I can update an existing L3Firewall rule let us say there 100 rules and I want to add 2 more rules to make it 102 rules. How can I do this?

Your help is appreciated here and if someone has a template for this and would like to share, please let me know. This is my very posting in this community but I always read stuff from here to rich my skillset and kudos to the contributors here !

This is the link I used for reference when I created my code for a single device test lab. The only difference was of-course the Network ID and my API. The script works but I run to the above mentioned issues.

https://developer.cisco.com/meraki/api-v1/#!update-network-appliance-firewall-l-3-firewall-rules 

Regards,
Abdul

[RaphaelL]

Hi ,

it's pretty simple. You have to GET the current rule base then append your changes and then PUT. 🙂 

You can't simply ''add'' , ''remove'' or ''edit'' a rule. You edit the ruleset then push it.

[Abdul-USA]

Hi Raphael,

Thanks for the quick response, I understood what you meant but that is not a solution to my problem which is not scalable, if I do that way. I hope there is either work around or Meraki will implement a method that does update an actual existing rule. I wish they had a way to add a rule ID # to differentiate the existing rules so that I can say this is rule # xyz from the list and boom the problem solved 😀.  

[RaphaelL]

I agree with you. You will have the same issues when looking at the syslogs , you can't filter a firewall hit by rule ID.

[PhilipDAth]

That's not that hard to do.

When you retrieve all the rules, the can call the first rule #1, the second rule #2, etc.

You can also use the rule description and add your own tag.  For example, you could use a description "workstation", then to do a change, get the rules, update the one with "workstation" in the description, and then put it back.

There are no issues with scale.  There might be an issue with how the rules are organised to make updating them easy ...