SCCM Boundaries - IP Subnets and Subnet Masks

Hi All,
1st Question:
When it comes to SCCM Boundaries and entering in IP Subnets with their Subnet Masks is pretty simple until some time down the road when you can't remember what Subnet Mask you entered in.  It doesn't display the subnet mask when you go back into the properties of an IP Subnet.  It's gone..  I did create a SQL report today and would like to see if some of you report gurus think this is the correct report to use or if you have a better one. Here is the code: (I Know I don't need the NAC.)
 
select
NAC.DNSHostName0,
NAC.IPAddress0,
NAC.IPSubnet0,
NAC.DefaultIPGateway0
from
dbo.v_GS_NETWORK_ADAPTER_CONFIGUR NAC

where
NAC.DNSHostName0 <> 'NULL' and NAC.DefaultIPGateway0 <> 'NULL'
OrderBy NAC.IPAddress0
 
the IpSubnet0 returns the IP Subnet mask I believe. This report returns all the systems I have in our organization. Sort of messy.  I would rather just report on the IP Subnets I have entered in the SCCM Boundaries.
 
2nd Question:?
?I have noticed inside the hman.log file on the server that when you add an IP Subnet to sccm, it seems to keep trying to add IP Subnets that I have entered in a long time ago.  There is only a handful of these IP Subnets that are showing up. The pcs with these boundaries are receiving sccm patches and packages. Is the fix for this is to remove it wait until inside the hman.log file says it has removed the ip subnet and then re add it?  I haven't tried that yet.
?
?Thanks
?Jerry

This is because IP Subnets don't use subnet masks, they use Subnet IDs -- they initially use the subnet mask to calculate the subnet ID after which time it is no longer needed and thus never stored.
 
Don't use them, they are evil! Convert all of them to IP Address Ranges and never look back.

Maybe in CM 2012.

IMO, there is no reason why to wait for CM12. IP Subnet and AD sites are evil. They will give you grief and they should never used.  Changing IP subnet to IP Range is one of the first recommendation that I always make to new clients.