Meraki

Ryan_Miles · ‎Nov 28 2021

That is tunneling the SSID to your MX. That is typically used for remote teleworker deployments where the AP is remote and tunnels over the internet back to the MX. I wouldn't use that mode in your topology.

Ryan_Miles · ‎Nov 27 2021

Make the port on the MX a trunk. Make the ports of the switch connected to the MX and the MRs trunks. Last, on the SSIDs use bridge mode and specify the tagged VLAN. That'll do it. Here's an example of my SSID putting clients on VLAN 80.

Ryan_Miles · ‎Nov 27 2021

They should not expire

Ryan_Miles · ‎Nov 27 2021

Exactly. Just like we've always had 10 free MV Sense licenses we're now adding 5 free MT licenses to encourage folks to try our Sensors.

Ryan_Miles · ‎Nov 26 2021

First thing you should do is upgrade to the current stable firmware. I can see your MR55s are running really old firmware from 2019. Your network says "Last upgraded on Saturday, November 17, 2018" 😲 Your other wireless networks appear to be running much more current firmware and have been updated more recently. Once you're on current firmware you can monitor to see if the issue clears up.

Ryan_Miles · ‎Nov 26 2021

Is there a default route in EIGRP or BGP that should be distributed via OSPF? I would typically expect to see default-information originate in the OSPF section to propagate the default route.

Ryan_Miles · ‎Nov 25 2021

what is the ospf config of the routers?

Ryan_Miles · ‎Nov 24 2021

this video does a good job of covering the basics to get started with postman and meraki api https://www.youtube.com/watch?v=TRhT-zNVlCw

Ryan_Miles · ‎Nov 24 2021

that doc is out of date. the mr44 is supported with secureconnect.i've requested the doc to be updated. if it's not working a support case should be opened.

Ryan_Miles · ‎Nov 23 2021

It's due to MDNS https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Rename_a_Client's_Hostname. Unfortunately anything that sends MDNS (mostly Macs, but other OS'es can too) the name will show up as the long MDNS string.

Ryan_Miles · ‎Nov 22 2021

The mgmt port is just for local connection with a laptop as you mentioned if you need to give it a static in order for it to reach dashboard. Otherwise the switch will pull DHCP for its logical mgmt interface which is the common way folks deploy Meraki switches (and APs, cameras, etc).

Ryan_Miles · ‎Nov 21 2021

are you using templates?

Ryan_Miles · ‎Nov 19 2021

@rajiw017 I was able to do it via Postman. I first tried with the bare minimum value of just the psk. It gave the "Authentication mode is not a valid SSID override option" error. I then added " "authMode": "psk" and the error changed to "Pre-shared key mode requires a valid encryption mode". So, last I added ""encryptionMode": "wpa" and that allowed the PUT to work.

Ryan_Miles · ‎Nov 18 2021

The error sounds like you're trying to change the auth type and not just the PSK. What exactly are you sending in the API call? Can you paste it here (minus a PSK for privacy)?

Ryan_Miles · ‎Nov 18 2021

ah, i never bothered to look into why it does that. some articles simply say to hard set the speed on the adapter. so maybe that's the only way to "disable" eee.

Ryan_Miles · ‎Nov 17 2021

Try whitelisting the URL or IP https://documentation.meraki.com/MX/Content_Filtering_and_Threat_Protection/URL_Filtering

Ryan_Miles · ‎Nov 17 2021

Feel free to PM the serial number of the MX and I'll take a look at it

Ryan_Miles · ‎Nov 17 2021

Not sure what AP mode on a Netgear means. You want it to just bridge the traffic. Is the AP doing some NAT function for clients that connect to it?

Ryan_Miles · ‎Nov 17 2021

what happens if you connect a host directly to port 4? does it receive a DHCP IP? does the NVR on port 3/VLAN 100 work ok?

Ryan_Miles · ‎Nov 17 2021

Brandon is correct. I'd just point out the SKU you mentioned is the MR advanced license that adds in the native Umbrella policies. This also requires the org runs per device licensing. You perhaps want the standard enterprise MR licenses which are LIC-ENT-xYR

Ryan_Miles · ‎Nov 17 2021

Is the netgear getting that 10.10.11.2 via DHCP or did you set it as a static? And the MX shouldn't need a reboot, but have you tried rebooting it? Btw, what model MX and what firmware is it running?

Ryan_Miles · ‎Nov 17 2021

How are clients connected to this MX? Directly on a LAN port, downstream via switch or AP? You've done a DHCP renew or reboot of the client being tested? If you've changed the VLANs on the MX and saved the config it shouldn't be handing out 192.168.128.0 IP's anymore.

Ryan_Miles · ‎Nov 17 2021

#1 I believe we can create reports that span up to 180 days #2 Is noted at the bottom of this table https://documentation.meraki.com/General_Administration/Privacy_and_Security/Cloud_Data_Retention_Policies#Data_Retention_Times

Ryan_Miles · ‎Nov 17 2021

Devices turning on & off will result in events like that. Normal behavior when the ports are connected to PC's and such. I would only be concerned if I saw STP flaps on ports going to other infrastructure devices like switches, firewall, routers, etc. Links that shouldn't be bouncing short of device failure or reboot. Also, port 17 connected to the iMac is toggling between 100Mbps and 1Gbps. I've seen this behavior on my wired Macs and often I hard set the port to 1Gbps to stabilize it.

Ryan_Miles · ‎Nov 16 2021

It will switch to a non region specific SKU on Nov 30. So, it will just be MA-INJ-4. And you'd then add the region specific power cord. In your case that would be MA-PWR-CORD-EU. You should be able to still order the MA-INJ-4-EU until Nov 30.

About Ryan_Miles

Ryan_Miles

Ryan Miles

Community Record

Badges