Hyper-V 2012 R2 & NLB (Network Load Balancing) with Unicast on VMs

Hi,
We set up a 2012 R2 Hyper-V Cluster. On this Cluster we would like to run 2 VM's which are using NLB (Network load Balancing) in Unicast mode.
We have created a External Virtual Switch wich is connected trough a 3x10GB LACP Team to a Cisco Nexux Switch.
We have tried to set the NLB up in the way we did with 2008 R2 but we were not be able to get this working. Is there any Change in 2012 R2 we did not think about?
Each time we form the Cluster one Node becomes unavailable.
Timo

Check the virtual network adapter properties - you must enable MAC address spoofing.  We had the same issues.
Note that this will absolutely pollute your host machine's system log with tons of spam and make it pretty much worthless.  I'm trying to find a way around this as we speak, actually.

Similar Messages

  • Windows Server 2012 R2 - Windows Network Load Balancing Converging Issue

    Hello,
    My name is Brandon. We have started upgrading our servers to Windows Server 2012 R2. We have some powerful servers for running ESXI 5.5 as the OS with the Guest Operating Systems as Windows Server 2012 R2. As far of our migrations/upgrades we have configured
    ADFS 2012 R2 into a Server Farm with Windows Network Load Balancing to add redundancy in the event a server goes down.
    I have been having issues with a Node with the Cluster getting stuck in the Status of Converging. The only way I have been able to get it back up is to restart the virtual server completely and it is temporary. When I first configure the Cluster the two
    virtual servers get added to the Node with no problems and fully converge. However, after some time a node will end up in Converging and this takes Authentication for ADFS down as the nodes can not be contacted over Port 443.
    Error: Host: server.domain.com Unable to connect to "server name"
    System
    Provider
    Name]
    Microsoft-Windows-NLB
    Guid]
    {F22AF71F-C4C3-425D-9653-B2F47B85DD30}
    EventID
    21
    I have tried using 1 & 2 Virtual NICs on the machines and still receive this error even if only 1 VNIC is assigned to the virtual machine. Could someone assist me with why I am having this issue? Has anyone had experience with a similar configuration
    and how were you able to make it work?
    Below is my configuration.
    Static ARP Entry for Cluster IP Address has been added to our Layer 3 switch.
    Physical Server 1:
    ESXI 5.5 HOST
    1 NIC CONNECTED (shared with virtual guest)
    IP ADDRESS: 192.168.0.5
    SUBNET: 255.255.255.0
    DGW: 192.168.0.1
    Virtual Server 1
    Physical Server 2:
    ESXI 5.5 HOST
    1 NIC CONNECTED (shared with virtual guest)
    IP ADDRESS: 192.168.0.6
    SUBNET: 255.255.255.0
    DGW: 192.168.0.1
    Virtual Server 2
    Virtual Servers
    Virtual Server 1
    MS SERVER 2012 R2 (VIRTUAL)
    NLB NODE
    2 – VIRTUAL NETWORK ADAPTERS
     VNIC1
    IP ADDRESS 192.168.0.10
    SUBNET: 255.255.255.0
    DGW: 192.168.0.1
     VNIC 2 (NLB)
    IP ADDRESS: 192.168.0.11
    SUBNET: 255.255.255.0
    Virtual Server 2
    MS SERVER 2012 R2 (VIRTUAL)
    NLB NODE
    2 – VIRTUAL NETWORK ADAPTERS
     VNIC1
    IP ADDRESS 192.168.0.20
    SUBNET: 255.255.255.0
    DGW: 192.168.0.1
     VNIC 2 (NLB)
    IP ADDRESS: 192.168.0.21
    SUBNET: 255.255.255.0
    Cluster Configuration/Properties
    CLUSTER PROPERTIES
    CLUSTER IP: 192.168.0.30
    CLUSTER SUBNET: 255.255.255.0
    FULL INTERNET NAME: FS.DOMAIN.COM
    CLUSTER OPERATION MODE: MULTICAST
    PORT RULES:
    CLUSTER IP ADDRESS  START END  PROTOCAL MODE   PRIORITY LOAD  AFFINITY
    ALL    80 80 BOTH  MULTIPLE  ..  EQUAL  NONE
    ALL    443 443 BOTH  MULTIPLE  ..  EQUAL  NONE
    CLUSTER NODES:
    1.) SERVER1.DOMAIN.COM
    a. IP: 192.168.0.11
    2.) SERVER2.DOMAIN.COM
    a. IP: 192.168.0.21

    Thank you for your response. It took me a while to figure it out, but the whole issue was related to the type of Virtual Network Adapter I was selecting.
    I changed the network adapter from E1000 to VMXNET 3 and have not had a single error in the event logs or Windows NLB.
    I read somewhere that VMXNET 3 is preferred for Windows Server 2012 R2.
    https://communities.vmware.com/thread/433792
    Leyuka       May 23, 2013 6:14 AM
    "Just a help for everyone with this problem :
    After 10 days of research for our virtual datacenter behind a vcloud as iias ,  i found a solution .
    I only run windows 2012 server .
    Install vmware tools , remove e1000 network card after a vm stop, add a card same vswitch etc BUT with a vmxnet3 TYPE . DONT USE DEFAULT CARD
    Start and enjoy this solution . E1000 and E1000e are just unstable in windows8 / windows 2012 , the network card reset randomly with or without heavy IO. No log in windows , and as a vcloud user i don"t have esxi logs (damn i don't like cloud) and provider
    don"t know why ..."

  • Host Unreachable intermittently within a Windows Network Load Balancing Cluster

    Hi,
    We have 2 Windows 2008 R2 servers running multiple IIS web sites and load balanced across Windows Network Load Balancer in unicast mode. Although there are two interfaces in each server, only 1 interface in each server participates in load balancing and
    other interface is used for a different backup LAN. The problem I am going to mention was not seen within the NLB for almost 1 year.
    I have noticed intermittent "host unreachable" detected from NLB in each host from time to time since 3 weeks ago. After servers are rebooted, both hosts can be reached and can be detected from NLB manager. However it becomes unreachable in both
    servers within minutes and then becomes reachable again after several minutes. This behavior is noticed in the load balancer and pings do not work between the two hosts when the issue occurs. I did a packet capture to see what was going on with ARP message
    when the issue occurs. ARP entry goes missing in each server when the problem occurs and no ARP replies are returned from each server. But ARP requests are dispatched from both servers when the issue occurs. ARP replies come back after sometime after which
    hosts become reachable again.
    I tried to create a permanent static ARP entry (By copying the MAC address from ARP table when the two hosts are reachable) in each host but that hasn't solved the issue either. It seems like the individual MAC address generated by each host is a virtual
    one and it doesn't seem to respond when the problem occurs.
    However load balancing and web sites are fully functional without any issues even while "host unreachability" issue is detected.
    Appreciate if someone could help me to dig the real problem out.
    Thank you.

    Hi,
    Did you do some change of your network or the NLB firewall settings recently?
    If you are using the NLB cluster in Hyper-V guest vm you need to enable the spoofing of MAC address.
    The related article:
    Cannot access the virtual or dedicated IP address of an NLB node (Guest) running in Unicast Mode on Windows Server 2008 R2 Hyper-V
     http://blogs.technet.com/b/networking/archive/2010/02/12/cannot-access-the-virtual-or-dedicated-ip-address-of-an-nlb-node-guest-running-in-unicast-mode-on-windows-server-2008-r2-hyper-v.aspx
    More information:
    Selecting the Unicast or Multicast Method of Distributing Incoming Requests
    http://technet.microsoft.com/en-us/library/cc782694(v=ws.10).aspx
    Single network adapter
    http://technet.microsoft.com/en-us/library/cc776178(v=ws.10).aspx
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Bug with Network Load Balancing Services and SkipAsSource always reverting to true

    Steps to reproduce:
    Add an IP address to the cluster (2 nodes running Windows Server 2012) using the Network Load Balancing Manager
    Using PowerShell set the SkipAsSource flag on the IP Address to true (Set-NetIpAddress -IpAddress 192.168.1.10 -SkipAsSource $true). The flag is correctly set.
    Try to reverse the setting (Set-NetIpAddress -IpAddress 192.168.1.10 -SkipAsSource $false). Flag stays as true.
    It appears as though Network Load Balancing Services is remembering the setting from someone.
    Things I've tried all without success (in no particular order):
    Removing the IP address from the cluster and adding it back in
    Using PowerShell to remove the IP address and add it back in manually (on each host).Flag stays set as true on the 1st node but takes a second before it reverts back to true on the 2nd node.
    Using netsh to remove the IP address and add it back in manually (on each host). Flag stays set as true on the 1st node but takes a second before it reverts back to true on the 2nd node.
    Deleting each host from the cluster (one at a time), removing the registry keys CurrentControlSet\Services\WLBS and
    Removing both hosts from the cluster
    Restarting the hosts
    Using processmon (sysinternals) to try and find a registry entry that might be set when SkipAsSource is set
    Does anyone know:
    How to resolve this issue? I'm guessing resetting the TCP/IP stack would work but that's a last resort as it requires an on sight visit to the datacentre.
    Where the SkipAsSource flag it stored?
    How to reset the master/global cluster config?
    Thank in advance,
    Antony

    Hi Antony,
    I am trying to involve someone familiar with this topic to further look at this issue.
    There might be some time delay. Appreciate your patience.
    Best Regards.
    Steven Lee
    TechNet Community Support

  • Network Load Balancing for AFP Sharing

    Dear all,
    Anyone can kindly teach me how can I configure network load balancing with 2 xserve?
    Currently I success to bond 6 ethernet port with a virtual IP in a single machine and I have a link aggregation setup in my switch. It works fine.
    How to configure 2 xserve with 6 ethernet port per each to have a single virtual IP?
    my switch do not support link aggregation with a virtual IP to do the load balancing so I just can consider to do it in software level.
    Anyone know whether OS Leopard/Snow Leopard can do it? Or any suggestion for 3rd party software can perform this?
    Thanks expert!
    Karl

    It sounds like you need a load balancer. There's nothing built-in to Mac OS X Server that's going to support one virtual IP address shared across multiple physical servers.
    Your problem, though, is likely to be one of throughput - I don't know any cheap load balancers that will sustain that kind of throughput, so you may be looking at some serious $$$$s.
    There are some software-based load balancers that might be able to handle the load balancing side of things but many of them are designed around HTTP so might not work so well for other protocols.
    In addition, the software load balancer is going to suffer the same bottleneck as your AFP server, but doubly so - two servers with 6 x 1gbps links each you have a theoretical limit of 12gbps.
    To run that through a load balancer, the load balancer will need double that - 12gbps for the client-side, plus 12gbps for the server side. In reality you're probably looking at needing 10gbps interfaces and switches if you're really pulling that much bandwidth.

  • Windows Server 2012 R2 - ADFS/Windows Network Load Balancing Converging Issue

    Hello,
    My name is Brandon. We have started upgrading our servers to Windows Server 2012 R2. We have some powerful servers for running ESXI 5.5 as the OS with the Guest Operating Systems as Windows Server 2012 R2. As far of our migrations/upgrades we have configured
    ADFS 2012 R2 into a Server Farm with Windows Network Load Balancing to add redundancy in the event a server goes down.
    I have been having issues with a Node with the Cluster getting stuck in the Status of Converging. The only way I have been able to get it back up is to restart the virtual server completely and it is temporary. When I first configure the Cluster the two
    virtual servers get added to the Node with no problems and fully converge. However, after some time a node will end up in Converging and this takes Authentication for ADFS down as the nodes can not be contacted over Port 443.
    Error: Host: server.domain.com Unable to connect to "server name"
    System
    Provider
    [ Name]
    Microsoft-Windows-NLB
    [ Guid]
    {F22AF71F-C4C3-425D-9653-B2F47B85DD30}
    EventID
    21
    I have tried using 1 & 2 Virtual NICs on the machines and still end up with communication issues. Could someone assist me with why I am having this issue? This is not an issue with a firewall. If it was a firewall it would never communicate the first
    time. Has anyone had experience with a similar configuration and how were you able to make it work?
    Below is my configuration.
    Static ARP Entry for Cluster IP Address has been added to our Layer 3 switch.
    Physical Server 1:
    ESXI 5.5 HOST
    1 NIC CONNECTED (shared with virtual guest)
    IP ADDRESS: 192.168.0.5
    SUBNET: 255.255.255.0
    DGW: 192.168.0.1
    Virtual Server 1 (Guest OS)
    Physical Server 2:
    ESXI 5.5 HOST
    1 NIC CONNECTED (shared with virtual guest)
    IP ADDRESS: 192.168.0.6
    SUBNET: 255.255.255.0
    DGW: 192.168.0.1
    Virtual Server 2 (Guest OS)
    Virtual Servers
    Virtual Server 1
    MS SERVER 2012 R2 (VIRTUAL)
    NLB NODE 2 
    VIRTUAL NETWORK ADAPTERS
     VNIC1 IP ADDRESS 192.168.0.10
    SUBNET: 255.255.255.0
    DGW: 192.168.0.1
     VNIC 2 (NLB)
    IP ADDRESS: 192.168.0.11
    SUBNET: 255.255.255.0
    Virtual Server 2
    MS SERVER 2012 R2 (VIRTUAL)
    NLB NODE 2
    VIRTUAL NETWORK ADAPTERS
     VNIC1
    IP ADDRESS 192.168.0.20
    SUBNET: 255.255.255.0
    DGW: 192.168.0.1
     VNIC 2 (NLB)
    IP ADDRESS: 192.168.0.21
    SUBNET: 255.255.255.0
    Cluster Configuration/Properties
    CLUSTER PROPERTIES CLUSTER IP: 192.168.0.30
    CLUSTER SUBNET: 255.255.255.0
    FULL INTERNET NAME: FS.DOMAIN.COM
    CLUSTER OPERATION MODE: MULTICAST
    PORT RULES:
    CLUSTER IP ADDRESS
    START
    END
    PROTOCAL
    MODE
    PRIORITY
    LOAD
    AFFINITY
    ALL
    80
    80
    BOTH
    MULTIPLE
    EQUAL
    NONE
    ALL
    443
    443
    BOTH
    MULTIPLE
    EQUAL
    NONE
    CLUSTER NODES:
    1.) SERVER1.DOMAIN.COM
    a. IP: 192.168.0.11
    2.) SERVER2.DOMAIN.COM
    a. IP: 192.168.0.21

    Hi,
    According to your description, my understanding is that:2 ESXI 5.5 physical devices (192.168.0.5 and 192.168.0.6), each of them has a virtual WS 2012 R2(192.168.0.10 and 192.168.0.20). Cluster the 2 virtual servers successfully, but they corrupt with event
    ID 21, and a restart of virtual device will resolve this problem temporarily.
    Event ID 21 means that NLB failed to converge due to inconsistencies in the port rules between this host and cluster host. This will occur if the number of port rules or the type of port rules are different between hosts.
    Ensure that all NLB hosts have identical port rules. Detailed steps you may reference:
    Event ID 21 — NLB Port Rules Configuration
    https://technet.microsoft.com/en-us/library/dd364034%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
    Best Regards,
    Eve Wang
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Network Load balancing for Server 2003 and Server 2012

    Our environment currently has 2 web servers running Windows Server 2003 with Network Load Balancing.  We are looking to update the servers to Windows Server 2012.  Is it possible to add Windows Server 2012 into the Windows Server 2003 Network Load
    balancing cluster?  This way we could bring up 2 new servers add them into the network load balancing and then take out the 2003 servers without disrupting our production.
    Any thoughts or suggestions on how to make this work properly?

    Hi,
    You can upgrade an existing Network Load Balancing (NLB) cluster to Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012 by taking the entire cluster offline
    and upgrading all the hosts, or you can leave the NLB cluster online and perform a rolling upgrade. A rolling upgrade entails taking individual cluster hosts offline one at a time, upgrading each host, and returning the host to the cluster. You continue upgrading
    individual cluster hosts until the entire cluster is upgraded. A rolling upgrade allows the cluster to continue running during the upgrade.
    The related KB:
    Upgrading an Existing Network Load Balancing Cluster
    http://technet.microsoft.com/en-us/library/cc731691(v=ws.10).aspx
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Network Load Balancing (NLB)

    Dear Support,
    I have install NLB feature on two windows 2008 R2 servers both have configured with IIS. However I have tested both are working fine and both are accepting the request successfully.
    Since we have performed load test the load balance between the server is not equal
    Host 1
    CPU Utilization =53%
    Host 2
    CPU Utilization = 10%
    Please suggest.
    Regards
    Naveed
    Naveed Amir

    Hi naveed,
    This is normal. NLB is using the node that has the fastest response / highest priority and/or your configuration you can find more info about this here :
    Network Load Balancing Technical Overview
    http://technet.microsoft.com/en-us/library/bb742455.aspx
    Greetings, Robert Smit Follow me @clustermvp http://robertsmit.wordpress.com/ “Please click "Vote As Helpful" if it is helpful for you and Proposed As Answer” Please remember to click “Mark as Answer” on the post that helps you

  • Network Load Balancing not failing over properly

    I have 2 MS 2012 servers setup in a NLB unicast configuration, with 2 NICs each on the same subnet.  When I take down the second server (and only the second server) the FQDN goes offline.  Below are the ipconfigs for each server.  Any help
    would be greatly appreciated!
    Ethernet adapter Data NIC 192.168.220.172:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) I350 Gigabit Network
    #4
       Physical Address. . . . . . . . . : 6C-3B-E5-B2-48-60
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.220.172(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.220.1
       DNS Servers . . . . . . . . . . . : 192.168.220.100
                                           192.168.200.10
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter Cluster NIC:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM57810 NetXtreme II
    DIS VBD Client) #67
       Physical Address. . . . . . . . . : 02-BF-C0-A8-DC-AA
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.220.171(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       IPv4 Address. . . . . . . . . . . : 192.168.220.170(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.220.1
       DNS Servers . . . . . . . . . . . : 192.168.220.100
                                           192.168.200.10
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter Data NIC 192.168.220.174:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : HP FlexFabric 10Gb 2-port 533FLR-
    r #54
       Physical Address. . . . . . . . . : A0-D3-C1-F6-96-08
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.220.174(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.220.1
       DNS Servers . . . . . . . . . . . : 192.168.220.100
                                           192.168.200.10
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter Cluster NIC:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : HP NC523SFP 10Gb 2-port Server Ad
       Physical Address. . . . . . . . . : 02-BF-C0-A8-DC-AA
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.220.173(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       IPv4 Address. . . . . . . . . . . : 192.168.220.170(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.220.1
       DNS Servers . . . . . . . . . . . : 192.168.220.100
                                           192.168.200.10
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Hi MS DEF,
    A second network adapter is required to provide peer-to-peer communication between cluster hosts. Please isolate your heartbeat network. With unicast when cluster is connected
    to a switch, incoming packets are sent to all the ports on the switch, which can cause switch flooding, please confirm you have setup your switch correct, you can refer the following Cisco Switch related unicast configuration.
    The Cisco switch unicast related information:
    How to configure Microsoft Network Load Balancing on two switches
    https://supportforums.cisco.com/discussion/11918276/how-configure-microsoft-network-load-balancing-two-switches
    More information:
    Selecting the Unicast or Multicast Method of Distributing Incoming Requests
    http://technet.microsoft.com/en-us/library/cc782694(v=ws.10).aspx
    An Optimal Network Load Balancing (NLB) Configuration
    http://blogs.technet.com/b/clint_huffman/archive/2007/10/08/an-optimal-network-load-balancing-nlb-configuration.aspx
    Selecting the Unicast or Multicast Method of Distributing Incoming Requests
    http://technet.microsoft.com/en-us/library/cc782694(v=ws.10).aspx
    I’m glad to be of help to you!
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Network Load Balancing - "access denied" when loading configuration information from host2

    We have 2 Windows 2012 R2 servers, both are running on workgroup.
    We set up NLB cluster.  When we open NLB Manager on the server2, then message shows "loading configuration information. Access denied. Error connecting to server1". 
    There is no issue doing this on server1, NLB Manager is able to connect to both servers. We login using default administrator account, both account name and password are the same for 2 servers.
    When we check security event log on server1, there is this strange Audit Failure log using account "test_nlb" from server2 which related to "Access denied" error. Please let us know how to resolve this. Thanks in advance.
          Event ID: 4776
          The computer attempted to validate the credentials for an account.
          Authentication Package:   
    MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
          Logon Account:   
    test_nlb
          Source Workstation:   
    WPAAP2
          Error Code:   
    0xc0000064           
          An account failed to log on.
    Event ID: 4625
    Subject:
        Security ID:       
    S-1-0-0
        Account Name:       
        Account Domain:       
        Logon ID:       
    0x0
    Logon Type:           
    3
    Account For Which Logon Failed:
        Security ID:       
    S-1-0-0
        Account Name:       
    test_nlb
       Account Domain:       
    WPAAP2
    Failure Information:
        Failure Reason:       
    Unknown user name or bad password.
        Status:           
    0xc000006d
        Sub Status:       
    0xc0000064
    Process Information:
        Caller Process ID:   
    0x0
        Caller Process Name:   
    Network Information:
        Workstation Name:   
    WPAAP2
        Source Network Address:   
    192.168.70.45
        Source Port:       
    55136
    Detailed Authentication Information:
        Logon Process:       
    NtLmSsp
        Authentication Package:   
    NTLM
        Transited Services:   
        Package Name (NTLM only):   
        Key Length:       
    0
    This event is generated when a logon request fails. It is generated on the computer where access was attempted.
    The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
    The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
    The Process Information fields indicate which account and process on the system requested the logon.
    The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
    The authentication information fields provide detailed information about this specific logon request.
        - Transited services indicate which intermediate services have participated in this logon request.
        - Package name indicates which sub-protocol was used among the NTLM protocols.
        - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

    Hi Zhong Gang,
    When you are using Network Load Balancing (NLB) Manager, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated
    the appropriate authority. If you are configuring a cluster or host by running NLB Manager from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer. Please disable your nodes firewall and
    try again.
    The related KB:
    Add a Host to the Network Load Balancing Cluster
    http://technet.microsoft.com/en-us/library/cc753744.aspx
    I’m glad to be of help to you!
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Windows Network Load Balancing - Virtual MAC Address

    Hi All,
    I have environment that running 2 Exchange 2010 server with CASHT and join windows network load balancing as a node.
    My question is,
    If NLB service is restart, is it virtual MAC Address for NLB will change to new virtual MAC Address?
    Thanks for response,
    Best Regards,
    Henry Stefanus

    Hi Henry Stefanus,
    The NLB work mechanism will not change whether what higher application we used and I am not very familiar with Exchange NLB architecture, may the following KB and article
    may help you.
    When you use the unicast method, all cluster hosts share an identical unicast MAC address. Network Load Balancing overwrites the original MAC address of the cluster adapter
    with the unicast MAC address that is assigned to all the cluster hosts.
    When you use the multicast method, each cluster host retains the original MAC address of the adapter. In addition to the original MAC address of the adapter, the adapter is
    assigned a multicast MAC address, which is shared by all cluster hosts. The incoming client requests are sent to all cluster hosts by using the multicast MAC address.
    Selecting the Unicast or Multicast Method of Distributing Incoming Requests
    http://technet.microsoft.com/en-us/library/cc782694(v=ws.10).aspx
    The related third party article:
    Building NLB Exchange 2010 RTM CAS / HT Servers (Hyper-V) – Part 1
    http://blog.morecoffeeany1.com/2010/03/19/building-nlb-exchange-2010-rtm-cas-ht-servers-hyper-v-%E2%80%93-part-1/
    I’m glad to be of help to you!
    *** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these
    sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use
    of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Acrhitecture of network load balancing solution

    i'm working on a setup that will transition our existing data center setup to a network load balancing solution. i'm far from understanding what components to use and how to approach the problem so any help would be very welcome. here is what we currently have:
    1. 3 web servers (serverA, serverB, serverC)
    2. 1 sql server
    3. 2 layer two unmanaged switches
    4. 1 cisco firewall
    each one of the web servers runs a dedicated web app. what i would like is to replace serverA with a NLB cluster of 3 servers and replace serverB with another NLB cluster of 3 servers. serverC is not getting that much usage and it can stay as is.
    i have looked at possible solution with Windows Server 2008 NLB and it seems that the best way to do it would be using multicasting which requires upgrading out switches. at the same time if would much more prefer to use hardware load balancing than Windows Server. so i looked at Cisco ACE 4710 appliance. however it seems that some of the cisco switches will also do load balancing. now i'm completely confused whether to upgrade the switches and use them for load balancing or use the ACE appliance. i would appreciate any advices and suggestions. also, any recommendations on breaking up the network using VLANs - if it is necessary with either one of the solutions or if there is some benefit. i guess i'm looking for a "best practices" solution...
    any links or documents would be very welcomed.
    thanks.

    thanks for your response. i think i'm going with ace 4710. now, as far as vlans go why would i need internet, dmz and internal vlan in my datacenter? i understand that this may be a bit off topic but what is really bugging me is this: with the current setup all of the web servers have 2 nics - one with public IP and one with private IP. same goes with the sql server. on web servers nics with private IPs are used for communicating with the database server. they could very well communicate using nics with public IPs but the person that set this up (i recently inherited it) was convincing me that with the existing setup "public" nics are not burdened with communication between web servers and database server. is this "correct" way of doing it?

  • Multicast not working with Window2K Network Load Balancing.

    I'm using W2K Network Load Balancing (WBLB) for our cluster machines (2
              boxes) to load balance between IIS (one IIS instance on each box). Each IIS
              instance is a proxy to the weblogic cluster (one app server instance on each
              box). Currently I only have a single network card configured for each box,
              so I have had to enable multicast support for the WNLB. But if I do this
              I'm unable to get multicasting working correctly for the weblogic cluster.
              When I run the multicast tester (utils.MulticastTest) one box is able to
              receive multicast messages from both boxes, but the other box is only
              receiving multicast messages from itself (but not the other box). Does
              anyone have any experience with configuring weblogic clustering on machines
              with WNLB also configured?
              Thank you.
              Marko.
              

    Hi
    NLB return traffic for UDP would come from the node IPs.
    You could use NAT on your firewalls so they come from the same public IP.
    Otherwise you'd be looking at something other than MS NLB.
    Cheers
    GF

  • How to enable Network load balancing for Enterprise portal

    Hello,
    We have installed EP 7.0 central instance(00) and dialog instance (01) and would like to enable network load balancing between these two EP servers.Have installed network balancer and the configuration has been done at network level.
    The below URLs are being used for accessing the portal
    Central instance :
    http://CIhostname:50000/irj/portal
    Dialog Instance:
    http://DIhostname:50100/irj/portal
    Both the port number has to be same for enabling load balancing.In order to acive this we have to map this port to http port by making some changes in Visual Administrator.
    Can you please let me know step by step  procedure or any link where i can find the same?
    Appreciate your response
    Thanks,
    Vadi

    Dear Jay,
    Thnaks for your reply.
    No...NLB will helpful in load balancing between different 2 different  application (Ep)servers.
    We are using microsoft network load balancer.Found the service http provider in VA for making those changes.
    Any way thanks.
    Regards,
    Vadi

  • Internet load balancing with two machine (NLB)

    i have install two TMG 2010 and one is manger and one managed , but seems once manager down , other server not passing the traffic with vip , my question is does it supported like NLB with two machine ?

    Hi,
    Coud you confirm you can ping sucecssfully both of two machine before?
    To check if the NLB status is green:
    In the Forefront TMG Management console, in the tree, click the Monitoring node.
    In the Alerts tab, check that NLB Started for each array member.
    In the Network Load Balancing Manager (nlbmgr), check the status of the current node for all clusters define. Repeat this for each member.
    Run nlb display to view the current state of the NLB cluster and hosts. Repeat this for each membe
    http://technet.microsoft.com/es-es/library/ff849728.aspx#s3
    Best Regards
    Quan Gu

Maybe you are looking for