@chengineer : It worked, thank you one more for your help. ... View more

Hey , @chengineer That is the difference from me a script kiddie and a pro :-D. Thank you very much for talking the time to answer me. No problem, I did ask the question a couple of hours after the presentation was over. 😉 And I don't expect to get a reply the moment after I post something :-D. I will check up on that, but I think that is the problem. I remember that under the 0.32 installation, I did copy something to that library. Regards, kruse ... View more

Hi,   Attended the seminar, and I really liked it 🙂   One thing, when I try to use the new API, I get this error:   AttributeError: module 'meraki' has no attribute 'DashboardAPI'   I get the error when I try run the example script: New_Client_Listing.   This is an example code I am running, and the same error: api_key = 'A_API_KEY' import meraki m = meraki.DashboardAPI(api_key) orgs = m.organizations.getOrganizations() print(orgs)   Sure I am doing something wrong here, but what? Can you point me in the right direction. I have upgraded the 'Meraki' module from 0.32 to 0.70.4 with pip3 install --upgrade.   Thank you ... View more

Hey,   Sorry for the long reply, but are on vacation right now, and I do not login that frequently   No problem. Link away :-).   Just so I understand: You use the same VLAN throughout the network, but lets users (Only you?) add the VLAN based on the device IP address?   -kruse ... View more

Hey Denis,   Lot of water under the bridge since then :-D. I don't remember exactly what I did, and I have deleted (By accident) the old script. But from what I can remember, I managed to get the Python code to read a comma separated Excel sheet, and add the VLANs one by one using loops. It was not fast, but compared to doing it via the dashboard, it was blazing fast 😄 😄   I have not seen any being able to creating multiple VLANs in one go, even on the same device. Maybe it can be done, but I don't see how, actually, as there are no 'bulk' VLAN creation in the API, as far as I know.   BTW: I will do it in another way today, as back then I was using JSON to contact the API. Today I have installed a Meraki library, and calls that when I what to use the Meraki API. Much easier, and I do not have to keep track when Meraki updates their API. I am using this right now, but there are others:   https://github.com/meraki/dashboard-api-python   I have been looking at this: https://github.com/meraki/meraki-python-sdk, which have a build in function allowing it not to flood the API, and thus avoid your script from failing if you get to busy; i.e. making to many calls per sec. From the tests my colleague have made, it is also a little bit faster to use again maybe because it is not flooding the API.   I was creating a lot of VLANs on a MX, and I must warn you: When you reach a certain number of VLANs on the MX, the dashboard and the browser becomes very slow; i.e. very long response times. I don't know what exactly is going on, but I think it is because the browser tries to load all the information at once, and that takes time. Mind you I created more than 300 VLAN interfaces on the MX, and maybe you will create less so you will not have that problem. It is running fine, with DHCP and all; it is just the webpage that loads slowly.   Br Kruse   ... View more

Hi, Thank you for your reply and for the update 🙂 I managed to get it to work, but not using the form-data; using the raw in JSON format, as you do 😉 This 'shard' ID, will that always be the same for the organization/network I am trying to configure? Is there some way that I can see it, using Postman, like I can see (GET) organizations/network ID's using Postman? Again, due to my lack of knowledge; can I POST (Again using Postman) multiple VLAN in the same call? E.g. I have 25+ VLAN I need to deploy. It is a hassle to do it via the dashboard, but if could do it via Postman (Like I can in Putty) it would help a lot 🙂 ... View more

Hi, I see the same problem; POST request is just sitting there and not going anywhere. GET works fine. I have tried with cURL(I have removed KEY and NETWORK id): curl --request POST \ --url 'https://dashboard.meraki.com/api/v0/networks/<network>/vlans' \ --header 'content-type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW' \ --header 'x-cisco-meraki-api-key: <key>' \ --form id=856 --form name=Test2 \ --form applianceIp=172.17.255.1 \ --form subnet=172.17.255.0/24 and this works fine. I also imported this cURL stuff into Postman; still no luck :-/; POST still . I guess I am doing something wrong, but lack the knowledge to find the error. If anybody could point me in the right direction, it would be much appreciated :-). I think I need to configure something in Postman; some environment variables maybe, but I am not sure. There is also missing the 'id' key in the 'add vlan' Postman collection from Meraki ;-). Remember to add that. ... View more

Yes it would, sorry 😉 ... View more

Hello hinewwiner,   Looking at your design, I have the following suggestions:   1) As PhillipDAth write use the vMX100 in the AWS. You will ned to pay for the license, of course, but also for the server itself. You can take a look at this document. It explains in detail what you need: https://documentation.meraki.com/MX-Z/Installation_Guides/vMX100_Setup_Guide_for_Amazon_AWS   2) You might consider using the MX65 (Not W). The MX65 has 8 regular Ethernet switch ports and two additional PoE ports for external AP's. One AP would be more than enough for 15 people, unless they are placed on different floors ;-). MR42 is a nice all-round AP. Using the switch ports on the MX65 together with the MR42, will enable you to use the EAP-TLS or PEAP fully. This is not possible with the build-in AP in the MX64/65. Also it will be somewhat easier for you to configure guest access. I know that Meraki together with Cisco ISe, has a lot of functionality. Take a look at this document: https://communities.cisco.com/docs/DOC-68192. You can download the ISE as a VM-image and try it for 90 days.   3) The traffic will flow to the HUB, in this case the MX84, and then further on to the AWS. So the MX84 will be single point of failure, unless you configure two hubs: the MX84 and the vMX100. Add them in the list on the spokes, with the MX84 as the first one. If this one fails, the spokes will connect to the vMX100. Just a suggestion ;-).   4) Make sure you do a proper site survey when installing the AP's. This will ensure you have a good user experience, when the network goes live. Nothing more cumbersome, than users complaining all the time ;-). Also, if the environment is dense, in terms of your own AP's and neighbour AP's, or you live close to the harbour/airport, you might want to use smaller channels 20/40MHz and disable DFS. Configure band-steering and disable 802.11b devices. This is also not possible in the 64/65W   5) The client-VPN should work just fine. I think if you use the default Meraki authentication, it is PEAP-MSCHAPv2, but I am not sure. It is if you use the default Meraki authentication together with the MR. I have heard that EAP-TLS is supported with the client-VPN, but this somebody else have to verify. Again EAP-TLS is supported if you use it together with the MR.   HTH -kruse ... View more