Solved

Lost client connectivity in Exchange 2013

Posted on 2014-11-10
3
462 Views
Last Modified: 2014-11-11
We have updated to Exchange 2013 CU6 w/ coexistance with 2007. We've migrated all resouces and settings to exchange 2013 and have shutdown the 2007 environment (3 weeks ago) with no negative impact.

An issue we've been dealing with for about 2.5 months is client connectivity. Randomly all outlook users will disconnect and email will no longer be delivered to mobile devices. There are no log entries leading up to the failure or during.

To resolve the issue I do the following:
Reboot both CAS servers
Make the active node passive and the passive node active
Client connectivity restored

**Note: After talking with multiple VARs and collegues I now know that NLB clusters are not recommended by Microsoft and we should be using hardware for load balancing. We're in the process of purchasing a hardware load balancer, but we're 2 month from having one in house.

Environment:

Front End- 2 virtual Windows server 2012 R2 on VMware 5.1. Each have 2 cpu and 8gb ram. Running Exchange server 2013 cu6 Standard in A active/passive NLB configuration (unicast).

Back End- 2 virtual Windows server 2012 R2 on VMware 5.1. Each 12 cpu and 32gb ram. Running Exchange server 2013 cu6 Standard in a DAG.
Questions:
1. Has anyone seen this behavior before?
2. Any suggestions on tools/troubleshooting?
3. Recommendations?

We've used the following VMware links to configure and QC server settings:

3) VMware: Articles and Blog

• Microsoft Network Load Balancing Multicast and Unicast operation modes (1006580)
http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1006580

• Sample Configuration - Network Load Balancing (NLB) unicast mode configuration (1006778)
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006778
Comments:
If your Windows Network Load Balancing is configure with unicast communication mode, review the section on RARP packets in this article .
The transmission of RARP packets is prevented on the portgroup / virtual switch as explained in the later part of the article.
Microsoft NLB not working properly in Unicast Mode (1556)
http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1556
Check out this blog:
Back To Basics: Configuring Standard vSwitch (Part Two of Three)
http://blogs.vmware.com/smb/2014/04/back-basics-configuring-standard-vswitch-part-two-three.html
Scroll to the “Notify Switches” section where you will see:
Microsoft NLB software when configured in a unicast mode is incompatible with Notify Switches set to Yes.

• Sample Configuration - Network Load Balancing (NLB) Multicast Mode Configuration (1006558)
http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1006558
0
Comment
Question by:Mwaddams
  • 2
3 Comments
 
LVL 118

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE) earned 500 total points
ID: 40433688
1. Has anyone seen this behavior before?

More times, that I've had hot dinners, and regular question on EE!

2. Any suggestions on tools/troubleshooting?

Switch to multicast.

3. Recommendations?

firstly to pick holes, I would not use NLB in unicast mode, switch to Multicast, this is what is recommended in a VMware environment.

and when you have switched to Multicast, it is important to follow the documents you have referenced to statically allocate ARP MAC and IP addresses in your routers, and every physical port and uplink you would expect multicast traffic to appear on needs to be in the config!

OF ALL the NLB configurations we visit on a monthly basis, this is the reason for failure, someone does not configure the physical switches!

If you cannot do the above, abandoned NLB, and wait for your hardware load balancer, or you could try...

http://www.zenloadbalancer.com/

which is a virtual appliance!
0
 

Author Comment

by:Mwaddams
ID: 40434154
Andrew,

Thank you for taking the time to respond to my question.
We've decided to abandon NLB and do the following:

Build a new standalone CAS server
Point the firewall to the new server
Shutdown CAS Array
Purchase and install a hardware load balancer
Stand up additional CAS servers as necessary after load balancer installed.

By simply removing NLB from the environment do you believe all of our random client connectivity outages will go away?
0
 
LVL 118
ID: 40434167
Yes, otherwise you've got another issue!
0

Featured Post

U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

Question has a verified solution.

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

In this article, I will show you HOW TO: Create your first Windows Virtual Machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, the Windows OS we will install is Windows Server 2016.
In this article, I show you step by step with screenshots to assist you - HOW TO: Deploy and Install the VMware vCenter Server Appliance 6.5 (VCSA 6.5), with some helpful tips along the way.
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…
how to add IIS SMTP to handle application/Scanner relays into office 365.

932 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

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now