OID reference

bgpPeergrDisableSenderLoopDetect

1.2.826.0.1.1578918.5.65.1.5.7.1.9

Description

This field is used in conjunction with bgpPeergrAfiSafiDisSndLpDetect to indicate whether BGP should disable sender-side loop detection when sending routes to the peer. 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…

Full description and source information

Identification

Identifier and names

Parent
1.2.826.0.1.1578918.5.65.1.5.7.1 (bgpPeergrEntry)
Node code
9
Node name
bgpPeergrDisableSenderLoopDetect
Category
SNMP management object
Numeric OID
1.2.826.0.1.1578918.5.65.1.5.7.1.9
URN notation
urn:oid:1.2.826.0.1.1578918.5.65.1.5.7.1.9
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 2 826 0 1 1578918 5 65 1 5 7 1 9}

  • {iso(1) member-body(2) gb(826) national(0) eng-ltd(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpPeergrTable(7) bgpPeergrEntry(1) bgpPeergrDisableSenderLoopDetect(9)}
  • {iso(1) member-body(2) gb(826) national(0) gbNatCompany(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpPeergrTable(7) bgpPeergrEntry(1) bgpPeergrDisableSenderLoopDetect(9)}
  • {iso(1) member-body(2) gb(826) gbNational(0) eng-ltd(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpPeergrTable(7) bgpPeergrEntry(1) bgpPeergrDisableSenderLoopDetect(9)}
  • {iso(1) member-body(2) gb(826) gbNational(0) gbNatCompany(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpPeergrTable(7) bgpPeergrEntry(1) bgpPeergrDisableSenderLoopDetect(9)}
  • {iso(1) memberBody(2) gb(826) national(0) eng-ltd(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpPeergrTable(7) bgpPeergrEntry(1) bgpPeergrDisableSenderLoopDetect(9)}
  • {iso(1) memberBody(2) gb(826) national(0) gbNatCompany(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpPeergrTable(7) bgpPeergrEntry(1) bgpPeergrDisableSenderLoopDetect(9)}
  • {iso(1) memberBody(2) gb(826) gbNational(0) eng-ltd(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpPeergrTable(7) bgpPeergrEntry(1) bgpPeergrDisableSenderLoopDetect(9)}
  • {iso(1) memberBody(2) gb(826) gbNational(0) gbNatCompany(1) dataConnection(1578918) 5 65 bgpMib(1) bgpPib(5) bgpPeergrTable(7) bgpPeergrEntry(1) bgpPeergrDisableSenderLoopDetect(9)}
OID-IRI notation
  • /1/2/826/0/1/1578918/5/65/1/5/7/1/9
  • /ISO/Member-Body/GB/0/1/1578918/5/65/1/5/7/1/9
  • /ISO/Member-Body/826/0/1/1578918/5/65/1/5/7/1/9
  • /ISO/2/826/0/1/1578918/5/65/1/5/7/1/9
Named path variants
  • /iso/member-body/gb/national/eng-ltd/1578918/5/65/bgpMib/bgpPib/bgpPeergrTable/bgpPeergrEntry/bgpPeergrDisableSenderLoopDetect
  • /iso/member-body/gb/national/eng-ltd/dataConnection/5/65/bgpMib/bgpPib/bgpPeergrTable/bgpPeergrEntry/bgpPeergrDisableSenderLoopDetect
  • /iso/member-body/gb/national/gbNatCompany/1578918/5/65/bgpMib/bgpPib/bgpPeergrTable/bgpPeergrEntry/bgpPeergrDisableSenderLoopDetect
  • /iso/member-body/gb/national/gbNatCompany/dataConnection/5/65/bgpMib/bgpPib/bgpPeergrTable/bgpPeergrEntry/bgpPeergrDisableSenderLoopDetect
  • /iso/member-body/gb/gbNational/eng-ltd/1578918/5/65/bgpMib/bgpPib/bgpPeergrTable/bgpPeergrEntry/bgpPeergrDisableSenderLoopDetect
  • /iso/member-body/gb/gbNational/eng-ltd/dataConnection/5/65/bgpMib/bgpPib/bgpPeergrTable/bgpPeergrEntry/bgpPeergrDisableSenderLoopDetect
  • /iso/member-body/gb/gbNational/gbNatCompany/1578918/5/65/bgpMib/bgpPib/bgpPeergrTable/bgpPeergrEntry/bgpPeergrDisableSenderLoopDetect
  • /iso/member-body/gb/gbNational/gbNatCompany/dataConnection/5/65/bgpMib/bgpPib/bgpPeergrTable/bgpPeergrEntry/bgpPeergrDisableSenderLoopDetect
  • /iso/memberBody/gb/national/eng-ltd/1578918/5/65/bgpMib/bgpPib/bgpPeergrTable/bgpPeergrEntry/bgpPeergrDisableSenderLoopDetect
  • /iso/memberBody/gb/national/eng-ltd/dataConnection/5/65/bgpMib/bgpPib/bgpPeergrTable/bgpPeergrEntry/bgpPeergrDisableSenderLoopDetect
  • /iso/memberBody/gb/national/gbNatCompany/1578918/5/65/bgpMib/bgpPib/bgpPeergrTable/bgpPeergrEntry/bgpPeergrDisableSenderLoopDetect
  • /iso/memberBody/gb/national/gbNatCompany/dataConnection/5/65/bgpMib/bgpPib/bgpPeergrTable/bgpPeergrEntry/bgpPeergrDisableSenderLoopDetect
  • /iso/memberBody/gb/gbNational/eng-ltd/1578918/5/65/bgpMib/bgpPib/bgpPeergrTable/bgpPeergrEntry/bgpPeergrDisableSenderLoopDetect
  • /iso/memberBody/gb/gbNational/eng-ltd/dataConnection/5/65/bgpMib/bgpPib/bgpPeergrTable/bgpPeergrEntry/bgpPeergrDisableSenderLoopDetect
  • /iso/memberBody/gb/gbNational/gbNatCompany/1578918/5/65/bgpMib/bgpPib/bgpPeergrTable/bgpPeergrEntry/bgpPeergrDisableSenderLoopDetect
  • /iso/memberBody/gb/gbNational/gbNatCompany/dataConnection/5/65/bgpMib/bgpPib/bgpPeergrTable/bgpPeergrEntry/bgpPeergrDisableSenderLoopDetect

SNMP properties

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

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.

bgpPeergrDisableSenderLoopDetect OBJECT-TYPE
    SYNTAX      TruthValue
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION "This field is used in conjunction with
                 bgpPeergrAfiSafiDisSndLpDetect to indicate whether BGP
                 should disable sender-side loop detection when sending
                 routes to the peer.

                 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 bgpPeergrAllowLocalAs).  In this case it is necessary
                 to disable sender-side loop detection, by setting
                 bgpPeergrDisableSndLpDetect to 'true'.

                 Sender-side loop detection may be disabled independently
                 for each address family.  When bgpPeergrDisableSndLpDetect
                 is set to 'true', set bgpPeergrAfiSafiDisSndLpDetect to
                 'true' or 'false' to disable or enable sender-side loop
                 detection for each address family.

                 If the value is changed while the peer session is active, BGP
                 will check for any routes that need to be advertised or
                 withdrawn as a result of the change."
    DEFVAL { false }
    ::= { bgpPeergrEntry 9 }

Meaning

Descriptions

1 unique

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

This field is used in conjunction with bgpPeergrAfiSafiDisSndLpDetect to indicate whether BGP should disable sender-side loop detection when sending routes to the peer. 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 bgpPeergrAllowLocalAs). In this case it is necessary to disable sender-side loop detection, by setting bgpPeergrDisableSndLpDetect to 'true'. Sender-side loop detection may be disabled independently for each address family. When bgpPeergrDisableSndLpDetect is set to 'true', set bgpPeergrAfiSafiDisSndLpDetect to 'true' or 'false' to disable or enable sender-side loop detection for each address family. If the value is changed while the peer session 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

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

Status in source: current.

Names: bgpPeergrDisableSenderLoopDetect

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "bgpPeergrDisableSenderLoopDetect",
    "OBJECT-TYPE",
    "SYNTAX",
    "TruthValue",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This field is used in conjunction with bgpPeergrAfiSafiDisSndLpDetect to indicate whether BGP should disable sender-side loop detection when sending routes to the peer. 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 bgpPeergrAllowLocalAs). In this case it is necessary to disable sender-side loop detection, by setting bgpPeergrDisableSndLpDetect to 'true'. Sender-side loop detection may be disabled independently for each address family. When bgpPeergrDisableSndLpDetect is set to 'true', set bgpPeergrAfiSafiDisSndLpDetect to 'true' or 'false' to disable or enable sender-side loop detection for each address family. If the value is changed while the peer session is active, BGP will check for any routes that need to be advertised or withdrawn as a result of the change.\"",
    "DEFVAL",
    "{",
    "false",
    "}",
    "::=",
    "{",
    "bgpPeergrEntry",
    "9",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "TruthValue"
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This field is used in conjunction with bgpPeergrAfiSafiDisSndLpDetect to indicate whether BGP should disable sender-side loop detection when sending routes to the peer. 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 bgpPeergrAllowLocalAs). In this case it is necessary to disable sender-side loop detection, by setting bgpPeergrDisableSndLpDetect to 'true'. Sender-side loop detection may be disabled independently for each address family. When bgpPeergrDisableSndLpDetect is set to 'true', set bgpPeergrAfiSafiDisSndLpDetect to 'true' or 'false' to disable or enable sender-side loop detection for each address family. If the value is changed while the peer session 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",
      "false"
    ]
  ]
}

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 (11)

OIDNameDirect childrenDescendantsDescription
1.2.826.0.1.1578918.5.65.1.5.7.1.2 bgpPeergrIndex00
1.2.826.0.1.1578918.5.65.1.5.7.1.3 bgpPeergrRowStatus00
1.2.826.0.1.1578918.5.65.1.5.7.1.4 bgpPeergrConfig00
1.2.826.0.1.1578918.5.65.1.5.7.1.5 bgpPeergrArea00
1.2.826.0.1.1578918.5.65.1.5.7.1.6 bgpPeergrAggrConfedAS00
1.2.826.0.1.1578918.5.65.1.5.7.1.7 bgpPeergrSoftResetWithStoredInfo00
1.2.826.0.1.1578918.5.65.1.5.7.1.8 bgpPeergrAllowLocalAs00
1.2.826.0.1.1578918.5.65.1.5.7.1.10 bgpPeergrNxtHopSlf00
1.2.826.0.1.1578918.5.65.1.5.7.1.11 bgpPeergrThirdPtyNxtHop00
1.2.826.0.1.1578918.5.65.1.5.7.1.12 bgpPeergrNxtHopPeer00
1.2.826.0.1.1578918.5.65.1.5.7.1.13 bgpPeergrEnableAttributeDiscard00