whenever I set the BDAReverseHash to 1 for the internal cluster, it's being reset to 0 after the wlbs reload command. (I tried modifying the setting through regedit as well as with a script, no difference)
I did all initial NLB configuration through the ISA server Management Console (Enterprise Edition). Then I copied the script example from your article and changed the VIP and the BDATeamID.
I'm not familiar with WMI scripts, but I assumed it's a normal VBS script?
I'm not familiar enough with NLB yet -- but have this question.
I've read that NLB can be used to maintain High Availability for INCOMING traffic. What about for OUTBOUND traffic? If one of our ISA 2004 EE servers goes down, we want the other ISA 2004 EE server in the array to take over.
NLB Cluster 129.83.31.126 : Inconsistent bi-directional affinity (BDA) teaming configuration detected on host 3. The team in which this cluster participates will be marked inactive and this cluster will remain in the converging state until consistent teaming configuration is detected.
And looks like, ISA doesn't allow any traffic once I get this error on one of the server.
I am assuming, the script Tom has provided will fix the issue, correct?
But I am not sure about applying that script, mostly due to my lack of knowledge on VBS.
If I am to apply that script ...I am not sure about some values specially ... Cluster.BDATeamId = "{12345678-9012-3456-7890-1234546890ab}"
What is BDATeamId? and how do I find the value of it?
Thanks for your help.
mikoo
< Message edited by mikoo1965 -- 3.Oct.2006 2:46:56 PM >
I've tried to set up ISA 2006 Enterprise in an NLB cluster, and I'm wondering if this BDA script is actually what's necessary to accomplish my goal.
I'm trying to make it so that requests going from the internal network (using the internal VIP) to the external network are using the external's VIP as its source address when it connects to the destination. Is it even possible?
During my last attempt, the outgoing requests were using the array member's own external ip, not the cluster's Virtual IP, as source ip.
Regards, WallOfFirePlusOne
_____________________________
I test clusters in a production environment. What? Okay! Yeah!