C
Curtis Koenig [MSFT]
Hi Mike,
The wlbs drainstop command does not close the connections that are already
on the box only the stop command does this. The drainstop command causes
the NLB to not accept any new connections that arrive into the cluster.
However the node continues to service any connections that are already
balanced to it. Essentially the box waits for any connected clients to
terminate their connections.
303768 HOW TO: Perform Basic Network Load Balancing Procedures in Windows
2000
http://support.microsoft.com/?id=303768
Excerpt:
When you use the wlbs stop command, client computer connections that are
already in progress may be interrupted. To avoid interrupting active
connections, use the drainstop cluster control command.
__
Curtis Koenig
Microsoft Clutering Technologies Support
MCSA, MCSAS,MCSE, MCSES
This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit. Thanks!
--------------------
| >Content-Class: urn:content-classes:message
| >From: "Ed M" <[email protected]>
| >Sender: "Ed M" <[email protected]>
| >References: <elbSrZ1iCHA.2256@tkmsftngp12>
| >Subject: NLB - Drainstop problem
| >Date: Thu, 14 Nov 2002 13:55:01 -0800
| >Lines: 34
| >Message-ID: <03bb01c28c28$7b76f810$89f82ecf@TK2MSFTNGXA01>
| >MIME-Version: 1.0
| >Content-Type: text/plain;
| > charset="iso-8859-1"
| >Content-Transfer-Encoding: 7bit
| >X-Newsreader: Microsoft CDO for Windows 2000
| >X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| >Thread-Index: AcKMKHt2aRkPVmCiS2C5zOb1/C6fww==
| >Newsgroups: microsoft.public.win2000.advanced_server
| >NNTP-Posting-Host: TK2MSFTNGXA01 10.40.1.47
| >Path: cpmsftngxa08!cpmsftngxa09
| >Xref: cpmsftngxa08 microsoft.public.win2000.advanced_server:34254
| >X-Tomcat-NG: microsoft.public.win2000.advanced_server
| >
| >Doing a WLBS drain stop on that box kills all concurrent
| >connections to that service imediately. If you are going
| >to do this, you are better off rebooting the machine.
| >You can however, use the "wlbs drain all" command that
| >will not allow any "NEW" connections, but will not
| >disconnect the current users. One you have performed
| >your task, stop and start the service, reboot the
| >machine, or use the "wlbs enable all" command to re-
| >enable the the windows load balancing. To verify the
| >current users, (I use this for exchange 2000 Outlook Web
| >Access) use a perfmon counter, i.e. Web Service-->Default
| >Website-->Current Non-Anonymous users, which tells me the
| >current users that are logged on to my Exchange OWA
| >server.
| >
| >Ed M.
| >>-----Original Message-----
| >>Hi,
| >>
| >>I have a Windows 2000 NLB system.
| >>I issued the command wlbs drainstop on one of the nodes.
| >The node is always
| >>in the draining stage and never stop. Any idea what
| >cause this? Is there any
| >>way to view the connections to the node?
| >>Thanks for your help in advance.
| >>
| >>
| >>
| >>
| >>
| >>
| >>.
| >>
| >
The wlbs drainstop command does not close the connections that are already
on the box only the stop command does this. The drainstop command causes
the NLB to not accept any new connections that arrive into the cluster.
However the node continues to service any connections that are already
balanced to it. Essentially the box waits for any connected clients to
terminate their connections.
303768 HOW TO: Perform Basic Network Load Balancing Procedures in Windows
2000
http://support.microsoft.com/?id=303768
Excerpt:
When you use the wlbs stop command, client computer connections that are
already in progress may be interrupted. To avoid interrupting active
connections, use the drainstop cluster control command.
__
Curtis Koenig
Microsoft Clutering Technologies Support
MCSA, MCSAS,MCSE, MCSES
This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit. Thanks!
--------------------
| >Content-Class: urn:content-classes:message
| >From: "Ed M" <[email protected]>
| >Sender: "Ed M" <[email protected]>
| >References: <elbSrZ1iCHA.2256@tkmsftngp12>
| >Subject: NLB - Drainstop problem
| >Date: Thu, 14 Nov 2002 13:55:01 -0800
| >Lines: 34
| >Message-ID: <03bb01c28c28$7b76f810$89f82ecf@TK2MSFTNGXA01>
| >MIME-Version: 1.0
| >Content-Type: text/plain;
| > charset="iso-8859-1"
| >Content-Transfer-Encoding: 7bit
| >X-Newsreader: Microsoft CDO for Windows 2000
| >X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| >Thread-Index: AcKMKHt2aRkPVmCiS2C5zOb1/C6fww==
| >Newsgroups: microsoft.public.win2000.advanced_server
| >NNTP-Posting-Host: TK2MSFTNGXA01 10.40.1.47
| >Path: cpmsftngxa08!cpmsftngxa09
| >Xref: cpmsftngxa08 microsoft.public.win2000.advanced_server:34254
| >X-Tomcat-NG: microsoft.public.win2000.advanced_server
| >
| >Doing a WLBS drain stop on that box kills all concurrent
| >connections to that service imediately. If you are going
| >to do this, you are better off rebooting the machine.
| >You can however, use the "wlbs drain all" command that
| >will not allow any "NEW" connections, but will not
| >disconnect the current users. One you have performed
| >your task, stop and start the service, reboot the
| >machine, or use the "wlbs enable all" command to re-
| >enable the the windows load balancing. To verify the
| >current users, (I use this for exchange 2000 Outlook Web
| >Access) use a perfmon counter, i.e. Web Service-->Default
| >Website-->Current Non-Anonymous users, which tells me the
| >current users that are logged on to my Exchange OWA
| >server.
| >
| >Ed M.
| >>-----Original Message-----
| >>Hi,
| >>
| >>I have a Windows 2000 NLB system.
| >>I issued the command wlbs drainstop on one of the nodes.
| >The node is always
| >>in the draining stage and never stop. Any idea what
| >cause this? Is there any
| >>way to view the connections to the node?
| >>Thanks for your help in advance.
| >>
| >>
| >>
| >>
| >>
| >>
| >>.
| >>
| >