OID reference

bgpPeerStatusTable

1.2.826.42.1.1578918.5.65.1.3.1.4

Description

BGP peer status table. This table reports BGP peer status and statistics. It also allows a user to control BGP peer statistics and peer sessions. This table does not contain any BGP peer configuration - the bgpPeerTable MIB is the BGP peer configuration MIB. This table contains entries for both configured and dynamic …

Full description and source information

Identification

Identifier and names

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

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

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

SNMP properties

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

bgpPeerStatusTable OBJECT-TYPE
  -- FAMILY-SHORT-NAME BGP_PEER_STAT
    SYNTAX      SEQUENCE OF BgpPeerStatusEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "BGP peer status table.

                 This table reports BGP peer status and statistics.  It also
                 allows a user to control BGP peer statistics and peer
                 sessions.

                 This table does not contain any BGP peer configuration -
                 the bgpPeerTable MIB is the BGP peer configuration MIB.

                 This table contains entries for both configured and dynamic
                 peers.

                 For configured peers the corresponding rows in the
                 bgpPeerTable MIB and bgpPeerStatusTable MIB have identical
                 index fields.

                 The lifetime of a BGP peer status entry depends on whether
                 the BGP peer is configured or dynamic.
                 -  The entry for a configured peer is created and destroyed
                 when the corresponding entry in the BGP peer
                 configuration table (bgpPeerTable) is created and
                 destroyed.
                 -  The entry for a dynamic peer is created when the BGP
                 peering session is established.  It is destroyed when
                 the BGP session has terminated and the graceful restart
                 timer has expired.  Unless the BGP session is
                 re-established during the graceful restart period the
                 entry persists for only a short period after BGP
                 session termination, and if graceful restart is not in
                 use then the entry is destroyed as soon as the BGP
                 session terminates."
    ::= { bgpPeerData 4 }

Meaning

Descriptions

1 unique

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

BGP peer status table. This table reports BGP peer status and statistics. It also allows a user to control BGP peer statistics and peer sessions. This table does not contain any BGP peer configuration - the bgpPeerTable MIB is the BGP peer configuration MIB. This table contains entries for both configured and dynamic peers. For configured peers the corresponding rows in the bgpPeerTable MIB and bgpPeerStatusTable MIB have identical index fields. The lifetime of a BGP peer status entry depends on whether the BGP peer is configured or dynamic. - The entry for a configured peer is created and destroyed when the corresponding entry in the BGP peer configuration table (bgpPeerTable) is created and destroyed. - The entry for a dynamic peer is created when the BGP peering session is established. It is destroyed when the BGP session has terminated and the graceful restart timer has expired. Unless the BGP session is re-established during the graceful restart period the entry persists for only a short period after BGP session termination, and if graceful restart is not in use then the entry is destroyed as soon as the BGP session terminates.

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

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

Status in source: current.

Names: bgpPeerStatusTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "bgpPeerStatusTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "BgpPeerStatusEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"BGP peer status table. This table reports BGP peer status and statistics. It also allows a user to control BGP peer statistics and peer sessions. This table does not contain any BGP peer configuration - the bgpPeerTable MIB is the BGP peer configuration MIB. This table contains entries for both configured and dynamic peers. For configured peers the corresponding rows in the bgpPeerTable MIB and bgpPeerStatusTable MIB have identical index fields. The lifetime of a BGP peer status entry depends on whether the BGP peer is configured or dynamic. - The entry for a configured peer is created and destroyed when the corresponding entry in the BGP peer configuration table (bgpPeerTable) is created and destroyed. - The entry for a dynamic peer is created when the BGP peering session is established. It is destroyed when the BGP session has terminated and the graceful restart timer has expired. Unless the BGP session is re-established during the graceful restart period the entry persists for only a short period after BGP session termination, and if graceful restart is not in use then the entry is destroyed as soon as the BGP session terminates.\"",
    "::=",
    "{",
    "bgpPeerData",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "BgpPeerStatusEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "BGP peer status table. This table reports BGP peer status and statistics. It also allows a user to control BGP peer statistics and peer sessions. This table does not contain any BGP peer configuration - the bgpPeerTable MIB is the BGP peer configuration MIB. This table contains entries for both configured and dynamic peers. For configured peers the corresponding rows in the bgpPeerTable MIB and bgpPeerStatusTable MIB have identical index fields. The lifetime of a BGP peer status entry depends on whether the BGP peer is configured or dynamic. - The entry for a configured peer is created and destroyed when the corresponding entry in the BGP peer configuration table (bgpPeerTable) is created and destroyed. - The entry for a dynamic peer is created when the BGP peering session is established. It is destroyed when the BGP session has terminated and the graceful restart timer has expired. Unless the BGP session is re-established during the graceful restart period the entry persists for only a short period after BGP session termination, and if graceful restart is not in use then the entry is destroyed as soon as the BGP session terminates."
    ],
    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.4.1 bgpPeerStatusEntry105105

Siblings (5)

OIDNameDirect childrenDescendantsDescription
1.2.826.42.1.1578918.5.65.1.3.1.1 bgpPeerTable1132
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.5 bgpPeerAfiSafiStatusTable16
1.2.826.42.1.1578918.5.65.1.3.1.6 bgpPeerDebugTable18