Application Delivery (ADX)

Reply
N/A
Posts: 1
Registered: ‎04-30-2012

Windows 2008 R2 RDP Hosts - Fail Healthchecks


Hello all,

We currently run a group of Windows 2003 Servers for RDP access with no problems.  We recently tried to add a pair of 2008 R2 Servers under a separate VIP.  The "server real" definitions seem to work, however when we bind the servers to the VIP they alternate between "Acitve" and "Failed" every 30 seconds or so and will not function correctly.   Are there any known issues with 2008 R2 server load balancing?  Do we perhaps need to upgrade the OS/firmware?  Please advise.

Thanks .. DS

System Version: 12.1.00bT403

Brocadian
Posts: 70
Registered: ‎03-14-2009

Re: Windows 2008 R2 RDP Hosts - Fail Healthchecks

Hi DS,

yes, there is something special with W2k8.

AFAIR both Windows7 and 2008 R2 will not respond even icmp. And both has built in syn-cookie feature which can’ be disabled even with registry or something.

If you do L4 or L7 health check, you will see very strange behavior for RDP SLB.

'First did you have the "server no-fast-bringup" configured? This eliminates the HC flapping.

For HC you have to use binary Health Checks. Here is an example from a collegue that one of my customers is using:

server real t1 10.9.104.200

no-l3-check

port 13389

port 13389 content-check-carray m1

port 13389 content-check-carray send "0x03,0x00,0x00,0x1e,0x19,0xe0,0x00,0x00,0x00,0x00,0x00,0x43,0x6f,0x6f,0x6b,0x69,0x65,0x3a,0x20,0x6d,0x73,0x74,0x73,0x68,0x61,0x73,0x68,0x3d,0x0d,0x0a"

port 13389 keepalive

port 3389

port 3389 no-health-check

!

server real t2 10.9.104.150

no-l3-check

port 13389

port 13389 content-check-carray m1

port 13389 content-check-carray send "0x03,0x00,0x00,0x1e,0x19,0xe0,0x00,0x00,0x00,0x00,0x00,0x43,0x6f,0x6f,0x6b,0x69,0x65,0x3a,0x20,0x6d,0x73,0x74,0x73,0x68,0x61,0x73,0x68,0x3d,0x0d,0x0a"

port 13389 keepalive

port 3389

port 3389 no-health-check

!

!

server virtual test 10.9.104.55

port 13389

port 13389 use-alias-port-state

port 3389

port 23389 disable

bind 3389 t1 13389 real-port 3389 t2 13389 real-port 3389

bind 23389 t2 3389 t1 3389

I would recommend the 12.3.01 release train.


Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.