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.