About ww

ww

make sure your switches are online. and ports are configured correct as stack. if stack is build and correct up and working, and crc is still going up then maybe you got a bad cable.

ww

did you convert ports to stackports? https://documentation.meraki.com/MS/Installation_Guides/MS425_Series_Installation_Guide

ww

https://www.google.com/url?sa=t&source=web&rct=j&url=https://meraki.cisco.com/lib/pdf/meraki_datasheet_sfp.pdf&ved=2ahUKEwjftqOfwczdAhUCxhoKHYyvAkIQFjAAegQIAhAB&usg=AOvVaw3ZPtU2-sojFcUUhTYDnvWa

ww

you talking about roaming? https://documentation.meraki.com/MR/WiFi_Basics_and_Best_Practices/Seamless_Roaming_with_MR_Access_Points and not about meraki mesh? https://documentation.meraki.com/MR/WiFi_Basics_and_Best_Practices/Mesh_Networking

ww

gateway of your ip adres in vlan 2 is also at the upstream / internet device?

ww

you can access the switch locally and see how ports are configured https://documentation.meraki.com/zGeneral_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page native 1, allowed all

ww

mr-xx? what speed you get? both cliënts on 5ghz? what snr value are your cliënts reporting on the dashboard? what ping values you get from client to ap?

ww

you are running a wlc with licenses? you can add dhcp options so the AP can find the wlc

ww

yes. also with previous models and dongle. for now its best to use external 3/4G router and put it in the wan port then its also usable as active connection.

ww · does the customer vpn know where 172.16.2.0/24 is. ... View more

does the customer vpn know where 172.16.2.0/24 is.

ww

contact Meraki Support

ww

for the core , yes. it does not use its own routing table. https://community.meraki.com/t5/Switching/MS350-switch-not-able-to-reach-the-cloud-by-configured/m-p/26463#M2182 https://community.meraki.com/t5/Switching/Management-VLAN/m-p/19025#M1520

ww

the management ip of the 350 can't route to its own svi. you need to set this to an ip and gateway in the subnet of your upstream link.

ww

and 250 and 350 have a management ip from the same subnet and have the same gateway?

ww

firewall is blocking something? at help 》 firewall you can see the ports that are used for connecting to the cloud.

ww

it should be under help》 hardware replacement of you have one of the problem switches

ww

if you mean the test you can start from the dashboard. its not reliable at the ms for some reason. mr and mx work fine

ww

did it work fine before? or did it start after a upgrade? running latest firmware? tryed a factory reset?

ww

https://documentation.meraki.com/MR/Group_Policies_and_Blacklisting/Blocking_and_Whitelisting_Clients

ww

so its connecting 2.4ghz. how about you run 5ghz only

ww

yeah, still missing a lot, not only on mx.

ww

from the switch. its used for things like the management interface and stp

ww

@Bigbub wrote: Hi There, Here's the link to the required ports to open on the Palo Alto. https://documentation.meraki.com/zGeneral_Administration/Other_Topics/Firewall_Rules_for_Cloud_Connectivity BB. its not for every org the same, so best is to check on the dashboard where the mx is added

ww

browse to your dashboard. 》 help 》 firewall info

ww

no. Meraki APs with an integrated Bluetooth Low Energy radio can emit Beacons with following technical specifications: Beacon interval: 100 ms (best effort) Transmit power: 0 dBm

ww

Community Record

Badges