Understanding the number of subnets reported | 2pint Knowledge Base

Understanding the number of subnets reported

Applies to

BranchCache Reporting

Symptoms

The number of Subnets in BranchCache Reports has unexpectedly increased from the same Report that was run only a few days before.

In an actual customer environment, a Report showed 238 Subnets and one day and 258 only two days later. This environment had 117 ‘IP address range’ boundaries and 29 boundary groups configured in SCCM.

Boundaries in SCCM had not been changed.

Cause

The first thing to highlight is that BranchCache Reporting does not recognize SCCM boundaries.

Each SCCM client reports its IP configuration to the site server through hardware inventory. This requires that the client is within an SCCM boundary.

Complexity arises through Network Discovery which means that SCCM actually knows of a lot more subnets than just the ones covered by boundaries. This information is stored in the SCCM database.

The BranchCache Reporting data is drawn from the SCCM database and therefore the Reports reflect the entire network topology not limited by SCCM boundaries.

Further to the above, boundaries are not limited to Subnet or IP address range. You could have a single AD site boundary to cover an entire enterprise but have 200 subnets that are bound to that AD site.

Solution

BranchCache and 2Pint’s reporting tools should be considered separately from your SCCM infrastructure. BranchCache is simply a tool used to improve the distribution efficiency of SCCM content without regard to the SCCM infrastructure.