Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
We were looking to purchase at least 1 MV44X as part of an upcoming camera project.However both the MV44X & MV84X share a different licence SKU to other cameras - LIC-MV-MULTCAM (replacing X/Y with the chosen term length like 1Y, 3Y, 5Y, 7Y, or 10Y)....
All our networks have only MS series switches in them.However on the firmware page it says Status Critical yet we are already on the recommended release 17.2.2 ...and why does it list 2 diff current CS versions when we don't have any CS in any networ...
I have started to receive a number of these alerts from cameras across three different sites that started Friday, 03-Jul-26 19:16:44 UTC.Has anyone else started receiving these? - all the cameras reported are working quote happily.Is it something I s...
It appears as though none of the posts from the Sensor section on the old Meraki community have been migrated across to this Cisco Community.Is this an oversight? Will these be migrated over shortly?@AmyReyes
I've seen the new MV44 dual imager camera that's been announced - High camera deployment costs? Not with Cisco - Cisco BlogsI cannot however find a Tech Datasheet for this.Does anyone know if this can be deployed outdoors?
@spaladug But if I have to add devices to a network to prevent someone else claiming them and am on a subscription licence that those numbers would get factored into our True-Up when we are not actually using them. Or is this why it says to create ...
Well that makes perfect sense, thanks @hellencharless54 - not sure why it hasn't always been this way.Maybe someone needs to ask Meraki to update the documentation
Well that's a new one on me, I had always assumed (apparently incorrectly based on the link to the documentation you posted), that if a device had been claimed and was sat in your inventory that nobody else could claim it).May be worth opening a case...
I see 32.2.4 is now the Recommended Release so will plan to upgrade and see if it resolves the issue at a couple of our sites that were impacted by this.