About Ryan_Miles

Ryan_Miles

MR (AP) license SKUs are listed here

Ryan_Miles

AFAIK it should prefer the master switch first. Then switch ID 2, 3, 4, etc. Although you can't necessarily see those switch IDs in dashboard. Exposing that would require a feature enhancement.

Ryan_Miles

What addressing mode is used on the SSID? Are you tunneling the SSID to a MX?

Ryan_Miles

APs are only different in that they have regulatory domains for RF transmission. But you can still override that under network wide settings. Switches don't care about where they live nor does licensing have any location relevance. They will work wherever you place them.

Ryan_Miles · ‎08-17-2022

I've upgraded MX HA pairs for years (as run now and scheduled) and honestly never looked at the connectivity bar to see if the times match.

Ryan_Miles · ‎08-17-2022

A MX HA pair will upgrade each unit separately so I would anticipate different times. Although, I would expect the opposite then of what you posted as the primary should upgrade first.

Ryan_Miles · ‎08-15-2022

It's under the client IP assignment section https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/SSID_Modes_for_Client_IP_Assignment L3 roaming is specifically for when you say for example have 3 floors with layer 3 subnets pushed to the access layer. So, clients get IPs in subnet 1, 2, 3 depending on which floor they're on. If devices are going to roam from one floor to another (meaning actively using device during the physical move) then layer 3 roaming is a good option. If however a user will move and say carry a laptop, tablet, etc with them from their desk on 1st floor to a conf room on floor 3 that's not really a use case or need for L3 roaming. Standard mapping of the SSID/APs to their respective floor VLAN ID with bridged mode is fine. Time and time again I see dashboards with L3 roaming enabled and mapped to a single VLAN. That does literally nothing different than standard bridged mode to a single VLAN 😉 Btw this is all explained in great detail here https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MR_Wireless/Wireless_Layer_3_Roaming_Best_Practices

Ryan_Miles · ‎08-14-2022

Update firmware and factory reset them and see if it persists

Ryan_Miles · ‎08-12-2022

I'd give factory reset a shot https://documentation.meraki.com/MV/Initial_Configuration/MV2_Wireless_Onboarding#Factory_Resetting_the_camera If it still continues to fail then I'd recommend opening a Support case

Ryan_Miles · ‎08-12-2022

This should now be GA https://developer.cisco.com/meraki/api-v1/#!get-network-appliance-ssid

Ryan_Miles · ‎08-11-2022

So, does VLAN 30 exist/is allowed on the trunks all the way to the L3 switch? Then on that L3 switch is there a DHCP helper/relay to the IP of the DHCP server? And when you say the camera worked on another switch. Which one? The switchport is configured exactly the same, the uplink is configured the same?

Ryan_Miles · ‎08-10-2022

Open a Support case and they can tell you

Ryan_Miles · ‎08-09-2022

This 3rd party AP is connected to what? A MX LAN port, a switchport? Is the VLAN for the AP provisioned on the MX? You mentioned a GP with zero rules. Why is there a GP applied if it has no rules? Are you trying to access this AP locally or over S2S VPN? More details on the topology & config or a diagram would be really helpful here.

Ryan_Miles · ‎08-08-2022

Use the firewall rules. The default object "Local LAN" represents 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16

Ryan_Miles · ‎08-05-2022

Rebooting the primary does not reboot the spare. The spare would become master upon rebooting the primary.

Ryan_Miles · ‎08-04-2022

Choose whatever most closely matches your third party antenna.

Ryan_Miles · ‎08-03-2022

Unfortunately you need Insight which allows for per WAN alerts to be configured.

Ryan_Miles · ‎08-02-2022

Was the VPN config done locally on that Mac? If so, maybe try pushing it via Apple Configurator. Or, if you have a MDM deployed push the config that way. I've recently had to do this on any Mac running the Ventura beta. It breaks the VPN config and recreating it on the Mac itself doesn't work. Has to be built externally then imported/pushed. Using the Apple Configurator is super simple. Install it from the App Store. Open it, file > new profile, choose VPN section, create config, file > save. Last step is open that .mobileconfig file on the client Mac and it should install it.

Ryan_Miles · ‎08-02-2022

VRRP is sent on all configured VLANs on the LAN ports (in NAT routed mode). So, it does mean all VRRP packets (on all/any VLANs) would need to stop being seen by the MXs in order to transition the master role.

Ryan_Miles · ‎08-01-2022

You should open a Support case.

Ryan_Miles · ‎07-30-2022

The MX67C has a cat 6 LTE radio which is rated at 300 Mbps down/50 Mbps up. So, I would expect to see those numbers as a maximum value. The wired WAN interfaces should support up to 600 Mbps up/down.

Ryan_Miles · ‎07-30-2022

You should open a Support case. Might be something more than just internet reachability issue.

Ryan_Miles · ‎07-28-2022

It won't work. Meraki APs don't act like client bridges/clients in such that they won't roam seamlessly. The mesh process takes time to form a connection. https://documentation.meraki.com/MR/Deployment_Guides/Mesh_Deployment_Guide#Mesh_convergence_time You'd want to use something like an autonomous Cisco AP in universal workgroup bridge mode.

Ryan_Miles · ‎07-25-2022

It’s covered here https://documentation.meraki.com/General_Administration/Templates_and_Config_Sync/Managing_Multiple_Networks_with_Configuration_Templates#Local_Overrides

Ryan_Miles · ‎07-25-2022

You would need to note the max power load per the MS225 data sheet Then, check the max output power of the RPS2300 in both configurations and do the math. It appears you'd want the 1150 W if supporting two 24 port switches or a 48 port full power switch.

Ryan_Miles

Ryan Miles

Community Record

Badges