Dear @jeff13 ，

 

Thank you so much for taking the time to report the issue to TP-Link community!

 

1. Generally speaking, TL-SG3424P could power EAP225-Outdoor properly.

Have you test the cable between them?

If you use a short Ethernet cable to connect them for testing, it will be more better.

 

2. Does the POE LED lit up when connect EAP225 to TL-SG3424P?

  @jeff13 

 

Hi Jeff...sorry to hear about the issues you're having.  I have a number of 225-outdoors on 2008P's and 2210P's and they all work fine (but are running older 5.0.5 firmware if that matters).  I was however wondering if your 3424P has a bad POE switch module?  Most TPLlink POE capable switches are built in blocks of 4 ports, so I suspect each POE control chip can cover 4 ports...and you said you had three 330's running just fine on the 3424.  My question is have you tested the 225 in a known good block of 4 ports (for instance if 330 #1 is plugged into port 3 and is working, then POE should be working on ports 1,2 and 4).  I would be very surprised if there is *ANY* software interaction during the power negotiation...other than maybe 'approve' because I still have power budget or reject because I don't.  That leads me to believe you might have faulty internal components in the switch, or the POE AC supply for the switch is having issues.

 

Curious to get to the bottom of this one!

  @jeff13 

 

Are you able to get any logging info off the switch regarding the POE negotiations?  You might have to SSH in as opposed to using the web UI.

  @jeff13 

 

Actually I think I know what the problem is.  Have you tested the EAP225-outdoor on the SG3424P yet using the cable that came in the box?  I suspect you are using cables you had lying around and those cables might be wired differently than straight through EIA568B (google this for images) ie you are using crossovers or other oddball configs (4wire etc).  I have had zero issue powering my EAP225's using TPlink 2008P and 2210P switches and straight EIA568B cables.

 

The reason for this is that the EAP225-outdoor is non-standard from a POE point of view.  Ethernet provides 4 pairs of wires and 1 or 2 pairs can be used for POE applications.  The problem with the EAP225-outdoor is that it tries to satisfy BOTH passive POE (24V) AND active POE (48V, 802.3af/at)  If you try to apply the 802.3af/at auto-negotiate power to the wrong pair, it won't negotiate, and won't power up.  You can also burn out the EAP225-outdoor by forcing 48V onto the 24V passive input pair.

 

For others that find this post, it's also the reason why you can't power an EAP225-outdoor via a POE++ (90W) injector, or a long range injector...  

 

So try a standard pre-fab cable between the AP and switch and let's see if that makes a difference.  If not, I'll figure out some CLI for you, like maybe:

 

TL-SG3424(config)# show logging buffer level 0

 

(see here for more info/help:  https://static.tp-link.com/res/down/doc/TL-SG3216(UN)_V2.0_CLI.pdf )

  @jeff13 

 

You don't need to buy a cable, you just need an SSH client like PUTTY (fwiw, the native OSX ssh client doesn't like the DH1 encryption offered by the TPlink devices, but PUTTY allows you to override)

 

Next you need to enable SSH local in your system

 

 

Then you need the management credentials from your controller (if using Omada SDN)

 

 

Then you can just SSH to the IP address of your switch.  Some useful commands I found are:

 

TL-SG2008P#show power inline information interface gigabitEthernet 1/0/1

 

Interface  Power(w)  Current(mA)  Voltage(v)  PD-Class  Power-Status    

---------- --------  -----------  ----------  --------  ----------------

Gi1/0/1    3.4       64           53.4        Class 4   ON    

 

TL-SG2008P#show cable-diagnostics interface gigabitEthernet 1/0/8

Port        Pair      Status      Length         Error          

Gi1/0/8     Pair-A    Normal      8 m            ---            

            Pair-B    Normal      8 m            ---            

            Pair-C    Normal      8 m            ---            

            Pair-D    Normal      8 m            ---

 

 

TL-SG2008P#show logging 5                                                      

#2023-02-20 03:02:03,[Link]/5/Gi1/0/8 changed state to up.

#2023-02-20 03:00:20,[Link]/5/Gi1/0/8 changed state to down.

#2023-02-19 17:15:42,[Link]/5/Gi1/0/5 changed state to up.

#2023-02-19 17:15:37,[Link]/5/Gi1/0/5 changed state to down.

#2023-02-19 13:05:45,[Link]/5/Gi1/0/8 changed state to up.

#2023-02-19 13:04:03,[Link]/5/Gi1/0/8 changed state to down.

#2023-02-13 20:46:48,[Link]/5/Gi1/0/1 changed state to up.

#2023-02-13 20:46:32,[PoE]/3/Power supply status of port 1 changes from off to on.

#2023-02-13 20:42:38,[NETIF]/5/Line protocol on Interface VLAN2, changed state to up.

#2023-02-13 20:42:38,[NETIF]/5/Line protocol on Interface VLAN1, changed state to down.

#2023-02-13 20:42:36,[NETIF]/5/Line protocol on Interface VLAN1, changed state to up.

#2023-02-13 20:42:34,[NETIF]/5/Line protocol on Interface VLAN2, changed state to down.

#2006-01-01 08:00:50,[Link]/5/Gi1/0/2 changed state to up.

#2006-01-01 08:00:48,[Link]/5/Gi1/0/3 changed state to up.

#2006-01-01 08:00:48,[Link]/5/Gi1/0/2 changed state to down.

#2006-01-01 08:00:47,[Link]/5/Gi1/0/2 changed state to up.

#2006-01-01 08:00:45,[PoE]/3/Power supply status of port 1 changes from on to off.

#2006-01-01 08:00:33,[PoE]/3/Power supply status of port 3 changes from off to on.

#2006-01-01 08:00:31,[PoE]/3/Power supply status of port 2 changes from off to on.

#2006-01-01 08:00:30,[PoE]/3/Power supply status of port 1 changes from off to on.

#2006-01-01 08:00:27,[Link]/5/Gi1/0/8 changed state to up.

#2006-01-01 08:00:26,[NETIF]/5/Line protocol on Interface VLAN2, changed state to up.

#2006-01-01 08:00:26,[Link]/5/Gi1/0/6 changed state to up.

#2006-01-01 08:00:26,[Link]/5/Gi1/0/7 changed state to up.

#2006-01-01 08:00:25,[Link]/5/Gi1/0/5 changed state to up.

 

Total read-out entry number is 5.

There is no log in flash.