If the 750 was in auto, was the long-poe-in-setting on or off? if it was set to allow long-poe-in there is a short detection that is turned off in the 750. That may have allowed the 750 to keep testing the poe out circuit for a device and each time shorted out the connection eventually frying the circuitry... That is my speculation. Probably would not have happened if the 750 was turned to off for poe on that port with the injector...

On 09/27/2016 08:37 AM, Nate Burke wrote:
That is correct in the setup.  I'm not sure if the injector has surge or
not.  It was a Ruckus POE block which physically looks the same as a
UBNT POE block.

On 9/27/2016 10:28 AM, That One Guy /sarcasm wrote:
this was a POE OUT port on the mikrotik connected to the non POE port
on the injector? is it an injector with surge suppression?

On Tue, Sep 27, 2016 at 10:07 AM, Nate Burke <[email protected]
<mailto:[email protected]>> wrote:

    I was using a RB951Ui-2HnD and a 750UP on my desk for some testing
    because they were laying within reach.  I was NOT using the POE
    Out functionality of the boards.  I was using an external 48V gig
    POE Injector to bench test a Ruckus AP.

    On both boards, after using them in the test setup for a few days,
    the Interface on the mikrotik that had the LAN side of the
    external POE Injector plugged into it now remains 'link ok' even
    when there is nothing plugged in, and the Mikrotik thinks the port
    is in a network loop.  The only thing that looked out of the
    ordinary was that the Mikrotik POE was set to 'auto' and was
    showing state of 'short circuit'  I did not realize this until
    after the problem started.  I'm pretty sure the Mikrotik boards
    are fried, as nothing I do will stop them from having the
    interface up and in a loop state, but I'm not sure why it
    happened.  Was there something with the mikrotik set to Auto POE
    and an external Gig POE adapter that fried the port?  If so,
    warning to others out there to watch out for this.




--
If you only see yourself as part of the team but you don't see your
team as part of yourself you have already failed as part of the team.

Reply via email to