Non-NLB network segment clients cannot access NLB

Non-NLB network segment clients cannot access NLB

Environment: ESXi 5.5U2

Two units VM Windows R2

NLB VIP 10.172.25.15

Configuration the NLB process is omitted here, Google, Baidu have steps

when configured, such as NLB chooses to work in multicast mode for unicast issues, see VMware KB

Http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId =2040916

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M01/76/F1/wKioL1Zfm1vSGSxsAABj8IKo99Y548.png "style=" float: none; "title=" 1.png "alt=" Wkiol1zfm1vsgsxsaabj8iko99y548.png "/>

after the NLB configuration is complete, the following issues occur

in and NLB VIP servers with the same VLAN can communicate with NLB , non- NLB vipvlan servers cannot communicate with NLB

Troubleshoot firewalls and NLB configuration, no problem found

After querying the information, found the problem

Http://ontheair.cn/?p=28

in multicast mode,NlbThe node is not modified forNlbThe network adapter for the communicationMacaddress, but assigns it a two-layer multicastMacaddress, specifically forNlbthe communication (thisMacAddresscalled a clusterMacaddress), soNlbbetween the nodes can be used by their own original privateIpaddress for communication. But in multicast mode,Nlbnode sends theARP (Address Resolution Protoco)the reply message will clusterIpaddress mapping to multicastMacaddresses, and many routers or switches (includingCISCOproduct) rejects this behavior, thereby discarding theArpreplymessages. When this happens, you must manually add the static mappings on the routers and switches, and the clusterIpaddress mapping to cluster multicastMacaddress.

after that, in The NLB VIP is configured on the gateway switch with a static ARP binding such as

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M02/76/F1/wKioL1Zfm1vzTP2PAAAQNFYGdeU824.png "style=" float: none; "title=" 2.png "alt=" Wkiol1zfm1vztp2paaaqnfygdeu824.png "/>

After testing, communication is normal.

This article is from the "nothing to write a point" blog, please be sure to keep this source http://makkapakka.blog.51cto.com/10500099/1719093

Non-NLB network segment clients cannot access NLB