Meraki

Make_IT_Simple · ‎Jul 8 2022

This KB may help to troubleshoot the issue: https://documentation.meraki.com/MR/Encryption_and_Authentication/RADIUS_Issue_Resolution_Guide

Make_IT_Simple · ‎Jul 8 2022

unfortunately, Meraki doesn't have a site that lists outages. Usually, when there is a major outage, someone from Meraki will create a post in the community. OR, you may create a case with support and they can let you know if this is something affecting multiple clients or just your organization. If the issue is only within your organization, it would mean that you would have to work with support to narrow down the issue to understand why the radius requests are failing.

Make_IT_Simple · ‎Jul 7 2022

It should be a simple task. Just power off both switches and make sure the stacking cables are properly connected, then connect them back. 410s are compatible with 40Gb so it should work as simple as that. Did you purchase the cables from Meraki? are they new? were they tested before? DM me the serial number of one of the switches.

Make_IT_Simple · ‎Jul 7 2022

The video has everything you need, if the stack doesn't come up, I would advise opening a case with support to doublecheck the switch's configuration or it could be a layer 1 issue. Which switches are you using?

Make_IT_Simple · ‎Mar 23 2022

This was a bad one. Meraki had multiple versions of this issue and I worked closely with Support in our LAB to help them gather data. It was affecting MS425 stack and stand-alone. They even had me test with a custom build to confirm their fix was working. At least in our environment, 14.33 did fix these abnormalities including our MS390 control plane issues which drove me crazy.

Make_IT_Simple · ‎Mar 23 2022

Please give it a try and update the post. good luck

Make_IT_Simple · ‎Mar 23 2022

I think your MX was failing to upgrade to 16.16 that's why it was rebooting. This is a known issue with MX100 if there is an upstream device using an SFP or media converter. This issue was fixed in 17.6.

Make_IT_Simple · ‎Mar 23 2022

This would be a feature request at the moment. If Meraki has enough feedback, they may think to have new generation MXs with 3 or more WAN ports. On the other hand, even if they are planning to release something in the future, they won't be able to announce it publically. This could also be a software/hardware limitation. BUT, it would be great to have more than 2 WAN interface because cellular sucks 🙂

Make_IT_Simple · ‎Mar 23 2022

how many users connect to this MX64? do you see the same problem with other computers connected from other physical locations?

Make_IT_Simple · ‎Mar 23 2022

Meraki MXs don't support port-channel and yes the MX will allow you to use IPs from the same subnet. But what is the point of using both wan interfaces if they will eventually through the same gateway?

Make_IT_Simple · ‎Mar 22 2022

Disconnect anything behind the firewall and only connect your computer, run a speed test. If the speed is OK, it could be a problem with your LAN and you can confirm that with iPerf: https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Troubleshooting_Client_Speed_using_iPerf If the speed is bad behind the firewall, make sure the firewall is negotiating full-duplex and at least 100 Mbps. replace the cable and start from there.

Make_IT_Simple · ‎Mar 22 2022

I am not sure why you are not able to get to the AP from your computer, but I am doing the same thing and I can get to the local page. Maybe something upstream of your device is not allowing you to get to it. Since the local page is not used that much, I would suggest disabling it completely: https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page#Disabling_the_Local_Status_Page

Make_IT_Simple · ‎Mar 22 2022

You are absolutely right. Then, It is not possible to list the basic RF profiles for one network.

Make_IT_Simple · ‎Mar 22 2022

This will show you all the RF profiles: https://developer.cisco.com/meraki/api-v1/#!get-network-wireless-rf-profiles

Make_IT_Simple · ‎Mar 22 2022

Hopefully, all traffic is coming from one country and you guys don't have any business there. I one time had port forwarding enabled for testing and I did see some requests coming from at least 5 different countries. UK, China, France, Russia, Germany.

Make_IT_Simple · ‎Mar 21 2022

That makes perfect sense, the MX will drop everything if the CPU reaches 100% and I don't believe that Meraki can do anything about this (I hope that I am wrong). If you are able to confirm support statement, then you need to check where those requests are coming from and how many of them. If they are coming from a specific country or specific IPs, then you can just have the ISP black hole them.

Make_IT_Simple · ‎Mar 21 2022

I don't believe that the MX will use any specific VLAN for the test, it will just use the primary uplink for the test, in your case is WAN2. I am not sure what is the end goal here, but I just want to say that dashboard throughput is not really something that you can use as speed test data. If you want to test the speed, it is better to just use any device downstream of the MX (server or any computer), then you can use the server/computer IP to create your traffic shaping rule.

Make_IT_Simple · ‎Mar 21 2022

If you don't want to failover to WAN1, the only way to do it is to add a new flow preference for the device that you will use for speed test. You need to make sure that you don't have any active flow on that computer because it may slow the traffic shaping to take effect.

Make_IT_Simple · ‎Mar 21 2022

There is no physical connection. The virtual MX will be hosted in the cloud and you will use auto VPN to connect it to your physical MX. If you are expanding, you will probably need a second physical MX, and if need be, the virtual MX to access your server in the cloud.

Make_IT_Simple · ‎Mar 21 2022

no worries. anything that you configure in 1:1 nat won't be filtered by the MX, except if you are doing something upstream with another device. If the server is open to the internet and you are allowing any public IP, just give it some time and you will see that people are trying to access your server from different parts of the world and you will see many of those requests. Yes, those requests will fail because your server is secure, but those requests will need to be processed by the MX, increasing CPU/memory usage. This will increase the device usage and could potentially bring it down. On the other hand, if you are lucky enough and your public IP stays private, then you should be fine.

Make_IT_Simple · ‎Mar 21 2022

The only challenge is to limit the use of that 1:1 NAT. It would be great if you know all the public IPs that need access to the server, if not, that server would be open to the internet. even if the server is secured, the MX still needs to process those requests which will increase the MX usage.

Make_IT_Simple · ‎Mar 21 2022

it is a little different with switches, you need to create a profile. This document can help you get started: https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MS_Switching/Templates_for_Switching_Best_Practices

Make_IT_Simple · ‎Mar 21 2022

yes, MR32 model is pretty old. If you have a Mixed network, call support and they can help you only downgrade the MR32s and let the other APs use the newer firmware.

Make_IT_Simple · ‎Mar 21 2022

I found that those MR32 won't play nice with newer firmware, I think MR32 can only install 26.9 as the highest version. Did you try moving the APs to an older firmware like 25.13 or 25.14?

Make_IT_Simple · ‎Mar 21 2022

I have advanced security enabled and I am only allowing a couple of countries, but it only works outbound. Even the MX can drop inbound traffic for port 443, it would be difficult to know which IPs to block or allow.

About Make_IT_Simple

Make_IT_Simple

Community Record

Badges