http://www.mnscug.org/blogs/jeff-carreon/364-posh-for-quickly-applying-bandwidth-limitation-on-sup-servers

might help in the short term..

From: [email protected] [mailto:[email protected]] On 
Behalf Of Sean Pomeroy
Sent: 12 August 2015 18:16
To: [email protected]
Subject: Re: [mssms] WSUS Traffic After Sync

We have that issue whenever we bring a boundary/location into the SUP fold.
We are assuming because all clients reach out to scan for updates within a 
short time of each other.

Have you tried deploying the new update agent to see if it fixes it?

On Wed, Aug 12, 2015 at 1:07 PM Jason Wallace 
<[email protected]<mailto:[email protected]>> wrote:
Do you scan clients very frequently?

Certainly there are a number of reports of high app pool. Try setting the App 
Pool to zero and at the very very least set it to 8GB.

You may need to set the WSUS server to restrict inbound sessions to 30 while 
you ride out the storm.  Certainly seriously consider having multiple SUPs in 
your sites.

Have you recently deployed updates to the WSUS servers or WUA updates to the 
estate?


On 12 Aug 2015, at 18:57, Barnes,Chris 
<[email protected]<mailto:[email protected]>> wrote:
Hey guys – Anyone else seen any issues with a massive amount of traffic to the 
SUPs after a sync in the last 24 hours?

It crushed our WAN pipes, and crushed the CPUs on our routers.

I heard someone at another company report 20MB per client connecting back to 
the SUP.

I turned the SUP back on last night, and the WSUS IIS App Pool kept on crashing.

Single Primary, a couple of secondaries. Single WSUS on the primary, roughly 
12K clients connecting to it.




Chris Barnes
Senior Technical Specialist
Penske Automotive Group
(248) 648-2528 Direct
(248) 767-4415 Mobile

[Penske75new]


________________________________

Penske Automotive Group and its affiliates will never sell or rent your email 
address in violation of applicable law. This email and any files transmitted 
with it are confidential and intended solely for use of the individual or 
entity to whom they are addressed. Please delete all copies if you are not the 
intended recipient.


Reply via email to