Use the following procedure to stop and start handling Network Load Balancing (NLB) cluster traffic. You might need to stop and restart NLB cluster traffic when:
- Undertaking troubleshooting or maintenance
- Dealing with application issues on one or
more hosts in the cluster.
- Scaling down the cluster because the traffic
no longer requires the current number of hosts.
You can also perform the task described in this procedure by using Windows PowerShell. For more information about using Windows PowerShell for NLB clusters, see http://go.microsoft.com/fwlink/?LinkId=140180.
|To stop or start handling Network Load Balancing cluster traffic by using the Windows interface|
To open NLB Manager, click Start, click Administrative Tools, and then click Network Load Balancing Manager. You can also open NLB Manager by typing Nlbmgr at a command prompt.
If NLB Manager does not list the cluster, connect to the cluster.
If you want to stop cluster operations on all cluster hosts, right-click the cluster, point to Control Hosts, and then click Stop.
If you want to stop the cluster service on only a particular host, right-click the host, point to Control Host, and then click Stop.
If you want to start cluster operations on all cluster hosts, right-click the cluster, point to Control Hosts, and then click Start.
If you want to start the cluster service on only a particular host, right-click the host, point to Control Host, and then click Start.
- When you are using Network Load Balancing
(NLB) Manager, you must be a member of the Administrators group on
the host that you are configuring, or you must have been delegated
the appropriate authority. If you are configuring a cluster or host
by running NLB Manager from a computer that is not part of the
cluster, you do not have to be a member of the Administrators group
on that computer.
- When you stop handling NLB cluster traffic,
client connections that are already in progress are interrupted. To
avoid interrupting active connections, consider using the
drainstop cluster-control command (instead of the
stop command), which allows the host to continue servicing
active connections but disables all new traffic to that host.
- You can restart cluster operations after
stopping or suspending them. When you click Start on the
cluster or host that you want to restart, it restarts cluster
operations, but it does not enable the use of cluster-control
commands, which have been disabled by a previous suspend