Hello everyone,   Thank you for the replies and your patience with my reply. I appreciate your messages. This little task has since passed and I haven't checked again if anything has been updated to check on PSUs in the way I was originally seeking. Have a great day. ... View more

Mystery new firmware, not yet in the dashboard...  I wonder what we can expect...? ... View more

Great, thanks 🙂 ... View more

I agree with @Mloraditch, it does look like the firewall might be blocking something.  Are you in a position to monitor the outbound communications from the C9300s to see if anything is being blocked or timing out? ... View more

Obviously JHA/regulatory domain always takes precedence with any freqs.  Irrespective of 6GHz being available or not in JHA, the 9163E offers the longest runway when compared to 78 , 76, and 86. If and when the the local JHA's catches up, 6GHz would be available, beats a truck roll and another budgetary cycle in my book. ... View more

Thanks for registering and confirming that this works for you, @ManuelS! Welcome to the Meraki Community. We hope you stick around. ... View more

Can you please provide more details? Can you share a screenshot of the error you are receiving? ... View more

Correct - no VMX for Oracle at this time.  Please contact your Cisco account team where they can register your interest and keep you updated. ... View more

thanks to all those who responded to clarify my doubts...highly appreciated!!! ... View more

What MTU are the client and server devices using? ... View more

@alemabrahao I'd suggest that the maximum (non realtime voice) clients is 30 per access point radio.  Therefore a CW9166I could have 90 clients with 30 on each radio (2.4, 5 and the 5/6 flex radio).  If they are realtime voice clients then 30 would be the maximum recommended, 10 on each radio. ... View more

To add some context, this error message "This device is using a DHCP IP address from VLAN X instead of using configured VLAN Y" occurs when the VLAN tag seen in the DHCP process is not the same VLAN tag as configured in the LAN IP section. When that message appears, it's trying to highlight that your device is operating in a different VLAN than you've configured it to, which can happen when the static IP fails the connection monitoring processes and it reverts to last-resort DHCP addressing to retain cloud connectivity. I've seen it also commonly happens when the VLAN ID in the LAN IP section is set to that of the native VLAN in the network: the device is told to expect a tag, but (per the intended purpose of the native VLAN, being to send traffic without a tag for devices that cannot understand 802.1Q) it receives none and states it as such in an error message. In this scenario, sometimes I've seen it shows VLAN 0, and sometimes it shows no value at all. ... View more

100% agree with @PhilipDAth here.  I've found a modern HP Probook Windows 11 laptop to be very reliable and a Samsung S22 Ultra to be a right pain...  Testing each device is definitely needed. ... View more

CS firmware versions CS 17.2.1 changelog Important notes Factory-default VLAN range is now 1-995, instead of 1-1000 as in previous firmware versions. Resetting the device to factory settings will apply this new VLAN range. This version's IOS image is based on 17.12.4 CCO. Upgrades to this version will result in a full system reload. New feature highlights Client Analytics Device Uptime for MS390s EEE (Energy Efficient Ethernet) Support Multi-auth with support for guest/failed/critical RADIUS Caching Support for Multicast in Live Tool VLAN to SGT mapping General fixed issues Introduced measures to significantly decrease occurrences of the Meraki container becoming trapped in a reboot loop while switches maintain data traffic flow. This scenario may still occur in rare cases. Corrected an issue that caused stack ports to be incorrectly displayed as "Disconnected" after a stack member was rebooted Fixed a bug that caused the Static Gateway IP to display as '0.0.0.0' in the L3 Routing Switch tab Resolved an issue that occasionally caused uplink ports to become stuck in an Uninitialized state Fixed a bug that caused a brief period of L3 traffic loss after the active member of a stack failed over Ms390 fixed issues Resolved an issue that prevented the application of fixed IP assignments if the IP being assigned had an active DHCP lease Fixed a bug that would infrequently prevent MS390 stacks from converging after a failover C9300 known issues Some C9300X stacks have been reported to fail due to memory exhaustion, requiring an ios restart to restore service General known issues Meraki native switches move LACP ports to an active forwarding state if configured. This can cause loops when connecting to an MS390 or other Catalyst switch unless the bundles are configured on the Catalyst side first. All Meraki native ports are configured in passive LACP mode so that loops do not occur between Meraki native switches (always present) Ms390 known issues In rare circumstances, MS390 stacks may display UDLD loop detection alerts that cannot be cleared by cycling the looping port MS390s may display an alert, "A power supply is offline" when a PSU isn't installed in the second slot ... View more

@van604 z3 works the same as an mx..w, as you expected. ... View more

That's what you should see.  If you have another non 6e/7 Asp in the same network the WPA3 client should connect to the 5GHz on that AP and when roaming should step up to 6GHz.  I've got this reliably working with CW9163E/CW9166I APs.  Before you say the 9163 is a 6GHz AP, it isn't in the UK, or pretty much any of the world other than the US... ... View more

When I'm replacing a core, I change it to the 'spare' 8k setting and then the new core can go back in at 4k without any other disruption. ... View more

Right Vlan with IP.   Appreciate your inputs.   Thank You, ... View more

@timmyver the Meraki SD-WAN is designed to connect with simplicity.  I don't think you can customise it to the level you are looking. ... View more

For your three cases I'd suggest:   1) Check the local status page, it might assist in recovery.  If not, power off the affected switch for a few minutes, repower and if that doesn't work, disconnect it from the stack.  Make sure it has an internet connection, then factory reset the affected switch, if that doesn't work RMA it.     2) Check the local status pages, if that doesn't help, make sure both switches have an internet connection, factory reset both switches.   3) Not likely. ... View more

So basically the cure was worse then the disease 🙂   ... View more

Switch firmware versions MS 17.2.1 changelog General important notes MS17 introduces a change to the default login credentials for the device local status page, using "admin" as the username, and the device serial number (upper case with dashes) as the password Ms12x important notes MS 16 introduced DAI on MS100 series platforms. If you are upgrading to a current release from MS 15 or earlier please ensure trusted ports and/or DAI-allow lists are configured prior to upgrading. New feature highlights DOM (Digital Optical Monitoring) Intelligent Capture RSPAN and VLAN Based SPAN SmartPorts New ms130x feature highlights Adaptive Policy on MS130X/R models General fixed issues All new LAG configurations will block redundant links if the connected device is not configured for LACP. This change fixes an issue where switches would sometimes move LAG ports to an active forwarding state prior to LACP convergence, creating the potential for loops. The change does not apply to existing LAG configurations. Corrected the Local Status Page to show the 1 Gbps (forced) option, previously mislabeled as 1 Gbps (auto) Fixed a bug that caused some clients using Hybrid, 802.1X, or MAB Access Policies to fail to authenticate after a switch reboot Port-bounce CoA commands now correctly cycle PoE ports Resolved an issue that caused some clients to be incorrectly added to a configured Guest VLAN when authenticated via RADIUS immediately after a switch reboot Resolved an issue that prevented some MS210 and MS225 devices from correctly releasing MAC addresses from the MAC forwarding table Resolved an issue that sometimes caused MS350 switches to remove existing L3 SVIs when enabling Auto-stacking Ms120 fixed issues Fixed a bug that prevented MS120-48 switches from correctly forwarding multicast traffic on ports 25-48 Resolved a bug that caused Epson POS printers to fail to authenticate when using MAB hybrid auth access policies Ms12x fixed issues Fixed an issue that prevented MS120 and MS125 switches from forwarding link-local multicast (224.0.0.x) traffic when 'Flood unknown multicast traffic' was disabled Ms130 fixed issues Fixed a bug that caused some MS130-X switches to experience slow upstream when connected directly to an MX device via an mGig port Ms225 fixed issues Resolved an issue that caused some MS225-48FP devices to become unresponsive and fail to forward traffic until rebooted Ms350 fixed issues Fixed a bug that prevented cable tests from correctly functioning on mGig ports Ms35x fixed issues Resolved an issue that caused some MS350-24X and MS355 switches to fail to negotiate 802.3bt UPoE LLDP connections General known issues LACP links may take up to two minutes to come back up when the Active Member of a stack reboots On MS250 and MS350 switches, MAC addresses learned via AGGR are not removed when LAG ports are disabled. Mac addresses will be removed correctly within 5 minutes of reenabling LAG ports. RADIUS communications may not recover after an initial failure when Critical Auth is enabled Some switches may encounter an error, "incompatible configuration for attributes: allowed_vlans" when attempting to aggregate ports regardless of allowed VLANs configured in Dashboard Ms120 known issues Switches may fail to provide PoE power to legacy access points (always present) Ms225 known issues In rare circumstances MS225 switches may encounter a software crash that results in a reboot Ms250 known issues In rare circumstances MS250 switches using Multi-Domain Hybrid auth access policies may enter a 'port not forwarding' state, sending clients to the Guest VLAN until the switch is rebooted Ms355 known issues When reconnecting a stack cable between MS355-48X2 swithces a stack member may go offline until both switches are rebooted Ms35x known issues In rare instances, stack ports fail to initialize after an upgrade (always present) Incorrect SFP port mappings may disrupt SFP functionality Switches may experience an unexpected reboot (present since MS 15) Ms425 known issues In rare circumstances MS425 switches may encounter a software crash that results in a reboot MS425s in stack configurations may periodically trigger New DHCP Server alerts that include mismatched VLANs/subnets Powering off the active switch in a MS425 stack may result in up to 5 minutes of downtime while the stack reconverges ... View more

I was wrong here. Meraki-managed IOS XE has the local status page. ... View more

@aplannet Access Manager is starting to roll out to Orgs via the Early Access page. It's not yet available on all Orgs/shards. So, if you don't see it yet it will be coming. Or, you can also reach out to your Cisco team and they can help.   https://documentation.meraki.com/Access_Manager   With Access Manager you can sync to your Entra deployment and tie that into SSID 802.1X auth now. ... View more