@baggins1us 

Did you enable SNMP for your switch? If yes, maybe you can check if  use the correct OID for PoE.

@Andone 

snmp is enabled, otherwise I would not be able to get the other information from the switch.

If I run "snmpwalk -v 2c -c <community name> <IP address of switch>" I get lots of info on the ports, but nothing related to PoE...

So I've setup 'The Dude' (from Mikrotik) to do some further investigating.

It appears that I have to provide a mib file in order for this to work.

From the TP-Link website I downloaded a zip file that contains a large number of mib files that all seem to depend on one another.

So how do I get these in 'The Dude'  so they are recognized?

I'll answer my own question:

-create a directory on the dude server under <paht-to/files

-copy all mibs in that directory (includingcreating subdirectories

-rename all mib file from .mib to -mib.txt

Now th SG3424 mib are recognized by The Dude.

However, doing a snmpwalk still shows nothing related to poe.

On the switch I have a created a view with MIB obj id: 1

Do I need to define another view?

@baggins1us 

I think TP-Link PoE switch should be able to show PoE config through SNMP. But cannot make sure whether can show PoE status.

In their private MIB file, we can see that the PoE config root OID is 1.3.6.1.4.1.11863.6.56. Maybe you can try to snmpwalk this OID.

@Andone 

Initially I had only copied the poe MIB to the Dude, but it appears that all of the MIB need to be copied over, which I did.

When I did a snmpwalk I got an error stating that the order of MIB was not correct.

Eventually I found out I could get the data of voltage, current and power at 1.3.6.1.4.1.11863.1.1.8.13.1.2.1.1.7, ....8 and ...9 which is what I was looking for.

When I did an snmpwalk of 1.3.6.1.4.1.11863.6.56, I simply got a message: "End of MIB"...

@baggins1us 

I found the OID through the following MIB file information. So I guess that TP-Link PoE OID is began with 1.3.6.1.4.1.11863.6.56. But in your test, other OIDs already meet your requirements. So maybe the OID of your test is correct.

【tplink.mib】

TPLINK-MIB DEFINITIONS ::= BEGIN

--iso             OBJECT IDENTIFIER ::= { 1 }
--org             OBJECT IDENTIFIER ::= { iso 3 }
--dod             OBJECT IDENTIFIER ::= { org 6 }
--internet        OBJECT IDENTIFIER ::= { dod 1 }
--private         OBJECT IDENTIFIER ::= { internet 4 }
--enterprises     OBJECT IDENTIFIER ::= { private 1 }

    IMPORTS
        enterprises 
                    FROM RFC1155-SMI
        OBJECT-IDENTITY
                    FROM SNMPv2-SMI;

    tplink             OBJECT IDENTIFIER ::= { enterprises 11863 }

    switch            OBJECT IDENTIFIER ::= { tplink 1 }
    router            OBJECT IDENTIFIER ::= { tplink 2 }
    wireless        OBJECT IDENTIFIER ::= { tplink 3 }
    adsl            OBJECT IDENTIFIER ::= { tplink 4 }
    
    
    tplinkProducts    OBJECT-IDENTITY
        STATUS      current
        DESCRIPTION
            "tplinkProducts is the root OBJECT IDENTIFIER from
            which sysObjectID values are assigned.  Actual
            values are defined in TPLINK-PRODUCTS-MIB."
        ::= { tplink 5 }
        
    tplinkMgmt    OBJECT-IDENTITY        
        STATUS    current
        DESCRIPTION
            "tplinkMgmt is the main subtree for new mib development."

        ::= { tplink 6 }

END

【tplink-powerOverEthernet.mib】

        tplinkPowerOverEthernetMIB MODULE-IDENTITY
            LAST-UPDATED    "201307030000Z"
            ORGANIZATION    "TP-LINK"
            CONTACT-INFO    " www.tplink.com"
            DESCRIPTION     "Private MIB for PoE module."
            REVISION        "201307030000Z"
            DESCRIPTION     "Initial version of this MIB module."
            ::= { tplinkMgmt 56 }