True(1) if the Relay 4 ouput is on (C and NO connected). False(2) if it is off (C and NC connected).
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
OID reference
relay4on
1.3.6.1.4.1.32050.2.2.39
Description
True(1) if the Relay 4 ouput is on (C and NO connected). False(2) if it is off (C and NC connected).
Identification
Identifier and names
- Parent
- 1.3.6.1.4.1.32050.2.2 (standbypower)
- Node code
- 39
- Node name
- relay4on
- Category
- SNMP management object
- Numeric OID
- 1.3.6.1.4.1.32050.2.2.39
- URN notation
- urn:oid:1.3.6.1.4.1.32050.2.2.39
ASN.1, OID-IRI and named path variants
- ASN.1 notation
-
{1 3 6 1 4 1 32050 2 2 39}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) packetflux(32050) packetfluxProductSpecific(2) standbypower(2) relay4on(39)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) packetflux(32050) packetfluxMgmt(2) standbypower(2) relay4on(39)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) packetflux(32050) packetfluxProductSpecific(2) standbypower(2) relay4on(39)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) packetflux(32050) packetfluxMgmt(2) standbypower(2) relay4on(39)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) packetflux(32050) packetfluxProductSpecific(2) standbypower(2) relay4on(39)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) packetflux(32050) packetfluxMgmt(2) standbypower(2) relay4on(39)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) packetflux(32050) packetfluxProductSpecific(2) standbypower(2) relay4on(39)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) packetflux(32050) packetfluxMgmt(2) standbypower(2) relay4on(39)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) packetflux(32050) packetfluxProductSpecific(2) standbypower(2) relay4on(39)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) packetflux(32050) packetfluxMgmt(2) standbypower(2) relay4on(39)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) packetflux(32050) packetfluxProductSpecific(2) standbypower(2) relay4on(39)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) packetflux(32050) packetfluxMgmt(2) standbypower(2) relay4on(39)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) packetflux(32050) packetfluxProductSpecific(2) standbypower(2) relay4on(39)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) packetflux(32050) packetfluxMgmt(2) standbypower(2) relay4on(39)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) packetflux(32050) packetfluxProductSpecific(2) standbypower(2) relay4on(39)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) packetflux(32050) packetfluxMgmt(2) standbypower(2) relay4on(39)}
- Additional combinations skipped.
- OID-IRI notation
- /1/3/6/1/4/1/32050/2/2/39
- /ISO/Identified-Organization/6/1/4/1/32050/2/2/39
- /ISO/3/6/1/4/1/32050/2/2/39
- Named path variants
- /iso/identified-organization/dod/internet/private/enterprise/32050/packetfluxProductSpecific/standbypower/relay4on
- /iso/identified-organization/dod/internet/private/enterprise/32050/packetfluxMgmt/standbypower/relay4on
- /iso/identified-organization/dod/internet/private/enterprise/packetflux/packetfluxProductSpecific/standbypower/relay4on
- /iso/identified-organization/dod/internet/private/enterprise/packetflux/packetfluxMgmt/standbypower/relay4on
- /iso/identified-organization/dod/internet/private/enterprises/32050/packetfluxProductSpecific/standbypower/relay4on
- /iso/identified-organization/dod/internet/private/enterprises/32050/packetfluxMgmt/standbypower/relay4on
- /iso/identified-organization/dod/internet/private/enterprises/packetflux/packetfluxProductSpecific/standbypower/relay4on
- /iso/identified-organization/dod/internet/private/enterprises/packetflux/packetfluxMgmt/standbypower/relay4on
- /iso/identified-organization/dod/internet/private/ldap-enterprise/32050/packetfluxProductSpecific/standbypower/relay4on
- /iso/identified-organization/dod/internet/private/ldap-enterprise/32050/packetfluxMgmt/standbypower/relay4on
- /iso/identified-organization/dod/internet/private/ldap-enterprise/packetflux/packetfluxProductSpecific/standbypower/relay4on
- /iso/identified-organization/dod/internet/private/ldap-enterprise/packetflux/packetfluxMgmt/standbypower/relay4on
- /iso/identified-organization/dod/internet/private/vendor-objects/32050/packetfluxProductSpecific/standbypower/relay4on
- /iso/identified-organization/dod/internet/private/vendor-objects/32050/packetfluxMgmt/standbypower/relay4on
- /iso/identified-organization/dod/internet/private/vendor-objects/packetflux/packetfluxProductSpecific/standbypower/relay4on
- /iso/identified-organization/dod/internet/private/vendor-objects/packetflux/packetfluxMgmt/standbypower/relay4on
- Additional combinations skipped.
SNMP properties
- Value type
- TruthValue
- Maximum access defined by MIB
- read-only
- Status in MIB
- current
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
Published definition
The displayed source records contain one distinct definition. Compare its source records.
relay4on OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION "True(1) if the Relay 4 ouput is on (C and NO connected).
False(2) if it is off (C and NC connected)."
::= { standbypower 39 }
Meaning
Descriptions
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Evidence
Source records
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
relay4on · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Status in source: current.
Names: relay4on
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"relay4on",
"OBJECT-TYPE",
"SYNTAX",
"TruthValue",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"True(1) if the Relay 4 ouput is on (C and NO connected). False(2) if it is off (C and NC connected).\"",
"::=",
"{",
"standbypower",
"39",
"}"
],
"syntax_tree": [
[
"row",
"TruthValue"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"True(1) if the Relay 4 ouput is on (C and NO connected). False(2) if it is off (C and NC connected)."
],
null,
null,
null,
null
]
}- Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
· Publisher's source file: PACKETFLUX-STANDBYPOWER
Vendor MIB copy from the LibreNMS archive.
Module: PACKETFLUX-STANDBYPOWER
See published definition above
· Download PACKETFLUX-STANDBYPOWERModule imports
{'SNMPv2-TC': ['TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'Integer32', 'OBJECT-TYPE', 'Gauge32', 'TimeTicks'], 'SNMPv2-CONF': ['OBJECT-GROUP'], 'PACKETFLUX-SMI': ['packetfluxProductSpecific']}Related source files and packages:
- Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
· Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.
Module: PACKETFLUX-STANDBYPOWER
· Download PACKETFLUX-STANDBYPOWERModule imports
{'SNMPv2-TC': ['TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'Integer32', 'OBJECT-TYPE', 'Gauge32', 'TimeTicks'], 'SNMPv2-CONF': ['OBJECT-GROUP'], 'PACKETFLUX-SMI': ['packetfluxMgmt']}Related source files and packages:
Registration