OID reference

keyInterface

1.3.6.1.4.1.3052.12.4

Description

This object represents a setting key interface. When setting this object, the value to set is the 'sk' command you would enter on the command line (without the 'sk'). To get the result of the operation, read this object after you write it. For example, to configure EventSensor 1 contact closure 34 event actions to be …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.3052.12 (s530)
Node code
4
Node name
keyInterface
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.3052.12.4
URN notation
urn:oid:1.3.6.1.4.1.3052.12.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 3052 12 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) asentria(3052) s530(12) keyInterface(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) omnitronix(3052) s530(12) keyInterface(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) asentria(3052) s530(12) keyInterface(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) omnitronix(3052) s530(12) keyInterface(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) asentria(3052) s530(12) keyInterface(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) omnitronix(3052) s530(12) keyInterface(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) asentria(3052) s530(12) keyInterface(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) omnitronix(3052) s530(12) keyInterface(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) asentria(3052) s530(12) keyInterface(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) omnitronix(3052) s530(12) keyInterface(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) asentria(3052) s530(12) keyInterface(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) omnitronix(3052) s530(12) keyInterface(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) asentria(3052) s530(12) keyInterface(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) omnitronix(3052) s530(12) keyInterface(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) asentria(3052) s530(12) keyInterface(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) omnitronix(3052) s530(12) keyInterface(4)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/3052/12/4
  • /ISO/Identified-Organization/6/1/4/1/3052/12/4
  • /ISO/3/6/1/4/1/3052/12/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/asentria/s530/keyInterface
  • /iso/identified-organization/dod/internet/private/enterprise/omnitronix/s530/keyInterface
  • /iso/identified-organization/dod/internet/private/enterprises/asentria/s530/keyInterface
  • /iso/identified-organization/dod/internet/private/enterprises/omnitronix/s530/keyInterface
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/asentria/s530/keyInterface
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/omnitronix/s530/keyInterface
  • /iso/identified-organization/dod/internet/private/vendor-objects/asentria/s530/keyInterface
  • /iso/identified-organization/dod/internet/private/vendor-objects/omnitronix/s530/keyInterface
  • /iso/org/dod/internet/private/enterprise/asentria/s530/keyInterface
  • /iso/org/dod/internet/private/enterprise/omnitronix/s530/keyInterface
  • /iso/org/dod/internet/private/enterprises/asentria/s530/keyInterface
  • /iso/org/dod/internet/private/enterprises/omnitronix/s530/keyInterface
  • /iso/org/dod/internet/private/ldap-enterprise/asentria/s530/keyInterface
  • /iso/org/dod/internet/private/ldap-enterprise/omnitronix/s530/keyInterface
  • /iso/org/dod/internet/private/vendor-objects/asentria/s530/keyInterface
  • /iso/org/dod/internet/private/vendor-objects/omnitronix/s530/keyInterface
  • Additional combinations skipped.

SNMP properties

Value type
DisplayString
Maximum access defined by MIB
read-write
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.

The displayed source records contain one distinct definition. Compare its source records.

keyInterface OBJECT-TYPE
    SYNTAX DisplayString
    MAX-ACCESS read-write
    STATUS current
    DESCRIPTION
        "This object represents a setting key interface.  When
        setting this object, the value to set is the 'sk' command
        you would enter on the command line (without the 'sk').  To
        get the result of the operation, read this object after you
        write it.

        For example, to configure EventSensor 1 contact closure 34
        event actions to be an SNMP InformRequest to host foo, set
        this object to:
        'event.sensor[1].cc[34].eventactions=inform(foo)'.  The SNMP
        response is the result of the operation: if setting that key
        to that value was a success then the SNMP response will be a
        success and the response value will be what you had set.  If
        you subsequently read this object then you will see a
        message 'OK: ...'.

        If setting that key to that value failed then the SNMP
        response will be a failure (a badValue response).  If you
        subsequently read this object then the value returned is the
        reason that setting that key to that value failed.

        For another example, to read user 3's pass-through access
        for port 7, set this object to:
        'sec.user[3].port[7].ptaccess'.  The SNMP response is the
        result of the operation: if reading that key is a success
        then the SNMP response will be a success and the response
        value will be what you had SET (i.e., the opertion of
        reading a key, which is just the key itself with no '='
        operator, and this is not the key value you want to read).
        If you subsequently read this object then the value
        returned is the value of the key you want to read.

        If reading that key failed (e.g., if the key is invalid)
        then the SNMP response to your SNMP set operation (the
        value you set being the invalid key to read) will be a
        failure (a badValue response).  If you subsequently read
        this object then the value returned is the reason that
        reading that key failed (i.e., 'invalid key')."
    ::= { s530 4 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

This object represents a setting key interface. When setting this object, the value to set is the 'sk' command you would enter on the command line (without the 'sk'). To get the result of the operation, read this object after you write it. For example, to configure EventSensor 1 contact closure 34 event actions to be an SNMP InformRequest to host foo, set this object to: 'event.sensor[1].cc[34].eventactions=inform(foo)'. The SNMP response is the result of the operation: if setting that key to that value was a success then the SNMP response will be a success and the response value will be what you had set. If you subsequently read this object then you will see a message 'OK: ...'. If setting that key to that value failed then the SNMP response will be a failure (a badValue response). If you subsequently read this object then the value returned is the reason that setting that key to that value failed. For another example, to read user 3's pass-through access for port 7, set this object to: 'sec.user[3].port[7].ptaccess'. The SNMP response is the result of the operation: if reading that key is a success then the SNMP response will be a success and the response value will be what you had SET (i.e., the opertion of reading a key, which is just the key itself with no '=' operator, and this is not the key value you want to read). If you subsequently read this object then the value returned is the value of the key you want to read. If reading that key failed (e.g., if the key is invalid) then the SNMP response to your SNMP set operation (the value you set being the invalid key to read) will be a failure (a badValue response). If you subsequently read this object then the value returned is the reason that reading that key failed (i.e., 'invalid key').

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 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)1 record · 1 source

Description 1

keyInterface · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: keyInterface

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "keyInterface",
    "OBJECT-TYPE",
    "SYNTAX",
    "DisplayString",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object represents a setting key interface. When setting this object, the value to set is the 'sk' command you would enter on the command line (without the 'sk'). To get the result of the operation, read this object after you write it. For example, to configure EventSensor 1 contact closure 34 event actions to be an SNMP InformRequest to host foo, set this object to: 'event.sensor[1].cc[34].eventactions=inform(foo)'. The SNMP response is the result of the operation: if setting that key to that value was a success then the SNMP response will be a success and the response value will be what you had set. If you subsequently read this object then you will see a message 'OK: ...'. If setting that key to that value failed then the SNMP response will be a failure (a badValue response). If you subsequently read this object then the value returned is the reason that setting that key to that value failed. For another example, to read user 3's pass-through access for port 7, set this object to: 'sec.user[3].port[7].ptaccess'. The SNMP response is the result of the operation: if reading that key is a success then the SNMP response will be a success and the response value will be what you had SET (i.e., the opertion of reading a key, which is just the key itself with no '=' operator, and this is not the key value you want to read). If you subsequently read this object then the value returned is the value of the key you want to read. If reading that key failed (e.g., if the key is invalid) then the SNMP response to your SNMP set operation (the value you set being the invalid key to read) will be a failure (a badValue response). If you subsequently read this object then the value returned is the reason that reading that key failed (i.e., 'invalid key').\"",
    "::=",
    "{",
    "s530",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "DisplayString"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object represents a setting key interface. When setting this object, the value to set is the 'sk' command you would enter on the command line (without the 'sk'). To get the result of the operation, read this object after you write it. For example, to configure EventSensor 1 contact closure 34 event actions to be an SNMP InformRequest to host foo, set this object to: 'event.sensor[1].cc[34].eventactions=inform(foo)'. The SNMP response is the result of the operation: if setting that key to that value was a success then the SNMP response will be a success and the response value will be what you had set. If you subsequently read this object then you will see a message 'OK: ...'. If setting that key to that value failed then the SNMP response will be a failure (a badValue response). If you subsequently read this object then the value returned is the reason that setting that key to that value failed. For another example, to read user 3's pass-through access for port 7, set this object to: 'sec.user[3].port[7].ptaccess'. The SNMP response is the result of the operation: if reading that key is a success then the SNMP response will be a success and the response value will be what you had SET (i.e., the opertion of reading a key, which is just the key itself with no '=' operator, and this is not the key value you want to read). If you subsequently read this object then the value returned is the value of the key you want to read. If reading that key failed (e.g., if the key is invalid) then the SNMP response to your SNMP set operation (the value you set being the invalid key to read) will be a failure (a badValue response). If you subsequently read this object then the value returned is the reason that reading that key failed (i.e., 'invalid key')."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.3052)

Renton Paul

Siblings (227)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.3052.12.1 status8170
1.3.6.1.4.1.3052.12.2 config12894
1.3.6.1.4.1.3052.12.3 productIds1010
1.3.6.1.4.1.3052.12.110 s530StockContactClosureTrap00
1.3.6.1.4.1.3052.12.120 s530StockTempTrap00
1.3.6.1.4.1.3052.12.130 s530StockHumidityTrap00
1.3.6.1.4.1.3052.12.140 s530StockAnalogTrap00
1.3.6.1.4.1.3052.12.150 s530StockOutputTrap00
1.3.6.1.4.1.3052.12.180 s530StockPDCurrentTrap00
1.3.6.1.4.1.3052.12.190 s530StockPDVoltageTrap00
1.3.6.1.4.1.3052.12.210 s530StockPDFuseTrap00
1.3.6.1.4.1.3052.12.501 s530StockDbasePfullTrap00
1.3.6.1.4.1.3052.12.503 s530StockDataAlarmTrap00
1.3.6.1.4.1.3052.12.505 s530StockNoDataAlarmTrap00
1.3.6.1.4.1.3052.12.506 s530StockSchedTrap00
1.3.6.1.4.1.3052.12.507 s530StockImmediateTrap00
1.3.6.1.4.1.3052.12.510 s530StockCTSTrap00
1.3.6.1.4.1.3052.12.511 s530CPEDownTrap00
1.3.6.1.4.1.3052.12.515 s530FuelSensorDisconnectTrap00
1.3.6.1.4.1.3052.12.519 s530FuelSensorVolumeTrap00
1.3.6.1.4.1.3052.12.520 s530ACPowerMonitorAvgVoltageTrap00
1.3.6.1.4.1.3052.12.521 s530ACPowerMonitorAvgCurrentTrap00
1.3.6.1.4.1.3052.12.522 s530ACPowerMonitorFrequencyTrap00
1.3.6.1.4.1.3052.12.523 s530ACPowerMonitorTRPTrap00
1.3.6.1.4.1.3052.12.524 s530ACPowerMonitorDisconnectTrap00
1.3.6.1.4.1.3052.12.540 s530ACTotalPowerFactorTrap00
1.3.6.1.4.1.3052.12.543 s530ResetTrap00
1.3.6.1.4.1.3052.12.1000 s530UserTrap100000
1.3.6.1.4.1.3052.12.1001 s530UserTrap100100
1.3.6.1.4.1.3052.12.1002 s530UserTrap100200
1.3.6.1.4.1.3052.12.1003 s530UserTrap100300
1.3.6.1.4.1.3052.12.1004 s530UserTrap100400
1.3.6.1.4.1.3052.12.1005 s530UserTrap100500
1.3.6.1.4.1.3052.12.1006 s530UserTrap100600
1.3.6.1.4.1.3052.12.1007 s530UserTrap100700
1.3.6.1.4.1.3052.12.1008 s530UserTrap100800
1.3.6.1.4.1.3052.12.1009 s530UserTrap100900
1.3.6.1.4.1.3052.12.1010 s530UserTrap101000
1.3.6.1.4.1.3052.12.1011 s530UserTrap101100
1.3.6.1.4.1.3052.12.1012 s530UserTrap101200
1.3.6.1.4.1.3052.12.1013 s530UserTrap101300
1.3.6.1.4.1.3052.12.1014 s530UserTrap101400
1.3.6.1.4.1.3052.12.1015 s530UserTrap101500
1.3.6.1.4.1.3052.12.1016 s530UserTrap101600
1.3.6.1.4.1.3052.12.1017 s530UserTrap101700
1.3.6.1.4.1.3052.12.1018 s530UserTrap101800
1.3.6.1.4.1.3052.12.1019 s530UserTrap101900
1.3.6.1.4.1.3052.12.1020 s530UserTrap102000
1.3.6.1.4.1.3052.12.1021 s530UserTrap102100
1.3.6.1.4.1.3052.12.1022 s530UserTrap102200