Meraki

CptnCrnch · ‎Sep 30 2020

Greetings from south of your border 🙂

CptnCrnch · ‎Sep 18 2020

@rhbirkelund wrote: I'll go out in a limb here and say; if there's a SNORT rule for that CVE, then it's handled by AMP. A little bit of nitpicking here: if we're talking Snort it's handled by IDS/IPS, not AMP. 😉

RodrigoC · ‎Aug 27 2020

Hey Everyone, Just wanted to confirm what Gary has posted as the solution on this thread. If anyone has any lingering issues, please check in with your ISPs and/or reach out to Meraki Support. If anyone has any specific questions for myself please don't hesitate to send me a DM. Rodrigo Meraki Support

rhbirkelund · ‎Aug 12 2020

I tend to see "DNS is misconfigured" even while the configuration is verified, and correct. Often, it's due to some sort of caching going on, so I'd wait a couple of hours and see if it goes away on it's own.

PhotoJoseph · ‎Aug 7 2020

Thanks @kYutobi (and others who said the same thing) — curiously, I had to ask for it, and they granted it. Strange thing to have to ask for, but OK! Sadly I still can't get my legacy devices on the network. I'm giving up. Time to upgrade I guess.

rhbirkelund · ‎Aug 2 2020

Hah... I was actually looking at that post earlier. Didn't see the he mentioned the Make A Wish..

rhbirkelund · ‎Jul 23 2020

I believe what @JimmyPhelan is trying to convey is that Meraki Autovpn feature only works between Networks within the same Organizations, in terms of Meraki. If you have MX'es at all locations, but they are not in the same organization, you'll have to treat the Site-to-Site VPN as third party VPNs. You will not be able to leverage Meraki's AutoVPN feature.

rhbirkelund · ‎Jul 22 2020

Thanks for the appreciation. 🙂

andyshaw · ‎Jul 16 2020

Thanks for this. It was a bit of a random question from the customer, so just doing my due diligence. Appreciate the reply.

Narnia534 · ‎Jul 9 2020

Below is what it looks like now (hopefully a better drawing): That port on the core is now configured as Access, Vlan 95. Nothing else on the Core is configured for Vlan 95 (no routes, no ACLs. It just goes to the MX), But the MX is configured for V95. STP disables the redundant ports on the Cores

koshien · ‎Jul 8 2020

@PhilipDAth Thank you, at the end of the day I will probably go with the MR36.

JohnD · ‎Jul 7 2020

The WPA2 standard requires the PSK to be at least 8 characters, so this should be consistent across all compliant vendors (including clients), not just a Meraki specific thing.

SobyKuruvilla · ‎Jul 5 2020

Thank you 🙂

Uberseehandel · ‎Jul 4 2020

To be honest, I'd wonder if the data being aggregated and reported is statistically accurate. For example missing data points should not distort what is reported. I'm not talking about Meraki, but I do know of another Bay Area networking hardware and software company that produces great looking charts, most of which are b.s., because the software developers have no regard for data science, database design, or statistics and drop alpha hardware and software of customers and let them find the problems. Checking the data is a low priority. Customers are mostly happy, they like dynamic graphics.

Maclanta · ‎Jun 23 2020

That’s awesome that it worked. The Linn documentation you shared gave me some doubts. I had a crash course on all this last month, and it’s good to know you did not have to go through the weeks of hell swapping out equipment like we did (UniFi to Meraki) to get it straightened out!

LuisCruz · ‎Jun 23 2020

Leaving the VLAN field blank means that the AP will try to get an IP from the native VLAN DHCP scope (VLAN555 in your case). Try changing the native VLAN on the 2960 to something else, then set the VLAN field on the AP to 555, this way the AP will try to get an IP from tagged VLAN 555 scope. This would be some strange behavior, but at least we will get some info to have a case open.

lchan · ‎Jun 15 2020

Awesome! Will look into the scanning API. Thanks everyone!

morris · ‎Jun 3 2020

that's what i'm thinking. So, I'm guessing that documentation listed all the available value that I can use.

CarolineS · ‎May 18 2020

Thanks! We will report this to the web team.

rhbirkelund · ‎May 17 2020

As @MerakiDave says, there is no specific How-To, since every deployment is different. However, then I'm out deploying a Full Stack Meraki, I usually prioritize getting the MX up and running as the first thing. I even wait before powering and uplinking any device further down, untill the MX is up. All Meraki devices upon firsttime boot will contact the dashboard, and perform firsttime upgrade. So also before setting the MX up, make sure you've set whatever firmware you wish to be running in the Dashboard. Then make sure all basic settings are made (Mgmt DHCP), downlink ports an so on. After the MX is up, I go about uplinking the switches in the chained way that I have designed, and then work my way through the topology. One could connect it all as once, and go get lunch while it's everything is contacting the dashboard, upgrading, rebooting, and so on. But I prefer doing one device at a time. When all switches are online, I go about the rest. AP's, client facing ports and so on, as part of the comfiguration process. When all the basics are done, I go about doing all the finetuning, with everything online. Those are just my 2 cents..

Thygesen · ‎May 6 2020

Hi .. No I found that one 🙂 I have a request for direct polling of the network devices.. Our friends in the industry provides packages for the devices for different monitoring systems, and I was hoping the same for our great Meraki stuff .. Found these links though .. https://thwack.solarwinds.com/t5/NPM-Discussions/SNMP-Polling-Meraki-Devices-NPM-12-0-11-0-1-How-To/td-p/158452 https://documentation.meraki.com/MR/Monitoring_and_Reporting/Monitoring_the_Wireless_Network#SNMP_Polling

samgbuyi · ‎May 4 2020

Both Vlans are on the Route-table!

MC1 · ‎Apr 30 2020

What! I’m sure jealous about the sun glasses and stickers.

Johnfnadez · ‎Apr 20 2020

Hi @PhilipDAth I been working with Meraki Support and We can confirm tht there`s two-way traffic and that we have all the Firewall Rules in my upstream firewall. But when we started to deploy meraki branches (1 year ago till now) I have been registering MR,MX and MX in each brach without problems. But we are a Financial Institution and we have to be aware about our firewall rules. And we deployed more than 100 branches with the NTP bloking in our Upstream Firewall. But now this is the issue bc MS cannot connect to the principal cluster in USA. So it tries to establish the M-Tunnel against the secondary cluster and to acompplish this M-tunnel needs NTP and It`s the port that we have deny in our firewall.... The issue now is that we cannot perform a rule to permit NTP with any any entries bc We are a bank. So we will try to modify our DNS entries to simulate a DNS Poisoning to resolve an internal NTP to the domain that MS tries to resolve the URL that uses to get NTP services....

RobMcLean · ‎Apr 16 2020

I think I have solved the issue. So far no more VLAN mismatch errors in the event log. I ended up ensuring that only necessary VLANs were allowed on the trunk links instead of 'ALL'.

About rhbirkelund

rhbirkelund

Community Record

Badges