OID reference

bgpRmEntUpdateGroups

1.2.826.0.1.1578918.5.65.1.2.1.1.58

Description

This field indicates that DC-BGP should treat each configured peer group for IBGP peers as an update group. This means that all the peers in the peer group will share a single Adj-RIB-Out and will receive the same set of updates. Note that setting bgpRmEntUpdateGroups to 'true' requires that all of the peers in each I…

Full description and source information

Identification

Identifier and names

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

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

  • {iso(1) member-body(2) gb(826) national(0) eng-ltd(1) dataConnection(1578918) 5 65 bgpMib(1) bgpRm(2) bgpRmEntTable(1) bgpRmEntEntry(1) bgpRmEntUpdateGroups(58)}
  • {iso(1) member-body(2) gb(826) national(0) gbNatCompany(1) dataConnection(1578918) 5 65 bgpMib(1) bgpRm(2) bgpRmEntTable(1) bgpRmEntEntry(1) bgpRmEntUpdateGroups(58)}
  • {iso(1) member-body(2) gb(826) gbNational(0) eng-ltd(1) dataConnection(1578918) 5 65 bgpMib(1) bgpRm(2) bgpRmEntTable(1) bgpRmEntEntry(1) bgpRmEntUpdateGroups(58)}
  • {iso(1) member-body(2) gb(826) gbNational(0) gbNatCompany(1) dataConnection(1578918) 5 65 bgpMib(1) bgpRm(2) bgpRmEntTable(1) bgpRmEntEntry(1) bgpRmEntUpdateGroups(58)}
  • {iso(1) memberBody(2) gb(826) national(0) eng-ltd(1) dataConnection(1578918) 5 65 bgpMib(1) bgpRm(2) bgpRmEntTable(1) bgpRmEntEntry(1) bgpRmEntUpdateGroups(58)}
  • {iso(1) memberBody(2) gb(826) national(0) gbNatCompany(1) dataConnection(1578918) 5 65 bgpMib(1) bgpRm(2) bgpRmEntTable(1) bgpRmEntEntry(1) bgpRmEntUpdateGroups(58)}
  • {iso(1) memberBody(2) gb(826) gbNational(0) eng-ltd(1) dataConnection(1578918) 5 65 bgpMib(1) bgpRm(2) bgpRmEntTable(1) bgpRmEntEntry(1) bgpRmEntUpdateGroups(58)}
  • {iso(1) memberBody(2) gb(826) gbNational(0) gbNatCompany(1) dataConnection(1578918) 5 65 bgpMib(1) bgpRm(2) bgpRmEntTable(1) bgpRmEntEntry(1) bgpRmEntUpdateGroups(58)}
OID-IRI notation
  • /1/2/826/0/1/1578918/5/65/1/2/1/1/58
  • /ISO/Member-Body/GB/0/1/1578918/5/65/1/2/1/1/58
  • /ISO/Member-Body/826/0/1/1578918/5/65/1/2/1/1/58
  • /ISO/2/826/0/1/1578918/5/65/1/2/1/1/58
Named path variants
  • /iso/member-body/gb/national/eng-ltd/1578918/5/65/bgpMib/bgpRm/bgpRmEntTable/bgpRmEntEntry/bgpRmEntUpdateGroups
  • /iso/member-body/gb/national/eng-ltd/dataConnection/5/65/bgpMib/bgpRm/bgpRmEntTable/bgpRmEntEntry/bgpRmEntUpdateGroups
  • /iso/member-body/gb/national/gbNatCompany/1578918/5/65/bgpMib/bgpRm/bgpRmEntTable/bgpRmEntEntry/bgpRmEntUpdateGroups
  • /iso/member-body/gb/national/gbNatCompany/dataConnection/5/65/bgpMib/bgpRm/bgpRmEntTable/bgpRmEntEntry/bgpRmEntUpdateGroups
  • /iso/member-body/gb/gbNational/eng-ltd/1578918/5/65/bgpMib/bgpRm/bgpRmEntTable/bgpRmEntEntry/bgpRmEntUpdateGroups
  • /iso/member-body/gb/gbNational/eng-ltd/dataConnection/5/65/bgpMib/bgpRm/bgpRmEntTable/bgpRmEntEntry/bgpRmEntUpdateGroups
  • /iso/member-body/gb/gbNational/gbNatCompany/1578918/5/65/bgpMib/bgpRm/bgpRmEntTable/bgpRmEntEntry/bgpRmEntUpdateGroups
  • /iso/member-body/gb/gbNational/gbNatCompany/dataConnection/5/65/bgpMib/bgpRm/bgpRmEntTable/bgpRmEntEntry/bgpRmEntUpdateGroups
  • /iso/memberBody/gb/national/eng-ltd/1578918/5/65/bgpMib/bgpRm/bgpRmEntTable/bgpRmEntEntry/bgpRmEntUpdateGroups
  • /iso/memberBody/gb/national/eng-ltd/dataConnection/5/65/bgpMib/bgpRm/bgpRmEntTable/bgpRmEntEntry/bgpRmEntUpdateGroups
  • /iso/memberBody/gb/national/gbNatCompany/1578918/5/65/bgpMib/bgpRm/bgpRmEntTable/bgpRmEntEntry/bgpRmEntUpdateGroups
  • /iso/memberBody/gb/national/gbNatCompany/dataConnection/5/65/bgpMib/bgpRm/bgpRmEntTable/bgpRmEntEntry/bgpRmEntUpdateGroups
  • /iso/memberBody/gb/gbNational/eng-ltd/1578918/5/65/bgpMib/bgpRm/bgpRmEntTable/bgpRmEntEntry/bgpRmEntUpdateGroups
  • /iso/memberBody/gb/gbNational/eng-ltd/dataConnection/5/65/bgpMib/bgpRm/bgpRmEntTable/bgpRmEntEntry/bgpRmEntUpdateGroups
  • /iso/memberBody/gb/gbNational/gbNatCompany/1578918/5/65/bgpMib/bgpRm/bgpRmEntTable/bgpRmEntEntry/bgpRmEntUpdateGroups
  • /iso/memberBody/gb/gbNational/gbNatCompany/dataConnection/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 treat each
                 configured peer group for IBGP peers as an update group.
                 This means that all the peers in the peer group will share
                 a single Adj-RIB-Out and will receive the same set of
                 updates.

                 Note that setting bgpRmEntUpdateGroups to 'true' requires
                 that all of the peers in each IBGP peer group are
                 configured such that they require the same set of routes.
                 This imposes a number of configuration restrictions.

                 Inconsistent entity MIB settings will be rejected.

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

                 -  Non-persistent AROs (NPA) must be disabled
                    (bgpRmEntNonPersistentAros must be 'false').

                 The value of bgpPeerCheckNextHop is ignored (assumed to be
                 'false') for peers in an IBGP peer group when update
                 groups are enabled.

                 If a peer session starts and one of the following values
                 does not match the value for a peer in the peer group's
                 update group, then the new peer will not be added to the
                 update group.

                 -  The negotiated AS number size for the session.
                 -  The configured value for bgpPeerConfedMember.
                 -  The configured value for bgpPeerReflectorClient.

                 The following timer values will be taken from an arbitrary
                 member of the update group and will be applied to the
                 whole update group.  The timer values will therefore be
                 deterministic only if the same values are used for all
                 peers in a peer group.

                 -  bgpPeerMinASOriginationInterval.
                 -  bgpPeerMinRouteAdvertiseInterval.
                 -  bgpPeerMinRouteWithdrawInterval.

                 The local IP address used for next-hop-self will be taken
                 from an arbitrary member of the update group and will be
                 applied to the whole update group.  The local IP address
                 used will therefore be deterministic only if the same
                 values are used for all peers in a peer group.

                 Note also that setting bgpRmEntUpdateGroups to 'true'
                 limits the use of ORF (Outbound Route Filtering) for the
                 peers in an update group.  In particular, DC-BGP will
                 continue to send outbound route filters to peers, but
                 received filters are ignored.

                 In addition, when bgpRmEntUpdateGroups is 'true', the
                 value of bgpPeerConfigPeergr for a peer can only be
                 changed while the peer MIB row admin status is 'down'.

                 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 treat each configured peer group for IBGP peers as an update group. This means that all the peers in the peer group will share a single Adj-RIB-Out and will receive the same set of updates. Note that setting bgpRmEntUpdateGroups to 'true' requires that all of the peers in each IBGP peer group are configured such that they require the same set of routes. This imposes a number of configuration restrictions. Inconsistent entity MIB settings will be rejected. - Split-horizon aggregates must be disabled (bgpRmEntAggSplitHorizon must be 'false'. - Non-persistent AROs (NPA) must be disabled (bgpRmEntNonPersistentAros must be 'false'). The value of bgpPeerCheckNextHop is ignored (assumed to be 'false') for peers in an IBGP peer group when update groups are enabled. If a peer session starts and one of the following values does not match the value for a peer in the peer group's update group, then the new peer will not be added to the update group. - The negotiated AS number size for the session. - The configured value for bgpPeerConfedMember. - The configured value for bgpPeerReflectorClient. The following timer values will be taken from an arbitrary member of the update group and will be applied to the whole update group. The timer values will therefore be deterministic only if the same values are used for all peers in a peer group. - bgpPeerMinASOriginationInterval. - bgpPeerMinRouteAdvertiseInterval. - bgpPeerMinRouteWithdrawInterval. The local IP address used for next-hop-self will be taken from an arbitrary member of the update group and will be applied to the whole update group. The local IP address used will therefore be deterministic only if the same values are used for all peers in a peer group. Note also that setting bgpRmEntUpdateGroups to 'true' limits the use of ORF (Outbound Route Filtering) for the peers in an update group. In particular, DC-BGP will continue to send outbound route filters to peers, but received filters are ignored. In addition, when bgpRmEntUpdateGroups is 'true', the value of bgpPeerConfigPeergr for a peer can only be changed while the peer MIB row admin status is 'down'. This field can only be changed when the Admin Status is down.

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

bgpRmEntUpdateGroups · currentData Connection / MetaSwitch MIB copies (MibBrowser.online)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 treat each configured peer group for IBGP peers as an update group. This means that all the peers in the peer group will share a single Adj-RIB-Out and will receive the same set of updates. Note that setting bgpRmEntUpdateGroups to 'true' requires that all of the peers in each IBGP peer group are configured such that they require the same set of routes. This imposes a number of configuration restrictions. Inconsistent entity MIB settings will be rejected. - Split-horizon aggregates must be disabled (bgpRmEntAggSplitHorizon must be 'false'. - Non-persistent AROs (NPA) must be disabled (bgpRmEntNonPersistentAros must be 'false'). The value of bgpPeerCheckNextHop is ignored (assumed to be 'false') for peers in an IBGP peer group when update groups are enabled. If a peer session starts and one of the following values does not match the value for a peer in the peer group's update group, then the new peer will not be added to the update group. - The negotiated AS number size for the session. - The configured value for bgpPeerConfedMember. - The configured value for bgpPeerReflectorClient. The following timer values will be taken from an arbitrary member of the update group and will be applied to the whole update group. The timer values will therefore be deterministic only if the same values are used for all peers in a peer group. - bgpPeerMinASOriginationInterval. - bgpPeerMinRouteAdvertiseInterval. - bgpPeerMinRouteWithdrawInterval. The local IP address used for next-hop-self will be taken from an arbitrary member of the update group and will be applied to the whole update group. The local IP address used will therefore be deterministic only if the same values are used for all peers in a peer group. Note also that setting bgpRmEntUpdateGroups to 'true' limits the use of ORF (Outbound Route Filtering) for the peers in an update group. In particular, DC-BGP will continue to send outbound route filters to peers, but received filters are ignored. In addition, when bgpRmEntUpdateGroups is 'true', the value of bgpPeerConfigPeergr for a peer can only be changed while the peer MIB row admin status is 'down'. 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 treat each configured peer group for IBGP peers as an update group. This means that all the peers in the peer group will share a single Adj-RIB-Out and will receive the same set of updates. Note that setting bgpRmEntUpdateGroups to 'true' requires that all of the peers in each IBGP peer group are configured such that they require the same set of routes. This imposes a number of configuration restrictions. Inconsistent entity MIB settings will be rejected. - Split-horizon aggregates must be disabled (bgpRmEntAggSplitHorizon must be 'false'. - Non-persistent AROs (NPA) must be disabled (bgpRmEntNonPersistentAros must be 'false'). The value of bgpPeerCheckNextHop is ignored (assumed to be 'false') for peers in an IBGP peer group when update groups are enabled. If a peer session starts and one of the following values does not match the value for a peer in the peer group's update group, then the new peer will not be added to the update group. - The negotiated AS number size for the session. - The configured value for bgpPeerConfedMember. - The configured value for bgpPeerReflectorClient. The following timer values will be taken from an arbitrary member of the update group and will be applied to the whole update group. The timer values will therefore be deterministic only if the same values are used for all peers in a peer group. - bgpPeerMinASOriginationInterval. - bgpPeerMinRouteAdvertiseInterval. - bgpPeerMinRouteWithdrawInterval. The local IP address used for next-hop-self will be taken from an arbitrary member of the update group and will be applied to the whole update group. The local IP address used will therefore be deterministic only if the same values are used for all peers in a peer group. Note also that setting bgpRmEntUpdateGroups to 'true' limits the use of ORF (Outbound Route Filtering) for the peers in an update group. In particular, DC-BGP will continue to send outbound route filters to peers, but received filters are ignored. In addition, when bgpRmEntUpdateGroups is 'true', the value of bgpPeerConfigPeergr for a peer can only be changed while the peer MIB row admin status is 'down'. 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.0.1)

None (see information above)

Current Registration Authority (inferred from ancestor 1.2.826.0)

Telecoms CSC

Siblings (59)

OIDNameDirect childrenDescendantsDescription
1.2.826.0.1.1578918.5.65.1.2.1.1.51 bgpRmEntPeakNumAroRoutes00
1.2.826.0.1.1578918.5.65.1.2.1.1.52 bgpRmEntClearStats00
1.2.826.0.1.1578918.5.65.1.2.1.1.53 bgpRmEntFastExtFallover00
1.2.826.0.1.1578918.5.65.1.2.1.1.54 bgpRmEntRemainDelayTime00
1.2.826.0.1.1578918.5.65.1.2.1.1.55 bgpRmEntPathAttrs00
1.2.826.0.1.1578918.5.65.1.2.1.1.56 bgpRmEntAggSplitHorizon00
1.2.826.0.1.1578918.5.65.1.2.1.1.57 bgpRmEntAggAdvSuppr00
1.2.826.0.1.1578918.5.65.1.2.1.1.59 bgpRmEntPhase3DelayTime00
1.2.826.0.1.1578918.5.65.1.2.1.1.60 bgpRmEntTrapOperState00