MS130-24P & MR46

AY2022
Getting noticed

MS130-24P & MR46

Good y'all.

 

I'm currently having some issue with these above 2 models.

When the MR46 are plugged into the switchports, none of MR46 power up. No lights whatsoever on the switchports / MR. Cable test seems to be good (all 4 pairs lights up and correct).

 

However, when the MR are plugged into a MX75, the MR power up and comes online..

 

Switch currently on MS16.9.

 

Anyone has similar setup? 

7 Replies 7
GIdenJoe
Kind of a big deal
Kind of a big deal

That means your MS130 is not supplying power to the AP's.
Make sure PoE is enabled on the ports.

AY2022
Getting noticed

By default POE is already enabled.

And power usage is just 7.82 W / 370 W.

Btw it's only 3 WAPs.

 

Anything else to check? 

 

GIdenJoe
Kind of a big deal
Kind of a big deal

I know it's the default but check the port configs anyway 😉
Maybe even put them on PoE disabled and back on enabled after a minute.
You should also check on the status of the switch to see the little lightning bolts on the switchports where you connected the AP's.

ww
Kind of a big deal
Kind of a big deal

try reboot the switch.

If it still doesn't work after reboot contact support.

 

AY2022
Getting noticed

Checked the switchport physically and there is no light at all. Also rebooted the switch many times.

Also tested with other POE device and the same ports work i.e. power + connectivity.

Forgot to mention this is a new RMA unit. 

 

Now I wondering, is there a difference in the way the 4 pairs of wires (network cable) is used?

Why the same MR works on MX75 but not the MS. Coz testing with a basic network tester shows no error. 

GIdenJoe
Kind of a big deal
Kind of a big deal

The normal EIA/TIA 568.A or B should work.
Normally in 802.3af and at only the blue and brown pairs are used to provide power.  So if your cables are fully wired up it should be ok.

Can you show a screenshot of one port configuration and perhaps a picture of the front of your switch?

DavidC1
New here

Same issue here but only with 802.3af devices, 802.3at works as expected. Meraki support confirmed to me that it is a known problem and that they are working on it but have no resolution timeframe. when I told them that this problem is impacting the business of the company I work for, they simply stopped responding and never contacted me again.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels