This MIB is intended for devices powered by external power sources, in particular Power Over Ethernet (PoE or formerly called inline power), to provide power usage configuration and information for NMS. For example, PoE supplies DC power over standard Category 5 unshielded twisted-pair (UTP) cable. Instead of requiring wall power, powered devices such as IP telephones can utilize power provided from power source equipments. By using Cisco
Discovery Protocol (CDP), powered devices
can negotiated with power source equipment to obtain optimum power supply.
GLOSSARY
Midspan Injector The midspan PSE sends out a signal tone down one of the unused pairs of the standard Category 5 cable and detects tone on the other unused pair when the PD loops this tone back to it through a loopback transformer. Once the midspan PSE detects this tone, it begins to provide power down the cable using the unused pairs. The midspan PSE provide no physical layer capability.
Powered Device ( PD ) These are devices powered by external electrical power sources. They are, for example, IP telephones and wireless Access Points or bridges.
Power Source Equipment ( PSE ) These are devices supplying electrical power to other equipments. They are, for example, inline power switches and power patch panels.
This identifies the currently how much power is consummed by the device at which this agent is running. The level shall be one of the cpoePdSupportedPowerLevel in the cpoePdSupportedPowerTable.
cpoePdCurrentPowerSource
1.3.6.1.4.1.9.9.414.1.1.2
CpoePdPowerSourceType1 = pending2 = acAdaptor3 = thirdParty4 = classic5 = midspan6 = cdpNegotiated7 = highPowerClassicThis is the type of power source equipment supplying DC power to the PD.
pending -- power source is not yet determined.
acAdaptor -- power is supplied by an AC adapter
thirdParty -- power is supplied by a PSE not
supporting Cisco CDP
classic -- power is supplied and limited by
a classic Cisco PSE
midspan -- power is supplied by a midspan
injector
cdpNegotiated -- power is negotiated using Cisco
CDP highPowerClassic -- power is supplied by Cisco PSE without negotiation. · Integer32
This is the current power source type obtained from device power source detection.
Table details
cpoePdSupportedPowerLevelTable
1.3.6.1.4.1.9.9.414.1.1.3
Index: cpoePdSupportedPowerLevel
This table shows all the supported electrical power consumption levels of this agent and the corresponding modes of operation at those power levels. The mode of operation and the device capability changes as the supplied power level varies. The number of supported levels is platform and implementation dependent.
cpoePdSupportedPowerLevel
1.3.6.1.4.1.9.9.414.1.1.3.1.1
Unsigned32 (1..65535)
This index uniquely identifies the supported power consumption level.
cpoePdSupportedPower
1.3.6.1.4.1.9.9.414.1.1.3.1.2
Unsigned32 (1..65535) · milliwatts
This is the electrical power consummed by the device operating at this supported power consumption level.
cpoePdSupportedPowerMode
1.3.6.1.4.1.9.9.414.1.1.3.1.3
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
This is a text string describing the mode of operation or capability of the device at the power consumption level. For example, the comsumption level and corresponding mode should look like these:
1 'Full power mode'
2 'Low power mode - dot11radio 0 disabled'
3 'Low power mode - dot11radio 1 disabled'
4 'Low power mode - dot11 radios disabled'.