OID reference

bgpPeerAfiSafiTable

1.2.826.42.1.1578918.5.65.1.3.1.2

Description

Peer <AFI, SAFI> configuration table. This table allows a user to configure peer characteristics on a per AFI/SAFI basis. This table is a configuration table - all status, statistics and control fields are deprecated in favor of the BGP peer AFI/SAFI status table (bgpPeerAfiSafiStatusTable). Rows in this table cannot …

Full description and source information

Identification

Identifier and names

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

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

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

SNMP properties

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

bgpPeerAfiSafiTable OBJECT-TYPE
  -- FAMILY-SHORT-NAME BGP_AFI
    SYNTAX      SEQUENCE OF BgpPeerAfiSafiEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION "Peer <AFI, SAFI> configuration table.

                 This table allows a user to configure peer characteristics
                 on a per AFI/SAFI basis.

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

                 Rows in this table cannot be created or destroyed manually.
                 A table entry for each supported address family is created
                 automatically when an entry in the bgpPeerTable is created.
                 The entries are destroyed when the bgpPeerTable entry is
                 destroyed.

                 This table does not contain entries for dynamic peers.

                 If the peer belongs to a peer group, then the peer's
                 per-afi-safi configuration values may be taken from either
                 the peer level (bgpPeerTable and bgpPeerAfiSafiTable) or the
                 peer group level (bgpPeergrTable and bgpPeergrAfiSafiTable).
                 Which level is used is controlled by
                 bgpPeerAfiSafiConfigFromGr, and by the configuration usage
                 fields in bgpPeerTable (bgpPeerConfigUsage,
                 bgpPeerConfigUsage2 and bgpPeerConfigUsage3).  Each of these
                 fields contains a set of bit flags.

                 bgpPeerAfiSafiConfigFromGr takes precedence, and behaves as
                 follows.

                 -  For each configuration field in bgpPeerAfiSafiTable, a
                    a corresponding bit is defined in
                    bgpPeerAfiSafiConfigFromGr.

                 -  If the bit flag is set, then the configuration is taken
                    from the peer group level.

                 The bit flag in the configuration usage fields in
                 bgpPeerTable is only relevant if the
                 bgpPeerAfiSafiConfigFromGr bit is clear.  The peer
                 configuration usage fields behave as follows.

                 -  If a configuration field exists in both bgpPeerTable
                    and the bgpPeerAfiSafiTable, then a corresponding bit
                    flag is defined.

                 -  If the bit flag is set, then the configuration is taken
                    from the peer group level (if the row/rows is/are
                    active).  Otherwise, the value is taken from the peer
                    level."
    ::= { bgpPeerData 2 }

Meaning

Descriptions

1 unique

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

Peer <AFI, SAFI> configuration table. This table allows a user to configure peer characteristics on a per AFI/SAFI basis. This table is a configuration table - all status, statistics and control fields are deprecated in favor of the BGP peer AFI/SAFI status table (bgpPeerAfiSafiStatusTable). Rows in this table cannot be created or destroyed manually. A table entry for each supported address family is created automatically when an entry in the bgpPeerTable is created. The entries are destroyed when the bgpPeerTable entry is destroyed. This table does not contain entries for dynamic peers. If the peer belongs to a peer group, then the peer's per-afi-safi configuration values may be taken from either the peer level (bgpPeerTable and bgpPeerAfiSafiTable) or the peer group level (bgpPeergrTable and bgpPeergrAfiSafiTable). Which level is used is controlled by bgpPeerAfiSafiConfigFromGr, and by the configuration usage fields in bgpPeerTable (bgpPeerConfigUsage, bgpPeerConfigUsage2 and bgpPeerConfigUsage3). Each of these fields contains a set of bit flags. bgpPeerAfiSafiConfigFromGr takes precedence, and behaves as follows. - For each configuration field in bgpPeerAfiSafiTable, a a corresponding bit is defined in bgpPeerAfiSafiConfigFromGr. - If the bit flag is set, then the configuration is taken from the peer group level. The bit flag in the configuration usage fields in bgpPeerTable is only relevant if the bgpPeerAfiSafiConfigFromGr bit is clear. The peer configuration usage fields behave as follows. - If a configuration field exists in both bgpPeerTable and the bgpPeerAfiSafiTable, then a corresponding bit flag is defined. - If the bit flag is set, then the configuration is taken from the peer group level (if the row/rows is/are active). Otherwise, the value is taken from the peer level.

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

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

Status in source: current.

Names: bgpPeerAfiSafiTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "bgpPeerAfiSafiTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "BgpPeerAfiSafiEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Peer <AFI, SAFI> configuration table. This table allows a user to configure peer characteristics on a per AFI/SAFI basis. This table is a configuration table - all status, statistics and control fields are deprecated in favor of the BGP peer AFI/SAFI status table (bgpPeerAfiSafiStatusTable). Rows in this table cannot be created or destroyed manually. A table entry for each supported address family is created automatically when an entry in the bgpPeerTable is created. The entries are destroyed when the bgpPeerTable entry is destroyed. This table does not contain entries for dynamic peers. If the peer belongs to a peer group, then the peer's per-afi-safi configuration values may be taken from either the peer level (bgpPeerTable and bgpPeerAfiSafiTable) or the peer group level (bgpPeergrTable and bgpPeergrAfiSafiTable). Which level is used is controlled by bgpPeerAfiSafiConfigFromGr, and by the configuration usage fields in bgpPeerTable (bgpPeerConfigUsage, bgpPeerConfigUsage2 and bgpPeerConfigUsage3). Each of these fields contains a set of bit flags. bgpPeerAfiSafiConfigFromGr takes precedence, and behaves as follows. - For each configuration field in bgpPeerAfiSafiTable, a a corresponding bit is defined in bgpPeerAfiSafiConfigFromGr. - If the bit flag is set, then the configuration is taken from the peer group level. The bit flag in the configuration usage fields in bgpPeerTable is only relevant if the bgpPeerAfiSafiConfigFromGr bit is clear. The peer configuration usage fields behave as follows. - If a configuration field exists in both bgpPeerTable and the bgpPeerAfiSafiTable, then a corresponding bit flag is defined. - If the bit flag is set, then the configuration is taken from the peer group level (if the row/rows is/are active). Otherwise, the value is taken from the peer level.\"",
    "::=",
    "{",
    "bgpPeerData",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "BgpPeerAfiSafiEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Peer <AFI, SAFI> configuration table. This table allows a user to configure peer characteristics on a per AFI/SAFI basis. This table is a configuration table - all status, statistics and control fields are deprecated in favor of the BGP peer AFI/SAFI status table (bgpPeerAfiSafiStatusTable). Rows in this table cannot be created or destroyed manually. A table entry for each supported address family is created automatically when an entry in the bgpPeerTable is created. The entries are destroyed when the bgpPeerTable entry is destroyed. This table does not contain entries for dynamic peers. If the peer belongs to a peer group, then the peer's per-afi-safi configuration values may be taken from either the peer level (bgpPeerTable and bgpPeerAfiSafiTable) or the peer group level (bgpPeergrTable and bgpPeergrAfiSafiTable). Which level is used is controlled by bgpPeerAfiSafiConfigFromGr, and by the configuration usage fields in bgpPeerTable (bgpPeerConfigUsage, bgpPeerConfigUsage2 and bgpPeerConfigUsage3). Each of these fields contains a set of bit flags. bgpPeerAfiSafiConfigFromGr takes precedence, and behaves as follows. - For each configuration field in bgpPeerAfiSafiTable, a a corresponding bit is defined in bgpPeerAfiSafiConfigFromGr. - If the bit flag is set, then the configuration is taken from the peer group level. The bit flag in the configuration usage fields in bgpPeerTable is only relevant if the bgpPeerAfiSafiConfigFromGr bit is clear. The peer configuration usage fields behave as follows. - If a configuration field exists in both bgpPeerTable and the bgpPeerAfiSafiTable, then a corresponding bit flag is defined. - If the bit flag is set, then the configuration is taken from the peer group level (if the row/rows is/are active). Otherwise, the value is taken from the peer level."
    ],
    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.2.1 bgpPeerAfiSafiEntry3838

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.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