Hi @Indian1 you can check the below as well, those are specific to the STP:   STP Overview Configuring Spanning Tree on Meraki Switches (MS)  ... View more

Status-Server packets are sent by a RADIUS client to a RADIUS server in order to test the status of that server. The Status-Server packet is not a "Keep-Alive" as discussed in [RFC2865], Section 2.6. ... View more

  Below are overrides that can be configured for networks bounded to a template. Please refer to the product specific guides for more details:   MX/Z - MX Templates Best Practices Addressing & VLANs subnets DHCP exceptions NAT / Forwarding rules SD-WAN & Traffic shaping Uplink Configuration Client VPN   MS - Templates for Switching Best Practices Switch ports (Access Policies*, Port Schedules*) Routing and DHCP OSPF Routing Port Management Profile Stack Management DHCP Snooping Dynamic ARP Inspection (DAI)   MR Access Points SSIDs (name, enable/disable) Access control Radio Settings (RF Profiles) *Note: These configuration must be defined at the template level   If anything else you think it's suitable to be override please submit a feature request . Any wish that is made it sends an email to our Product Managers and Development Teams. ... View more

Here is the common troubleshooting steps can be done for this situation: - Perform a cable test on the upstream switch port and ensure there are no breaks in the pairs - Ensure that the ethernet connection between the switch and the AP is less than 100m in length - Move the AP to another switch port (confirmed to be working at 1000Mbps) and confirm that the uplink speed is still under 1000Mbps - Use a new ethernet cable and confirm if the uplink speed is still under 1000Mbps - If the AP is connected via a patch panel, temporarily connect it directly into the switch with a cable that is under 10m in length - Run a packet capture on the switch port whilst the AP is physically connected. This will allow us to review the LLDP exchange during link negotiation - Confirm if you are observing this issue on the latest stable release of MR firmware   If anything else has been noticed, please create a new case and mention all the steps that are already done and checked. ... View more

I do understand what you mean, however currently the auto updates are pushed out in batches to different customer dashboards, this is where you are facing the issue. As mentioned feel free to add the feature requests as if there's many ask for this, would take higher consideration.  ... View more

"When new firmware becomes available it will immediately be available on dashboard for an administrator to upgrade to. Though it will eventually be pushed to qualified networks via the automated upgrade process, the automated upgrade process does not happen immediately after release and is rolled out over time. The automated process can sometimes take weeks to occur on all networks, depending on certain factors."   As you can see, the timing is not immediate or set to a specific timeframe. After a stable firmware release is made available, it will be pushed out in batches to different customer dashboards. There is no guarantee as to when this firmware upgrade will be pushed out to a specific dashboard but when it is, it will fall within the upgrade window specified under Network-wide > General. We recommend network administrators to check all of their Dashboard networks periodically for available firmware upgrades and upgrade them manually to the latest firmware versions in such scenarios.   There is nothing that you are required to do to mitigate problems with auto-update. What we are observing here is expected behaviour and is simply the way that the auto-update mechanism works. I do appreciate the confusion that the menu can cause and I hope that you find the documentation useful to review.   https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practices_for_Meraki_Firmware#Automated_Firmware_Upgrades   Meanwhile, feel free to submit feature request for new ideas, as any feature request that is made, sends an email to our Product Managers and Development Teams. ... View more

All unsolicited inbound traffic is blocked by default and the L3 firewall is a stateful firewall the only way to open up specific ports inbound is by using port forwarding or NAT rules.    Please check the below documentation: https://documentation.meraki.com/MX/NAT_and_Port_Forwarding/Port_Forwarding_and_NAT_Rules_on_the_MX   https://documentation.meraki.com/MX/NAT_and_Port_Forwarding/Blocking_Inbound_Traffic_on_MX_Security_Appliances ... View more

Hi there, unfortunately if not stated in the documentation means there is no info if this would be supported or not. The support team won't know either as no ETA or confirmation would be provided to them. The Meraki sales might have more insight about this feel free to give them call. https://meraki.cisco.com/en-uk/form/contact/ ... View more

For WAN VIP addresses are shared by both the primary and warm spare appliance. Inbound and outbound traffic use this address to maintain the same IP address during a failover and reduce disruption. The virtual IPs are configured on the Security & SD-WAN > Monitor > Appliance status page, under the Spare section in the upper-left corner of the page. If two uplinks are configured, a VIP can be configured for each uplink. Each VIP must be in the same subnet as the IP addresses of both appliances for the uplink it is configured for, and it must be unique. In particular, it cannot be the same as either the primary or the warm spare's IP address. https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair   Regarding the License, yes only one license is required for an HA pair. The warm spare unit does not require a separate license.  ... View more

For the APs main page there is a known issue ongoing "loading issue", if anything else noticed please raise a case so this can be checked internally. ... View more

As well keep in mind to check the 2.4GhZ is not blocked via Wireless>Radio settings under Overview tab. ... View more

Then nope, would be feature request. ... View more

The simple answer would be no for this. But if you can provide more details/example of what you are exactly trying to achieve in case there's workarounds.  ... View more

If you notice the shared link shows the New URL which is:  https://fde-nonceapi-b2b-prd-na-gkf3gmc8amfbckcy.a01.azurefd.net   For example: " *fde-nonceapi-b2b-prd-na-gkf3gmc8amfbckcy.a01.azurefd.net/health "   Here is the documentation for reference: https://documentation.meraki.com/MX/Content_Filtering_and_Threat_Protection/Content_Filtering   Allow 10-15min to make sure the changes took affect.  If the issue is still ongoing, change the policy to one of the affected clients to be allow-list as this will bypass all the Meraki rules, check the below documentation if you are unsure how to apply it, scroll down to "using client list": https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Blocking_and_Allowing_Clients   Wait 10-15min and recheck if it works then check the other applied policies in the network. If still the same check the upstream devices. ... View more