Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"hpnicfMainPsePowerLimit",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"The object specifies the power limit set for the unit as a whole. The PoE unit will already have a nominal power defined by the IETF Power MIB [1] pethMainPsePower object. This OPTIONAL object specifies a further limit to this nominal power value. This may be useful to control the thermals of the unit, or for internal testing purposes. One possible use for this object may be to lower the power consumption of the unit if one or more of the internal fans have broken. It is a read/write integer value with units of Watts (note - Watts is chosen instead of milliWatts here since the IETF Power MIB [1] measures unit based parameters, such as the pethMainPsePower object, in units of Watts).\"",
"::=",
"{",
"hpnicfMainPseEntry",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The object specifies the power limit set for the unit as a whole. The PoE unit will already have a nominal power defined by the IETF Power MIB [1] pethMainPsePower object. This OPTIONAL object specifies a further limit to this nominal power value. This may be useful to control the thermals of the unit, or for internal testing purposes. One possible use for this object may be to lower the power consumption of the unit if one or more of the internal fans have broken. It is a read/write integer value with units of Watts (note - Watts is chosen instead of milliWatts here since the IETF Power MIB [1] measures unit based parameters, such as the pethMainPsePower object, in units of Watts)."
],
null,
null,
null,
null
]
}