Cloud Management with IOS XE 17.18.1 is now available in Beta!

Solved
gregpalmer2
Getting noticed

Cloud Management with IOS XE 17.18.1 is now available in Beta!

Cloud Management with IOS XE Overview

 

17.18_Beta.png

 

 

 

 

 

 

 

NEW! Experience the power of IOS XE 17.18.1 (beta) for Cloud Management with cloud configuration. This release expands more C9000 switching platform support (such as C9200/CX, C9300LM, and selected C9500H) and packs with power capabilities. Learn more.

 

  • 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. 

 
Personal Take: I'm really excited to see the C9500 supported on the Meraki Dashboard for "cloud configuration source". The Intelligent Pack Capture feature of Dashboard should provide immediate value to network administrators.

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
1 Accepted Solution
Kevin_R
Meraki Employee All-Star Meraki Employee All-Star
Meraki Employee All-Star

Hello @gregpalmer2,

 

The document is used for conversions from CLI to configuration source: cloud mode for IOS XE. At this time, IOS XE 17.18.1 is not yet available on Dashboard, so updating the firmware for CLI mode devices and attempting to onboard them in config: cloud mode should not be done. Updating the firmware for CLI mode devices to IOS XE 17.18.1 in preparation for a config: cloud migration is definitely an option though! IOS XE 17.18.1 will likely be released soon™ for the Meraki Dashboard.

If you found this post helpful, please give it kudos. If my answer solved your problem, click "accept as solution" so that others can benefit from it.

View solution in original post

26 Replies 26
thomasthomsen
Kind of a big deal

Hmmmm does not seem to be a selectable option under software firmware upgrades yet.

gregpalmer2
Getting noticed

Thanks for verifying @thomasthomsen! That's odd the download is not available in the dashboard.

 

New behavior?

 

I saw the download made avaible on Cisco software central and the announcement on the Meraki documentation site. The instructions - "Conversion from CLI-managed IOS XE Catalyst Switches to Cloud Management with Cloud Configuration" - are directing the network administrator to download the software manually.

 

Firmware VersionSoftware Download Page
17.15For C9300/L/X, please use image cat9k_iosxe.17.1x.xx.SPA.bin that can be downloaded from the software download page.
 For C9200L, please use image cat9k_lite_iosxe.17.xx.xx.SPA.bin that can be downloaded from the software download page.
17.18.1 (beta)For C9300/C9500H, please use image cat9k_iosxe.17.18.01.SPA.bin that can be downloaded from the software download page
 For C9200/L/CX, please use image cat9k_lite_iosxe.17.18.01.SPA.bin that can be downloaded from the software download page

 

 

17_18_download_available.png


If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
Kevin_R
Meraki Employee All-Star Meraki Employee All-Star
Meraki Employee All-Star

Hello @gregpalmer2,

 

The document is used for conversions from CLI to configuration source: cloud mode for IOS XE. At this time, IOS XE 17.18.1 is not yet available on Dashboard, so updating the firmware for CLI mode devices and attempting to onboard them in config: cloud mode should not be done. Updating the firmware for CLI mode devices to IOS XE 17.18.1 in preparation for a config: cloud migration is definitely an option though! IOS XE 17.18.1 will likely be released soon™ for the Meraki Dashboard.

If you found this post helpful, please give it kudos. If my answer solved your problem, click "accept as solution" so that others can benefit from it.
thomasthomsen
Kind of a big deal

So what you are telling us, is that if we want to try this NOW (with all the new features), we should, basically, get support to revert our current cloud-managed IOS-XE Catalyst switches back to normal "catalyst mode", then we can manually upgrade the switch to 17.18.1 and then we can redeploy it to the dashboard in cloud-managed. 🙂

gregpalmer2
Getting noticed

Thank you Kevin. The C9500 and C9350 require IOS-XE 17.18.1 for cloud connectivity. Are you outlining that the code is in beta for new 9350/9500 devices but not available for in service upgrades of existing cloud managed 9200/9300 devices?


If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
Lurick
Getting noticed

I wish we could get a roadmap/timeline for IPv6 RA support so we can at least have SLAAC addresses at least but alas it seems at least 17.18.1 won't support it at release either 😞 

Minyi
Meraki Employee All-Star Meraki Employee All-Star
Meraki Employee All-Star

Hi community friends - as of Aug 20th, this has not been released to dashboard yet (we are getting too excited and getting ahead of ourselves here with documentations.)

 

Please stay tuned, I promise you will be first to know here when it's available. We are doing everything we can to deliver - just need a few more final testing!

 

gregpalmer2
Getting noticed

Thank you @Minyi I see the documentation has been updated to read coming soon. We're very excited to hear of the official update.


If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
thomasthomsen
Kind of a big deal

It seems that ALL information on 17.18.1 with the new models, and new features where removed from the documentation pages.
Did I take screenshots ? ... yes .. yes I did 🙂

Minyi
Meraki Employee All-Star Meraki Employee All-Star
Meraki Employee All-Star

i know you would, Thomas! We removed them so it won't confuse the folks who are not on community(but they should 🙂

 

It's released now! Please let us know your feedback. 

GIdenJoe
Kind of a big deal
Kind of a big deal

Still testing?  what's happening with this version?

thomasthomsen
Kind of a big deal

Seems to be released now 🙂

But there was a page previously (I have a screenshot before it was taken down) with licensing information for all the routing features, where everything was basically in "Enterprise" license, is this still true ?

thomasthomsen
Kind of a big deal

Ahh found it .. it is still there.

Enterprise for "all", customers will absolutely LOVE this.

GIdenJoe
Kind of a big deal
Kind of a big deal

Could you link the exact document?

thomasthomsen
Kind of a big deal
gregpalmer2
Getting noticed

@thomasthomsen  Were you able to find 17.18.1 in the firmware downloads on Dashboard?


If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
thomasthomsen
Kind of a big deal

Yes

Skærmbillede 2025-09-03 195718.png

thomasthomsen
Kind of a big deal

And switches are also updated

thomasthomsen_0-1756928139355.png

 

thomasthomsen
Kind of a big deal

I think i broke UAC.

I had a static IP set on a SVI on my switch for mgmt, and of course a "uplink" config on that interface in the UI.

By mistake I configured another port as a routed port with the "uplink" checkbox checked (this port has no link), so of course the switch went offline.
Should UAC not "save" me here, but trying the other interface at some point ?

GIdenJoe
Kind of a big deal
Kind of a big deal

Normally if you have any other interfaces with DHCP then uac should pick that one.

thomasthomsen
Kind of a big deal

Both interfaces where static IP.
But I think I have found the error, someone(tm) was messing around with the upstream MX at the same time ... I HAVE ABSOLUTELY NO IDEA WHO WOULD DO SUCH A THING ... 🙂

thomasthomsen
Kind of a big deal

Im happy to report that IPv6 and VRFs are working as expected.
Now if only I could just create a interface on a MX that could be something less then a /64 for a small router net (between the MX and the Catalyst switch), that would be lovely. - I know we have "enough" IPv6 adresses, but setting aside a /64 just for a link net .. seems ... excessive 🙂

PS: When setting up BGP routing you cannot select a VRF, you can see the VRF option after, but it is greyed out. 

Lurick
Getting noticed

Does IPv6 work for your end clients via SLAAC @thomasthomsen ?

That's the one thing that was blocked on 17.15 that I'm hoping is working in 17.18 in meraki managed mode for me.

thomasthomsen
Kind of a big deal

Ill tell you later today.

Lurick
Getting noticed

Thanks! Fingers crossed but not holding my breath 🙂

gregpalmer2
Getting noticed

You are a great man @thomasthomsen !!!


If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
Get notified when there are additional replies to this discussion.