@PhilipDAth those limits I know. I mean the limits of that specific call. For example with a batch job you can only do 100 changes in 1 API call. But that limit of how many is unknown to me for this specific call. ... View more

Created an Ansible script to do this. Just couldn't find the limits of the concurrent objects that could be changed. So created a loop with enough retries to accommodate the API limits of Meraki I hope 🙂   - name: Get organizations cisco.meraki.networks_info: meraki_api_key: "{{ meraki_api_key }}" organizationId: "{{ meraki_organizationId }}" perPage: 1000 total_pages: -1 register: meraki_networks   - name: Update FeatureTiers ansible.builtin.uri: url: "https://api.meraki.com/api/v1/administered/licensing/subscription/networks/featureTiers/batchUpdate" method: POST body_format: json headers: Accept: application/json X-Cisco-Meraki-API-Key: "{{ meraki_api_key }}" body: items: - network: id: "{{ Network['id'] }}" productTypes: - productType: appliance featureTier: advantage isAtomic: true register: uri_output retries: 20 delay: 5 until: "uri_output.status == 200" loop: "{{ meraki_networks['meraki_response'] | list }}" loop_control: label: "{{ Network['id'] }} - {{ Network['name'] }} - {{ network_idx + 1}} out of {{ meraki_networks['meraki_response'] | length }}" loop_var: Network index_var: network_idx   ... View more

I see the logs on Meraki being flooded by the following message. Does anybody experience the same?   Switch 1 R0/0: linux_iosd-image: Number of IPC messages held in the application reached the maximum channel threshold. IPC channel 'ngwc fed bipc': ipc_ctl_id 49 (ipc_fd 132, seq_num 210), curr IPC msg hel in appl 49415 ... View more

I upgraded my first 9200-48P in a lab environment. When you have you're network set to 17.18.1 in the Meraki Dashboard and you're switch is running 17.15.3 you don't have to upgrade before adding it in Cloud mode on the Meraki Dashboard. Onboarding works with 17.15.3 and it automatically upgrades the firmware for you. ... View more

aaa new-model aaa group server tacacs+ GROUP_TAC server name TAC-AUTH1 server name TAC-AUTH2 aaa authentication login default local group GROUP_TAC aaa authentication login MERAKI local aaa authentication enable default enable group GROUP_TAC aaa authorization config-commands aaa authorization exec default local group GROUP_TAC if-authenticated aaa authorization exec MERAKI local aaa authorization commands 15 default group GROUP_TAC if-authenticated aaa authorization commands 15 MERAKI local aaa accounting update periodic 3 aaa accounting commands 15 default start-stop group tacacs+ aaa session-id common ... View more

@Ryan_Miles is there any update on this topic? ... View more

It only supports OSPF on the LAN side of the MX when using single-LAN settings. But it only supports AutoVPN route distribution to Layer3 uplink devices. It does not learn routes from the Layer3 device.   https://documentation.meraki.com/MX/Site-to-site_VPN/Using_OSPF_to_Advertise_Remote_VPN_Subnets   If you want bidirectional routing you need to use BGP as mentioned above. ... View more

How much time is between when working fine till not working at all? The most equipment we are still using today is the MX68 but are looking to move over to the MX75.   ... View more

You need to have SD-WAN+ to utilize SD Internet. This is what you are describing.   https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MX_Security_and_SD-WAN/SD-WAN_Internet_Policies_(SD-Internet) ... View more

From the 17.15.3 version there is a new way of management called Hybrid Mode. This is also a configuration change on the switch it self. With that you gain additional features in the dashboard.   https://documentation.meraki.com/MS/Cloud-Native_IOS_XE/Upgrading_Cloud-Monitored_Switches_to_Hybrid_Operating_Mode   Probably that is the reason you can't upgrade directly, because it requires an change in Management. The bug you speak of was in the with the Cloud-Native IOSXE version for the MS390, C9300(X) and C9200L versions for management in the Meraki Dashboard. ... View more

Good morning @Brash    We use a lot of reasonable dynamic packing tables. Every packing table has at least 1 Thin Client and 2 printers connected to it, but it can go up to 4 printers connected. To keep the cables in the patch cabinet as low as possible we chose to use the MS130-8 connected to the back of a packing table to distribute the devices on this table.    It also gives us the flexibility to assign different vlans to Thin-Clients and printer, or to add additional security by 802.1x for example ... View more

Also the C9300 switches are running the Cloud Native IOS-XE 17.15.3 ... View more

Must say I was steadily upgrading al networks to this firmware version. Everything was working correct till last Friday. An upgrade of the MS390 to this version failed. Now I have 2 dead switches. Maybe that's the reason I don't know. Seems like the troublesome MS390 will not end and this moment.  Working on RMA for that one though.    - Reboot not working - Factory reset not working - RMA pain in the ass at the moment   Luckily the switch with the most AP's is still working. ... View more

I see this firmware has been removed from the dashboard. Any reason why? ... View more

I'm already running several locations on this new firmware. I would say this looks good, also for the MS390 switches. You finally have an console for show commands. ... View more

Had a case with Meraki to fix this. Essentially I did add them via the old way again and removed it afterwards. Then I was able to add them again using the new way. ... View more

I've got Hybrid mode now available for my org. I migrated a stack of 4 switches to hybrid mode from cloud-monitoring mode. First of all it's a very easy process. as stated I added only the active member (in my opinion the stack master) to the network. But then the other switches aren't added at all. Does anybody know how this works? I tried to add a stack member later, but it failed to add and gave some ssh errors.   Also the device tracking and monitoring commands aren't added to the stack member switches. ... View more

Migrating back to Cat9k mode took about 7 minutes. Than you have a factory default switch you need to reconfigure.  Re-configuring is easy when you have a backup config ... View more

@Jeff-Lthe thing is, Our organization was enrolled in the private beta testing this before. So I already have several switches in this Org running in Hybrid mode. That is why in my understanding it was already working in my org. ... View more

According to my Cisco Account manager this shouldn't be possible. They want me to contact support again to see what is happening. ... View more

We've got a whole bunch of 9200s that  would love to have in Meraki mode. I want to wait what Cisco gives me back on this before I go forward moving all 9200s from the old Cloud-Monitored mode to Hybrid mode, because if it failes more I would seriously have a problem. Now I've got enough spares to swap this one. ... View more