OID reference

bgpPeerRangeTable

1.2.826.42.1.1578918.5.65.1.10

Description

Peer range table. This table allows a user to configure BGP dynamic neighbors. Instead of being configured individually in the BGP peer table, BGP dynamic neighbors are configured as ranges of remote addresses with associated peer groups. Each range is configured as a remote address prefix. Any BGP peer with a remote …

Full description and source information

Identification

Identifier and names

Parent
1.2.826.42.1.1578918.5.65.1 (bgpMib)
Node code
10
Node name
bgpPeerRangeTable
Category
SNMP management object
Numeric OID
1.2.826.42.1.1578918.5.65.1.10
URN notation
urn:oid:1.2.826.42.1.1578918.5.65.1.10
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

Value type
SEQUENCE OF BgpPeerRangeEntry
Maximum access defined by MIB
not-accessible
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.

bgpPeerRangeTable OBJECT-TYPE
  -- FAMILY-SHORT-NAME BGP_PR
    SYNTAX      SEQUENCE OF BgpPeerRangeEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Peer range table.

                 This table allows a user to configure BGP dynamic neighbors.
                 Instead of being configured individually in the BGP peer
                 table, BGP dynamic neighbors are configured as ranges of
                 remote addresses with associated peer groups.  Each range
                 is configured as a remote address prefix.  Any BGP peer with
                 a remote address that matches the remote address prefix
                 becomes a member of the associated peer group.

                 Each entry in this table configures a remote address prefix
                 and specifies the associated peer group.

                 DC-BGP handles incoming connections from BGP peers as
                 follows.
                 -  If the connection matches a peer configured in the
                    BGP peer table then the peer is a configured peer.
                 -  Otherwise if the connection matches a remote address
                    prefix in the BGP peer range table then the peer is
                    a dynamic peer.
                -  Otherwise if the listen socket is configured to accept
                   all incoming connections then the connection is accepted
                   and uses the default peer configuration.
                -  Otherwise the connection is rejected.

                For an incoming connection to match an entry in this table
                the following conditions must all be satisfied.
                -  The remote address of the incoming connection must match
                   the remote address prefix of the peer range entry.
                -  The row status of the peer range entry must be 'active'.
                -  The admin status of the peer range entry must be 'up'.
                -  The peer range entry must specify a peer group.
                -  The peer group must exist.
                -  The row status of the peer group must be 'active'.
                -  The admin status of the peer group must be 'up'.

                If an incoming connection doesn't satisfy all these
                conditions for one peer range entry then it can still be
                accepted if it matches another peer range entry or if the
                listen socket is configured to accept all incoming
                connections.

                If an incoming connection matches multiple peer range
                entries then the entry with the longest remote address
                prefix is selected.

                Although it is possible to configure overlapping peer ranges
                with different remote address prefix lengths, this is not
                recommended - peer range configuration is simpler and
                clearer if peer ranges do not overlap.

                Dynamic peers are always passive.  It is not possible to
                initiate outbound connections to dynamic peers because
                their addresses aren't known until they initiate an
                incoming connection.

                Deactivating a peer range entry causes BGP sessions with
                matching dynamic BGP peers to be dropped.  This does not
                apply to configured BGP peers with matching remote
                addresses, nor to dynamic BGP peers with remote addresses
                matching peer range entries with longer remote address
                prefixes."
      ::= { bgpMib 10 }

Meaning

Descriptions

1 unique

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

Peer range table. This table allows a user to configure BGP dynamic neighbors. Instead of being configured individually in the BGP peer table, BGP dynamic neighbors are configured as ranges of remote addresses with associated peer groups. Each range is configured as a remote address prefix. Any BGP peer with a remote address that matches the remote address prefix becomes a member of the associated peer group. Each entry in this table configures a remote address prefix and specifies the associated peer group. DC-BGP handles incoming connections from BGP peers as follows. - If the connection matches a peer configured in the BGP peer table then the peer is a configured peer. - Otherwise if the connection matches a remote address prefix in the BGP peer range table then the peer is a dynamic peer. - Otherwise if the listen socket is configured to accept all incoming connections then the connection is accepted and uses the default peer configuration. - Otherwise the connection is rejected. For an incoming connection to match an entry in this table the following conditions must all be satisfied. - The remote address of the incoming connection must match the remote address prefix of the peer range entry. - The row status of the peer range entry must be 'active'. - The admin status of the peer range entry must be 'up'. - The peer range entry must specify a peer group. - The peer group must exist. - The row status of the peer group must be 'active'. - The admin status of the peer group must be 'up'. If an incoming connection doesn't satisfy all these conditions for one peer range entry then it can still be accepted if it matches another peer range entry or if the listen socket is configured to accept all incoming connections. If an incoming connection matches multiple peer range entries then the entry with the longest remote address prefix is selected. Although it is possible to configure overlapping peer ranges with different remote address prefix lengths, this is not recommended - peer range configuration is simpler and clearer if peer ranges do not overlap. Dynamic peers are always passive. It is not possible to initiate outbound connections to dynamic peers because their addresses aren't known until they initiate an incoming connection. Deactivating a peer range entry causes BGP sessions with matching dynamic BGP peers to be dropped. This does not apply to configured BGP peers with matching remote addresses, nor to dynamic BGP peers with remote addresses matching peer range entries with longer remote address prefixes.

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

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

Status in source: current.

Names: bgpPeerRangeTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "bgpPeerRangeTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "BgpPeerRangeEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Peer range table. This table allows a user to configure BGP dynamic neighbors. Instead of being configured individually in the BGP peer table, BGP dynamic neighbors are configured as ranges of remote addresses with associated peer groups. Each range is configured as a remote address prefix. Any BGP peer with a remote address that matches the remote address prefix becomes a member of the associated peer group. Each entry in this table configures a remote address prefix and specifies the associated peer group. DC-BGP handles incoming connections from BGP peers as follows. - If the connection matches a peer configured in the BGP peer table then the peer is a configured peer. - Otherwise if the connection matches a remote address prefix in the BGP peer range table then the peer is a dynamic peer. - Otherwise if the listen socket is configured to accept all incoming connections then the connection is accepted and uses the default peer configuration. - Otherwise the connection is rejected. For an incoming connection to match an entry in this table the following conditions must all be satisfied. - The remote address of the incoming connection must match the remote address prefix of the peer range entry. - The row status of the peer range entry must be 'active'. - The admin status of the peer range entry must be 'up'. - The peer range entry must specify a peer group. - The peer group must exist. - The row status of the peer group must be 'active'. - The admin status of the peer group must be 'up'. If an incoming connection doesn't satisfy all these conditions for one peer range entry then it can still be accepted if it matches another peer range entry or if the listen socket is configured to accept all incoming connections. If an incoming connection matches multiple peer range entries then the entry with the longest remote address prefix is selected. Although it is possible to configure overlapping peer ranges with different remote address prefix lengths, this is not recommended - peer range configuration is simpler and clearer if peer ranges do not overlap. Dynamic peers are always passive. It is not possible to initiate outbound connections to dynamic peers because their addresses aren't known until they initiate an incoming connection. Deactivating a peer range entry causes BGP sessions with matching dynamic BGP peers to be dropped. This does not apply to configured BGP peers with matching remote addresses, nor to dynamic BGP peers with remote addresses matching peer range entries with longer remote address prefixes.\"",
    "::=",
    "{",
    "bgpMib",
    "10",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "BgpPeerRangeEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Peer range table. This table allows a user to configure BGP dynamic neighbors. Instead of being configured individually in the BGP peer table, BGP dynamic neighbors are configured as ranges of remote addresses with associated peer groups. Each range is configured as a remote address prefix. Any BGP peer with a remote address that matches the remote address prefix becomes a member of the associated peer group. Each entry in this table configures a remote address prefix and specifies the associated peer group. DC-BGP handles incoming connections from BGP peers as follows. - If the connection matches a peer configured in the BGP peer table then the peer is a configured peer. - Otherwise if the connection matches a remote address prefix in the BGP peer range table then the peer is a dynamic peer. - Otherwise if the listen socket is configured to accept all incoming connections then the connection is accepted and uses the default peer configuration. - Otherwise the connection is rejected. For an incoming connection to match an entry in this table the following conditions must all be satisfied. - The remote address of the incoming connection must match the remote address prefix of the peer range entry. - The row status of the peer range entry must be 'active'. - The admin status of the peer range entry must be 'up'. - The peer range entry must specify a peer group. - The peer group must exist. - The row status of the peer group must be 'active'. - The admin status of the peer group must be 'up'. If an incoming connection doesn't satisfy all these conditions for one peer range entry then it can still be accepted if it matches another peer range entry or if the listen socket is configured to accept all incoming connections. If an incoming connection matches multiple peer range entries then the entry with the longest remote address prefix is selected. Although it is possible to configure overlapping peer ranges with different remote address prefix lengths, this is not recommended - peer range configuration is simpler and clearer if peer ranges do not overlap. Dynamic peers are always passive. It is not possible to initiate outbound connections to dynamic peers because their addresses aren't known until they initiate an incoming connection. Deactivating a peer range entry causes BGP sessions with matching dynamic BGP peers to be dropped. This does not apply to configured BGP peers with matching remote addresses, nor to dynamic BGP peers with remote addresses matching peer range entries with longer remote address prefixes."
    ],
    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

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.2.826.42.1.1578918.5.65.1.10.1 bgpPeerRangeEntry99

Siblings (10)

OIDNameDirect childrenDescendantsDescription
1.2.826.42.1.1578918.5.65.1.1 bgpNotifications112
1.2.826.42.1.1578918.5.65.1.2 bgpRm2145
1.2.826.42.1.1578918.5.65.1.3 bgpPeer3348
1.2.826.42.1.1578918.5.65.1.4 bgpRib8238
1.2.826.42.1.1578918.5.65.1.5 bgpPib13292
1.2.826.42.1.1578918.5.65.1.6 bgpHaf428
1.2.826.42.1.1578918.5.65.1.7 bgpNm340
1.2.826.42.1.1578918.5.65.1.8 bgpNotification115
1.2.826.42.1.1578918.5.65.1.9 bgpConformance245
1.2.826.42.1.1578918.5.65.1.11 bgpUpdateGroup258