Firmware Upgrade Questions

[shawnkst]

Hi All

while trying to schedule a firmware upgrade for my switches in my network zone. I realized it detected Switch-CS （Catalyst） in my network zone. I am pretty sure that I do not have any Catalyst switches in my environment as well as a Security appliance with a MX18.211.2 firmware. Am I missing out something?

Thank you all for your time!

[aleabrahao]

Do you have any combined networks?

If you use combined templates or auto‑firmware scheduling, the Dashboard will list firmware tracks for all device families in that network type including Catalyst CS firmware.

[shawnkst]

Hi There

No combined templates or auto-firmware schedule.

[aleabrahao · Accepted solution]

Are you sure you don't have any networks created in the combined type?

[shawnkst]

Hi Bro

You are right, when I check under Organization- Overview, it display that network zone was created as a combined network type.

[dunky]

It lists both for me to and I don't have and Catalyst switches either.

I've learnt to just ignore the CS line 😀

[Philip D'Ath]

This is expected behaviour.

You could add a CS switch in the future, so it needs some concept of which firmware version to use.

[shawnkst]

Hi Philip

What about the security appliance that doesnt exist in my network zone but the firmware update is asking to upgrade it firmware version?

[Philip D'Ath · Accepted solution]

That is expected behaviour if it is a combined network, or the network has had a security appliance in it, or was cloned from a network that contained a security appliance.

[khalidbochajra]

The Meraki dashboard still shows those devices just to tell you "Hey! I'm supporting these devices." but that doesn't mean they exist physically. I mean after all we can manage a device even before adding it physically, so why would that be any different?

[khalidbochajra]

Sorry, my bad! I mean before we add the device physically we add it to Inventory first.. But you got the idea of how combined networks work and how they can combine the MX,MS and MR networks into one for ease of management even though those devices don't exist.

[Bill Hart]

The problem I face is the crying wolf aspect of this. Even after upgrading all my switches (MX Firmware, not Catalyst, because I don't own any), my Network Firmware is Showing as Critical Status, which is crying wolf (which has terrible consequences because everyone will ignore Critical states moving forward). 

Whoever thought this was a good idea at Cisco Meraki needs to go back to school or work on the other side of the fence for a few years to know our pain.