Unsolved
This post is more than 5 years old
1 Rookie
•
21 Posts
0
203362
April 22nd, 2013 12:00
5548P- inconsistent PoE experiences
I have a recently deployed stack of 3 5548P switches. I'm having some issues when trying to supply power to Ruckus 7372 wireless APs: in some ports, the APs will power on, and transit data exactly as expected. In other ports, the APs never show power.
In most of the ports that will not power a Ruckus AP, I can power a Meraki MR12. Except for one tested port: where the experience is that the MR12 power light does a very rapid flicker, and none of the port's lights on the switch light up. (Switches are in production, not all ports can be tested for PoE)
This power problem was first observed under firmware 4.0.1.11, and continues through an upgrade to 4.1.0.8.
I have carefully compared PoE configuration between working and non-working ports, and see no difference. No Power Limit threshold that could be exceeded, no port locking, Green Ethernet Config is the same.
The only PoE devices attached to the stack are 2 other Ruckus 7372s, each pulling 3Watts, from different switches. This is not a total power budget problem.
With a 7273 plugged into a port, I can refresh System: General PoE: and see the Invalid Signature Counter steadily increasing.
Can anyone provide some troubleshooting ideas to help my 5548 and Ruckus gear get along properly?
ziyouren1121
2 Posts
0
September 17th, 2013 01:00
IEEE 802.3af/at Power over Ethernet switch is an idea choose for IP-based camera, Wireless AP
PoE switch
billflu
1 Message
0
October 29th, 2013 07:00
I had a similar issue with an HP switch (2910-24G-PoE+ al) and 7982's. I would get the orange blinking PoE light on an HP switch, tested with W_15_08_0012 and W_15_12_0011. With the firmware downgraded to W_14_38, the AP's powered up, but I didn't want to revert the firmware. Also, tested on a CIsco PoE switch, the AP's would not power.
I RMA'ed one of the 7982's and it worked on both the Cisco and updated HP. The rest of the AP's (being used with Ruckus PoE injectors) are currently being RMA'ed. The existing "broken" AP's had serial numbers starting with 3213 and 3313, while the new AP started with a 36. This lends credence to another forum posting about a change in hardware for the later revisions of the 7982's. If you are having a similar issue, please try RMA'ing at least one AP to test, even though you may not think it will fix the issue.
cpangker
16 Posts
0
October 29th, 2013 14:00
Please keep us posted.
I'd like to see the results with the replacement APs.
Cooter1945
2 Posts
0
November 16th, 2013 05:00
You fool. You never use cat3 on an Ethernet network.
Cooter1945
2 Posts
0
November 16th, 2013 05:00
You are incompetent. Cat 3? You never use cat 3 on an Ethernet network for any device anywhere any time. Cat 3... Good grief.
su_A_ve
1 Rookie
•
100 Posts
0
August 26th, 2016 07:00
Resurrecting an old thread but I wonder if anyone resolved this problem without having to switch switch models or brands.
We've user a few 5524P and 5548P to power some Aruba AP-105. We are replacing them with new AP-325 and also adding more. In the past, these switches would be 1/2 to 3/4 full. Now these are 3/4 to full.
The switches are supposed to be full power (I also have the external power supply on the 48 port one) But we've seen this same problem where 1,2 or 3 of the 4 ports per quad not working. In a few cases, all four ports work, but that's maybe one or two quads per switch. On some cases it's just one port that only works.
Same as others. If I have an AP plugged in ports 1 and 2, only 1 works. Unplug port 1, and port 2 lights up. Plug port 1 back and nothing. Unplug port 2 and port 1 lights up. Similar results on other quads, except we also have 2 or even 3 ports working at a time. No rhyme or reason.
Aruba wants packet capture and logs, but the APs either see power or they don't. I haven't try this yet, but doubt that would help as I don't think it's a negotiation issue but an electronics issue with ports turning or not and not sure if it's configurable.
The latest settings that seem to have given me 3 our of 4 for most of the ports (at least on a 24 port switch) have been:
no eee enable
spanning-tree portfast
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
lldp med enable poe-pse
power inline priority critical
switchport mode general
power mode is set to per port.
Most switches are running old 4.0.0.3 version, but even with 4.1.0.20.
Any ideas? TIA
syuroff
1 Rookie
•
21 Posts
0
August 26th, 2016 08:00
I'm of the opinion that the Dell 55xx switches are just oddly flaky re PoE. Just yesterday, we punched down a new port in the building. Wiring checked out on the tester. Patched into the 5548P, attached a computer: auto-negotiated to 1Gig as it should, data flows both ways. All systems go.
Swap out the computer for the VoIP phone. No power to the phone... nothin. Take phone directly to switch port via 1M patch cable- it boots as expected. OK... that's what I need, but hanging out in the server room isn't the destination for this phone.
Use that same patch cable to connect the switch to the punchdown panel in the server room again, return phone to intended remote jack. Plug in using the same cable we originally tested with.
Now it works.
I have no idea why. Except for flaky switch is flaky.