OID reference

bgpPeerTable

1.2.826.42.1.1578918.5.65.1.3.1.1

Description

BGP peer configuration table. This table allows a user to configure individual BGP peers. This table is a configuration table - all status, statistics and control fields are deprecated in favor of the BGP peer status table (bgpPeerStatusTable). This table does not contain entries for dynamic peers. If a user configure…

Full description and source information

Identification

Identifier and names

Parent
1.2.826.42.1.1578918.5.65.1.3.1 (bgpPeerData)
Node code
1
Node name
bgpPeerTable
Category
SNMP management object
Numeric OID
1.2.826.42.1.1578918.5.65.1.3.1.1
URN notation
urn:oid:1.2.826.42.1.1578918.5.65.1.3.1.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

Value type
SEQUENCE OF BgpPeerEntry
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.

bgpPeerTable OBJECT-TYPE
  -- FAMILY-SHORT-NAME BGP_PER
    SYNTAX      SEQUENCE OF BgpPeerEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "BGP peer configuration table.

                 This table allows a user to configure individual BGP peers.

                 This table is a configuration table - all status, statistics
                 and control fields are deprecated in favor of the BGP peer
                 status table (bgpPeerStatusTable).

                 This table does not contain entries for dynamic peers.

                 If a user configures a new BGP peer that matches an existing
                 dynamic BGP peer then DC-BGP terminates any BGP session with
                 the dynamic BGP peer to force it to use the new
                 configuration.

                 If the peer belongs to a peer group, then the peer's
                 configuration values may be taken from either the peer MIB
                 or the peer group MIB.  Which values are used is controlled
                 by the config_usage, config_usage2 and config_usage3 fields
                 in the peer MIB.  These fields contains a set of bit flags.

                 These fields may themselves be overridden by per-AFI/SAFI
                 configuration as described in the description of
                 bgpPeerAfiSafiTable.

                 Unless specified under the description of a MIB field below,
                 or overridden by the bgpPeerAfiSafiTable, the following
                 applies.

                 -  Each configuration field in the bgpPeerTable MIB has a
                    copy in the bgpPeerGrTable MIB and a corresponding config
                    usage flag.

                 -  If the bit flag is set, then the value in the
                    bgpPeerGrTable MIB is used provided the MIB row exists
                    and is active.  Otherwise, the value in the bgpPeerTable
                    MIB is used.

                 -  If the configuration field also has a per-afi-safi
                    version in the bgpPeerAfiSafiTable MIB, then there is
                    also a per-afi-safi version in the
                    bgpPeergrAfiSafiTable MIB and the bit flag applies to
                    these values as well."
    ::= { bgpPeerData 1 }

Meaning

Descriptions

1 unique

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

BGP peer configuration table. This table allows a user to configure individual BGP peers. This table is a configuration table - all status, statistics and control fields are deprecated in favor of the BGP peer status table (bgpPeerStatusTable). This table does not contain entries for dynamic peers. If a user configures a new BGP peer that matches an existing dynamic BGP peer then DC-BGP terminates any BGP session with the dynamic BGP peer to force it to use the new configuration. If the peer belongs to a peer group, then the peer's configuration values may be taken from either the peer MIB or the peer group MIB. Which values are used is controlled by the config_usage, config_usage2 and config_usage3 fields in the peer MIB. These fields contains a set of bit flags. These fields may themselves be overridden by per-AFI/SAFI configuration as described in the description of bgpPeerAfiSafiTable. Unless specified under the description of a MIB field below, or overridden by the bgpPeerAfiSafiTable, the following applies. - Each configuration field in the bgpPeerTable MIB has a copy in the bgpPeerGrTable MIB and a corresponding config usage flag. - If the bit flag is set, then the value in the bgpPeerGrTable MIB is used provided the MIB row exists and is active. Otherwise, the value in the bgpPeerTable MIB is used. - If the configuration field also has a per-afi-safi version in the bgpPeerAfiSafiTable MIB, then there is also a per-afi-safi version in the bgpPeergrAfiSafiTable MIB and the bit flag applies to these values as well.

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

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

Status in source: current.

Names: bgpPeerTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "bgpPeerTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "BgpPeerEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"BGP peer configuration table. This table allows a user to configure individual BGP peers. This table is a configuration table - all status, statistics and control fields are deprecated in favor of the BGP peer status table (bgpPeerStatusTable). This table does not contain entries for dynamic peers. If a user configures a new BGP peer that matches an existing dynamic BGP peer then DC-BGP terminates any BGP session with the dynamic BGP peer to force it to use the new configuration. If the peer belongs to a peer group, then the peer's configuration values may be taken from either the peer MIB or the peer group MIB. Which values are used is controlled by the config_usage, config_usage2 and config_usage3 fields in the peer MIB. These fields contains a set of bit flags. These fields may themselves be overridden by per-AFI/SAFI configuration as described in the description of bgpPeerAfiSafiTable. Unless specified under the description of a MIB field below, or overridden by the bgpPeerAfiSafiTable, the following applies. - Each configuration field in the bgpPeerTable MIB has a copy in the bgpPeerGrTable MIB and a corresponding config usage flag. - If the bit flag is set, then the value in the bgpPeerGrTable MIB is used provided the MIB row exists and is active. Otherwise, the value in the bgpPeerTable MIB is used. - If the configuration field also has a per-afi-safi version in the bgpPeerAfiSafiTable MIB, then there is also a per-afi-safi version in the bgpPeergrAfiSafiTable MIB and the bit flag applies to these values as well.\"",
    "::=",
    "{",
    "bgpPeerData",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "BgpPeerEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "BGP peer configuration table. This table allows a user to configure individual BGP peers. This table is a configuration table - all status, statistics and control fields are deprecated in favor of the BGP peer status table (bgpPeerStatusTable). This table does not contain entries for dynamic peers. If a user configures a new BGP peer that matches an existing dynamic BGP peer then DC-BGP terminates any BGP session with the dynamic BGP peer to force it to use the new configuration. If the peer belongs to a peer group, then the peer's configuration values may be taken from either the peer MIB or the peer group MIB. Which values are used is controlled by the config_usage, config_usage2 and config_usage3 fields in the peer MIB. These fields contains a set of bit flags. These fields may themselves be overridden by per-AFI/SAFI configuration as described in the description of bgpPeerAfiSafiTable. Unless specified under the description of a MIB field below, or overridden by the bgpPeerAfiSafiTable, the following applies. - Each configuration field in the bgpPeerTable MIB has a copy in the bgpPeerGrTable MIB and a corresponding config usage flag. - If the bit flag is set, then the value in the bgpPeerGrTable MIB is used provided the MIB row exists and is active. Otherwise, the value in the bgpPeerTable MIB is used. - If the configuration field also has a per-afi-safi version in the bgpPeerAfiSafiTable MIB, then there is also a per-afi-safi version in the bgpPeergrAfiSafiTable MIB and the bit flag applies to these values as well."
    ],
    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.3.1.1.1 bgpPeerEntry131131

Siblings (5)

OIDNameDirect childrenDescendantsDescription
1.2.826.42.1.1578918.5.65.1.3.1.2 bgpPeerAfiSafiTable139
1.2.826.42.1.1578918.5.65.1.3.1.3 bgpPeerOrfCapabilityTable16
1.2.826.42.1.1578918.5.65.1.3.1.4 bgpPeerStatusTable1106
1.2.826.42.1.1578918.5.65.1.3.1.5 bgpPeerAfiSafiStatusTable16
1.2.826.42.1.1578918.5.65.1.3.1.6 bgpPeerDebugTable18