Comments for Webscaling

Comment on MySQL through Netscalers not a good idea without connection pool. by admin

admin — Fri, 06 Aug 2010 17:31:48 +0000

Good point.

Comment on MySQL through Netscalers not a good idea without connection pool. by Citrix_Jiayuan

Citrix_Jiayuan — Fri, 06 Aug 2010 09:57:10 +0000

Because netscaler does SYN flood protection on TCP virtual server, so it is normal that you sometimes would have this issue.

If you setup a type “Any” virtual server instead of TCP virtual server in netscaler, you should not have this problem anymore then.

Comment on Netscaler implementation tips, Part 1 by wtf

wtf — Tue, 13 Jul 2010 19:52:32 +0000

Sorry, didn’t mean to sound snarky.

Comment on Netscaler implementation tips, Part 1 by admin

admin — Tue, 13 Jul 2010 14:01:22 +0000

Oops. 2002. Corrected, thanks

Comment on Netscaler implementation tips, Part 1 by wtf

wtf — Mon, 12 Jul 2010 22:23:09 +0000

You’ve been using Netscalers since 1992? Really?

6 years before the company was founded?

Comment on MySQL through Netscalers not a good idea without connection pool. by admin

admin — Thu, 08 Jul 2010 16:50:03 +0000

True enough. Syn cookies are not unique to netscalers – although most other OS’s have a threshold of unacknowledged Syn’s before they start relying on cookies.
So the statement should really be “terminated on a device that did not use a SYN cookie to manage this specific connection.”
Thanks for the clarification.

Comment on MySQL through Netscalers not a good idea without connection pool. by Greg

Greg — Thu, 08 Jul 2010 16:40:12 +0000

This is actually not a “NetScaler’ problem, it is a problem with any server using SYN Cookies. In this case the NetScaler is terminating the client request, so it is a server.

The statement “TCP will retransmit if the connection is terminated on any other device except the NetScaler” is not accurate. What would be accurate is “TCP will retransmit if the connection is terminated on any device not implementing SYN Cookies, such as the NetScaler”.

Comment on Netscaler implementation tips, Part 1 by admin

admin — Sat, 19 Jun 2010 19:46:49 +0000

Poppy: certainly. You’d have a load balancing virtual server (say lb1) that points to http://www.somewebsite.com, another that points to wherever the content should come from for the rest of http://www.mydomain.com (say lb2), and a rule that says:
add cs policy ToSomeWeb -url /SomeWebSite/
then:
bind cs vserver mydomain lb1 -policyName ToSomeWeb
bind cs vserver mydomain lb2

If it doesn’t match the url rule, it will go to lb2. If it does, it will go to lb1.

Comment on Netscaler implementation tips, Part 1 by poppy

poppy — Wed, 16 Jun 2010 22:34:09 +0000

Is it possible to configure content switching to point a subfolder to an external web site? When users go to http://www.mydomain.com/SomeWebSite, it will display web site content from http://www.someWebSite.com but not changing the URL address on user’s browser.

Comment on Netscaler implementation tips, Part 3 by admin

admin — Mon, 06 Jul 2009 18:47:24 +0000

If the netscaler crashes, there should be some indications of the failure once you drop to the shell, in:
/var/log/messages
kernel dumps in:
/var/crash

Of course, most of the reasons will not mean much except to Netscaler support.
e.g.
/flash/ns-8.0-55.3: kernel trap 28 with interrupts disabled at eip=305f6810
ns /flash/ns-8.0-55.3: Fatal trap 28: machine check trap while in kernel mode

So the best recourse is usually to open a case, or just upgrade to most recent GD release (as that is usually Netscaler support’s recommendation.)
If you think you have a new bug, then open a case, certainly.