Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NLB Affinity after drain single TCPIP port on host

Status
Not open for further replies.

Dubi123

Programmer
Joined
Apr 14, 2003
Messages
82
Location
HR
I use W2K Advanced Servers in NLB.

User can use several ports in range on all particular member hosts with single affinity.

Now, if I drain particular port on one member host where client is currently connected with simultaneous connections using few ports, and client try to connect to NLB with same port I have just drained with wlbs drain again will it
a) disconnect remaining active connections and establish new connection on new NLB member where drain has not been activated?
b) refuse to connect to new NLB member because it has single affinity and remaining active TCPIP connections on host member where I activate drain for particular port (NOT ALL ports).
c) use both hosts (but than what single affinity mean?)
d) something else?

When one read NLB tutorials all looks simple, but can't resolve this from anything I have read till now.

Also wlbs drainstop is supposed to work on all NLB member hosts at same time, but what with eg. wlbs drain 123, will it drain port 123 just from particular host, or from all member hosts.

This may help resolve previous question.

Regards

Dubi






 
After I formulated question in writting, things get more clear to me. Client should remain sticked to host with single affinity until particular host is put out of NLB with wlbs stop or wlbs drainstop (this commands should influence particular host).

I am out of office now (weekend) to try it, but after wlbs drain <port> from defined range in port rules, that port should remain inactive across all hosts because of single affinity until host where current client affinity resides get out of NLB with wlbs stop or wlbs drainstop and get in again with wlbs start or alternatively enabling <port> again without getting out and in with particular host from/to NLB.

Yet, it seems that if there are many clients connected with affinity to particular host and one strarts wlbs drainstop on that host, once disconnected these clients can't connect to NLB again, because of affinity, until last client connection is drained and host get out of NLB (or "cycled" out/in). This could be potentially anoying as drainstop could last for minutes and more, yet disconnected clients can't use any host in NLB (because of still valid affinity on draining host till final wlbs stop).

Will try all this after weekend.

Regards

Dubi



 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top