Switch stack switches report "Failed to fetch interface data."

[NHFarmer]

Not sure when this started, but our switch stack (four MS210 & one MS225) are reporting "Failed to fetch interface data. This endpoint is not supported for switches in switch stack" when I click on a switch port. This wasn't happening after the stack was put together. Not sure exactly when this issue started as I haven't needed to make any port changes in quite a while.

The displayed information when clicking on "Ports" at the top of the screen is correctly showing each port status and traffic. When clicking on any port, aside from the error above, the displayed information looks correct, as does the list of clients. I have not yet tried to make any changes as I'd like to understand the issue first.

We have an MX84 at 18.107.10. The switches are at MS 17.1.3 and it says there is an update available on the switch status page, but not on the Organization->Firmware page.

Any thoughts on how to fix this? Thanks in advance.

[Mloraditch]

I've not seen this before.

This is likely either a GUI bug and you can try switching to the old or new version in the upper right of the switch view, depending on which version you are on and see if it clears. If it does I'd open a support case and make them aware.

Or it's a backend data issue that could be on the backend or could require a reboot of the switches or a firmware update.

If switching the gui doesn't work, I'd open a support case and ask them for further guidance so the issue can be logged and tracked if necessary.

[NHFarmer]

I forgot about the GUI change. Yes, switching back to the old version makes the problem go away and things work OK.

[Mloraditch]

Good to hear. they may already know but I'm sure it could everyone in the long run if you take a few seconds to open a support case to help elevate the issue for them.

[NHFarmer]

Support case created.

[Dunky]

Same here, is happening to every switch stack (all physical) across our organization, MS210's and MS150's.

Support case opened.

Only started happening very recently.

All switches are on 17.2.1

[alemabrahao]

Are you doing the physical stack? Note that stacking between MS210 and MS 225 is only supported when done via physical stack.

Have you checked the physical connections? I suggest you open a support case if you have already checked everything.

[NHFarmer]

Yes, it is a physical stack. Everything worked fine after the stack was implemented, which was about 3 months ago. The stack ports all show a status of connected.

[r2kat]

Hi NHFarmer,

I face the same problem since monday on different sites. Just recognized that this error is just showing up on switches with the current firmware MS 17.2.1.1 and not on switches with MS 16.9.
But i can not see any real problems. All information seems to be ok. 
Also no problems in the old view.

Edit: also got the problems now on MS 16.9, so it looks like a GUI bug.

Best regards
René

[sheepfield]

Hi together, 

i got the same "problem" but i can't notice any disadvantages. No changes made the last days and it is displayed on stacks and solo switches. I guess it's a GUI bug.

MS225 with MS 17.1.4. 

BR Frederik

[NHFarmer]

The response from Cisco Meraki Support:

Please note that this is a known issue that is currently being investigated by the Engineering team. I have attached your case to the original issue that is being reviewed by Engineering. This will ensure that we receive the latest updates.

Please click on the View Old Version on the top-right of the Meraki dashboard and view the port details as a workaround. This issue is persistent only on the new version. Please note that I will reach out to you as soon as I have more information. Meanwhile ,please let me know if you have any other questions or concerns.

[NHFarmer]

Oddly, this morning when I went to take a screen capture of the problem, it's gone. No change in firmware.

[r2kat]

Thats true, i also dont see this error any more. 
Was still there today in the morning at my network.