|
Node 1:
Cluster Parameters
Primary 157.231.32.211 (this is the shared IP on
adapter 2)
Subnet mask: 255.255.224.0
Full Internet name: mail.exchlab.net
network address: xxxxxxxxxxxx
Multicast Support: Enabled
Remote control: Disabled
Host Parameters
Priority (Unique host ID): 1
Initial cluster state: Active
Dedicated IP address: 157.231.32.187 (this is the
unique IP on adapter 1 - could this be the issue?)
Subnet Mask: 255.255.224.0
Port Rules
1 Rule: Start 0
End 65535
Protocol Both
Mode Multiple
Priority null
Load Equal
Affinity Single
The second node is exactly the same except
for:
Host Parameters
Priority (Unique host ID): 2
Dedicated IP address: 157.231.32.188 (this is the
unique IP on adapter 1)
Oh, and I didn't IP this forsaken beast... lol
Did I misunderstand the Dedicated IP address purpose?
Marc
----- Original Message -----
Sent: Wednesday, March 05, 2003 3:14
PM
Subject: RE: [ActiveDir] OT: WLBS and
Exchange 2000
Marc,
How are your Host Parameters setup?
Do a wlbs display, that will give more detailed
information.
All, I apologize for continuing the off topic
posts. However, I think this may be a good place to get an
answer.
I'm getting a very perplexing problem with
Exchange 2000 SP3, Win2K SP3 and WLBS. We have 2 front end servers and 3
back end servers. For about a half hour, we were able to get them working no
problem. The front ends each have 2 NICs, one for direct connection (unique
IP) and one for WLBS (shared IP w/ load balancing). WLBS on each server is
setup as follows with the shared IP as the only IP running on its adapter.
In addition, the host headers on the Exchange Virtual Server are set up with
the DNS name of the WLBS.
It originally worked like a charm and then
after about a half hour, the servers had connectivity problems. It's a
pre-staging lab so I restarted the machines. Then the System Attendant
wouldn't start. Even if done manually. I was getting 2102 errors saying that
the server couldn't communicate with the global catalog (pre-stage lab has
one DC which is a GC). 2 Backend clusters (running MS cluster service) could
communicate fine. Everyone could ping everyone, even the problem servers.
The load balanced IP was registered in DNS and WINS correctly.
I disabled the adapters that were running WLBS
and rebooted the machines. Exchange came up like a charm. No
problems.
I reenabled them again and rebooted. Same
problems.
Does anyone have any suggestions? I'm open and
tapped out of ideas.
Thank you,
Marc
Zukerman
| 