OID reference

bgpPeergrAddrSource

1.2.826.42.1.1578918.5.65.1.5.7.1.65

Description

If an address is specified with a type matching bgpPeergrRemoteAddrType, and bgpPeergrAddrSourceIf is NOT specified, then BGP will use this address as the source address for the BGP session to this peer. This field is ignored for peers identified only by interface (bgpPeerLocalAddr and bgpPeerRemoteAddr are both zero)…

Full description and source information

Identification

Identifier and names

Parent
1.2.826.42.1.1578918.5.65.1.5.7.1 (bgpPeergrEntry)
Node code
65
Node name
bgpPeergrAddrSource
Category
SNMP management object
Numeric OID
1.2.826.42.1.1578918.5.65.1.5.7.1.65
URN notation
urn:oid:1.2.826.42.1.1578918.5.65.1.5.7.1.65
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 2 826 42 1 1578918 5 65 1 5 7 1 65}

  • {iso(1) member-body(2) gb(826) 42 1 1578918 5 65 bgpMib(1) bgpPib(5) bgpPeergrTable(7) bgpPeergrEntry(1) bgpPeergrAddrSource(65)}
  • {iso(1) memberBody(2) gb(826) 42 1 1578918 5 65 bgpMib(1) bgpPib(5) bgpPeergrTable(7) bgpPeergrEntry(1) bgpPeergrAddrSource(65)}
OID-IRI notation
  • /1/2/826/42/1/1578918/5/65/1/5/7/1/65
  • /ISO/Member-Body/GB/42/1/1578918/5/65/1/5/7/1/65
  • /ISO/Member-Body/826/42/1/1578918/5/65/1/5/7/1/65
  • /ISO/2/826/42/1/1578918/5/65/1/5/7/1/65
Named path variants
  • /iso/member-body/gb/42/1/1578918/5/65/bgpMib/bgpPib/bgpPeergrTable/bgpPeergrEntry/bgpPeergrAddrSource
  • /iso/memberBody/gb/42/1/1578918/5/65/bgpMib/bgpPib/bgpPeergrTable/bgpPeergrEntry/bgpPeergrAddrSource

SNMP properties

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

bgpPeergrAddrSource OBJECT-TYPE
    SYNTAX      InetAddress
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION "If an address is specified with a type matching
                bgpPeergrRemoteAddrType, and bgpPeergrAddrSourceIf is NOT
                specified, then BGP will use this address as the source
                address for the BGP session to this peer.

                This field is ignored for peers identified only by
                interface (bgpPeerLocalAddr and bgpPeerRemoteAddr are both
                zero).

                If the type does not match bgpPeergrRemoteAddrType, or
                bgpPeergrAddrSourceIf is specified, then the source address
                is chosen as described in bgpPeergrAddrSourceIf.

                If this address is used for peer sessions in this group
                then, for dynamic peers, the local address of the incoming
                TCP connection must match the address, or else the
                connection is rejected.

                This field is only taken into account for peer-group members
                if the conditions described in the bgpPeerTable description
                are met.

                This field can be changed at any time.  However, if a peer
                is configured to use the peer group field and the field is
                changed while the peer is row_status ACTIVE, the change
                will only take effect after the peer has been cycled
                row_status NOT_IN_SERVICE and then ACTIVE, thus forcing
                the peer session to be recreated.  In this case, until the
                peer is set row_status NOT_IN_SERVICE, the peer will be
                marked as out of date (as reported by the config_state
                field in the AMB_BGP_PEER_STATUS row for the peer)."
    ::= {bgpPeergrEntry 65 }

Meaning

Descriptions

1 unique

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

If an address is specified with a type matching bgpPeergrRemoteAddrType, and bgpPeergrAddrSourceIf is NOT specified, then BGP will use this address as the source address for the BGP session to this peer. This field is ignored for peers identified only by interface (bgpPeerLocalAddr and bgpPeerRemoteAddr are both zero). If the type does not match bgpPeergrRemoteAddrType, or bgpPeergrAddrSourceIf is specified, then the source address is chosen as described in bgpPeergrAddrSourceIf. If this address is used for peer sessions in this group then, for dynamic peers, the local address of the incoming TCP connection must match the address, or else the connection is rejected. This field is only taken into account for peer-group members if the conditions described in the bgpPeerTable description are met. This field can be changed at any time. However, if a peer is configured to use the peer group field and the field is changed while the peer is row_status ACTIVE, the change will only take effect after the peer has been cycled row_status NOT_IN_SERVICE and then ACTIVE, thus forcing the peer session to be recreated. In this case, until the peer is set row_status NOT_IN_SERVICE, the peer will be marked as out of date (as reported by the config_state field in the AMB_BGP_PEER_STATUS row for the peer).

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

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

Status in source: current.

Names: bgpPeergrAddrSource

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "bgpPeergrAddrSource",
    "OBJECT-TYPE",
    "SYNTAX",
    "InetAddress",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"If an address is specified with a type matching bgpPeergrRemoteAddrType, and bgpPeergrAddrSourceIf is NOT specified, then BGP will use this address as the source address for the BGP session to this peer. This field is ignored for peers identified only by interface (bgpPeerLocalAddr and bgpPeerRemoteAddr are both zero). If the type does not match bgpPeergrRemoteAddrType, or bgpPeergrAddrSourceIf is specified, then the source address is chosen as described in bgpPeergrAddrSourceIf. If this address is used for peer sessions in this group then, for dynamic peers, the local address of the incoming TCP connection must match the address, or else the connection is rejected. This field is only taken into account for peer-group members if the conditions described in the bgpPeerTable description are met. This field can be changed at any time. However, if a peer is configured to use the peer group field and the field is changed while the peer is row_status ACTIVE, the change will only take effect after the peer has been cycled row_status NOT_IN_SERVICE and then ACTIVE, thus forcing the peer session to be recreated. In this case, until the peer is set row_status NOT_IN_SERVICE, the peer will be marked as out of date (as reported by the config_state field in the AMB_BGP_PEER_STATUS row for the peer).\"",
    "::=",
    "{",
    "bgpPeergrEntry",
    "65",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "InetAddress"
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "If an address is specified with a type matching bgpPeergrRemoteAddrType, and bgpPeergrAddrSourceIf is NOT specified, then BGP will use this address as the source address for the BGP session to this peer. This field is ignored for peers identified only by interface (bgpPeerLocalAddr and bgpPeerRemoteAddr are both zero). If the type does not match bgpPeergrRemoteAddrType, or bgpPeergrAddrSourceIf is specified, then the source address is chosen as described in bgpPeergrAddrSourceIf. If this address is used for peer sessions in this group then, for dynamic peers, the local address of the incoming TCP connection must match the address, or else the connection is rejected. This field is only taken into account for peer-group members if the conditions described in the bgpPeerTable description are met. This field can be changed at any time. However, if a peer is configured to use the peer group field and the field is changed while the peer is row_status ACTIVE, the change will only take effect after the peer has been cycled row_status NOT_IN_SERVICE and then ACTIVE, thus forcing the peer session to be recreated. In this case, until the peer is set row_status NOT_IN_SERVICE, the peer will be marked as out of date (as reported by the config_state field in the AMB_BGP_PEER_STATUS row for the peer)."
    ],
    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 (69)

OIDNameDirect childrenDescendantsDescription
1.2.826.42.1.1578918.5.65.1.5.7.1.52 bgpPeergrDistListAclIn00
1.2.826.42.1.1578918.5.65.1.5.7.1.53 bgpPeergrDistListAclOut00
1.2.826.42.1.1578918.5.65.1.5.7.1.54 bgpPeergrDistListPlIn00
1.2.826.42.1.1578918.5.65.1.5.7.1.55 bgpPeergrDistListPlOut00
1.2.826.42.1.1578918.5.65.1.5.7.1.56 bgpPeergrFilterListIn00
1.2.826.42.1.1578918.5.65.1.5.7.1.57 bgpPeergrFilterListOut00
1.2.826.42.1.1578918.5.65.1.5.7.1.58 bgpPeergrAddrSourceIf00
1.2.826.42.1.1578918.5.65.1.5.7.1.59 bgpPeergrUseImportLocalPref00
1.2.826.42.1.1578918.5.65.1.5.7.1.60 bgpPeergrImportLocalPref00
1.2.826.42.1.1578918.5.65.1.5.7.1.61 bgpPeergrUseExportLocalPref00
1.2.826.42.1.1578918.5.65.1.5.7.1.62 bgpPeergrExportLocalPref00
1.2.826.42.1.1578918.5.65.1.5.7.1.63 bgpPeergrSlowPeer00
1.2.826.42.1.1578918.5.65.1.5.7.1.64 bgpPeergrAddrSourceType00
1.2.826.42.1.1578918.5.65.1.5.7.1.66 bgpPeergrMaxPrfxClear00
1.2.826.42.1.1578918.5.65.1.5.7.1.67 bgpPeergrPrfxThresholdClear00
1.2.826.42.1.1578918.5.65.1.5.7.1.68 bgpPeergrTtlSecurityMinTtl00
1.2.826.42.1.1578918.5.65.1.5.7.1.69 bgpPeergrRemovePrivateAs00
1.2.826.42.1.1578918.5.65.1.5.7.1.70 bgpPeergrResetPeerOnCfgChange00
1.2.826.42.1.1578918.5.65.1.5.7.1.71 bgpPeergrAdminStatus00