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; representative source files are shown for each definition.

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.1025 s570UserTrap102500
1.3.6.1.4.1.3052.8.1026 s570UserTrap102600
1.3.6.1.4.1.3052.8.1027 s570UserTrap102700
1.3.6.1.4.1.3052.8.1028 s570UserTrap102800
1.3.6.1.4.1.3052.8.1029 s570UserTrap102900
1.3.6.1.4.1.3052.8.1030 s570UserTrap103000
1.3.6.1.4.1.3052.8.1031 s570UserTrap103100
1.3.6.1.4.1.3052.8.1032 s570UserTrap103200
1.3.6.1.4.1.3052.8.1033 s570UserTrap103300
1.3.6.1.4.1.3052.8.1034 s570UserTrap103400
1.3.6.1.4.1.3052.8.1035 s570UserTrap103500
1.3.6.1.4.1.3052.8.1036 s570UserTrap103600
1.3.6.1.4.1.3052.8.1037 s570UserTrap103700
1.3.6.1.4.1.3052.8.1038 s570UserTrap103800
1.3.6.1.4.1.3052.8.1039 s570UserTrap103900
1.3.6.1.4.1.3052.8.1040 s570UserTrap104000
1.3.6.1.4.1.3052.8.1041 s570UserTrap104100
1.3.6.1.4.1.3052.8.1042 s570UserTrap104200
1.3.6.1.4.1.3052.8.1043 s570UserTrap104300
1.3.6.1.4.1.3052.8.1044 s570UserTrap104400
1.3.6.1.4.1.3052.8.1045 s570UserTrap104500
1.3.6.1.4.1.3052.8.1046 s570UserTrap104600
1.3.6.1.4.1.3052.8.1047 s570UserTrap104700
1.3.6.1.4.1.3052.8.1048 s570UserTrap104800
1.3.6.1.4.1.3052.8.1049 s570UserTrap104900
1.3.6.1.4.1.3052.8.1050 s570UserTrap105000
1.3.6.1.4.1.3052.8.1051 s570UserTrap105100
1.3.6.1.4.1.3052.8.1052 s570UserTrap105200
1.3.6.1.4.1.3052.8.1053 s570UserTrap105300
1.3.6.1.4.1.3052.8.1054 s570UserTrap105400
1.3.6.1.4.1.3052.8.1055 s570UserTrap105500
1.3.6.1.4.1.3052.8.1056 s570UserTrap105600
1.3.6.1.4.1.3052.8.1057 s570UserTrap105700
1.3.6.1.4.1.3052.8.1058 s570UserTrap105800
1.3.6.1.4.1.3052.8.1059 s570UserTrap105900
1.3.6.1.4.1.3052.8.1060 s570UserTrap106000
1.3.6.1.4.1.3052.8.1061 s570UserTrap106100
1.3.6.1.4.1.3052.8.1062 s570UserTrap106200
1.3.6.1.4.1.3052.8.1063 s570UserTrap106300
1.3.6.1.4.1.3052.8.1064 s570UserTrap106400
1.3.6.1.4.1.3052.8.1065 s570UserTrap106500
1.3.6.1.4.1.3052.8.1066 s570UserTrap106600
1.3.6.1.4.1.3052.8.1067 s570UserTrap106700
1.3.6.1.4.1.3052.8.1068 s570UserTrap106800
1.3.6.1.4.1.3052.8.1069 s570UserTrap106900
1.3.6.1.4.1.3052.8.1070 s570UserTrap107000
1.3.6.1.4.1.3052.8.1071 s570UserTrap107100
1.3.6.1.4.1.3052.8.1072 s570UserTrap107200
1.3.6.1.4.1.3052.8.1073 s570UserTrap107300
1.3.6.1.4.1.3052.8.1074 s570UserTrap107400