OID reference
1.3.6.1.4.1.32050.3.2.2.1.4
The value of the sensor in anps. Note that this is reported from the controller with 6 fixed decimal digits which is enough to correctly represent mA and uA ranges. Some SNMP tools will automatically put the decimal in the right spot. If not, you will need to divide this value by 1,000,000 to get the value in Amps.
Identification
{1 3 6 1 4 1 32050 3 2 2 1 4}
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
The displayed source records contain one distinct definition. Compare its source records.
currentSensorValue OBJECT-TYPE
SYNTAX Fixed6DecimalDigits
UNITS "A"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of the sensor in anps. Note that this is reported
from the controller with 6 fixed decimal digits which is enough
to correctly represent mA and uA ranges. Some SNMP tools will
automatically put the decimal in the right spot. If not, you
will need to divide this value by 1,000,000 to get the value in
Amps."
::= { currentSensorEntry 4 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The value of the sensor in anps. Note that this is reported from the controller with 6 fixed decimal digits which is enough to correctly represent mA and uA ranges. Some SNMP tools will automatically put the decimal in the right spot. If not, you will need to divide this value by 1,000,000 to get the value in Amps.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: currentSensorValue
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"currentSensorValue",
"OBJECT-TYPE",
"SYNTAX",
"Fixed6DecimalDigits",
"UNITS",
[
"literal",
"224122"
],
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"The value of the sensor in anps. Note that this is reported from the controller with 6 fixed decimal digits which is enough to correctly represent mA and uA ranges. Some SNMP tools will automatically put the decimal in the right spot. If not, you will need to divide this value by 1,000,000 to get the value in Amps.\"",
"::=",
"{",
"currentSensorEntry",
"4",
"}"
],
"syntax_tree": [
[
"row",
"Fixed6DecimalDigits"
],
[
"UNITS",
"A"
],
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The value of the sensor in anps. Note that this is reported from the controller with 6 fixed decimal digits which is enough to correctly represent mA and uA ranges. Some SNMP tools will automatically put the decimal in the right spot. If not, you will need to divide this value by 1,000,000 to get the value in Amps."
],
null,
null,
null,
null
]
}Vendor MIB copy from the LibreNMS archive.
Module: PACKETFLUX-SENSORS-MIB
See published definition above
{'SNMPv2-TC': ['DisplayString', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'Unsigned32'], 'SNMPv2-CONF': ['OBJECT-GROUP'], 'PACKETFLUX-TC': ['Fixed2DecimalDigits', 'Fixed6DecimalDigits'], 'PACKETFLUX-SMI': ['packetfluxFeatureSpecific']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.32050.3.2.2.1.1 | currentSensorSlot | 0 | 0 | |
| 1.3.6.1.4.1.32050.3.2.2.1.2 | currentSensorIndex | 0 | 0 | |
| 1.3.6.1.4.1.32050.3.2.2.1.3 | currentSensorDescription | 0 | 0 | |
| 1.3.6.1.4.1.32050.3.2.2.1.5 | currentSensorFunction | 0 | 0 |