Changes

Jump to: navigation, search
Configuring Port and Client Affinity
== Configuring Port and Client Affinity ==
 
Network traffic arrives on one of a number of different ports (for example FTP traffic uses ports 20 and 21 while HTTP traffic uses port 80). Network Load Balancing may be configured on a port by port basis or range of ports. For each port three options are available to control the forwarding of the traffic:
 
* '''Single Host''' - Traffic to the designated port is forward to a singe node in the cluster.
 
* '''Multiple Hosts''' - Traffic to the designated port is distributed between the nodes in the cluster.
 
* '''Disabled''' - No filtering is performed.
 
Many client/server communications take place within a session. As such the server application will typically maintain some form of session sate during the client server transaction. Whilst this is not a problem in the case of a ''Single Host'' configuration described above, clearly problems may arise if a client is diverted to a different cluster node partway through a session since the new server will not have access to the session state. Windows Server 2008 Network Load Balancing addresses this issue by providing a number of ''client affinity'' configuration options. Client affinity involves the tracking of both destination port and source IP address information to optionally ensure that all traffic to a specific port from a client is directed to the same server in the cluster. The available Client affinity settings are as follows:
 
* '''Single''' - Requests from a single source IP address are directed to the same cluster node.
 
* '''Network''' - Requests originating from within the same Class C network address range are directed to the same cluster node.
 
* '''None''' - No client affinity. Requests are directed to nodes regardless of previous assignments.
 
== Configuring a Network Load Balanced Cluster ==

Navigation menu