Hi Zrb,
From what I understand you want a 2 node NLB cluster to cluster IIS, and
you want all the traffic to go to one node unless if fails then you want
the traffic to go to the second node.
This can be configured, but it should be noted that unlike cluster service
the 'passive" node will not move active connections back to the 'primary'
node when it comes back online. It will continue to service all the traffic
it is handling, any new requests that arrive when the 'primary' node comes
back online will however go to it. As connections are closed they will
leave the 'passive' node as well.
There are 2 ways to configure this through the "Port Rules" on the
"Filtering mode" options. The first way is to use the "Multiple host"
settings "Load weight" to an unequal load. Remove the check mark for
"Equal" and set the load number on the 'primary' node to 100, on the'
passive' node set the "Load weight" to 0.
The second way to do this is to set the "Filtering Mode" to "Single host"
you then set the "Handling priority" to 1 on the host that is to be
'primary' and 2 on the node that is to be 'secondary'. This causes the node
with the highest priority that is available to take any new requests.
Network Load Balancing does not restart the application on failover. It
assumes that an instance of the application is running on each host in the
cluster. This also allows you to load balance several different services on
the nodes that use different ports and set a primary node for each
application.
For Network Load Balancing to provide single-server failover support for a
specific application, the files that the application uses must be
simultaneously accessible to all hosts that run the application. These
files normally reside on a back-end file server. Some applications require
that these files be continuously open exclusively by one instance of the
group; in a Network Load Balancing cluster, you cannot have two instances
of a single file open for writing. These failover issues are addressed by
server clusters, which run the Cluster service.
Other applications open files only on client request. For these
applications, providing single-server failover support in a Network Load
Balancing cluster works well. Again, the files must be visible to all
cluster hosts. You can accomplish this by placing the files on a back-end
file server or by replicating them across the Network Load Balancing
cluster.
There are two alternatives for configuring the port rules for single-server
failover support:
* Use no port rules. All the traffic goes to the host with the highest
priority (the Host Priority ID with the lowest value). If that host fails,
all the traffic switches to the host with the next-highest priority.
* For each application for which you're configuring single-server failover
support, create a different port rule for the application's port range, in
which:
* Filtering Mode is set to Single.
* Handling priorities are set according to the desired failover priority
across the cluster hosts.
* This option overrides the Host Priority IDs with handling priorities for
each application's port range. With this configuration, you can run two
single-server applications on separate hosts and fail in opposite
directions.
__
Curtis Koenig
Windows 2000 MCSA,MCSE
Security MCSA,MCSE
Microsoft Clutering Technologies Support
This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit. Thanks!
--------------------
| >From: (e-mail address removed) (zrb)
| >Newsgroups: microsoft.public.win2000.advanced_server
| >Subject: NLB, failover and failback
| >Date: 23 Jul 2003 15:56:06 -0700
| >Organization:
http://groups.google.com/
| >Lines: 16
| >Message-ID: <
[email protected]>
| >NNTP-Posting-Host: 64.94.157.1
| >Content-Type: text/plain; charset=ISO-8859-1
| >Content-Transfer-Encoding: 8bit
| >X-Trace: posting.google.com 1059000966 8640 127.0.0.1 (23 Jul 2003
22:56:06 GMT)
| >X-Complaints-To: (e-mail address removed)
| >NNTP-Posting-Date: 23 Jul 2003 22:56:06 GMT
| >Path:
cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onlin
e.de!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!sn-xit-03!sn-xit-06!sn-
xit-08!sn-xit-09!supernews.com!postnews1.google.com!not-for-mail
| >Xref: cpmsftngxa06.phx.gbl microsoft.public.win2000.advanced_server:9796
| >X-Tomcat-NG: microsoft.public.win2000.advanced_server
| >
| >Hi,
| >
| > I am trying to configure a 2 node NLB cluster for active/passive
| >operation of IIS.
| >
| > 1) I have two machines M0 and M1.
| > 2) I want all traffic to go to M0 until it fails.
| > 3) I want all traffic to go to M1 if M0 fails.
| > 4) Even if M0 comes back online, all traffic should go to M1 only.
| >
| > Is there a way to do this using NLB. I know this is easy with
| >Server Clusters, but for cost reasons I do not want to do that.
| >
| >Regards
| >
| >zrb
| >
