Winows Server 2003, NLB, Error: WLBS 17 + 21

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



I have 5 Windows 2003 WebEdition Server
The IIS and some other ports of each server are loadbalanced with Windows
NLB.
The NLB is configured with 4 virtual IPs.

Every time I reboot one of the servers, an error message appears in the
eventlog of all other servers (same time)
I have to different errors:

When I reboot the server 1 (NLB priority 1) the following error is in the
eventlog at the other servers:

Event Type: Error
Event Source: WLBS
Event Category: None
Event ID: 21
User: N/A
Computer: xx
Description:
NLB Cluster x.x.x.x : Host 1 does not have the same number or type of port
rules as this host. Please check the NLB configuration on all hosts that
belong to the cluster and make sure that they all contain the same number
and type of port rules.

When I reboot one server with a NLB priority > 1 (server 2 to 4) I get the
following errors:
WLBS ID 21 (same as above) at the servers 2 to 4 (except the server which is
rebooted)
and the following error at server 1

Event Type: Error
Event Source: WLBS
Event Category: None
Event ID: 17
User: N/A
Computer: xx
Description:
NLB Cluster x.x.x.x : Duplicate host priority 1 was discovered on the
network. Please check the NLB configuration on all hosts that belong to the
cluster and make sure that they all contain unique host priorities between 1
and 32.

I verifed the NLB priorities, but the servers have the priorities from 1 to
5 (no duplicates)
I changed all priorities, result: at the first server the WLBS 17 error is
"replace" through the WLBS 21 error.
I chagend all priorities back: WLBS 17 is back again.
I watched the NLB configuration with "wlbs display", result: I have the same
number of rules at every server (watch rule examples from wlbs display
below)
I watched the NLB configuration in the registry, result I have 2 keys which
are different between the servers:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WLBS\ConfigurationHistory
at server 3, 4 and 5 a history is recorded, at 1 and 2 not??

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WLBS\Linkage
has the following keys "Bind" and "Route" but both values are empty and
only exist at server 3??

Now my questions:
- Knows someone about the error messages and how I can get rid of them?
- Knows some about the registry keys?
- Where is the duplicate NLB priority?

One further hint: I think the errors appeared the first time, after I add an
additional virtual IP to the NLB cluster
(The system was running 3-4 month without the errors, I have also created a
test environment without this errors)

The NLB is working but I hope someone can help me!

Thank you very much,
Roman

Examples of NLB Rules from server 1 and 2 from wlbs display, which shows the
same rules with different loads:
(server 3,4 and 5 have the same rules, just differnt loads ...)
Server 1:
Virtual IP addr Start End Prot Mode Load Affinity
10.6.51.71 25 25 TCP Multiple Equal N
10.6.51.71 80 80 TCP Multiple Equal N
10.6.51.71 389 389 TCP Multiple Equal N
10.6.51.71 443 443 TCP Multiple Equal N
10.6.51.72 80 443 TCP Multiple 0 S
10.6.51.72 8080 8080 TCP Multiple 0 N
10.6.51.73 80 443 TCP Multiple 0 S
10.6.51.73 16031 16031 TCP Multiple 0 S
10.6.51.74 80 80 TCP Multiple 0 N

Server 2:
Virtual IP addr Start End Prot Mode Load Affinity
10.6.51.71 25 25 TCP Multiple 0 N
10.6.51.71 80 80 TCP Multiple Equal N
10.6.51.71 389 389 TCP Multiple 0 N
10.6.51.71 443 443 TCP Multiple Equal N
10.6.51.72 80 443 TCP Multiple 0 S
10.6.51.72 8080 8080 TCP Multiple 0 N
10.6.51.73 80 443 TCP Multiple 0 S
10.6.51.73 16031 16031 TCP Multiple 0 S
10.6.51.74 80 80 TCP Multiple 0 N







.



Relevant Pages

  • Re: Routing interprocess connections between NLB cluster members
    ... MVP - Windows Server - Clustering ... Regarding your last question, the NLB machines ... The new router will be set up with static route table entries as well. ... attachment to the NLB switch. ...
    (microsoft.public.windows.server.clustering)
  • Re: Local traffic and active/standby NLB configs
    ... If I have a server failure, though, I want failover to ... Configuring NLB in single-host mode allows me to keep ... To minimize configuration ... sharing a NLB cluster address. ...
    (microsoft.public.windows.server.clustering)
  • Re: NLB Cluster - Ping fails or long time to reply from outside local subnet - SOLVED
    ... If you run the command 'wlbs query' and the node it is run on says it is converged with all of your nodes in the cluster, that basically says the NLB configuration is correct and the nodes are talking to each other. ... Windows Server 2008 Readiness Team ... Now of course when the permanent MAC is reinstated the router will get confused over the IP/MAC combination of the dedicated cluster NIC. ...
    (microsoft.public.windows.server.clustering)
  • ISA Server 2000 dual NLB on Windows 2003
    ... An Exchange 2003 Front-end / Back-end configuration. ... Front-end servers are configured with NLB and back-end clustered with MSCS. ... Now I want to publish front-end servers to the Internet with an ... ISA Server 2000 NLB cluster located in the ...
    (microsoft.public.isa.publishing)
  • ISA Server 2000 NLB question
    ... An Exchange 2003 Front-end / Back-end configuration. ... Front-end servers are configured with NLB and back-end clustered with MSCS. ... Now I want to publish front-end servers to the Internet with an ... ISA Server 2000 NLB cluster located in the ...
    (microsoft.public.isa.publishing)