BITS not throttling transfers correctly, help! (Full Version)

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager



Message

mhughes2 -> BITS not throttling transfers correctly, help! (7/3/2008 10:09:02 AM)

Under my main site server, under computer client agent properties is the only spot where BITS throttling is set, correct?
For some reason, anytime I distribute software from my secondary DPs to locations/clients that fall under their boundries, the BITS throttling is ignored and goes full blast. The DPs have BITS/Webdav extensions installed on IIS. Is there something else I need to be checking?

EDIT: I know that there are group policies regarding BITS in place for WSUS that our administrator set; could these be having an affect?
EDIT2: I just checked out Netflow logs and it definitely looks like throttling is working correctly when I distribute from my primary site server. It's only from my secondary DPs. What gives?



wbracken -> RE: BITS not throttling transfers correctly, help! (7/3/2008 2:02:29 PM)

(Not having done enough research on BITS 2.5, I cant say for sure if any of the following statements still hold true, these are based on what I know of Bits 2.0)..

Remember that BITS is only LAN aware..  Meaning if it sees a 100MB connection to a Cisco switch it assumes it has a full 100MB connection and uses that as the baseline.  Now if that switch is then connected to a 256K link you will indeed utilize that majority of the bandwidth since the BITS client is not aware that at somepoint in the route back to the DP there is a slower connection.

Again, i dont believe this has changed in BITS 2.5 but I cant say for sure...



asaxton -> RE: BITS not throttling transfers correctly, help! (7/16/2008 9:17:50 AM)

Under your primary site, site settings, addresses you will find an address listings for all of your secondary sites.  Open the properties of this to set the schedule and the rate limits.  Then under all of the secondary site listings, site settings, addresses you will find the address entry for the primary.  You must set the schedule and rate limits here also.

If you are only using DP and BDP's for remote sites with small bandwidth pipes, it will be best to set these sites up as a management point (within secondary site) if they have the equipment for it.  This allows for better management of the bandwidth.  For example, we have over 170 remote sites.  Most of these only have 512kbps pipes.  We had huge issues with the remote sites when we only had them designated as DP's and BDP's.  Especially at the larger offices.  Once we moved to secondary sites with a management point, all of our troubles have started to go away.  The management point throttles ALL communications between the sites.  This includes the clients hardware and software reporting. 



asaxton -> RE: BITS not throttling transfers correctly, help! (7/23/2008 8:49:27 AM)

I forgot to mention that on the secondary site you will need to set the scheduling for the send back to the primary.



rjarrett -> RE: BITS not throttling transfers correctly, help! (7/24/2008 3:11:44 PM)

To expand on what WBraken said, remember that BITS throttling is a CLIENT side feature only.  BITS checks YOUR activity with the LAN.  It does not monitor the LAN for ITS workload.  In other words, if you are doing nothing with your LAN connection (e.g. downloading Sports Illustrated pictures of Danica Patrick) then it has no need to throttle.  Its job is to make the "user experience" better when multiple demands are being made to the network.

Thus, when your demands are low, the throttling is high.  Regardless of how overloaded your network may be.






Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.203125