Meraki

alemabrahao · ‎Apr 4 2022

@mjenks I don't know what type of devices are you testing, but Have you checked the firewall on the device? Have you performed a packet capture?

PhilipDAth · ‎Apr 4 2022

One thing you can ask support is how long a device has been up. An easy way to determine if a device has been crashing ...

GelC · ‎Apr 3 2022

Hi @PhilipDAth. Noted on this Thank you for you help.

MakaraMEAS · ‎Apr 3 2022

I maybe difficult to explain, but please kindly find the image for reference. When we try to modified and save, it alert as the image reference.

alemabrahao · ‎Apr 3 2022

OVERKILL · ‎Apr 2 2022

I had to get the CPU utilization figure from support. In my case, I had all active ports flapping, not just the WAN links, so if you are only seeing it on the WAN side I'd assume the issue isn't the same. Just figured I'd mention it.

Inderdeep · ‎Apr 2 2022

@Arif4869 : It is for Concurrent users https://documentation.meraki.com/MX/MX_Overviews_and_Specifications/MX95%2F%2F105_Datasheet

pistolpete13 · ‎Apr 1 2022

You are correct! Looks like the sorting function is back working again. Time to hunt and block bandwidth hogs again...

JonP · ‎Apr 1 2022

Of course! I'm dumb. When I connected the switch it was sending out BPDU's like crazy, and because we had BPDU guard enabled, the Meraki port transitioned to a disabled state. Because it is a switch and not a client device it would always send BPDU's. Thank you @ww and @alemabrahao for the info.

alemabrahao · ‎Mar 31 2022

Yep, there is no easy way, you have to change your addressing.

LC_IT · ‎Mar 31 2022

Sim, aumentei o Radius Timeout de 1 para 10 conforme esse doc: https://documentation.meraki.com/MR/Access_Control/MR_Meraki_RADIUS_2.0#Server_Timeout_and_Retry_Count

ronnieshih75 · ‎Mar 31 2022

"Assign group policies automatically by device type" option works within each SSID network where it's defined, as I tested using an Apple ipad and an android phone. A single Deny Any to Any rule + an Allow UDP port 67 allows a device to obtain an IP address seemingly to allow access but all traffic to anywhere is denied. Although, you do need to allow for existing traffic streams to die off then all new traffic would effectively be blocked. This fulfills my goal of kicking all personal devices off our existing PSK SSID without changing the passphrase. This forces everyone to use the guest SSID instead. After the above is done for a while, we'll implement iPSK with RADIUS where we have a central MAB database of devices using different PSKs.

alemabrahao · ‎Mar 31 2022

I had the same "problem" and I had to configure all the switches again. 😑

KDedesko · ‎Mar 30 2022

The issue wasn't with the Meraki. The software on the server on the inside interface was faulting. It was not able to start up correctly. Thanks for all the valuable feedback.

alemabrahao · ‎Mar 30 2022

Take a look at this link : https://www.sciencedirect.com/topics/computer-science/logical-link-control

pcanters · ‎Mar 30 2022

I kind of agree. As much as I wish I could do this on the Meraki MX, it's not really designed to handle this network setup. Thanks for the response

harmankardon · ‎Mar 30 2022

I didn't even know this Meraki document existed! Thanks for pointing me in the right direction. The Client VPN Overview Meraki doc doesn't even mention that page. The URL for anyone else seeing this is: https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Managing_User_Accounts_using_Meraki_Cloud_Authentication

alemabrahao · ‎Mar 30 2022

No, It's not normal. Try to reserve the IP via MAC on your DHCP server.

Sming · ‎Mar 30 2022

will try and observed the same...

PhilipDAth · ‎Mar 29 2022

This is common. What happens is the combined network can support an MX, even though one isn't configured at the moment, and as such can have a firmware version set. You can use this to do things like set the desired firmware for a new network before adding an MX to it. I've used it as well when swapping out an MX from a network for a new MX, and the old MX and new MX could not run the same firmware version due to the age difference.

alemabrahao · ‎Mar 29 2022

I think a good test might be to configure a port in access mode on each VLAN and test the connection with a laptop to validate that the connection to each VLAN is working as expected.

alemabrahao · ‎Mar 28 2022

I don't know If they have a calculator to calculate that, but you can check the BSSID MAC on "BSSID Details":

Satsuki · ‎Mar 28 2022

No gotchas I can think of. But I'm going to assume you're prob moving an MX, I've used this doc before. Might want to take a look and read through it: https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MX_Security_and_SD-WAN/MX_Templates_Best_Practices There are other docs for different devices though so might want to take a look beforehand just in case. Something I do just in practice is taking screenshots of the info I need and saving them with the device name/page so I can go back and do it. You made mention of ports and stuff. This doc is helpful to create a switch profile for ports: https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MS_Switching/Templates_for_Switching_Best_Practices#Creating_and_Using_Switch_Profiles Looks like switch profiles are good for the same switches/same ports so might want to take that into consideration for deployment.

MakaraMEAS · ‎Mar 27 2022

Thank you, your link is useful for me. I just wonder why it sometime not switch from one rule to one rule not properly. sometime it match to general group policy, which is not the requirement.

alemabrahao · ‎Mar 25 2022

Check this link, I think It can be helpful 🙂 https://community.meraki.com/t5/Security-SD-WAN/UPnP-Help/m-p/10861

About alemabrahao

alemabrahao

Alessandro Abrahao

Community Record

Badges