OID reference

fsbgp4TCPMKTAuthRecvKeyId

1.3.6.1.4.1.2076.41.42.1.1.2

Description

Receive Key-id of the MKT. Receive Key-id of the MKT. The MKT that is ready at the sender to be used to authenticate received segments is indicated to the peer by filling the receive key id of the MKT in the RNExtKeyId field of the TCP-AO option in TCP header.

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2076.41.42.1.1 (fsbgp4TCPMKTAuthEntry)
Node code
2
Node name
fsbgp4TCPMKTAuthRecvKeyId
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2076.41.42.1.1.2
URN notation
urn:oid:1.3.6.1.4.1.2076.41.42.1.1.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2076 41 42 1 1 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 fsbgp(41) fsbgp4TCPMKTAuth(42) fsbgp4TCPMKTAuthTable(1) fsbgp4TCPMKTAuthEntry(1) fsbgp4TCPMKTAuthRecvKeyId(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 fsbgp(41) fsbgp4TCPMKTAuth(42) fsbgp4TCPMKTAuthTable(1) fsbgp4TCPMKTAuthEntry(1) fsbgp4TCPMKTAuthRecvKeyId(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fsbgp(41) fsbgp4TCPMKTAuth(42) fsbgp4TCPMKTAuthTable(1) fsbgp4TCPMKTAuthEntry(1) fsbgp4TCPMKTAuthRecvKeyId(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fsbgp(41) fsbgp4TCPMKTAuth(42) fsbgp4TCPMKTAuthTable(1) fsbgp4TCPMKTAuthEntry(1) fsbgp4TCPMKTAuthRecvKeyId(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 2076 fsbgp(41) fsbgp4TCPMKTAuth(42) fsbgp4TCPMKTAuthTable(1) fsbgp4TCPMKTAuthEntry(1) fsbgp4TCPMKTAuthRecvKeyId(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 2076 fsbgp(41) fsbgp4TCPMKTAuth(42) fsbgp4TCPMKTAuthTable(1) fsbgp4TCPMKTAuthEntry(1) fsbgp4TCPMKTAuthRecvKeyId(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fsbgp(41) fsbgp4TCPMKTAuth(42) fsbgp4TCPMKTAuthTable(1) fsbgp4TCPMKTAuthEntry(1) fsbgp4TCPMKTAuthRecvKeyId(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fsbgp(41) fsbgp4TCPMKTAuth(42) fsbgp4TCPMKTAuthTable(1) fsbgp4TCPMKTAuthEntry(1) fsbgp4TCPMKTAuthRecvKeyId(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 fsbgp(41) fsbgp4TCPMKTAuth(42) fsbgp4TCPMKTAuthTable(1) fsbgp4TCPMKTAuthEntry(1) fsbgp4TCPMKTAuthRecvKeyId(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 fsbgp(41) fsbgp4TCPMKTAuth(42) fsbgp4TCPMKTAuthTable(1) fsbgp4TCPMKTAuthEntry(1) fsbgp4TCPMKTAuthRecvKeyId(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fsbgp(41) fsbgp4TCPMKTAuth(42) fsbgp4TCPMKTAuthTable(1) fsbgp4TCPMKTAuthEntry(1) fsbgp4TCPMKTAuthRecvKeyId(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fsbgp(41) fsbgp4TCPMKTAuth(42) fsbgp4TCPMKTAuthTable(1) fsbgp4TCPMKTAuthEntry(1) fsbgp4TCPMKTAuthRecvKeyId(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 fsbgp(41) fsbgp4TCPMKTAuth(42) fsbgp4TCPMKTAuthTable(1) fsbgp4TCPMKTAuthEntry(1) fsbgp4TCPMKTAuthRecvKeyId(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 fsbgp(41) fsbgp4TCPMKTAuth(42) fsbgp4TCPMKTAuthTable(1) fsbgp4TCPMKTAuthEntry(1) fsbgp4TCPMKTAuthRecvKeyId(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 fsbgp(41) fsbgp4TCPMKTAuth(42) fsbgp4TCPMKTAuthTable(1) fsbgp4TCPMKTAuthEntry(1) fsbgp4TCPMKTAuthRecvKeyId(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 fsbgp(41) fsbgp4TCPMKTAuth(42) fsbgp4TCPMKTAuthTable(1) fsbgp4TCPMKTAuthEntry(1) fsbgp4TCPMKTAuthRecvKeyId(2)}
OID-IRI notation
  • /1/3/6/1/4/1/2076/41/42/1/1/2
  • /ISO/Identified-Organization/6/1/4/1/2076/41/42/1/1/2
  • /ISO/3/6/1/4/1/2076/41/42/1/1/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/2076/fsbgp/fsbgp4TCPMKTAuth/fsbgp4TCPMKTAuthTable/fsbgp4TCPMKTAuthEntry/fsbgp4TCPMKTAuthRecvKeyId
  • /iso/identified-organization/dod/internet/private/enterprises/2076/fsbgp/fsbgp4TCPMKTAuth/fsbgp4TCPMKTAuthTable/fsbgp4TCPMKTAuthEntry/fsbgp4TCPMKTAuthRecvKeyId
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/2076/fsbgp/fsbgp4TCPMKTAuth/fsbgp4TCPMKTAuthTable/fsbgp4TCPMKTAuthEntry/fsbgp4TCPMKTAuthRecvKeyId
  • /iso/identified-organization/dod/internet/private/vendor-objects/2076/fsbgp/fsbgp4TCPMKTAuth/fsbgp4TCPMKTAuthTable/fsbgp4TCPMKTAuthEntry/fsbgp4TCPMKTAuthRecvKeyId
  • /iso/org/dod/internet/private/enterprise/2076/fsbgp/fsbgp4TCPMKTAuth/fsbgp4TCPMKTAuthTable/fsbgp4TCPMKTAuthEntry/fsbgp4TCPMKTAuthRecvKeyId
  • /iso/org/dod/internet/private/enterprises/2076/fsbgp/fsbgp4TCPMKTAuth/fsbgp4TCPMKTAuthTable/fsbgp4TCPMKTAuthEntry/fsbgp4TCPMKTAuthRecvKeyId
  • /iso/org/dod/internet/private/ldap-enterprise/2076/fsbgp/fsbgp4TCPMKTAuth/fsbgp4TCPMKTAuthTable/fsbgp4TCPMKTAuthEntry/fsbgp4TCPMKTAuthRecvKeyId
  • /iso/org/dod/internet/private/vendor-objects/2076/fsbgp/fsbgp4TCPMKTAuth/fsbgp4TCPMKTAuthTable/fsbgp4TCPMKTAuthEntry/fsbgp4TCPMKTAuthRecvKeyId
  • /iso/iso-identified-organization/dod/internet/private/enterprise/2076/fsbgp/fsbgp4TCPMKTAuth/fsbgp4TCPMKTAuthTable/fsbgp4TCPMKTAuthEntry/fsbgp4TCPMKTAuthRecvKeyId
  • /iso/iso-identified-organization/dod/internet/private/enterprises/2076/fsbgp/fsbgp4TCPMKTAuth/fsbgp4TCPMKTAuthTable/fsbgp4TCPMKTAuthEntry/fsbgp4TCPMKTAuthRecvKeyId
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/2076/fsbgp/fsbgp4TCPMKTAuth/fsbgp4TCPMKTAuthTable/fsbgp4TCPMKTAuthEntry/fsbgp4TCPMKTAuthRecvKeyId
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/2076/fsbgp/fsbgp4TCPMKTAuth/fsbgp4TCPMKTAuthTable/fsbgp4TCPMKTAuthEntry/fsbgp4TCPMKTAuthRecvKeyId
  • /iso/iso-organization/dod/internet/private/enterprise/2076/fsbgp/fsbgp4TCPMKTAuth/fsbgp4TCPMKTAuthTable/fsbgp4TCPMKTAuthEntry/fsbgp4TCPMKTAuthRecvKeyId
  • /iso/iso-organization/dod/internet/private/enterprises/2076/fsbgp/fsbgp4TCPMKTAuth/fsbgp4TCPMKTAuthTable/fsbgp4TCPMKTAuthEntry/fsbgp4TCPMKTAuthRecvKeyId
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/2076/fsbgp/fsbgp4TCPMKTAuth/fsbgp4TCPMKTAuthTable/fsbgp4TCPMKTAuthEntry/fsbgp4TCPMKTAuthRecvKeyId
  • /iso/iso-organization/dod/internet/private/vendor-objects/2076/fsbgp/fsbgp4TCPMKTAuth/fsbgp4TCPMKTAuthTable/fsbgp4TCPMKTAuthEntry/fsbgp4TCPMKTAuthRecvKeyId

SNMP properties

Value type
Integer32
Maximum access defined by MIB
read-write
Status in MIB
current
Allowed ranges
0–255

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In ARICENT-BGP-MIB, the row index fsbgp4TCPMKTAuthKeyId is declared as Integer32. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.2076.41.42.1.1.2.<fsbgp4TCPMKTAuthKeyId>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

Published row index: fsbgp4TCPMKTAuthKeyId.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.2076.41.42.1.1.2

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

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.

fsbgp4TCPMKTAuthRecvKeyId OBJECT-TYPE
       SYNTAX      Integer32 (0..255)
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "Receive Key-id of the MKT. Receive Key-id of the MKT. 
            The MKT that is ready at the sender to 
            be used to authenticate received segments is indicated to the 
            peer by filling the receive key id of the MKT in the RNExtKeyId 
            field of the TCP-AO option in TCP header."
       ::=  { fsbgp4TCPMKTAuthEntry 2 }

Meaning

Descriptions

1 unique

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

Receive Key-id of the MKT. Receive Key-id of the MKT. The MKT that is ready at the sender to be used to authenticate received segments is indicated to the peer by filling the receive key id of the MKT in the RNExtKeyId field of the TCP-AO option in TCP header.

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

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

Status in source: current.

Names: fsbgp4TCPMKTAuthRecvKeyId

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsbgp4TCPMKTAuthRecvKeyId",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "0",
    ".",
    ".",
    "255",
    ")",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Receive Key-id of the MKT. Receive Key-id of the MKT. The MKT that is ready at the sender to be used to authenticate received segments is indicated to the peer by filling the receive key id of the MKT in the RNExtKeyId field of the TCP-AO option in TCP header.\"",
    "::=",
    "{",
    "fsbgp4TCPMKTAuthEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            0,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Receive Key-id of the MKT. Receive Key-id of the MKT. The MKT that is ready at the sender to be used to authenticate received segments is indicated to the peer by filling the receive key id of the MKT in the RNExtKeyId field of the TCP-AO option in TCP header."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2076)

Division Products

Siblings (5)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2076.41.42.1.1.1 fsbgp4TCPMKTAuthKeyId00
1.3.6.1.4.1.2076.41.42.1.1.3 fsbgp4TCPMKTAuthMasterKey00
1.3.6.1.4.1.2076.41.42.1.1.4 fsbgp4TCPMKTAuthAlgo00
1.3.6.1.4.1.2076.41.42.1.1.5 fsbgp4TCPMKTAuthTcpOptExc00
1.3.6.1.4.1.2076.41.42.1.1.6 fsbgp4TCPMKTAuthRowStatus00