Boundary Groups and Peer Cache

When you create a boundary group the option “Allow peer downloads in this boundary group” is enabled by default.  You might be in for a surprise when you start doing peer cache testing in some boundary groups and find computers from all over the hierarchy are trying to get content from your new superpeer(s).    Use the following SQL query and the flag values below to make sure your BG options are configured correctly.  I would typically recommend leaving the top option enabled in the BG options but also enable the second option to only use peers in the same subnet.  If that boundary group has a local distribution point then the third option might also be helpful.

SELECT Name, Description, DefaultSiteCode, Flags

FROM BoundaryGroup

where flags is not NULL

and some of the relevant flag values are:

Flag 0: the top option “allow peer downloads” is enabled in the BG option tab

Flag 1: no options enabled

Flag 2: the top option and the “during peer downloads only use peers in the same subnet” options are selected