ProxySG TCP Regulations

I need a solution

Hi, our current SG300-10’s are frequently experiencing tcp regulations due to memory pressures. Not sure when it started to occur but it somehow the change we only had was when we upgraded to 6.6 from 6.5.9.x to be able to use BCIS. Well, this does not affect the operations unless the regulation remains ON for quite some time which could take up to an hour or more somtimes. Question is how can we forcefully stop this TCP regulation? Funny thing is we only experience this with SG300-10s, we have some SG300-5 and S200s but none behaves like that.

-Rey

0

Related:

ITM Service Console not consistent

We have a zOS environment with agents and RTEMS on zOS.
We have an ITM Service Console that is not consistent:
the first time you access it you see the RTEMS service point and nothing more…Then you refresh the browser page and only the service point for another zOS agent is shown.
We have reserved port 1920 in our TCPIP profile member in the following way:

1920 TCP DB2STC SHAREPORT BIND a.b.c.d
1920 TCP NVSTC SHAREPORT BIND e.f.g.h
1920 TCP HTEMS1 SHAREPORT
1920 TCP HTEMS SHAREPORT
1920 TCP IMSSTC SHAREPORT BIND i.j.k.l
1920 TCP OTEMS BIND x.y.z.w
1920 TCP OT1* BIND m.n.o.p

How can we resolve this issue?

Related:

TCP Window size increases drastically and sender don’t send until the receive buffer is not empty

I have a download stream over TCP in an application (running on Win2k12).
The problem is that the connection gets closed by the sender because it times out.

I used wireshark to see what happens on 2 different servers (on one server it works ok, on the other it gets timed out).
I have noticed the same behavior on both:
When the download starts, everything seems ok, window size is 64k and remains the same for some time, segments get acknowledged. Then at some point the window size starts to decrease until it is 0. (As far as I know this is ok, the receiver cannot keep up with the sender.) However, there is no ACK or Window update message from the receiver until the entire buffer is read by the app, then a Window update advertises 64k window size again. Then it starts over again. Window size decreases until zero.
This does not seem right for me. As the application reads from the buffer it should have free space in it and a Window update should be sent, so the sender can send the next segment.

The other thing I don’t understand is the behavior on the failing server. This server advertises larger and larger window sizes in every such cycle, in the last cycle before the timeout the window size was ~800 000. The timeout occures because the buffer is not emptied quick enough. But I have no clue why is the window size increasing on this server? Is there a setting on the server to prevent this?

Are my assumptions right, or I misunderstood something about the TCP protocol?
Any ideas to solve this issue is appreciated.

Thanks.

Related: