Leo asked that we create a separate thread and not contaminate the germane thread with this speculative discssion, I am creating this new thread only because I promised some tests in an earlier post: POE Discussions on MX65
So, I grabbed the POE switch which is rated for 802.3at standards and hooked up the MX65 (port 11) device to it. It failed to power up.
Then, while it is still connected to the POE switch, I supplied power to the MX65 using a DC jack and it powered up and the port 11 also lit up. I wondered now that this device has booted up, perhaps it will draw power from the switch and disconnected the DC supply, the MX65 shut down.
I then connected a CISCO meraki MR52 device to this same port of the POE switch and the switch was able to supply power to MR52 without any DC connection and upon logging in, the POE switch reported the POE device to be a Class 4 POE device.
So, my conclusion is that "ALL" of the MX65 can not be powered using a 802.3at switch. Some may be but the few that I tested did not power up using the switch.
Most people have seen this, I think. There was a discussion on whether it can be powered from a POE switch, and I had access, so I conducted these tests to put that "Easter egg" speculation to rest.
The MX65 can be powered solely by PoE from the Meraki MS220 but only when the MS220 is running the original Meraki firmware.
I maintain a FOSS firmware for the MS220 series, which has a custom daemon to manage the pd690xx PSE controller in the MS220. An MS220 running my firmware cannot power the MX65.
I haven't dug into the configuration registers of the pd690xx on the MS220 running Meraki's firmware, but they're somehow sending power without negotiation, which is a violation of the PoE specification.
So, I grabbed the POE switch which is rated for 802.3at standards and hooked up the MX65 (port 11) device to it. It failed to power up.
A switch or POE midplane conforming to the 802.3af/at/bt standard will not power the MX65.