Skip to main content

Hyper-V problem with Network Load Balancing (NLB) in virtual machines running Windows 2008

I recently had a problem with virtualized Exchange 2007 SP1 with CAS role installed and NLB enabled. Exchange is installed on top of Windows Server 2008 and two network cards were added to configuration. One network card for Outlook Anywhere on port 443 in NLB and the other card for other traffic and server management.

After some time one of the virtualized Exchange 2007 servers started to reboot unexpectedly without any useful information in event logs.

Since I had many problems with NLB in my career I thought that maybe Hyper-V and NLB are not working well together.

During the search for error I ran into Rob Whitehouse’s blog post in which he posted the link to Microsoft’s knowledge base article with exactly the same error/problem I got.

Microsoft provided a hotfix for this error that was described with following symptoms:

  • You are running a Windows Server 2008 virtual machine in the Hyper-V environment on a Windows Server 2008 host computer.
  • You try to create a new Network Load Balancing (NLB) cluster on this virtual machine. Or, you try to add this virtual machine to an existing NLB cluster.
In this scenario, the NLB host on the virtual machine does not converge as expected. Additionally, if a large volume of traffic occurs in the NLB cluster, the guest system on the virtual machine may restart unexpectedly, and you may receive the following Stop error message:

 

STOP: 0x000000E1 (parameter1, parameter2, parameter3, parameter4)

In my case hosts were converged properly (after the reboot) just that one of the servers was constantly unexpectedly rebooting.

Reference:

Windows Server 2008 Hyper-V virtual machines generate a Stop error when NLB is configured or when the NLB cluster does not converge as expected

 

Comments

  1. On the subject of load balancing, why not get the highest availability while not getting caught in high prices? Kemp’s got some great load balancers that are low priced and high in quality:

    http://www.kemptechnologies.com/?utm_source=blog&utm_medium=pv&utm_content=zs&utm_campaign=home

    ReplyDelete

Post a Comment

Popular posts from this blog

Error "<#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP#" when you send attachment in your mail

Some users were receiving error <#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP# when they sent message with attachment. The problem is when attached document name is longer than 50 characters. Some Firewalls have header size restriction and that limit blocks this messages to be sent. To correct this, change header limit on affected Firewall or shorten the name of the document you are sending (which is probably not good permanent solution).******
Update #1: Default header size limit in Exchange 2007 is 64K.Update #2: It might be the SMTP version problem. Mail is rejected with CONTENT-DISPOSITION error (overly long message header field for CONTENT-DISPOSITION) but not for all SMTP servers (same mail sent through different SMTP servers). If you send mail with attachment that has name longer than 50 characters from Exchange 2007 directly through DNS you may encounter this error, but if you send same mail from Exchange 2007 through smart host (other than Exchange) mail is d…

Change SMTP port 25 in Exchange 2007, 2010

For some reason you might want to change default SMTP port number 25 Exchange 2007 is using. Exchange 2007 uses RECEIVE AND SEND connectors, one for receiving mails and other for sending mails (obviously ;)
So you need to change ports on those connectors. I will not say those two, because you might be using more than two.
You change Receive connector port by opening the connector properties in Exchange Management Console --> Hub Transport --> RECEIVECONNECTORNAME --> Properties --> Network --> Local IP Addresses (Edit Receive Connector Binding)
Just to clarify what "Local IP Addresses" and "Remote Servers" are (from Exchange 2007 help), because I find it little bit confusing: Use these local IP Addresses to receive mail Use this list to specify the IP addresses and port numbers on which this Receive connector listens for incoming mail. Receive mail from remote servers which have these IP addresses Use this list to specify the remote IP address range fr…

The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange setup

You get this error "The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange setup" when you try to install Exchange 2016 on Windows 2016 server. Exchange 2016 pre CU3 does not support Windows 2016, therefore you need to download Exchange 2016 CU3, which is in fact full copy of Exchange 2016 server in order to install it on Windows 2016 machine.