Meraki

Ryan_Miles · ‎Dec 2 2021

Twilio is not used. As the doc mentions you send SMS alerts by using your phone number and SMS provider string.

Ryan_Miles · ‎Dec 2 2021

https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Alerts_and_Notifications#Receiving_Email_Alerts_via_SMS

Ryan_Miles · ‎Dec 1 2021

Gotcha. As you've seen if you just leave a value out when using API it should ignore/not change the current value. You'd probably need to use Runner in Postman and use a source spreadsheet with a column of all the switch serials. I've not tried this specific scenario, but I assume it should work. If you haven't used Runner you'll need to read up on it and do some testing to get the basics down.

Ryan_Miles · ‎Dec 1 2021

As Russ said it's the MDNS name. If a custom name has not been given to a client in dashboard MDNS is the next value to be used if detected. The order dashboard uses to show the client name is here. If you'd rather have DHCP above MDNS (like I would) please click the give feedback button in the lower right corner so Meraki can hear your input.

Ryan_Miles · ‎Dec 1 2021

I assumed you were using static mgmt IPs based on your initial question. If your switches are receiving DHCP IPs then just change the supplied DNS server IPs in your DHCP scope config. What is providing the DHCP?

Ryan_Miles · ‎Nov 30 2021

You'd need to use the API https://developer.cisco.com/meraki/api-v1/#!update-device-management-interface

Ryan_Miles · ‎Nov 30 2021

If you click the Allow more connections link you can enter lines for specific protocol, ports, and remote IPs to allow

Ryan_Miles · ‎Nov 30 2021

That is the recommended way and we have many customers using it.

Ryan_Miles · ‎Nov 30 2021

You don't need no nat feature. In the 1:1 NAT just enter the same IP in the Public and LAN boxes.

Ryan_Miles · ‎Nov 28 2021

Local LAN is a default object for subnets 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16. So you want this set to Allow so clients can access internal resources. If you want to lock things down you can add more explicit rules or do it at the MX.

Ryan_Miles · ‎Nov 28 2021

On page Wireless > Firewall & traffic shaping is the first rule showing as Deny or Allow? It needs to be Allow if this is an internal/employee SSID.

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)?

About Ryan_Miles

Ryan_Miles

Ryan Miles

Community Record

Badges