OID reference

keyInterface

1.3.6.1.4.1.3052.8.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.8 (s570)
Node code
4
Node name
keyInterface
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.3052.8.4
URN notation
urn:oid:1.3.6.1.4.1.3052.8.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 3052 8 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) asentria(3052) s570(8) keyInterface(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) omnitronix(3052) s570(8) keyInterface(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) asentria(3052) s570(8) keyInterface(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) omnitronix(3052) s570(8) keyInterface(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) asentria(3052) s570(8) keyInterface(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) omnitronix(3052) s570(8) keyInterface(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) asentria(3052) s570(8) keyInterface(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) omnitronix(3052) s570(8) keyInterface(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) asentria(3052) s570(8) keyInterface(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) omnitronix(3052) s570(8) keyInterface(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) asentria(3052) s570(8) keyInterface(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) omnitronix(3052) s570(8) keyInterface(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) asentria(3052) s570(8) keyInterface(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) omnitronix(3052) s570(8) keyInterface(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) asentria(3052) s570(8) keyInterface(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) omnitronix(3052) s570(8) keyInterface(4)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/3052/8/4
  • /ISO/Identified-Organization/6/1/4/1/3052/8/4
  • /ISO/3/6/1/4/1/3052/8/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/asentria/s570/keyInterface
  • /iso/identified-organization/dod/internet/private/enterprise/omnitronix/s570/keyInterface
  • /iso/identified-organization/dod/internet/private/enterprises/asentria/s570/keyInterface
  • /iso/identified-organization/dod/internet/private/enterprises/omnitronix/s570/keyInterface
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/asentria/s570/keyInterface
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/omnitronix/s570/keyInterface
  • /iso/identified-organization/dod/internet/private/vendor-objects/asentria/s570/keyInterface
  • /iso/identified-organization/dod/internet/private/vendor-objects/omnitronix/s570/keyInterface
  • /iso/org/dod/internet/private/enterprise/asentria/s570/keyInterface
  • /iso/org/dod/internet/private/enterprise/omnitronix/s570/keyInterface
  • /iso/org/dod/internet/private/enterprises/asentria/s570/keyInterface
  • /iso/org/dod/internet/private/enterprises/omnitronix/s570/keyInterface
  • /iso/org/dod/internet/private/ldap-enterprise/asentria/s570/keyInterface
  • /iso/org/dod/internet/private/ldap-enterprise/omnitronix/s570/keyInterface
  • /iso/org/dod/internet/private/vendor-objects/asentria/s570/keyInterface
  • /iso/org/dod/internet/private/vendor-objects/omnitronix/s570/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')."
    ::= { s570 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').\"",
    "::=",
    "{",
    "s570",
    "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 (225)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.3052.8.1 status7124
1.3.6.1.4.1.3052.8.2 config131030
1.3.6.1.4.1.3052.8.3 productIds1010
1.3.6.1.4.1.3052.8.110 s570StockContactClosureTrap00
1.3.6.1.4.1.3052.8.120 s570StockTempTrap00
1.3.6.1.4.1.3052.8.130 s570StockHumidityTrap00
1.3.6.1.4.1.3052.8.140 s570StockAnalogTrap00
1.3.6.1.4.1.3052.8.150 s570StockOutputTrap00
1.3.6.1.4.1.3052.8.503 s570StockDataAlarmTrap00
1.3.6.1.4.1.3052.8.505 s570StockNoDataAlarmTrap00
1.3.6.1.4.1.3052.8.506 s570StockSchedTrap00
1.3.6.1.4.1.3052.8.507 s570StockImmediateTrap00
1.3.6.1.4.1.3052.8.510 s570StockCTSTrap00
1.3.6.1.4.1.3052.8.511 s570CPEDownTrap00
1.3.6.1.4.1.3052.8.515 s570FuelSensorDisconnectTrap00
1.3.6.1.4.1.3052.8.519 s570FuelSensorVolumeTrap00
1.3.6.1.4.1.3052.8.520 s570ACPowerMonitorAvgVoltageTrap00
1.3.6.1.4.1.3052.8.521 s570ACPowerMonitorAvgCurrentTrap00
1.3.6.1.4.1.3052.8.522 s570ACPowerMonitorFrequencyTrap00
1.3.6.1.4.1.3052.8.523 s570ACPowerMonitorTRPTrap00
1.3.6.1.4.1.3052.8.524 s570ACPowerMonitorDisconnectTrap00
1.3.6.1.4.1.3052.8.525 s570StockLoadSheddingTrap00
1.3.6.1.4.1.3052.8.526 s570StockScriptTrap00
1.3.6.1.4.1.3052.8.540 s570ACTotalPowerFactorTrap00
1.3.6.1.4.1.3052.8.543 s570ResetTrap00
1.3.6.1.4.1.3052.8.1000 s570UserTrap100000
1.3.6.1.4.1.3052.8.1001 s570UserTrap100100
1.3.6.1.4.1.3052.8.1002 s570UserTrap100200
1.3.6.1.4.1.3052.8.1003 s570UserTrap100300
1.3.6.1.4.1.3052.8.1004 s570UserTrap100400
1.3.6.1.4.1.3052.8.1005 s570UserTrap100500
1.3.6.1.4.1.3052.8.1006 s570UserTrap100600
1.3.6.1.4.1.3052.8.1007 s570UserTrap100700
1.3.6.1.4.1.3052.8.1008 s570UserTrap100800
1.3.6.1.4.1.3052.8.1009 s570UserTrap100900
1.3.6.1.4.1.3052.8.1010 s570UserTrap101000
1.3.6.1.4.1.3052.8.1011 s570UserTrap101100
1.3.6.1.4.1.3052.8.1012 s570UserTrap101200
1.3.6.1.4.1.3052.8.1013 s570UserTrap101300
1.3.6.1.4.1.3052.8.1014 s570UserTrap101400
1.3.6.1.4.1.3052.8.1015 s570UserTrap101500
1.3.6.1.4.1.3052.8.1016 s570UserTrap101600
1.3.6.1.4.1.3052.8.1017 s570UserTrap101700
1.3.6.1.4.1.3052.8.1018 s570UserTrap101800
1.3.6.1.4.1.3052.8.1019 s570UserTrap101900
1.3.6.1.4.1.3052.8.1020 s570UserTrap102000
1.3.6.1.4.1.3052.8.1021 s570UserTrap102100
1.3.6.1.4.1.3052.8.1022 s570UserTrap102200
1.3.6.1.4.1.3052.8.1023 s570UserTrap102300
1.3.6.1.4.1.3052.8.1024 s570UserTrap102400