Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Using Hardware Load Balancer with existing WNLB

Posted on 2014-02-05
1
Medium Priority
?
258 Views
Last Modified: 2014-02-06
Hello,

I have 2 CAS/Hub (dual role) servers on Windows Server 2008 R2 that are currently using WNLB to load balance.  There is a virtual IP for the CAS array that point to them.  I am installing Kemp hardware load balancers but unfortunately I don't have any sort of dev environment to test with.  This would all be in the production environment.  So, for testing, I figured I would configure the HW LB's and when they are ready I could put in a host file entry on my own machine to point the CAS array and OWA to the new load balancers IP's, leaving the network DNS pointing to the existing WNLB so end users are none the wiser during testing.  I realize that this will not be a good test for all services but I could at least test some traffic to and from the HW LB's and of course, that I can get to my mailbox.  My ultimate goal is to test the configurations without interrupting production.


So over all, my question would be:

Will using the hardware load balancer while WNLB is active on the CAS servers cause any issues?  (i.e. Does anyone foresee any false positive results with this testing that I should look out for? Or will it cause any issues with production?)
0
Comment
Question by:ehosford80
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 2

Accepted Solution

by:
nifdrift earned 2000 total points
ID: 39838337
You will have no problem using your hardware load balancer as well as the wnlb.
The wnlb will work standalone just as your hwlb.

You have to configure your hwlb to point to the cashub nodes (dont think about the wnlb ip) and give the hwlb its own ip. This will have no impact on production since Exchange will only "listen" to hostname and since you set hostname to the hwnb ip in your hosts-file the Exchange will treat is as it will treat the wnlb.

Good luck :)

Edit: Remember to set the hostnames of your internal and external addresses in the hosts-file. Also, the failover will not affect each other since they are both standalone. Falover on hwlb will not affect wnlb
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

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

This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
There are times when we need to generate a report on the inbox rules, where users have set up forwarding externally in their mailbox. In this article, I will be sharing a script I wrote to generate the report in CSV format.
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

704 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