OID reference

bgpPeergrAfiSafiDisSndLpDetect

1.2.826.0.1.1578918.5.65.1.5.12.1.6

Description

Gives finer control of the sender-side loop detection configuration provided by bgpPeergrDisableSenderLoopDetect. By default, BGP performs sender side loop detection. That is, it will not advertise a route to a peer if the AS-Path of the route already contains the peer's AS number. A peer would typically discard such …

Full description and source information

Identification

Identifier and names

Parent
1.2.826.0.1.1578918.5.65.1.5.12.1 (bgpPeergrAfiSafiEntry)
Node code
6
Node name
bgpPeergrAfiSafiDisSndLpDetect
Category
SNMP management object
Numeric OID
1.2.826.0.1.1578918.5.65.1.5.12.1.6
URN notation
urn:oid:1.2.826.0.1.1578918.5.65.1.5.12.1.6
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 2 826 0 1 1578918 5 65 1 5 12 1 6}

  • {iso(1) member-body(2) gb(826) national(0) eng-ltd(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpPeergrAfiSafiTable(12) bgpPeergrAfiSafiEntry(1) bgpPeergrAfiSafiDisSndLpDetect(6)}
  • {iso(1) member-body(2) gb(826) national(0) gbNatCompany(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpPeergrAfiSafiTable(12) bgpPeergrAfiSafiEntry(1) bgpPeergrAfiSafiDisSndLpDetect(6)}
  • {iso(1) member-body(2) gb(826) gbNational(0) eng-ltd(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpPeergrAfiSafiTable(12) bgpPeergrAfiSafiEntry(1) bgpPeergrAfiSafiDisSndLpDetect(6)}
  • {iso(1) member-body(2) gb(826) gbNational(0) gbNatCompany(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpPeergrAfiSafiTable(12) bgpPeergrAfiSafiEntry(1) bgpPeergrAfiSafiDisSndLpDetect(6)}
  • {iso(1) memberBody(2) gb(826) national(0) eng-ltd(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpPeergrAfiSafiTable(12) bgpPeergrAfiSafiEntry(1) bgpPeergrAfiSafiDisSndLpDetect(6)}
  • {iso(1) memberBody(2) gb(826) national(0) gbNatCompany(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpPeergrAfiSafiTable(12) bgpPeergrAfiSafiEntry(1) bgpPeergrAfiSafiDisSndLpDetect(6)}
  • {iso(1) memberBody(2) gb(826) gbNational(0) eng-ltd(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpPeergrAfiSafiTable(12) bgpPeergrAfiSafiEntry(1) bgpPeergrAfiSafiDisSndLpDetect(6)}
  • {iso(1) memberBody(2) gb(826) gbNational(0) gbNatCompany(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpPeergrAfiSafiTable(12) bgpPeergrAfiSafiEntry(1) bgpPeergrAfiSafiDisSndLpDetect(6)}
OID-IRI notation
  • /1/2/826/0/1/1578918/5/65/1/5/12/1/6
  • /ISO/Member-Body/GB/0/1/1578918/5/65/1/5/12/1/6
  • /ISO/Member-Body/826/0/1/1578918/5/65/1/5/12/1/6
  • /ISO/2/826/0/1/1578918/5/65/1/5/12/1/6
Named path variants
  • /iso/member-body/gb/national/eng-ltd/1578918/5/65/bgpMib/bgpPib/bgpPeergrAfiSafiTable/bgpPeergrAfiSafiEntry/bgpPeergrAfiSafiDisSndLpDetect
  • /iso/member-body/gb/national/eng-ltd/dataConnection/5/65/bgpMib/bgpPib/bgpPeergrAfiSafiTable/bgpPeergrAfiSafiEntry/bgpPeergrAfiSafiDisSndLpDetect
  • /iso/member-body/gb/national/gbNatCompany/1578918/5/65/bgpMib/bgpPib/bgpPeergrAfiSafiTable/bgpPeergrAfiSafiEntry/bgpPeergrAfiSafiDisSndLpDetect
  • /iso/member-body/gb/national/gbNatCompany/dataConnection/5/65/bgpMib/bgpPib/bgpPeergrAfiSafiTable/bgpPeergrAfiSafiEntry/bgpPeergrAfiSafiDisSndLpDetect
  • /iso/member-body/gb/gbNational/eng-ltd/1578918/5/65/bgpMib/bgpPib/bgpPeergrAfiSafiTable/bgpPeergrAfiSafiEntry/bgpPeergrAfiSafiDisSndLpDetect
  • /iso/member-body/gb/gbNational/eng-ltd/dataConnection/5/65/bgpMib/bgpPib/bgpPeergrAfiSafiTable/bgpPeergrAfiSafiEntry/bgpPeergrAfiSafiDisSndLpDetect
  • /iso/member-body/gb/gbNational/gbNatCompany/1578918/5/65/bgpMib/bgpPib/bgpPeergrAfiSafiTable/bgpPeergrAfiSafiEntry/bgpPeergrAfiSafiDisSndLpDetect
  • /iso/member-body/gb/gbNational/gbNatCompany/dataConnection/5/65/bgpMib/bgpPib/bgpPeergrAfiSafiTable/bgpPeergrAfiSafiEntry/bgpPeergrAfiSafiDisSndLpDetect
  • /iso/memberBody/gb/national/eng-ltd/1578918/5/65/bgpMib/bgpPib/bgpPeergrAfiSafiTable/bgpPeergrAfiSafiEntry/bgpPeergrAfiSafiDisSndLpDetect
  • /iso/memberBody/gb/national/eng-ltd/dataConnection/5/65/bgpMib/bgpPib/bgpPeergrAfiSafiTable/bgpPeergrAfiSafiEntry/bgpPeergrAfiSafiDisSndLpDetect
  • /iso/memberBody/gb/national/gbNatCompany/1578918/5/65/bgpMib/bgpPib/bgpPeergrAfiSafiTable/bgpPeergrAfiSafiEntry/bgpPeergrAfiSafiDisSndLpDetect
  • /iso/memberBody/gb/national/gbNatCompany/dataConnection/5/65/bgpMib/bgpPib/bgpPeergrAfiSafiTable/bgpPeergrAfiSafiEntry/bgpPeergrAfiSafiDisSndLpDetect
  • /iso/memberBody/gb/gbNational/eng-ltd/1578918/5/65/bgpMib/bgpPib/bgpPeergrAfiSafiTable/bgpPeergrAfiSafiEntry/bgpPeergrAfiSafiDisSndLpDetect
  • /iso/memberBody/gb/gbNational/eng-ltd/dataConnection/5/65/bgpMib/bgpPib/bgpPeergrAfiSafiTable/bgpPeergrAfiSafiEntry/bgpPeergrAfiSafiDisSndLpDetect
  • /iso/memberBody/gb/gbNational/gbNatCompany/1578918/5/65/bgpMib/bgpPib/bgpPeergrAfiSafiTable/bgpPeergrAfiSafiEntry/bgpPeergrAfiSafiDisSndLpDetect
  • /iso/memberBody/gb/gbNational/gbNatCompany/dataConnection/5/65/bgpMib/bgpPib/bgpPeergrAfiSafiTable/bgpPeergrAfiSafiEntry/bgpPeergrAfiSafiDisSndLpDetect

SNMP properties

Value type
TruthValue
Maximum access defined by MIB
read-create
Status in MIB
current
Default value
true

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.

bgpPeergrAfiSafiDisSndLpDetect OBJECT-TYPE
    SYNTAX      TruthValue
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION "Gives finer control of the sender-side loop detection
                 configuration provided by bgpPeergrDisableSenderLoopDetect.

                 By default, BGP performs sender side loop detection.  That
                 is, it will not advertise a route to a peer if the AS-Path
                 of the route already contains the peer's AS number.  A
                 peer would typically discard such routes, so this is
                 normally a useful optimization.

                 However, the peer may be configured to accept such routes
                 (see bgpPeergrAfiSafiAllowLocalAs).  In this case it is
                 necessary to disable sender-side loop detection.

                 When bgpPeergrDisableSenderLoopDetect is 'true', BGP
                 disables sender-side loop detection for those address
                 families for which bgpPeergrAfiSafiDisSndLpDetect is
                 'true'.

                 When bgpPeergrDisableSenderLoopDetect is 'false',
                 sender-side loop detection is not disable for any address
                 families.

                 If the value of this object is changed while a peer in the
                 peer group is active, BGP will check for any routes that need
                 to be advertised or withdrawn as a result of the change."
    DEFVAL { true }
    ::= { bgpPeergrAfiSafiEntry 6 }

Meaning

Descriptions

1 unique

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

Gives finer control of the sender-side loop detection configuration provided by bgpPeergrDisableSenderLoopDetect. By default, BGP performs sender side loop detection. That is, it will not advertise a route to a peer if the AS-Path of the route already contains the peer's AS number. A peer would typically discard such routes, so this is normally a useful optimization. However, the peer may be configured to accept such routes (see bgpPeergrAfiSafiAllowLocalAs). In this case it is necessary to disable sender-side loop detection. When bgpPeergrDisableSenderLoopDetect is 'true', BGP disables sender-side loop detection for those address families for which bgpPeergrAfiSafiDisSndLpDetect is 'true'. When bgpPeergrDisableSenderLoopDetect is 'false', sender-side loop detection is not disable for any address families. If the value of this object is changed while a peer in the peer group is active, BGP will check for any routes that need to be advertised or withdrawn as a result of the change.

Sources for this description

Data Connection / MetaSwitch MIB copies (MibBrowser.online)

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 1Data Connection / MetaSwitch MIB copies (MibBrowser.online)1 record · 1 source

Description 1

bgpPeergrAfiSafiDisSndLpDetect · currentData Connection / MetaSwitch MIB copies (MibBrowser.online)1 source

Status in source: current.

Names: bgpPeergrAfiSafiDisSndLpDetect

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "bgpPeergrAfiSafiDisSndLpDetect",
    "OBJECT-TYPE",
    "SYNTAX",
    "TruthValue",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Gives finer control of the sender-side loop detection configuration provided by bgpPeergrDisableSenderLoopDetect. By default, BGP performs sender side loop detection. That is, it will not advertise a route to a peer if the AS-Path of the route already contains the peer's AS number. A peer would typically discard such routes, so this is normally a useful optimization. However, the peer may be configured to accept such routes (see bgpPeergrAfiSafiAllowLocalAs). In this case it is necessary to disable sender-side loop detection. When bgpPeergrDisableSenderLoopDetect is 'true', BGP disables sender-side loop detection for those address families for which bgpPeergrAfiSafiDisSndLpDetect is 'true'. When bgpPeergrDisableSenderLoopDetect is 'false', sender-side loop detection is not disable for any address families. If the value of this object is changed while a peer in the peer group is active, BGP will check for any routes that need to be advertised or withdrawn as a result of the change.\"",
    "DEFVAL",
    "{",
    "true",
    "}",
    "::=",
    "{",
    "bgpPeergrAfiSafiEntry",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "TruthValue"
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Gives finer control of the sender-side loop detection configuration provided by bgpPeergrDisableSenderLoopDetect. By default, BGP performs sender side loop detection. That is, it will not advertise a route to a peer if the AS-Path of the route already contains the peer's AS number. A peer would typically discard such routes, so this is normally a useful optimization. However, the peer may be configured to accept such routes (see bgpPeergrAfiSafiAllowLocalAs). In this case it is necessary to disable sender-side loop detection. When bgpPeergrDisableSenderLoopDetect is 'true', BGP disables sender-side loop detection for those address families for which bgpPeergrAfiSafiDisSndLpDetect is 'true'. When bgpPeergrDisableSenderLoopDetect is 'false', sender-side loop detection is not disable for any address families. If the value of this object is changed while a peer in the peer group is active, BGP will check for any routes that need to be advertised or withdrawn as a result of the change."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "true"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.2.826.0.1)

None (see information above)

Current Registration Authority (inferred from ancestor 1.2.826.0)

Telecoms CSC

Siblings (7)

OIDNameDirect childrenDescendantsDescription
1.2.826.0.1.1578918.5.65.1.5.12.1.3 bgpPeergrAfiSafiAfi00
1.2.826.0.1.1578918.5.65.1.5.12.1.4 bgpPeergrAfiSafiSafi00
1.2.826.0.1.1578918.5.65.1.5.12.1.5 bgpPeergrAfiSafiAllowLocalAs00
1.2.826.0.1.1578918.5.65.1.5.12.1.7 bgpPeergrAfiSafiNxtHopSlf00
1.2.826.0.1.1578918.5.65.1.5.12.1.8 bgpPeergrAfiSafiOrigDefault00
1.2.826.0.1.1578918.5.65.1.5.12.1.9 bgpPeergrAfiSafiOrigDefaultRtMap00
1.2.826.0.1.1578918.5.65.1.5.12.1.10 bgpPeergrAfiSafiSoftResetStore00