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 bgpPeergrUpdateGroup 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 bgpPeergrUpdateGroup 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 bgpPeergrUpdateGroup is 'true', the value of bgpPeerConfigPeergr for a peer can only be changed while the peer MIB row admin status is 'down'. Similarly, when bgpPeergrUpdateGroup is 'true', the value of bgpPeerRangeConfigPeergr for a peer range can only be changed while the peer range MIB row admin status is 'down'. This field can only be changed when the Admin Status is down.