<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Bi-Directional Affinity in ISA Server</title><link>http://blogs.technet.com/isablog/archive/2008/03/12/bi-directional-affinity-in-isa-server.aspx</link><description>The reason for having a network load balancing (NLB) Bi-Directional Affinity (BDA) feature in ISA Server is that it guarantees that traffic is handled in both directions by the same array server. This is very important and required if you have a Route</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: post</title><link>http://blogs.technet.com/isablog/archive/2008/03/12/bi-directional-affinity-in-isa-server.aspx#2992006</link><pubDate>Wed, 12 Mar 2008 21:15:14 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2992006</guid><dc:creator>gazanga</dc:creator><description>&lt;p&gt;I've not seen this occur, but I have wondered about this in production. &amp;nbsp;With most enterprise-class load-balancers, there are ways to bind the session throughout the infrastructure to a particular server. &amp;nbsp;To maintain that session affinity, is pretty crucial when you are working in tricky web-app environments. &amp;nbsp;For example, I work with a bank whose online banking applications require session affinity to assure that one users session doesn't switch over to another users session and suddenly, user a sees user b's bank info. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;A very large developer of switches and routers have had a similar problem with this recently. &amp;nbsp;Their large enterprise-class switch had two cpu's that would load-balance applications. &amp;nbsp;However while each cpu maintained a tcp-port session and usage table, the two cpu's did not. &amp;nbsp;Therefore, if request Alpha came in and was directed to server Bravo on cpu 1 redirecting traffic to port 5000, and then the reply came back through and hit cpu 2, then another request came in to cpu 2 and was told to hit port 5000, a tcp out of sequence error would occur and both sessions would be reset. &amp;nbsp;It wasn't a massive outage, as it only occured every now and then. &amp;nbsp;Session affinity can help resolve this. &amp;nbsp;That and using ISA for load-balancing versus hardware which can't easily address these issues.&lt;/p&gt;</description></item><item><title>Software a dokumenty ke stažení - duben 2008</title><link>http://blogs.technet.com/isablog/archive/2008/03/12/bi-directional-affinity-in-isa-server.aspx#3036418</link><pubDate>Mon, 14 Apr 2008 10:48:56 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3036418</guid><dc:creator>TechNet Blog CZ/SK</dc:creator><description>&lt;p&gt;SECURITY Security Tip of the Month: Initial Considerations for Secure Deployment &lt;a rel="nofollow" target="_new" href="http://go.microsoft.com/?linkid=8514049"&gt;http://go.microsoft.com/?linkid=8514049&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>