Skip to content

These scripts allow you to unBind a MX template from a templated network WHILE it's in production with minimal impact to client traffic.

License

Notifications You must be signed in to change notification settings

ez1mm/templateBreaker

 
 

Repository files navigation

templateBreaker

Meraki Template Tools

These scripts allow you to unBind a MX template from a templated network WHILE it's in production with minimal impact to client traffic.

The script creates a new network with identical settings (addresses, ports, firewall, trafficshapping, autoVPN, etc) as the templated network and moves the hardware into the non-Templated network preserving the original. It'll also ensure the firmware matches on the destination network so your MX/Z3 device will have minimal client impact. In testing, the local outtage wasn't noticable and the autoVPN outtage was <20seconds.

./unbind.py <networkID> - This unbinds a network where the networkID is a network that is currently BOUND to a template. (MX currently)

./rebind.py <networkID> - This reverses the unbind script, where the networkID is the networkID of the templated network (same used in unbinding) (MX)

./move.py <networkID> <target_TemplateID> <destination_OrgID>- This moves a network from one template, into another template. Preserving all settings. (MX/MS/MR/MV/MG) NOW SUPPORTS CROSS-ORG and NAMED SEARCH

**Named example:** ./move.py "Test Network" "Template-A" "ProductionORG_1"

About

These scripts allow you to unBind a MX template from a templated network WHILE it's in production with minimal impact to client traffic.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Python 100.0%