Bienvenue Kayode.   I hope you'll feel right at home! ... View more

Welcome to the community @rafaelertel ! Great to have some people over from over at Airheads. It's always good to know what it's like on the other side of the mountain!   @MackerTekGary you're entitled to your own topic, you know! Welcome to the community nonetheless! ... View more

Here, have some kudos y'all!     ... View more

It uses SSL VPN doesn't it? So no, MX won't be able to help you there. At least not at the moment. ... View more

Welcome to the community! ... View more

With pleasure. ... View more

@Ljungan80 wrote:    I dont have the Corona virus, yet.  If you do, please don't come near my posts. 😋   Welcome to the community! ... View more

@alexmccarthy wrote: Sorry, forgot the fun fact.   I restore police motorcycles.   Feel free to pop over to www.policebikes.com.au  to see what the other half of my brain does! That's awesome. I have a major soft spot for police motorcycles. The American TV show Chips is also probably the seed that made me get into motorcycling.   Welcome to the community. ... View more

I meant, as far as I know, there is no API for packet capture. No .pcap, or anything else. ... View more

Cradlepoint is a WiFi client of the MR84 and it can't ping the MR84? ... View more

Perpendicular to the floor. ... View more

Maybe there are scripts that can convert 3rd party configs into API calls for Meraki. But I haven't seen any of those yet. ... View more

Welcome to the community!   Sounds like you guys are doing a noble job. Thanks! ... View more

Welcome to the community. Meraki is not a bad way to start in networking! ... View more

I wonder if you're using an older version of the module.   What version does it say in the project settings (where you add the meraki module)? I'm using 0.80.3.   Also, what version of Python are you using?  I'm using 3.7. ... View more

This should get you a bit further. I think you used an older method to create the dashboard object. It think that's why it wasn't showing the code hints (Dashboard() vs DashboardAPI())   import meraki from pprint import pprint as pp import csv ''' Utility functions to be made as we go ''' # This will get us all of our network ids def getNetworkIDS(inventory): network_ids = set() # a set keeps unique values for device in inventory: network_id = device["networkId"] if network_id is not None: network_ids.add(network_id) return network_ids # This will output our inventory as a csv file for further reading def dictToCSV(inventory): keys = inventory[0].keys() with open('inventory.csv', 'w', encoding='utf8', newline='') as output_file: dict_writer = csv.DictWriter(output_file, fieldnames=inventory[0].keys()) dict_writer.writeheader() dict_writer.writerows(inventory) # Start our API calls by creating a dashboard instance dashboard = meraki.DashboardAPI(api_key = "aaabbbbccccdddd12345678") # In order to access the modules, we need to use the __getattr__ function # It will return to us an instance of that module # Other modules include admins, base, clients, devices, networks, organizations, and ssids organizations = dashboard.organizations.getOrganizations() # Next we will get an inventory of our devices inventory = dashboard.organizations.getOrganizationInventory(1234567) network_ids = getNetworkIDS(inventory) print(network_ids) for network_id in network_ids: print(network_id, ":") print(dashboard.vlans.getNetworkVlans(network_id))   ... View more

Two things. First, I'd have a good look at the API reference to determine a plan that'll get you the information you need.   For example. You can find out what devices you have in the network by querying the inventory. That'll likely save you some other steps: https://www.apimatic.io/api-docs/meraki-api/v/0_6_0#/rest/api-endpoints/organizations/get-organization-inventory   To get the VLANs you'll need the following call: https://www.apimatic.io/api-docs/meraki-api/v/0_6_0#/rest/api-endpoints/vlans/get-network-vlans   That call needs the network IDs so you'll also need a list of networks. But as you will see, the inventory call also returned the network IDs of the devices, so you could compile a list from there.   Now for the actual code. I'd recommend to setup a Python project in PyCharm or something alike. As soon as you've imported the meraki module into it, it can start giving you code hints. That'll make everything much easier for you:   To do that, in short, you need to create a project in pyCharm and the key is to go to the project properties like this:   In there you can add the meraki library to your project like this:   You may also want to try to simulate your plan via Postman first... That will allow you to test the calls and see their results before actually starting the coding: https://developer.cisco.com/meraki/build/meraki-postman-collection-getting-started/   ... View more

Yup kind of. In python terms it's called unpacking. If you want more information about it have a look here: https://realpython.com/python-kwargs-and-args/#using-the-python-kwargs-variable-in-function-definitions ... View more

The function is actually expecting the parameters in a different way.   Try changing it to:   result = dashboard.mx_vlan_ports.updateNetworkAppliancePort(def_network,"3",vlan=400, accessPolicy="open", enabled = True, type="access",dropUntaggedTraffic=False)   ... View more

Indeed, what @ww said. In the case of the MX250 the maximum number of tunnels is 3000, so you should be fine with 800 Z1/3's.   Edit: @ww correctly pointed out to me that the maximum recommended number of tunnels for the MX250 is 1000. If your MX is using dual uplinks that means you'll need 2 tunnels per Z1/3. So 800 would result in 1600 tunnels. I still think you will be fine with the 800 as you'll still be under 3000 tunnels which is the max number of tunnels. ... View more