OID reference
1.3.6.1.4.1.17409.1.15.7.1.4
Mark Power supply name, for example: +5 V DC power supply. This field value regulated by the user, it should be marked with the number of the power supply voltage and distinguish the multi-power supplies at least. When the object in this table give an alarm, the name of this object should be put into the alarmText tar…
Identification
{1 3 6 1 4 1 17409 1 15 7 1 4}
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
Available source records contain 2 distinct definitions; some records may not include a definition.
oswDCPowerName OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Mark Power supply name, for example: +5 V DC power supply.
This field value regulated by the user, it should be marked with the number of the power supply voltage and distinguish the multi-power supplies at least.
When the object in this table give an alarm, the name of this object should be put into the alarmText target in the hfcAlarmEvent trap.
"
::= { oswDCPowerEntry 4 }oswDCPowerName OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Mark Power supply name, for example: +5 V DC power supply.
This field value regulated by the user, it should be marked with the number of the power supply voltage and distinguish the multi-power supplies at least.
When the object in this table give an alarm, the name of this object should be put into the alarmText target in the hfcAlarmEvent trap.
"
::= { oswDCPowerEntry 4 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Mark Power supply name, for example: +5 V DC power supply. This field value regulated by the user, it should be marked with the number of the power supply voltage and distinguish the multi-power supplies at least. When the object in this table give an alarm, the name of this object should be put into the alarmText target in the hfcAlarmEvent trap.
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: mandatory.
Names: oswDCPowerName
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"oswDCPowerName",
"OBJECT-TYPE",
"SYNTAX",
"DisplayString",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Mark Power supply name, for example: +5 V DC power supply. This field value regulated by the user, it should be marked with the number of the power supply voltage and distinguish the multi-power supplies at least. When the object in this table give an alarm, the name of this object should be put into the alarmText target in the hfcAlarmEvent trap. \"",
"::=",
"{",
"oswDCPowerEntry",
"4",
"}"
],
"syntax_tree": [
[
"row",
"DisplayString"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Mark Power supply name, for example: +5 V DC power supply. This field value regulated by the user, it should be marked with the number of the power supply voltage and distinguish the multi-power supplies at least. When the object in this table give an alarm, the name of this object should be put into the alarmText target in the hfcAlarmEvent trap."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: NSCRTV-OSW
See published definition above
{'SNMPv2-TC': ['DisplayString'], 'RFC1155-SMI': ['enterprises']}Related source files and packages:
Vendor MIB copy from the Observium Community archive.
Module: NSCRTV-HFCEMS-ANALOG-MIB
See published definition above
{'SNMPv2-TC': ['DisplayString'], 'RFC1155-SMI': ['enterprises']}Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.17409.1.15.7.1.1 | oswDCPowerIndex | 0 | 0 | |
| 1.3.6.1.4.1.17409.1.15.7.1.2 | oswDCPowerVoltage | 0 | 0 | |
| 1.3.6.1.4.1.17409.1.15.7.1.3 | oswDCPowerCurrent | 0 | 0 |