OID reference

bgpPeerLocalAddr

1.2.826.42.1.1578918.5.65.1.3.1.1.1.8

Description

The local address configured for the peering session, or a zero length address if not specified. For outbound connections, if a local address is specified then DC-BGP will bind to the specified local address. Otherwise the local address is selected by the TCP/IP stack for the NM instance configured in the bgpPeerLocal…

Full description and source information

Identification

Identifier and names

Parent
1.2.826.42.1.1578918.5.65.1.3.1.1.1 (bgpPeerEntry)
Node code
8
Node name
bgpPeerLocalAddr
Category
SNMP management object
Numeric OID
1.2.826.42.1.1578918.5.65.1.3.1.1.1.8
URN notation
urn:oid:1.2.826.42.1.1578918.5.65.1.3.1.1.1.8
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 2 826 42 1 1578918 5 65 1 3 1 1 1 8}

  • {iso(1) member-body(2) gb(826) 42 1 1578918 5 65 bgpMib(1) bgpPeer(3) bgpPeerData(1) bgpPeerTable(1) bgpPeerEntry(1) bgpPeerLocalAddr(8)}
  • {iso(1) memberBody(2) gb(826) 42 1 1578918 5 65 bgpMib(1) bgpPeer(3) bgpPeerData(1) bgpPeerTable(1) bgpPeerEntry(1) bgpPeerLocalAddr(8)}
OID-IRI notation
  • /1/2/826/42/1/1578918/5/65/1/3/1/1/1/8
  • /ISO/Member-Body/GB/42/1/1578918/5/65/1/3/1/1/1/8
  • /ISO/Member-Body/826/42/1/1578918/5/65/1/3/1/1/1/8
  • /ISO/2/826/42/1/1578918/5/65/1/3/1/1/1/8
Named path variants
  • /iso/member-body/gb/42/1/1578918/5/65/bgpMib/bgpPeer/bgpPeerData/bgpPeerTable/bgpPeerEntry/bgpPeerLocalAddr
  • /iso/memberBody/gb/42/1/1578918/5/65/bgpMib/bgpPeer/bgpPeerData/bgpPeerTable/bgpPeerEntry/bgpPeerLocalAddr

SNMP properties

Value type
InetAddress
Maximum access defined by MIB
not-accessible
Status in MIB
current
Allowed size (octets)
0–32

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. The index encoding is not inferred here.

Published row index: bgpRmEntIndex, bgpPeerLocalAddrType, bgpPeerLocalAddr, bgpPeerLocalPort, bgpPeerRemoteAddrType, bgpPeerRemoteAddr, bgpPeerRemotePort, bgpPeerLocalAddrScopeId.

A query example is omitted because the source variants do not establish compatible read access.

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.

bgpPeerLocalAddr OBJECT-TYPE
    SYNTAX      InetAddress (SIZE(0..32))
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "The local address configured for the peering session, or
                 a zero length address if not specified.

                 For outbound connections, if a local address is specified
                 then DC-BGP will bind to the specified local address.
                 Otherwise the local address is selected by the TCP/IP stack
                 for the NM instance configured in the bgpPeerLocalNm field.

                 For incoming connections, if a local address is specified
                 then the incoming connection must match the specified local
                 address.  Otherwise the local address used by the incoming
                 connection is ignored.

                 This should typically be set to the local address that is
                 recognized by the peer, though for directly connected
                 peers (such as EBGP peers) it can be left unspecified.

                 The bgpPeerSelectedLocalAddr field shows the local address
                 actually in use.

                 Note that you can have 2 peer entries to the same remote
                 <address, port> if they come from a different local
                 <address, port>.  To configure this each local
                 <address, port> must be specified explicitly and not be zero
                 length.  You will not be allowed  to do this if you are
                 listening on all addresses as it will be impossible to tell
                 which peer an incoming connection is for.  You must
                 explicitly listen on each local address in this case."
    ::= { bgpPeerEntry 8 }

Meaning

Descriptions

1 unique

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

The local address configured for the peering session, or a zero length address if not specified. For outbound connections, if a local address is specified then DC-BGP will bind to the specified local address. Otherwise the local address is selected by the TCP/IP stack for the NM instance configured in the bgpPeerLocalNm field. For incoming connections, if a local address is specified then the incoming connection must match the specified local address. Otherwise the local address used by the incoming connection is ignored. This should typically be set to the local address that is recognized by the peer, though for directly connected peers (such as EBGP peers) it can be left unspecified. The bgpPeerSelectedLocalAddr field shows the local address actually in use. Note that you can have 2 peer entries to the same remote <address, port> if they come from a different local <address, port>. To configure this each local <address, port> must be specified explicitly and not be zero length. You will not be allowed to do this if you are listening on all addresses as it will be impossible to tell which peer an incoming connection is for. You must explicitly listen on each local address in this case.

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

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

Status in source: current.

Names: bgpPeerLocalAddr

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "bgpPeerLocalAddr",
    "OBJECT-TYPE",
    "SYNTAX",
    "InetAddress",
    "(",
    "SIZE",
    "(",
    "0",
    ".",
    ".",
    "32",
    ")",
    ")",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The local address configured for the peering session, or a zero length address if not specified. For outbound connections, if a local address is specified then DC-BGP will bind to the specified local address. Otherwise the local address is selected by the TCP/IP stack for the NM instance configured in the bgpPeerLocalNm field. For incoming connections, if a local address is specified then the incoming connection must match the specified local address. Otherwise the local address used by the incoming connection is ignored. This should typically be set to the local address that is recognized by the peer, though for directly connected peers (such as EBGP peers) it can be left unspecified. The bgpPeerSelectedLocalAddr field shows the local address actually in use. Note that you can have 2 peer entries to the same remote <address, port> if they come from a different local <address, port>. To configure this each local <address, port> must be specified explicitly and not be zero length. You will not be allowed to do this if you are listening on all addresses as it will be impossible to tell which peer an incoming connection is for. You must explicitly listen on each local address in this case.\"",
    "::=",
    "{",
    "bgpPeerEntry",
    "8",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "InetAddress",
      [
        "octetStringSubType",
        [
          [
            0,
            32
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The local address configured for the peering session, or a zero length address if not specified. For outbound connections, if a local address is specified then DC-BGP will bind to the specified local address. Otherwise the local address is selected by the TCP/IP stack for the NM instance configured in the bgpPeerLocalNm field. For incoming connections, if a local address is specified then the incoming connection must match the specified local address. Otherwise the local address used by the incoming connection is ignored. This should typically be set to the local address that is recognized by the peer, though for directly connected peers (such as EBGP peers) it can be left unspecified. The bgpPeerSelectedLocalAddr field shows the local address actually in use. Note that you can have 2 peer entries to the same remote <address, port> if they come from a different local <address, port>. To configure this each local <address, port> must be specified explicitly and not be zero length. You will not be allowed to do this if you are listening on all addresses as it will be impossible to tell which peer an incoming connection is for. You must explicitly listen on each local address in this case."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.2.826)

The UK Name Registration Authority

Current Registration Authority (inferred from ancestor 1.2.826)

Mark Barratt or Vanessa Tatler

Siblings (130)

OIDNameDirect childrenDescendantsDescription
1.2.826.42.1.1578918.5.65.1.3.1.1.1.2 bgpPeerIdentifier00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.3 bgpPeerState00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.4 bgpPeerRowStatus00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.5 bgpPeerAdminStatus00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.6 bgpPeerOperStatus00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.7 bgpPeerLocalAddrType00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.9 bgpPeerLocalPort00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.10 bgpPeerLocalNm00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.11 bgpPeerRemoteAddrType00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.12 bgpPeerRemoteAddr00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.13 bgpPeerRemotePort00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.14 bgpPeerRemoteAs00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.15 bgpPeerIndex00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.16 bgpPeerConfedMember00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.17 bgpPeerReflectorClient00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.18 bgpPeerTrapEstab00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.19 bgpPeerTrapBackw00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.20 bgpPeerCapsSupport00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.21 bgpPeerLastError00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.22 bgpPeerLastErrorDataLen00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.23 bgpPeerLastErrorData00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.24 bgpPeerFsmEstablishedTime00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.25 bgpPeerInUpdatesElapsedTime00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.26 bgpPeerConnectRetryInterval00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.27 bgpPeerHoldTimeConfigd00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.28 bgpPeerKeepAliveConfigd00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.29 bgpPeerMinASOriginationInterval00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.30 bgpPeerMinRouteAdvertiseInterval00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.31 bgpPeerHoldTime00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.32 bgpPeerKeepAlive00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.33 bgpPeerInUpdates00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.34 bgpPeerOutUpdates00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.35 bgpPeerInTotalMessages00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.36 bgpPeerOutTotalMessages00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.37 bgpPeerFsmEstablishedTransitions00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.38 bgpPeerConnectRetryCount00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.39 bgpPeerClearCnts00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.40 bgpPeerConfigPeergr00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.41 bgpPeerConfigIndex00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.42 bgpPeerConfigRtRefresh00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.43 bgpPeerConfigMaxPrfx00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.44 bgpPeerConfigDropWarn00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.45 bgpPeerConfigPassive00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.46 bgpPeerConfigOpenDelay00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.47 bgpPeerConfigIdleHold00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.48 bgpPeerPassword00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.49 bgpPeerTtl00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.50 bgpPeerCheckFirstAsNum00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.51 bgpPeerAggrInclConfedAS00
1.2.826.42.1.1578918.5.65.1.3.1.1.1.52 bgpPeerMinRouteWithdrawInterval00