Meraki

Ryan_Miles · ‎Feb 23 2022

Basic .1Q trunking rules. Your switch was expecting untagged VLAN 13 traffic. If you send it tagged from the AP the switch is going to see a mismatch. In short, if it's the native VLAN = no tag. Anything besides the native = tagged.

Ryan_Miles · ‎Feb 23 2022

The only antennas tested & supported are what is included. The connectors are RP-SMA however if you want to source non Meraki antennas keeping in mind my first sentence.

Ryan_Miles · ‎Feb 23 2022

You read the second paragraph of my response yes?

Ryan_Miles · ‎Feb 23 2022

No, not tied to any specific firmware release AFAIK.

Ryan_Miles · ‎Feb 23 2022

No hardware revision. It's now rolled out to any MX67/68.

Ryan_Miles · ‎Feb 23 2022

I'm not sure why 1.11 has been beta for so long. That said I'd absolutely use that as it contains a ton of fixes and improvements over 1.9.

Ryan_Miles · ‎Feb 23 2022

Are you setting it to a static IP on the same VLAN it's using the DHCP IP from? Or, changing to an entirely different subnet/VLAN? Typically this happens when the address you're attempting to use is failing to work and the AP (or even a switch or MX) will defer back to using DHCP. I think I found your network. If this is yours I see you have the AP static IP set and VLAN 13 specified. You also have native VLAN 13 on the upstream port. You can't tag the AP mgmt IP and have it native/untagged on the switch. Easiest fix just delete the VLAN tag on the AP static IP config.

Ryan_Miles · ‎Feb 22 2022

Feel free to DM your dashboard URL and I can take a look. At this point we can only make guesses as to what's going on.

Ryan_Miles · ‎Feb 22 2022

Just to confirm, you've moved the MVs to a new subnet and you're using DHCP reservations? In this new subnet are they now offline/unreachable? Are they wired or wirelessly connected to the network?

Ryan_Miles · ‎Feb 22 2022

If I'm not mistaken the script is renaming the tag from whatever its default state is. So, the backup_up tag for example wouldn't normally exist until the script creates it based on detected loss.

Ryan_Miles · ‎Feb 18 2022

I run all my Apple TVs on wireless so I've not seen this issue nor can I reproduce it. However, I did find tons of posts about this on apple and other sites with many different switch vendors and models having the issue. So, it sounds like more an Apple issue. What happens if you disable sleep mode (set to never) on the Apple TV?

Ryan_Miles · ‎Feb 17 2022

Also, when you say a pair is that a HA pair? If so, a template would be of no value as a HA pair is only a single network config in dashboard anyway.

Ryan_Miles · ‎Feb 17 2022

Templates were not designed for MXs larger than the 105. Typically the 250/450 are very large site firewalls or VPN concentrators and not "cookie cutter" site appliances that would fall into a template driven org. Whether right or wrong that's the reason why.

Ryan_Miles · ‎Feb 17 2022

https://documentation.meraki.com/MS/Other_Topics/Troubleshooting_and_Replacing_a_Faulty_MS_Switch#Switch_cloning_after_the_RMA

Ryan_Miles · ‎Feb 17 2022

This is a pesky error that often clears up on its own after some time. But, if you need the network/template upgraded now as ww mentioned open a Support case. Or, you can send me (in DM) your org URL and I can do it for you.

Ryan_Miles · ‎Feb 16 2022

It's an open bug. It's in the backlog of things to fix. Believe me we all give our feedback about this not working often 😉

Ryan_Miles · ‎Feb 16 2022

Indoor "E" APs have RP-TNC connectors. The outdoor APs and antennas are N-type.

Ryan_Miles · ‎Feb 15 2022

You can send me a private message through here with the serial and I can check

Ryan_Miles · ‎Feb 15 2022

Odd scenario. But, assuming it's not in any network today when you claim it and add it to the network it will assume a default config of all ports being trunks with native VLAN 1. Also, when it checks in to dashboard it may need to do a firmware update. So, I would do this in a maintenance window. I'd have to know the serial number to for sure see where it lives today logically.

Ryan_Miles · ‎Feb 12 2022

Ok then clearly the problem is not the API. If you want to DM your network URL to me I can take a look.

Ryan_Miles · ‎Feb 12 2022

Does it work when you set it from the standard dashboard UI?

Ryan_Miles · ‎Feb 11 2022

This is what I used and it worked { "twoFourGhzSettings": { "channel": "1", "targetPower": "11" }, "fiveGhzSettings": { "channel": "36", "channelWidth": "80", "targetPower": "8" } }

Ryan_Miles · ‎Feb 11 2022

I just tested using postman and it worked. I have to completely remove the line for the rfProfileId in the body. Leaving it as null would cause an error. Are you sending any value for the rfProfileId?

Ryan_Miles · ‎Feb 11 2022

All MS should support v3 (and hence v2). This doc mentions the RFC it adheres to.

Ryan_Miles · ‎Feb 11 2022

https://documentation.meraki.com/MR/Other_Topics/IPv6_Support_on_MR_Access_Points#RA_and_DHCP_Guards

About Ryan_Miles

Ryan_Miles

Ryan Miles

Community Record

Badges