dhcp renewal does not trigger port up/down status.   Is there a docking station connected? Did you already try another cable or try updating the network driver of the workstation? Any errors on the port? what is the result of a cable test? ... View more

Dit it come back online on the same channel?  ... View more

last time i checked the network device that connected the client did an arp to the client. (its not using icmp packets for this function.) chromecast uses routing discovery packets with a ttl 1 and without rebroadcasting this packets it will not work on other vlans ... View more

Not sure about the 120. the 220  however support cos 0-5 on the dashboard so only 6 queues possible to configure. (if there are 8,  cos 6 and 7 are most times dedicated for management protocol packets.) QoS remarking should work if you set the correct vlan / tcp/udp  src-dst, combined with the "set-dscp to" option. did you check on DSCP value in the trace?  ... View more

The articles are about how chromecast has a bug that produces lots of packets and can lock up your network. probably also produce high utilization now and then. ... View more

fyi. chromecast has some problems a.t.m.    http://bgr.com/2018/01/15/google-chromecast-home-wifi-problems-router-crashing/ https://www.theregister.co.uk/2018/01/15/router_vendors_update_firmware_to_protect_against_google_chromecast_traffic_floods/   ... View more

if you can't ping from the home MX to the home laptop you should check if the home laptop(laptop firewall) is not blocking the ICMP. ... View more

its not connecting the Wi-Fi? for testing, make a new ssid with a simpel ssid name.  enable wpa1+wpa2 disable  802.11w disable band steering. configure the lowest minimum bitrate.   try connecting the new ssid   ... View more

i dont see your static route for 100.100.100.0 ... View more

is your work laptop and the servers connected behind the mx or on the local network? why are you using the same subnets in the mx work vpn as on the lan?   try make a network drawing with routing included and share it. ... View more

you have now: Inside 192.168.0.0 / 255.255.0.0 / Gateway IP 10.14.130.250 you can try add a more specific: Inside 192.168.127.0 / 255.255.255.0 / Gateway IP 10.14.130.149 ... View more

maybe you can use qos in your network to prefer some traffic over the default based on your server/backup ip's/ports. ... View more

This document is a walkthrough for setting up a virtual MX (vMX100) appliance in the Microsoft Azure Marketplace. After completing the steps outlined in this document, you will have a virtual MX appliance running in Azure that serves as an AutoVPN termination point for your physical MX devices.   https://documentation.meraki.com/MX-Z/Installation_Guides/vMX100_Setup_Guide_for_Microsoft_Azure   https://documentation.meraki.com/MX-Z/Site-to-site_VPN/Site-to-site_VPN_Settings     ... View more

Did you check out this information / scenario's https://documentation.meraki.com/MX-Z/Networks_and_Routing/BGP#BGP_Terminology   ... View more

use link aggregation between the stacks and between the core and the firewall.  meraki is using the open standard LACP https://documentation.meraki.com/zGeneral_Administration/Tools_and_Troubleshooting/Link_Aggregation_and_Load_Balancing https://documentation.meraki.com/MS/Port_and_VLAN_Configuration/Switch_Ports#Link_Aggregation   ... View more

is the switch management also lost? maybe the traffic is still send to the former active mx because the link was never down. ... View more

do you have an additional failover link between the two mx devices? read this good blog: https://willette.works/mx-warm-spare/     ... View more

who is running your dhcp services?   is  192.168.11.41 is a dell server running dhcp for your network vlan 11? if not, you should block unknown dhcp servers under switch>dhcp ... View more

make sure how to config your AP's/network  before tranferring because the configuration wil be empty in your organization. ... View more

not sure if your account has a 8 digit code but if so,  you can check this in the right corner "help > get help" on the dashboard.   Your  IT supplier should contact meraki support they can transfer the hardware and license to your organization. maybe you have to add the it supplier account first to your new organization. but meraki will assist with that.     ... View more

i guess it depends on your contracts with the   IT supplier.    You should be able to take ownership by contacting support but the hardware/licenses need to be ordered/registered on your name   /   administrator email address.   Is there no way the previous IT supplier can help? ... View more

buy the key from your reseller and contact meraki to upgrade to advanced security and to release the current key from the organization. (you can not mix advanced/enterprise in one org)   https://documentation.meraki.com/zGeneral_Administration/Licensing/Licensing_FAQ#Q:_Can_I_upgrade_from_Enterprise_to_Advanced_Security_(MX_Only).3F   -> its best to create a case and let meraki support assist you. ... View more

and your radius is sending this?  https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/Tagging_Client_VLANs_with_RADIUS_Attributes and did you verify this attributes are send in the packet?   ... View more

did you configure to allow radius override? does the  RADIUS attribute match on the ap side and the radius server side? and is this really send to the ap? ... View more

what type are u using?   https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/VLAN_Tagging#Per-User_VLAN_Tagging A per-user VLAN tag can be applied in 3 different ways: The RADIUS server returns a Tunnel-Private-Group-ID attribute in the Access-Accept message, which specifies the VLAN ID that should be applied to the wireless user. This VLAN ID could override whatever may be configured in the MCC (which could be no VLAN tagging, or a per-SSID VLAN tag). To have this VLAN ID take effect, “RADIUS override” must be set to “RADIUS response can override VLAN tag” under the Configure tab on the Access Control page in the “VLAN setup” section.   The RADIUS server returns a group policy attribute (e.g., Filter-ID) in the Access-Accept message. The group policy attribute specifies a group policy that should be applied to the wireless user, overriding the policy configured on the SSID itself. If the group policy includes a VLAN ID, the group policy’s VLAN ID will be applied to the user.   On the Client Details page, a client can be manually assigned a group policy. If the group policy includes a VLAN ID, the group policy’s VLAN ID will be applied to the user.   all vlans are on the trunk? all dhcp scopes are present? did you make a wireshark capture on the uplink and check the radius server that its sending the correct attributes? ... View more