Description: When non-persistent AROs are in use, DC-BGP breaks up the processing and reduces the peak occupancy requirements by splitting the Adj-RIB-Outs into a number of processing groups. The number of AROs in a group is controlled by bgpRmEntNumArosInGroup. This field is used to specify the maximum number of such groups permitted to contain fully populated AROs.

Each group is processed to completion including the transmission of required UPDATEs to peers. Processing to completion allows the routes in a group to be freed before moving onto the next group thus limiting peak occupancy. A group is blocked if one or more of its member Adj-RIB-Outs are subject to flow control. If bgpRmEntMaxActiveAroGroups are blocked then DC-BGP will itself be blocked until a group is unblocked. Setting a high value for the number of groups decreases the chance of DC-BGP being blocked but increases peak occupancy.

This field can only be changed when the Admin Status is down and is only applicable if bgpRmEntNonPersistentAros is set to TRUE.