upgrade sw C9300L-48P-4X from MS 17.2.1 (latest stable) to IOS XE 17.15.3

[shlomoi]

Hi ,

yesterday we upgraded the switches C9300L-48P-4X

Since then the switches have been showing a message 

"Not running configured version"

We have rebooted and reset several times but the problem remain 
Does anyone know what the problem is

Thanks

[Mloraditch]

They may not have completed properly, or may be reporting incorrectly. You may be able to check from the  local status page to see the current version, but regardless Support would need to tell you for sure what needed to be done to correct.

[PhilipDAth]

Did you upgrade via the Meraki Dashboard, or manually via SSH?

Are these fully Meraki managed, or in "Hybrid" mode (used to be called "Meraki Monitoring")?

[shlomoi]

The new switch came with a Maraki version and we don't have a CLI. So we did it through the dashboard

Thank you

[cmr]

@shlomoi are they performing any L3 routing and did they have a static management IP address?

[shlomoi]

DHCP 

NO L3 ROUTING 

[cmr]

Also if you connect a cable to the management port and log in with user admin and the password from the Network/General section of the dashboard, you should see something like this that will help you see what version the switch is running and what might be the problem:

[cmr]

I just upgraded the above C9300L to 17.15.3 and there are a lot of entries in the event logs telling you what is happening.  I initiated the install at 22:59 and the below shows that the code was downloaded about 20 minutes later, it then took another 45 minutes to be installed, the switch rebooted and back in action:

[shlomoi]

I think it's not finishing the update.
I logged in again and it seems to still be on an old version.

[cmr]

It's definitely still on CS firmware.  What does the event log say?

[davidw2]

I was having similar issues with a MS390 upgrade to 17.15.3.   I spent a month back and forth with TAC on trying to get the upgrade to go.    Finally yesterday TAC responded that their is a bug if you have 7  or more dscp to cos rules in qos mappings.   I removed my mappings and on the next cycle the MS390 finally upgraded to 17.15.3