POE status

Given all my devices I'm worried about support the standard POWER-ETHERNET-MIB (Juniper, HP) here is my ideal of support:

1) NCM gathers the state of POE and stores it in its database, so that it can be used for driving configuration change templates. e.g. if a port does not current have working POE on it then POE could be disabled. (we would use this to bring nodes into compliance with new standards for POE for example)

2) UDT gathers the same information on a per-port basis (note the POE ports do not line up with the standard IF-MIB ifIndex :-( )

I need:

a) if POE was negotiated (or if it's searching)

b) if POE is administratively disabled

c) the POE priority (high/low)

d) the POE class.

[the standard MIB only provides the negotiated class, not the actual power draw)

3) NPM on a per-device basis a multiple PSE-guage widget showing the percentage of power available and being consumed by a PSE; I can have one linear chart per PSE, but this is a pain to configure when you really need a variable number of gauges depending on how mane PSE there are in a switch/stack. a nice stacked linear gauge display showing the percent of power consumed would be good.

While I'm at it...

4) consumption of POWER-ETHERNET-MIB traps to update the power currently being consumed (the current power/PSE is reported in the trap, so there is no real need to poll for this if you can capture and process the trap data)

IME not very useful; I only need to know when a node is running out of power so we can figure out if we're going to deploy another switch (or 208V power). Once we can turn off power for things that are not supposed to be plugged in and bring the POE under change control then we should only run out of power when we fail to plan properly...

5) Historical graphs of PSE power consumption for the node

Given all my devices I'm worried about support the standard POWER-ETHERNET-MIB (Juniper, HP) here is my ideal of support:

1) NCM gathers the state of POE and stores it in its database, so that it can be used for driving configuration change templates. e.g. if a port does not current have working POE on it then POE could be disabled. (we would use this to bring nodes into compliance with new standards for POE for example)

2) UDT gathers the same information on a per-port basis (note the POE ports do not line up with the standard IF-MIB ifIndex :-( )

I need:

a) if POE was negotiated (or if it's searching)

b) if POE is administratively disabled

c) the POE priority (high/low)

d) the POE class.

[the standard MIB only provides the negotiated class, not the actual power draw)

3) NPM on a per-device basis a multiple PSE-guage widget showing the percentage of power available and being consumed by a PSE; I can have one linear chart per PSE, but this is a pain to configure when you really need a variable number of gauges depending on how mane PSE there are in a switch/stack. a nice stacked linear gauge display showing the percent of power consumed would be good.

While I'm at it...

4) consumption of POWER-ETHERNET-MIB traps to update the power currently being consumed (the current power/PSE is reported in the trap, so there is no real need to poll for this if you can capture and process the trap data)

IME not very useful; I only need to know when a node is running out of power so we can figure out if we're going to deploy another switch (or 208V power). Once we can turn off power for things that are not supposed to be plugged in and bring the POE under change control then we should only run out of power when we fail to plan properly...

5) Historical graphs of PSE power consumption for the node

I would like to be able to generate alerts for PoE Denied.

Development info: For some reason the Juniper EXs don’t increment the denied counter OID and for some reason the HPs don’t accurately reflect detection status.

For HP e5406:

pethPsePortPowerDeniedCounter OBJECT-TYPE [1.3.6.1.2.1.105.1.1.1.12]

           SYNTAX Counter32

           MAX-ACCESS read-only

           STATUS current

           DESCRIPTION

           "This counter is incremented when the PSE state diagram

           enters the state POWER_DENIED." increments starting at 0, then 1, 2, 3 depending on how many times it’s unplugged and plugged in

           REFERENCE

           "IEEE Std 802.3af Section 30.9.1.1.8

            aPSEPowerDeniedCounter"

       ::= { pethPsePortEntry 12 }

e.g. values:

POWER-ETHERNET-MIB::pethPsePortPowerDeniedCounter.6.142 = Counter32: 3

POWER-ETHERNET-MIB::pethPsePortPowerDeniedCounter.6.143 = Counter32: 0

POWER-ETHERNET-MIB::pethPsePortPowerDeniedCounter.6.144 = Counter32: 2

For Juniper EX:

   pethPsePortDetectionStatus OBJECT-TYPE  [1.3.6.1.2.1.105.1.1.1.6]

           SYNTAX INTEGER   {

               disabled(1),

               searching(2),

               deliveringPower(3),

              fault(4),

               test(5),

               otherFault(6) ”6” will tell us if a PD is being starved of power

           }

Example values:

POWER-ETHERNET-MIB::pethPsePortDetectionStatus.1.32 = INTEGER: searching(2)

POWER-ETHERNET-MIB::pethPsePortDetectionStatus.1.33 = INTEGER: searching(2)

POWER-ETHERNET-MIB::pethPsePortDetectionStatus.1.34 = INTEGER: searching(2)

POWER-ETHERNET-MIB::pethPsePortDetectionStatus.1.35 = INTEGER: otherFault(6)

POWER-ETHERNET-MIB::pethPsePortDetectionStatus.1.36 = INTEGER: searching(2)

POWER-ETHERNET-MIB::pethPsePortDetectionStatus.1.37 = INTEGER: otherFault(6)