Meraki

lvsanita

Dear All, We managed to find out what is the problem. We have an existing network and we would like to shut that down and migrate all end users to Meraki. If the old router still advertises the IPs (user subnets) it won’t work over the new Meraki network too at the same time. This logical caveat will cause routing problems for the Meraki network and the end users won’t get internet connection. Therefore it’s essential to power off the old devices fist and disconnect from DHL network, only after that enable the VLAN given by DHL for the Meraki network, and then migrate the end users to the Meraki. Make sure that the VLAN is not enabled and not in use for more networks at the same time. In our case the routing problem was because we didn't do the cutover properly. I hope this is a lessons learn for others too. If you need any further information about the problem, you can turn to me, I am happy to share my experience in more details. I would like to thank you All who was trying to help me, I really appreciate. Kind regards, Anita

Adrian4 · ‎Oct 23 2024

hmmm, i may have to resort to that, thanks!

Red-Five · ‎Oct 22 2024

Helpful info. In my case, not all inventory items were expired for most orgs, but I have a couple that I can delete completely with this info. Thank you.

JoanaP · ‎Oct 22 2024

For Content filtering specifically, instead of adding the * wildcard for the *.outlook.com example, you will have to simply add the outlook.com to the blocked/allowed list. This will enable anything ending in outlook.com to be blocked or allowed. One thing to be aware is that the Allow list takes precedence over the Block list. You can see a breakdown of the process at this link: https://documentation.meraki.com/MX/Content_Filtering_and_Threat_Protection/Content_Filtering#Patterns_for_Blocking_or_Allow_Listing_Specific_URLs BR, Ioana

JoanaP · ‎Oct 22 2024

There is no global inventory across different organizations at the moment. As it was suggested, API might be helpful, for example with this call, which returns devices assigned to a network in an org: https://developer.cisco.com/meraki/api-v1/get-organization-devices/ One of the returned fields is the model of the device, which can help you identify the EOL devices. BR, Ioana

JoanaP · ‎Oct 22 2024

Yes, you can use the same license both on the MR18s and the MR36s. If you are using the Co-termination licensing model you won't have to move licenses from old devices to new devices, you will simply have to remove the unused MRs from the networks they are assigned to. If you are using the Per-device licensing model, you will have to unassign the license from the old device and reassign to the new device. BR, Ioana

JoanaP · ‎Oct 22 2024

Hi Samuel, You will have to open a case with Support and work to have 2fa disabled. Depending if there are other full admins in your organisation or not, there are two ways of recovering access to your account, which are detailed here: https://documentation.meraki.com/General_Administration/Other_Topics/Two-Factor_Authentication#Recovering_Access_to_Accounts_Protected_by_Two-Factor_Authentication BR, Ioana

Meraki

Community

About JoanaP

JoanaP

Community Record

Badges

Re: Internet is not working on Meraki network

Re: weird connection issue

Re: Removing a network disabled for non-payment.

Re: Wildcards in the Allow/Block lists

Re: Global inventory view

Re: Licensing for End of Support MR Appliances

Re: Traying to login my account without 2FA App config

Re: Wildcards in the Allow/Block lists

Re: Internet is not working on Meraki network

Re: Removing a network disabled for non-payment.