VMware vSphere

 View Only
  • 1.  Microsoft NLB - VMware vSwitch settings

    Posted Sep 21, 2015 02:17 PM

    Hi all

    I'm looking at configuring an NLB for RDS 2012R2 (for the roles RDWeb and RD Connection Broker) and having read several VMware KBs about NLB want to clarify what's needed at the vSwitch level.

    I've read this:  http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006580

    and

    kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=ex&bbid=TSEBB_1297207395792&url=&stateId=0 0 770360056&dialogID=770346747&docTypeID=DT_KB_1_1&externalId=1006778&sliceId=2&rfId=

    Will probably use Unicast as both these roles are active active, don't need persistence or to communicate with other NLB hosts. The RDWeb role is simply an IIS web server running over 443.

    We have Exchange 2013 CAS front ends already on their own vSwitch and using NLB (configured by third party) but I noticed Notify Switches is set to Yes, whereas the KBs point to No.

    Here's my plan, if someone could ratify that would be excellent.

    Create new vSwitch with the following settings:

    Promiscuous mode:  Reject

    MAC Address changes: Accept

    Forged Transmits: Accept

    Notify Switches: No

    All other settings default.

    Cheers all

    Lea



  • 2.  RE: Microsoft NLB - VMware vSwitch settings

    Posted Sep 21, 2015 02:24 PM

    Can you tell us if your Exchange CAS servers NLB is configured for Unicast or Multicast ?



  • 3.  RE: Microsoft NLB - VMware vSwitch settings

    Posted Sep 21, 2015 02:49 PM

    Unicast!



  • 4.  RE: Microsoft NLB - VMware vSwitch settings

    Posted Sep 21, 2015 02:58 PM

    To unicast mode require the Notify Switches configured to NO, ignoring this configuration can cause problem and may get the issue described here: VMware KB: Microsoft NLB not working properly in Unicast Mode

    Anyway, there is any reason why you're using Unicast instead of Multicast ? Take a look on this note from VMware:

    VMware recommends configuring the cluster to use NLB multicast mode even though NLB unicast mode should function correctly if you complete these steps. This recommendation is based on the possibility that the settings described in these steps might affect vMotion operations on virtual machines. Also, unicast mode forces the physical switches on the LAN to broadcast all NLB cluster traffic to every machine on the LAN.



  • 5.  RE: Microsoft NLB - VMware vSwitch settings

    Posted Sep 21, 2015 03:15 PM

    Thanks, I did spot this, but there is much talk of switch compatibility (or lack of).  We're running a mix of HP 3800s and HP 2910s and so headed for the more compatibile unicast mode.  Also, the Exchange CAS setup appears to function correctly which I have assumed was configured by more experienced Solution Providers, however I'm concerned the 'Notify Switches' is set to Yes.

    Anyway,for my RDS production roll out,  am I correct in thinking the settings I've noted are suitable for MS NLB in Unicast?

    Lea