Congratulations everyone! As usual, a huge effort across the board.   ... View more

If you compare the last couple of versions the main differences actually are:   Release highlights In this release, we are excited to support the following features and enhancements. Below are the key highlights: Introducing a new onboarding flow for cloud and hybrid operating modes: two powerful ways to manage your Catalyst 9000 switches from the Meraki dashboard. These modes give you the flexibility to choose between a fully cloud-managed experience (cloud operating mode) or a hybrid approach (previously referred to as cloud monitoring), that offers configuration via an embedded cloud CLI while leveraging the cloud for monitoring and troubleshooting. Learn more http://cs.co/9000F98vQ (Note that the new onboarding process for hybrid and cloud operating modes will be rolled out in phases. If you don’t see the new UI while adding your Catalyst switches to a network, please be assured it will be available soon. We appreciate your patience and understanding as we work to bring this feature to all eligible organizations.) Configuration Templates now supports C9200L switches Intelligent Capture now works with non master devices in stacks of C9300/MS390 Meraki Authentication (Meraki Auth) Alternate Management Interface (AMI) Port Schedules SNMPv3 Encrypted Traffic Analytics Energy Efficient Ethernet MAC Allow Lists Before you upgrade or migrate: key considerations Layer 3 switches with a DHCP management IP address are not supported. Please configure a static IP address for the management interface to avoid network disruptions and improper traffic flow. If the L3 switch’s default route and management interface gateways are NOT the same prior to the upgrade, after the upgrade to IOS XE all switch traffic will use the management interface’s DHCP acquired gateway as a next hop. Layer 3 switches cannot run DHCP servers on uplink interfaces. Please note that interfaces that have been designated as a preferred uplink cannot also run a DHCP server. Interfaces with both Preferred Uplink and DHCP server configurations will have the DHCP server configuration disabled on that interface. Switches using the Alternative Management Interface (AMI) will require an L3 SVI to be configured for the same vlan assigned to AMI. For AMI to work, your network must have AMI configured and your switch must have an SVI configured matching that AMI vlan. New known issues Clients Static DHCP reservation cannot be changed. Workaround requires removing static reservations and recreating them. Configuration application fails due to bad-cli errors related to et-analytics during each config push. Changing destination port configuration for encrypted traffic analytics, while active, can corrupt config. As a workaround, disable then re-enable with new port config. Named VLAN column is not displaying any values in the switches client summary table. IPv6 route for DNS is set with an empty Gateway IP, leading to configuration application failure. Devices lose all configurations after an upgrade from 17.15.2 to 17.15.3. Rebooting or shutting down a switch shortly after upgrade (17.15.2 to 17.15.3) might not preserve “safe-config”. Please wait 30 min after upgrade to ensure configuration is marked ‘safe’. MTR live tool does not function from the dashboard. 9200L 8-member stack: Stack merge occurs due to incompatibility when installing a new image. 8-member stacks may experience longer boot or upgrade times. Issue with upgrading a stack of 8 members on the 9200L series from one cloud-native IOS XE version to another. The Default VLAN profile API appends new configurations instead of overwriting existing ones potentially leading to unexpected behavior. The device uptime displayed for stack standby members is incorrect. Fixed issues Port scheduling is supported on this version. LACP is not functioning on the network module ports of NM-2Y modules. Transitioning from cs to ios xe 17.15: unsupported features The following CS features are not supported in this release: Sticky MAC Client Tracking does not work on 10G-MGig, 25G, 40G and 100G C9K ports Geo-cloud Certain features will be added to the IOS XE versions in future releases. Refer to the Cloud-native IOS XE documentation for further details: http://cs.co/9001Q4ALF   ... View more

Hi, Do we have API endpoint for configuring source based routes and Non-Meraki VPN peers ?  As we are in the migration of MX Devices, wanted to config via Python script using Meraki API's ... View more

Many thanks for your sharing guys. Just to let you know that without you we wouldn't be us 😉 ... View more

Thank you all for the information, much appreciated. ... View more

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