So far the only "problem", and I dont really see it as a problem, because, this is how I would like it to work 🙂 - but the dashboard text tells something different.
When you upgrade to a supported 17.15.x release, and you do your "service meraki connect" and "show meraki connect" to get all the into and the switch ready.
When you claim the serial in the dashboard, and add it to a network, the dashboard says this:
"Proceeding will overwrite all existing configuration". But I have never had this happen.
The switch never starts the actual conversion, I have to force it every time with the command:
"test platform software config mode managed".
Personally I think... this is nice, because up until then the switch actually stays in "config mode monitored", so you will actually see the switch be online in the dashboard, but in monitored mode, just the new way, instead of the old way with the onboarding app.
I really hope they keep it this way, so we can avoid using the app, and all the config it applies to the switch.
(Just like the 9800 in monitored mode).
And, of course we would like to be able ourselves to apply the "revert back command" that i guess is :
"test platform software config mode catalyst" 🙂
But as mentioned I have not seen any issues, on C9300 or C9200 with this new way of running native NexTunnel.
And I REALLY look forward to all the, ehhh, "normal" IOS-XE features coming here 🙂 - But I would settle for SmartPorts as the MS -> CS feature I feel I need the most.
I just did some 17.15.1m1 (the EFT release of native NexTunnel) to this official release with some ehhh mixed results.
A 9200L stand alone, no problems, upgraded as expected, nothing to see here 🙂
A 9300L stack uh oh .. this was a little "wonky".
The Switch seemed to upgrade just fine, and the equipment connected to the switch (APs, cameras, and clients) came online just fine and the whole thing was down for about perhaps 6 minutes.
BUT ... the switch itself never got back online on the dashboard.
So this was kinda strange to me, because as far as I know the new UAC feature and so on should "just work(tm)".
With everything working, except the switch not being online in the dashboard, i created a case, and went to bed.
This morning the switch IS online again, and the uptime graph looks like this.
Thats kinda strange right.
So of course there is some differences here versus the stand alone C9200L.
This was a C9300L stack, and this stack was setup with a static IP instead of DHCP, but that should of course not matter.
Im currently looking at logs to see if I can figure out what happened 🙂
