?
Solved

Everytime I reboot one of my Exchange 2010 CAS servers that are in a CAS Array, the WNLB won't come back up.

Posted on 2010-09-13
3
Medium Priority
?
703 Views
Last Modified: 2012-08-13
I have two Exchange 2010 CAS server configured in a CAS array.  These Exchange 2010 servers are on virtual machines using Hyper-V.  (Windows 2008 SP2)  Everything works fine until I have to reboot one of them.  After I reboot, I'll open the Network Load Balancing Manager and they are not converged.  It won't  even let me ping the NLB NIC anymore after I reboot.  I used the following article (http://support.microsoft.com/kb/953828) and did give the NLB NIC on each CAS Server a static MAC, but this only works until I reboot.  Has anyone experienced problem?  Its caused me so much of a headache that I'm not evening using the CAS array at the moment.  I just have all users pointed to one single CAS Server.  Any help would be greatly appreciated.  Thanks.



0
Comment
Question by:denver218
  • 2
3 Comments
 
LVL 13

Accepted Solution

by:
George Sas earned 2000 total points
ID: 33665906
When you plan to configure a WNLB array for virtual Exchange 2010 CAS servers that uses Hyper-V Server or Hyper-V Server R2 as the virtualization platform, you can configure the WNLB array in Unicast mode. But you will face an “expected” issue while you configure the WNLB array. The issue occurs because the MAC address of the NIC you use for the WNLB array is changed when you create the WNLB array. This will make the MAC address that Hyper-V assigned to the NIC different from the one originally assigned when you added the NIC under the Hyper-V settings of the virtual machine. To fix this issue, you need to configure a new static MAC address identical to the one assigned to the WNLB (Figure 1). If you are running the virtual Exchange 2010 CAS servers on Hyper-V Server R2, you should tick Enable spoofing of MAC addresses.

Please check the full article here :
http://www.msexchange.org/articles_tutorials/exchange-server-2007/planning-architecture/uncovering-new-rpc-client-access-service-exchange-2010-part3.html

I personally dropped teh NLB and I used round robin for a while until we bought a hardware balancer.
MS NLB on a HP switch just sux and will flood the whole network.
0
 
LVL 4

Author Comment

by:denver218
ID: 33666417
I've configured a static MAC address identical to the on assigned to WNLB, and it does work until I reboot.  Once I reboot the servers won't converge anymore.  I'm about to go to a DNS round robin, I've been dealing with this for months now.
0
 
LVL 4

Author Closing Comment

by:denver218
ID: 33808898
I also just dropped the WNLB for the CAS Servers.  It was more a pain than anything.  DNS Round Robin is the most painless solution for me at the moment.  
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The main intent of this article is to make you aware of ‘Exchange fail to mount’ error, its effects, causes, and solution.
This month, Experts Exchange sat down with resident SQL expert, Jim Horn, for an in-depth look into the makings of a successful career in SQL.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question