Export (0) Print
Expand All

NLB Bi-Directional Affinity (BDA) Configuration

Updated: November 13, 2007

Applies To: Windows Server 2008

Bi-directional affinity creates multiple instances of Network Load Balancing (NLB) on the same host, which work in tandem to ensure that responses from published servers are routed through the appropriate ISA servers in a cluster. Bi-directional affinity is commonly used when NLB is configured with Internet Security and Acceleration (ISA) servers. If bi-directional affinity is not consistent across all NLB hosts or if NLB fails to initialize bi-directional affinity, the NLB cluster will remain in the converging state until a consistent teaming configuration is detected.

 

Events

Event ID Source Message

55

Microsoft-Windows-NLB

NLB cluster [%2]: An inconsistent teaming configuration was detected for bi-directional affinity (BDA) on host %5. BDA configuration must be identical on all cluster hosts. 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.

56

Microsoft-Windows-NLB

NLB cluster [%2]: Invalid bi-directional affinity (BDA) team ID detected. Team IDs must be a GUID of the form {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}. To add this cluster to a team, correct the team ID and run 'nlb reload' followed by 'nlb start' from the command prompt.

57

Microsoft-Windows-NLB

NLB cluster [%2]: Invalid bi-directional affinity (BDA) teaming port rules detected. Each member of a BDA team may have no more than one port rule, and its affinity must be single or class C if multiple host filtering is specified. To add this cluster to a team, correct the port rules and run 'nlb reload' followed by 'nlb start' from the command prompt.

59

Microsoft-Windows-NLB

NLB cluster [%2]: The bi-directional affinity (BDA) team which this cluster has attempted to join already has a designated master. This cluster will not join the team and will remain in the stopped state until the parameter errors are corrected and the cluster is restarted by running 'nlb reload' followed by 'nlb start'. %3 %4

60

Microsoft-Windows-NLB

NLB cluster [%2]: The bi-directional affinity (BDA) team in which this cluster participates has no designated master. The team is inactive and will remain inactive until a master for the team is designated and consistent BDA teaming configuration is detected.

62

Microsoft-Windows-NLB

NLB cluster [%2]: This cluster has left a bi-directional affinity (BDA) team in which it was the designated master. If other adapters are still participating in the team, the team will be marked inactive and will remain inactive until a master for the team is designated and consistent BDA teaming configuration is detected.

114

Microsoft-Windows-NLB

NLB cluster [%2]: NLB failed to initialize bi-directional affinity (BDA) teaming on adapter '%3'. The BDA team in which this cluster participates will be marked inactive and this cluster will remain in the converging state until this is resolved. Using Control Panel or Device Manager, disable and re-enable the network adapter before attempting to bind NLB to the adapter.

Related Management Information

NLB Host

NLB Cluster

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft