OID reference

bgpRmEntUpdateGroups

1.2.826.42.1.1578918.5.65.1.2.1.1.58

Description

This field indicates that DC-BGP should combine peers into update groups. This means that peers which have similar configuration and export policies for a particular AFI/SAFI will share a single Adj-RIB-Out and will receive the same set of updates for that AFI/SAFI. The identity of the update group that a peer is plac…

Full description and source information

Identification

Identifier and names

Parent
1.2.826.42.1.1578918.5.65.1.2.1.1 (bgpRmEntEntry)
Node code
58
Node name
bgpRmEntUpdateGroups
Category
SNMP management object
Numeric OID
1.2.826.42.1.1578918.5.65.1.2.1.1.58
URN notation
urn:oid:1.2.826.42.1.1578918.5.65.1.2.1.1.58
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) member-body(2) gb(826) 42 1 1578918 5 65 bgpMib(1) bgpRm(2) bgpRmEntTable(1) bgpRmEntEntry(1) bgpRmEntUpdateGroups(58)}
  • {iso(1) memberBody(2) gb(826) 42 1 1578918 5 65 bgpMib(1) bgpRm(2) bgpRmEntTable(1) bgpRmEntEntry(1) bgpRmEntUpdateGroups(58)}
OID-IRI notation
  • /1/2/826/42/1/1578918/5/65/1/2/1/1/58
  • /ISO/Member-Body/GB/42/1/1578918/5/65/1/2/1/1/58
  • /ISO/Member-Body/826/42/1/1578918/5/65/1/2/1/1/58
  • /ISO/2/826/42/1/1578918/5/65/1/2/1/1/58
Named path variants
  • /iso/member-body/gb/42/1/1578918/5/65/bgpMib/bgpRm/bgpRmEntTable/bgpRmEntEntry/bgpRmEntUpdateGroups
  • /iso/memberBody/gb/42/1/1578918/5/65/bgpMib/bgpRm/bgpRmEntTable/bgpRmEntEntry/bgpRmEntUpdateGroups

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.

bgpRmEntUpdateGroups OBJECT-TYPE
    SYNTAX      TruthValue
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION "This field indicates that DC-BGP should combine peers into
                 update groups.  This means that peers which have similar
                 configuration and export policies for a particular
                 AFI/SAFI will share a single Adj-RIB-Out and will receive
                 the same set of updates for that AFI/SAFI.

                 The identity of the update group that a peer is placed in
                 for a particular AFI/SAFI can be found in the
                 bgpPeerAfiSafiStUpdateGroup field for the peer.

                 Information about update groups, including the effective
                 configuration and export policy that is shared by the
                 peers in the update group can be found in the
                 bgpUpdateGroupTable.  The members of an update group can
                 be found in the bgpUpdateGroupMembershipTable.

                 Note that setting bgpRmEntUpdateGroups to 'true' has the
                 following restrictions.

                 -  Split-horizon aggregates must be disabled
                    (bgpRmEntAggSplitHorizon must be 'false').

                 Inconsistent entity MIB settings will be rejected.

                 Enabling update groups also has the following limitations.

                 -  The value of bgpPeerCheckNextHop is ignored (assumed to
                    be 'false').

                 -  The use of ORF (Outbound Route Filtering) is
                    restricted.  In particular, DC-BGP will continue to
                    send outbound route filters to peers, but received
                    filters are ignored.

                 -  Sender-side loop detection is disabled for peers in
                    an update group.

                 This field can only be changed when the Admin Status is
                 down."
    DEFVAL       { false }
    ::= { bgpRmEntEntry 58 }

Meaning

Descriptions

1 unique

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

This field indicates that DC-BGP should combine peers into update groups. This means that peers which have similar configuration and export policies for a particular AFI/SAFI will share a single Adj-RIB-Out and will receive the same set of updates for that AFI/SAFI. The identity of the update group that a peer is placed in for a particular AFI/SAFI can be found in the bgpPeerAfiSafiStUpdateGroup field for the peer. Information about update groups, including the effective configuration and export policy that is shared by the peers in the update group can be found in the bgpUpdateGroupTable. The members of an update group can be found in the bgpUpdateGroupMembershipTable. Note that setting bgpRmEntUpdateGroups to 'true' has the following restrictions. - Split-horizon aggregates must be disabled (bgpRmEntAggSplitHorizon must be 'false'). Inconsistent entity MIB settings will be rejected. Enabling update groups also has the following limitations. - The value of bgpPeerCheckNextHop is ignored (assumed to be 'false'). - The use of ORF (Outbound Route Filtering) is restricted. In particular, DC-BGP will continue to send outbound route filters to peers, but received filters are ignored. - Sender-side loop detection is disabled for peers in an update group. This field can only be changed when the Admin Status is down.

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

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

Status in source: current.

Names: bgpRmEntUpdateGroups

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "bgpRmEntUpdateGroups",
    "OBJECT-TYPE",
    "SYNTAX",
    "TruthValue",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This field indicates that DC-BGP should combine peers into update groups. This means that peers which have similar configuration and export policies for a particular AFI/SAFI will share a single Adj-RIB-Out and will receive the same set of updates for that AFI/SAFI. The identity of the update group that a peer is placed in for a particular AFI/SAFI can be found in the bgpPeerAfiSafiStUpdateGroup field for the peer. Information about update groups, including the effective configuration and export policy that is shared by the peers in the update group can be found in the bgpUpdateGroupTable. The members of an update group can be found in the bgpUpdateGroupMembershipTable. Note that setting bgpRmEntUpdateGroups to 'true' has the following restrictions. - Split-horizon aggregates must be disabled (bgpRmEntAggSplitHorizon must be 'false'). Inconsistent entity MIB settings will be rejected. Enabling update groups also has the following limitations. - The value of bgpPeerCheckNextHop is ignored (assumed to be 'false'). - The use of ORF (Outbound Route Filtering) is restricted. In particular, DC-BGP will continue to send outbound route filters to peers, but received filters are ignored. - Sender-side loop detection is disabled for peers in an update group. This field can only be changed when the Admin Status is down.\"",
    "DEFVAL",
    "{",
    "false",
    "}",
    "::=",
    "{",
    "bgpRmEntEntry",
    "58",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "TruthValue"
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This field indicates that DC-BGP should combine peers into update groups. This means that peers which have similar configuration and export policies for a particular AFI/SAFI will share a single Adj-RIB-Out and will receive the same set of updates for that AFI/SAFI. The identity of the update group that a peer is placed in for a particular AFI/SAFI can be found in the bgpPeerAfiSafiStUpdateGroup field for the peer. Information about update groups, including the effective configuration and export policy that is shared by the peers in the update group can be found in the bgpUpdateGroupTable. The members of an update group can be found in the bgpUpdateGroupMembershipTable. Note that setting bgpRmEntUpdateGroups to 'true' has the following restrictions. - Split-horizon aggregates must be disabled (bgpRmEntAggSplitHorizon must be 'false'). Inconsistent entity MIB settings will be rejected. Enabling update groups also has the following limitations. - The value of bgpPeerCheckNextHop is ignored (assumed to be 'false'). - The use of ORF (Outbound Route Filtering) is restricted. In particular, DC-BGP will continue to send outbound route filters to peers, but received filters are ignored. - Sender-side loop detection is disabled for peers in an update group. This field can only be changed when the Admin Status is down."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "false"
    ]
  ]
}

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

Siblings (98)

OIDNameDirect childrenDescendantsDescription
1.2.826.42.1.1578918.5.65.1.2.1.1.51 bgpRmEntPeakNumAroRoutes00
1.2.826.42.1.1578918.5.65.1.2.1.1.52 bgpRmEntClearStats00
1.2.826.42.1.1578918.5.65.1.2.1.1.53 bgpRmEntFastExtFallover00
1.2.826.42.1.1578918.5.65.1.2.1.1.54 bgpRmEntRemainDelayTime00
1.2.826.42.1.1578918.5.65.1.2.1.1.55 bgpRmEntPathAttrs00
1.2.826.42.1.1578918.5.65.1.2.1.1.56 bgpRmEntAggSplitHorizon00
1.2.826.42.1.1578918.5.65.1.2.1.1.57 bgpRmEntAggAdvSuppr00
1.2.826.42.1.1578918.5.65.1.2.1.1.59 bgpRmEntPhase3DelayTime00
1.2.826.42.1.1578918.5.65.1.2.1.1.60 bgpRmEntTrapOperState00
1.2.826.42.1.1578918.5.65.1.2.1.1.61 bgpRmEntMaxASLimit00
1.2.826.42.1.1578918.5.65.1.2.1.1.62 bgpRmEntRestartTimeLeft00
1.2.826.42.1.1578918.5.65.1.2.1.1.63 bgpRmEntRestartExitReason00
1.2.826.42.1.1578918.5.65.1.2.1.1.64 bgpRmEntAsPathMultipathRelax00
1.2.826.42.1.1578918.5.65.1.2.1.1.65 bgpRmEntAsPathIgnore00
1.2.826.42.1.1578918.5.65.1.2.1.1.66 bgpRmEntPreferExistingRoute00
1.2.826.42.1.1578918.5.65.1.2.1.1.67 bgpRmEntMedMissingAsWorst00
1.2.826.42.1.1578918.5.65.1.2.1.1.68 bgpRmEntMedConfed00
1.2.826.42.1.1578918.5.65.1.2.1.1.69 bgpRmEntDynPeerRestartTime00
1.2.826.42.1.1578918.5.65.1.2.1.1.70 bgpRmEntCheckFirstAsNum00
1.2.826.42.1.1578918.5.65.1.2.1.1.71 bgpRmEntRibSizeWarning00
1.2.826.42.1.1578918.5.65.1.2.1.1.72 bgpRmEntRtiName00
1.2.826.42.1.1578918.5.65.1.2.1.1.73 bgpRmEntLmgrJoinStatus00
1.2.826.42.1.1578918.5.65.1.2.1.1.74 bgpRmEntLmgrEntIndex00
1.2.826.42.1.1578918.5.65.1.2.1.1.75 bgpRmEntDebug00
1.2.826.42.1.1578918.5.65.1.2.1.1.76 bgpRmEntLevel00
1.2.826.42.1.1578918.5.65.1.2.1.1.77 bgpRmEntAllFlagsEnabled00
1.2.826.42.1.1578918.5.65.1.2.1.1.78 bgpRmEntRxTxFlagsEnabled00
1.2.826.42.1.1578918.5.65.1.2.1.1.79 bgpRmEntProcId00
1.2.826.42.1.1578918.5.65.1.2.1.1.80 bgpRmEntRestartMultiplier00
1.2.826.42.1.1578918.5.65.1.2.1.1.81 bgpRmEntEnableAlarms00
1.2.826.42.1.1578918.5.65.1.2.1.1.82 bgpRmEntVrfName00
1.2.826.42.1.1578918.5.65.1.2.1.1.83 bgpRmEntDynPeerLimit00
1.2.826.42.1.1578918.5.65.1.2.1.1.84 bgpRmEntTableVersion00
1.2.826.42.1.1578918.5.65.1.2.1.1.85 bgpRmEntHelperOnly00
1.2.826.42.1.1578918.5.65.1.2.1.1.86 bgpRmEntInterClientReflEnabled00
1.2.826.42.1.1578918.5.65.1.2.1.1.87 bgpRmEntConfigRtRefresh00
1.2.826.42.1.1578918.5.65.1.2.1.1.88 bgpRmEntSupportIpv400
1.2.826.42.1.1578918.5.65.1.2.1.1.89 bgpRmEntUseHalProgramming00
1.2.826.42.1.1578918.5.65.1.2.1.1.90 bgpRmEntTenantId00
1.2.826.42.1.1578918.5.65.1.2.1.1.91 bgpRmEntStaleGr00
1.2.826.42.1.1578918.5.65.1.2.1.1.92 bgpRmEntSlaCommunity00
1.2.826.42.1.1578918.5.65.1.2.1.1.93 bgpRmEntSooAuto00
1.2.826.42.1.1578918.5.65.1.2.1.1.94 bgpRmEntSiteId00
1.2.826.42.1.1578918.5.65.1.2.1.1.95 bgpRmEntCliId00
1.2.826.42.1.1578918.5.65.1.2.1.1.98 bgpRmEntTenantName00
1.2.826.42.1.1578918.5.65.1.2.1.1.99 bgpRmEntVPSiteInfoLocal00
1.2.826.42.1.1578918.5.65.1.2.1.1.100 bgpRmEntVPSiteInfoRemote00
1.2.826.42.1.1578918.5.65.1.2.1.1.101 bgpRmEntCommOldFormat00