17.18.1 IOS-XE Beta is OUT! New Models, New Features, Read Carefully!

[Mloraditch]

This section is blank on the dashboard: 

Transitioning from cs to ios xe 17.15 or 17.18: unsupported features, will fix if/when they fix

Important notes

• After upgrading to IOS XE, downgrading to any CS version via the dashboard is restricted - a factory reset may be required and support assistance will be necessary. Please consider this before upgrading your network to Cloud Management with IOS XE. Learn more - http://cs.co/9002xhAan
• Please review the list of supported models with minimum firmware support versions in the release notes below before proceeding with the upgrade. Attempting to convert unsupported models such as C9500X may result in an unusable switch.
• Stacking Limit for C9200L series models: C9200L series models support stacking configurations of up to 5 members. Please ensure your stacks for these models adhere to this limit. Exceeding 5 members may lead to unexpected behavior. This will be resolved in a future release.
• Switch Templates with bound networks won’t be able to directly upgrade from CS firmware to IOS XE firmware. The recommendation is to unbind and migrate networks independently rebinding into IOS XE switch template.

Cloud management with ios xe overview

• Since the introduction of Cloud Management with IOS XE 17.15, users enjoy faster boot and initialization, a Cloud CLI Terminal for running troubleshooting commands directly from the dashboard, and a new generation of features powered by advanced IOS-XE capabilities!
• The new 17.18.1 release brings cloud management to more switch platforms, including the C9200, C9300, and C9500 high performance families. It also unlocks more powerful IOS XE features like advanced routing, high availability, and expanded cloud-powered value, so you can manage a seamless, secure, and scalable network from access to core, all within one intuitive dashboard.

Release highlights

• In this release, we are excited to support the following features and enhancements. Below are the key highlights:
• Extending cloud management support to additional switch platforms from access to core, including C9200/CX, C9300LM, C9500 high performance models, all existing supported C9200L, C9300/L/X and MS390 models, and corresponding network module support. Please see supported models section below for details.
• This release is also packed with powerful enterprise management capabilities, empowering you to deliver secure networking management with operational simplicity and scalability. Below are the key highlights:
• Advanced routing configurations: Border Gateway Protocol (BGP); Virtual Routing and Forwarding (VRF); Routed Ports
• High availability: StackWise Virtual (SVL) on C9500H; Rapid Per-VLAN STP (RPVST+); In-Service Software Upgrade (ISSU) is available from 17.18.1 and can be used for future upgrades
• Cloud value expansion: SmartPorts Profiles; Intelligent Capture Scheduling; Device Uptime; Digital Optical Monitoring; VLAN to SGT; Radius Caching
• Additional DHCP options (custom default router and domain-name suffix options)
• For supported models with specific features, please refer to documentations.

Before you upgrade or migrate: key considerations

• After migrating CLI/DNA managed switches to cloud configuration source, please note that console and SSH access are no longer available. All management access is only available via the cloud dashboard or the local status page through the rear management port.
• Please refer to Changes in Layer 3 Behavior on documentation: https://documentation.meraki.com/MS/Cloud-Native_IOS_XE/Cloud-Native_IOS_XE_Overview#Changes_in_Beha...
• 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.
• After upgrading from CS to Cloud Management with IOS XE firmware, port mirroring configurations on module ports will not be retained. Users will need to reconfigure port mirroring on module ports following the upgrade.
• The 30-day grace period applies to licensing for Catalyst switches onboarded to Meraki Dashboard, allowing customers to trial cloud mode prior to fully committing. Valid DNA licenses can be converted to Meraki licenses through a qualified promotion process. Refer to http://cs.co/9005aw6VH for more details.

Share your post-upgrade feedback!

• We value your feedback on our latest release! Please take a moment to complete this brief 5-minute survey http://cs.co/9001fpIhR and share your experience with us.

Supported models

• C9200L-24T-4X, C9200L-24P-4X, C9200L-48T-4X, C9200L-48P-4X, C9200L-48PL-4X, C9200L-24PXG-4X, C9200L-48PXG-4X, C9200L-24PXG-2Y, C9200L-48PXG-2Y, C9200L-24T-4G, C9200L-24P-4G, C9200L-48T-4G, C9200L-48P-4G, C9200L-48 PL-4G
• C9300-24T-M, C9300-24P-M, C9300-24U-M , C9300-24UX-M , C9300-48T-M , C9300-48P-M , C9300-48U-M , C9300-48UXM-M , C9300-48UN-M , C9300-24S-M, C9300-48S-M , C9300X-12Y-M, C9300X-24Y-M, C9300X-48HXN-M, C9300X-24HX-M, C9300X-48HX-M, C9300X-48TX-M, C9300L-24P-4X-M, C9300L-24T-4X-M, C9300L-24UXG-4X-M, C9300L-48P-4X-M, C9300L-48PF-4X-M, C9300L-48T-4X-M, C9300L-48UXG-4X-M, and its corresponding Catalyst switch SKUs for migration.
• MS390-24-HW, MS390-24P-HW, MS390-24U-HW, MS390-24UX-HW, MS390-48-HW, MS390-48P-HW, MS390-48U-HW, MS390-48UX-HW, MS390-48UX2-HW
• C9300-24UB, C9300-24UXB, C9300-48UB, C9300-24H, C9300-48H, C9300L-24T-4G, C9300L-48T-4G, C9300L-24P-4G, C9300L-48P-4G, C9300L-48PF-4G, C9300L-24UXG-2Q, C9300L-48UXG-2Q, C9300LM-48UX-4Y, C9300LM-48U-4Y, C9300LM-24U-4Y, C9300LM-48T-4Y
• C9200-24T, C9200-24P, C9200-24PB, C9200-24PXG, C9200-48T, C9200-48P, C9200-48PL, C9200-48PB, C9200-48PXG
• C9200CX-12T-2X2G, C9200CX-12P-2X2G, C9200CX-8P-2X2G, C9200CX-8UXG-2X, C9200CX-12P-2XGH, C9200CX-8P-2XGH, C9200CX-8UXG-2XH
• C9500-48Y4C, C9500-24Y4C, C9500-32C, C9500-32QC
• For supported network modules and their corresponding minimum firmware support, please refer to documentation http://cs.co/9006fsb86
• Breakout Cables aren’t supported at this time.
• C9350 Series Smart Switches. Please note, this is the first IOS XE release for C9350 series switch. These advanced layer 3 features are currently not supported: BGP, VRF, Rapid Per-VLAN STP (RPVST+), Routed Ports, Digital Optical Monitoring, Radius Caching, Intelligent Capture Scheduling, SmartPort- Profiles, Encrypted Traffic Analytics (ETA), Detailed Traffic Analytics on trunk ports, port channels, and uplink modules, and VLAN to SGT mapping. Certain fields in NetFlow exporters are not supported.
• The following CS features are not supported in this release:
• Sticky MAC
• Gov(Federal), Canada, China, or India Cloud
• Port mirroring (SPAN) configuration will need to be reconfigured post upgrade
• Certain features will be added to the IOS XE versions in future releases. Refer to the cloud management with IOS XE documentation for further details: http://cs.co/9001Q4ALF

Transitioning from cs to ios xe 17.15 or 17.18: unsupported features

•  

Known issues

• Fixed IP assignment via DHCP lease can fail if client MAC addresses or IP addresses overlap
• Adding an additional Fixed IP address or DHCP reserve range that is contiguous with an existing Fixed IP address or DHCP reserve range will will result in configuration update errors
• If QoS is in use, C9350 switches will encounter errors applying new configuration (including during the Meraki onboarding process). QoS can be disabled to allow for normal operation until a fix is available.
• Using MAC allow list on the default or currently installed network module ports will result in a config apply failure that will require a factory reset to resolve
• Modifying the default DSCP-to-COS Mappings in the Quality of Service section of Switch settings results in errors. Networks that use non-default DSCP-to-COS Mappings may fail to correctly upgrade from CS 17 and earlier firmware versions.
• Adaptive policy configurations are not carried over when migrating from a trunk / access port to a routed port and can cause configuration errors. You MUST remove the adaptive policy settings first before migrating to a routed port.
• SNMPv3 only supports AES 256 and will be reconfigured as part of your transition to IOS XE 17.1X
• CFLOW data may be missing when capturing packets from the uplink port
• Client tracking is not available on ports at 10G or faster
• Attempting to create a DHCP server using DHCP option 135 (DNS Suffix) with hex value greater than 180 characters results in an error
• Device uptime for stack members incorrectly displays the stack active device’s uptime instead of the member device’s uptime
• Named VLAN configuration for stacks generates configuration errors
• The Default VLAN profile API appends new configurations instead of overwriting existing ones potentially leading to unexpected behavior.
• Switch configuration is cleared after an immediate reboot following an upgrade from CS firmware to IOS XE firmware, causing the upstream Port-channel to enter a suspended state.
• Network locations with unstable Dashboard connectivity may trigger UAC to use a non-preferred uplink. Once stable connectivity is restored on the preferred uplink, management IP may not automatically fall back to the preferred one.
• Switch Client Summary displays incorrect VLAN for specific ports
• Exported Netflow flow records incorrectly omit Adaptive Policy group information
• Client devices that don’t support link auto-negotiation may cause their connected Port to show as disconnected on Dashboard
• Download config keeps failing on port-security with uplink ports
• When configuring an L3 aggregate interface you must first configure the required ports as routed ports on the switch ports page, then aggregate them as a L3 aggregate.
• Overlapping DHCP pools cause configuration generation errors if VRFs are not configured first. Configure VRF prior to DHCP pool configuration.
• The ARP table in Live Tools is incorrectly limited to a single page, showing only a partial list of ARP entries for both Default and custom VRFs.
• C9200L supports 1 VRF. To update an existing VRF please remove the existing VRF before creating a new one.

Fixed issues

• Resolved a bug that prevented the MTR life tool from correctly returning results

[rhbirkelund]

Looking at the known issues, I can’t believe that this is actually a beta release. It should be an alpha, or very early release.

Usually, I’m not that afraid of Meraki Beta software, since historically they’ve been rather stable. But this “beta” seems downright dangerous. 

[Mloraditch]

Considering what we were told about this coming out and when it did come out, I think some tradeoffs may have been made to get something out the door. Fingers crossed folks are rapidly coding those fixes.

One additional thought is, it would be nice to note for these releases if the bug ties back to a regular Cisco bug that everyone is affected by, or if it's solely tied to the dashboard management. Although we are still barely getting Meraki bug ids on some products, so I may be asking for too much. 😂 

[rhbirkelund]

• C9200L supports 1 VRF. To update an existing VRF please remove the existing VRF before creating a new one.

Does this include "Mgmt-intf"?

[GIdenJoe]

This is a great question and I'm also curious about the result.

[rhbirkelund]

Great that we got this fixed, in the first release!

• Resolved a bug that prevented the MTR life tool from correctly returning results

(sarcasm may occur)

[RaphaelL]

I will be trying most of the new "features" on a C9500 in the upcoming weeks. 

What hardware are you guys testing ?

[cmr]

C9300L-24UXG-4X upgraded this evening...

[RWelch]

@cmr Curious to learn about your upgrade (observations and experience) if you are able/willing to share.

[PhilipDAth]

My gut tells me I probably won't feel comfortable putting this in a customer production environment for another 12 to 24 months.

I am going to upgrade my test C9300-24UX now.  Nothing like giving bug feedback to get issues fixed.