Network Load Balancing and IPv6 Ping Timeout

I've noticed interesting behavior with NLB on Windows 2012 R2 and IPv6. I have two systems that use NLB on a Hyper-V cluster, each system is on a different node in the cluster. When I do an IPv6 ping within the same subnet, I notice that the reply time is
normally 1-3ms, but every so often it goes to 100+ms. I also notice that both members of the NLB reply to a ping to the cluster IPv6 address. This is interesting.
When I do a ping to the cluster IPv6 address from a different subnet, I notice that the reply is intermittent. The NLB nodes will either both reply to the ping or both won't. At first I thought that there was an issue with my network, but when I do a span
on the ports that the cluster is attached to, I see that the IPv6 ping packets arrive, but the NLB nodes don't always send a reply.
What is also interesting is that the NLB web farm I have setup seem to be working fine and is not intermittent, so this issue only has to do with ping. Has anyone else seen this type of issue, or is this a bug?
Thanks!

Hi Nathan,
So are you running both IPV6 and IPV4? Do you have any clients that can't connect at all? Just on ping?
The reason I ask is we had a server that was receiving IPV6 fine, but on receiving IPV4 would switch to IPV6 to connect SSL back to the client. Of course the clients never received it and just got a timeout. Funny thing is cell phones had no issue
at all because they were straight IPV6. Only clients with both protocols got the timeout.
So the ack was send back via the wrong protocol and nothing but the timeout is what the client sees. This may be an LLMNR issue. It came out from 2008R2 but think it may still apply
Check this out:
http://technet.microsoft.com/en-us/library/bb878128.aspx
David Perkins
IT Help Point, Inc.

Similar Messages

  • Network Load Balancing - Multicast IPv6

    I have a two servers with network load balancing. They are configured to use IGMP Multicast which works well with IPv4.  The switch correctly detects the group and sends the traffic to only the ports connected to the servers.
    However i can't get IPv6 working outside of the servers subnet.  You can access the loadbalanced IPv6 address from within the servers subnet but machines outside the subnet cannot access it.
    Does load balancing properly support IPv6?  Should it not support Multicast Listerner Discovery (MLD) to work properly with IPv6? 
    Thanks

    Thanks for your reply. 
    Yes - you are correct. We are using an IPv6 address as the cluster IP address for incoming connections but it can't be access outside of the subnet. The cluster has both a link-local and global address - both are only accessible from within the subnet.
    The two servers that are part of load balancing cluster both have IPv6 address assigned to their network adapters - these are accesible outside the subnet. Infact 80% of all our network traffic is IPv6 - routing is working fine between all servers, workstations
    and devices on our various subnets.  The problem is purley affecting the load balancing IPv6 address.
    The IP config and route tables are below.  Thanks for your help.
    Regards, Daniel
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.
    M:\>ipconfig /all
    Windows IP Configuration
    Host Name . . . . . . . . . . . . : indium
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . :
    Ethernet adapter Public:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Ada
    pter
    Physical Address. . . . . . . . . : 00-15-5D-CA-6C-04
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv6 Address. . . . . . . . . . . : 2001:630:34:1010::42(Preferred)
    IPv6 Address. . . . . . . . . . . : 2001:630:34:1010::40(Preferred)
    Link-local IPv6 Address . . . . . : fe80::4c7b:41a3:be85:e6c4%10(Preferred)
    Link-local IPv6 Address . . . . . : fe80::95f6:2da7:dcdb:1fc1%10(Preferred)
    IPv4 Address. . . . . . . . . . . : 10.0.0.42(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.252.0
    IPv4 Address. . . . . . . . . . . : 10.0.0.40(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.252.0
    Default Gateway . . . . . . . . . : 2001:630:34:1010::1
    10.0.0.1
    DHCPv6 IAID . . . . . . . . . . . : 234886493
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-D0-9F-CD-00-15-5D-01-14-35
    DNS Servers . . . . . . . . . . . : 2001:630:34:1010::10
    2001:630:34:1010::8
    10.0.0.10
    10.0.0.8
    NetBIOS over Tcpip. . . . . . . . : Disabled
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.
    M:\>ipconfig /all
    Windows IP Configuration
    Host Name . . . . . . . . . . . . : aluminium
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . :
    Ethernet adapter Public:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Ada
    pter
    Physical Address. . . . . . . . . : 00-15-5D-01-37-04
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv6 Address. . . . . . . . . . . : 2001:630:34:1010::43(Preferred)
    IPv6 Address. . . . . . . . . . . : 2001:630:34:1010::40(Preferred)
    Link-local IPv6 Address . . . . . : fe80::95f6:2da7:dcdb:1fc1%10(Preferred)
    Link-local IPv6 Address . . . . . : fe80::fcab:aeb9:175d:9994%10(Preferred)
    IPv4 Address. . . . . . . . . . . : 10.0.0.43(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.252.0
    IPv4 Address. . . . . . . . . . . : 10.0.0.40(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.252.0
    Default Gateway . . . . . . . . . : 2001:630:34:1010::1
    10.0.0.1
    DHCPv6 IAID . . . . . . . . . . . : 234886493
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-BF-55-42-00-15-5D-01-13-45
    DNS Servers . . . . . . . . . . . : 2001:630:34:1010::10
    2001:630:34:1010::8
    10.0.0.10
    10.0.0.8
    NetBIOS over Tcpip. . . . . . . . : Disabled
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.
    M:\>route print
    IPv6 Route Table
    ===========================================================================
    Active Routes:
    If Metric Network Destination Gateway
    10 261 ::/0 2001:630:34:1010::1
    1 306 ::1/128 On-link
    10 261 2001:630:34:1010::/64 On-link
    10 261 2001:630:34:1010::40/128 On-link
    10 261 2001:630:34:1010::42/128 On-link
    10 261 fe80::/64 On-link
    10 261 fe80::4c7b:41a3:be85:e6c4/128
    On-link
    10 261 fe80::95f6:2da7:dcdb:1fc1/128
    On-link
    1 306 ff00::/8 On-link
    10 261 ff00::/8 On-link
    ===========================================================================
    Persistent Routes:
    If Metric Network Destination Gateway
    0 4294967295 ::/0 2001:630:34:1010::1
    ===========================================================================

  • Network Load Balancing and failover for AFP Sharing

    Dear all,
    Somebody kindly teach me to use round robin DNS to perform the network load balancing, it's success but not the failover.
    I have 4 xserve and want to do the load balancing and failover at the same time.
    I have read the IP failover document and setup it successfully, but anyone know is it possible to do the IP failover for more than 2 server?
    For example, 4 server serving the AFP service at the same time, maybe I have 1 more extra server to do the IP failover for thoese 4 servers.
    As I know, IP failover require Firewire as the heartbeat detection. But one xserve only have 2 firewire ports. May I setting up the IP failover only by a ethernet port and an IP address? does it possible to detect and failover to any server after server down has been detected?
    I believe load balancer maybe the best solution but its cost is too high.
    Thanks any advance!
    Karllee

    well, u have 2 options here
    software load balancing
    request comes it foo.com -> ws7u2 hosting foo.com is configured to run as reverse proxy . this server sends any incoming requests to one of the four back end web server 7 handling your incoming request
    hardware load balancing (this you need to invest)
    request comes to hardware load balancer who responds for foo.com -> sends requests to four ws7 server hosting your application
    you could try out how software load balancing works out for you before you invest in hardware load balancing
    here is more instruction on configuring ws7 + reverse proxy (software load configuration)
    - install ws7 on foo.com
    - create a new configuration (choose port 80, disable java

  • 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 balancer for Agentry applications

    Hi Expert,
    I'm going to implement a SAP Mobile Platform solution that will use an agentry application and I need some clarification about the HA configuration and the usage of the network load balancer and relay server. Just for information I'm going to use SMP 2.3 SP4.
    My understanding is that Relay server is a reverse proxy and load balancer for SMP but It can't be used for the agentry applications. Is this correct?
    Based on the standard configuration in order to balance the load of the client devices in the SMP cluster I have to use a Network load balancer, therefore the technical architecture of my solution should be the following:
    |Agentry Client device|   ---->  | Network Load Balancer |  ----> | SMP and Agentry Cluster| -----> |Back end systems|
    Is this correct? I didn't find specifications about the Network load balancer.. Is there a list of the Network load balancer products supported from SAP for agentry application. Is there any best practice on the network load balancer?
    Thank you in advance for you collaboration.
    BR
    g.
    Tags edited by: Michael Appleby

    Because we don't test any directly with our QA we don't have have a preferred products.  Talking to our consulting group they normally just use what the customer already has installed in their network.   Both Software or hardware load balancers has been used.
    The key part needed for the load balancer for Agentry 6.0.x and SMP 2.3 (not SMP 3) that it is set to TCP Pass through.
    Stephen

  • 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

  • UAG External Load Balancing and ISATAP

    Hi Experts,
    I am deploying a UAG Array to be used for Direct Access. The Array will consist of two servers and use an F5 External Load Balancer. In addition and in similarity
    to 90% of the other corporate intranets out there, the internal network is IPv4 with no IPv6 transition technologies deployed. The article
    http://blogs.technet.com/b/edgeaccessblog/archive/2010/05/17/configuring-an-external-load-balanced-uag-directaccess-array-for-an-ipv4-only-network.aspx
    isgreat but to my mind has no information to support ‘Manage Out’ and throws up a number of questions: (Note that I want to enable ‘Manage Out’ capability and as far as I am aware that is achieved by using ISATAP)
    The article describes that you have to generate and configure your own IPv6 address for the internal interface when using an external load balancer. Does anyone know why? Why not let UAG assign
    the addresses as per the default?
    UAG by default configures itself as an ISATAP router when there is no IPv6 infrastructure deployed on the internal network
    to facilitate ‘manage out’. This still applies when using Windows NLB. Why does this no longer apply when using an external load balancer? I.e. Why does UAG no longer configure itself as a ISATAP router?
    In relation to question 2; you therefore need to move your ISATAP router to a different device (http://technet.microsoft.com/en-us/library/ee690463.aspx),
    in doing so how do you configure the ISATAP environment to traverse the UAG servers without some sort of load balancing on the internal interfaces? I’m assuming that you can only tell the ISATAP router to use the one default gateway i.e. either one UAG server
    or the other. This means that you would have all your outbound internally initiated traffic going via one server only – not very good for performance or fault tolerance.
    In relation to question 3; I thought therefore that NLB could be used on the internal interface to solve the above problem, except that I have read that you can’t mix and match external load
    balancing and NLB even though they are on separate networks due to bidirectional affinity. What does this actually mean and why does this not occur when load balancing is mixed in this manor?
    Therefore when you wish to use external load balancers, do you:
    A) Except the fact that you can’t use UAG as a ISATAP router and you do indeed need two devices
    and deploy it as described here (http://technet.microsoft.com/en-us/library/ee690463.aspx)
    or
    B) Except the fact that that you can’t use UAG as a ISATAP router and any internal outbound
    traffic travels via the one UAG server only.
    Apologies for the long post, but I wanted to make sure that I get my thoughts down concisely so that it may help others who come up with the same questions
    J
    Thanks for your time everyone
    Gary

    I am also facing the same issue.  I have UAG1 and UAG2, which are in an array, and externally load balanced.  I've configured an external ISATAP router according to: 
    http://www.windowsnetworking.com/articles_tutorials/Configuring-ISATAP-Router-Windows-Server-2008-R2-Part2.html.  However, as mentioned by others, the ISATAP router has to have either UAG1 or UAG2 as the next hop for IP-HTTPS traffic.  As
    a result, communication between the DirectAccess client and management devices will only work if the client is tunneling through the same UAG server that the ISATAP router has as the next hop for the IP-HTTPS prefix.  From what I can tell, my configuration
    is supported, but I can't figure out how to have the ISATAP router determine which UAG server a client is tunneling through.  I thought about having two separate IP-HTTPS prefixes for each UAG server, but this would get overwritten when activating
    the DirectAccess configuration.  Maybe some type of internal load balancing?

  • ISA570-Load balancing and Losing packets

    I am load balancing two isp's.  One isp is fine, but the other I have very high packet loss when pinging the corresponding wan interface from any machine located outside our network.  During the packet loss, I cannot https to our firewall from outside our network, but I can rdp using a different address on that same isp and ping another machine located inside our network, it seems only the wan interface is having the issues.  Our isp uses icmp to our wan interface and they started noticing the loss the other day, again the other isp loses no packets.  I have no issues with clients losing connection from that isp so it looks like it is an issue from outside in only on that wan interface.  
    I have a spare ISA and that is experiencing no packet loss when using another ip from the problem isp on it's wan interface.  The isa's have the same configuration and when I tried moving completely to the backup isa it continued with the same issue.  Upgraded to a later firmware, still the same issue.  I even took a laptop and put it on our switch that is before the isa and gave it a static public address and I can ping it with no problem from the outside.  I can also ping from the laptop to the wan port of the prod isa that is losing packets and it replies as it should, which I assumed would lose packets if it were the isa having issues, but it didn't.
    I know this has nothing to do with Cisco security services as on the backup firewall it was still losing packets when we moved the connections over to it.  
    I can ping from inside my network to the public wan address with no loss when outside machines are having problems.
    I can ping the problem wan address from a laptop or from isa(IP = 64.x.x.42) to isa(IP = 64.x.x.45) with no packet loss.  
    This is a head scratcher and I need some real help here.

    Never figured this one out.  However,  I was able to figure out how this starts. A couple of weeks ago we had an issue with an ISP and we disabled that interface during the day and re-enabled at the end of the day and thats when we noticed ICMP breaks to other ISP..  I don't know why but the ISP we renabled we can ping just fine, but the other one always has issues.  The only fix is to enable link failover detection and both WAN interfaces become pingable again.
    Now, we use load balancing and one issue we are experiencing is that randomly both WAN interfaces go down and I can confirm this with a ping utility we use off site that pings both WAN interfaces and also each ISP gateway they are connected to.  When this happens the ISP's gateways are reachable and neither WAN interface on the ISA are.  I am still on .15 version of the firmware, because there were too many issues with newer releases.  Is this a known issue?

  • 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.

  • 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.

  • 2 ISP load balancing and redundancy

    Hello!!
    Our small company has about 40 branches spreaded within city. Branches are connected by optic wire supplied by our ISP. So in ISP our branches are located in one VLAN. From every branch we created VPN tunnel to our server room in central office. Central office is like a cetner point. If optic wire fails to central office, there would no VPN tunnels and no network to all branches. Moreover, all the traffice goes through central office.
    Now we decided to pave one more optic line to our central office. And that will increase bandwidth and redundancy.
    Private network topology: There are no default gateways and ip-addresses. For examle, at first branch I will plug computer directly into media converter and at the second branch plug another computer to the media converter. After that this two computers became in one network. And can assign any ip addresses to them.
    What I have: our firewall do enough work, don't want to overload it. But we have some free ports in our new cisco 3750. The question is how to do load balancing and redundanccy? Can it do load balancing according to traffic? And how load balance incoming traffic? For example, connection was established from branche's router, how this router will choose through which line make connection? By the way, at all branches we use noisy cisco
    3700 series routers.

    Sorry for upping 1 year old threat.
    We talked to our Network Provider. They said "these two cables are coming from two different places, so there is no way to use etherchannel. You must use active-standby solution."
    Relying on STP we just put two cables into 3750 stack. But with default STP settings, connection was very unstable, many packet losses and disconnections. So we found easy solution with "flex links", making one interface backup of the other. And only now I recognized that this is not a failover solution. Because, if network beyond media converter will down, link from media converter to switch would still up.
    What could I do to make our L2 WAN redundant? Are there any additional STP settings.

  • Load balancing and Failover

    Hello,
    We are wondering how load-balancing and failover of tpcall() work with
    WTC:
    The scenario:
    We have one WLS Domain and two Tuxedo Domains. The Tuxedo Domains offer
    the same set of services.
    In the bdmconfig.xml, we specify connection_policy as 'ON_STARTUP' for
    both Remote Tuxedo Domains. We also Import (T_DM_IMPORT) the same
    Tuxedo Service from both Tuxedo Domains.
    Questions:
    1. Is there any load-balancing of the tpcall between the two Domains? If
    so, is it round-robin? If round-robin, what determines the order?
    2. If it is ONLY Failover, what determines the order of the tpcall? And,
    is the Failover automatic? Or do we need to code for retry on failure?
    3. ON_DEMAND vs ON_STARTUP: Does ON_DEMAND drop the connection to the
    remote domain upon tpterm? And does ON_STARTUP use a pool of
    TuxedoConnection objects?
    4. Are there any configuration parameters for
    'max_number-of_connections? What determines how many simultaneous
    connections can be made?
    Thanks,
    Suresh Mohan.

    Hi Suresh,
    The following are my answers to your questions.
    Suresh Mohan wrote:
    Hello,
    We are wondering how load-balancing and failover of tpcall() work with
    WTC:
    The scenario:
    We have one WLS Domain and two Tuxedo Domains. The Tuxedo Domains offer
    the same set of services.
    In the bdmconfig.xml, we specify connection_policy as 'ON_STARTUP' for
    both Remote Tuxedo Domains. We also Import (T_DM_IMPORT) the same
    Tuxedo Service from both Tuxedo Domains.
    Questions:
    1. Is there any load-balancing of the tpcall between the two Domains? If
    so, is it round-robin? If round-robin, what determines the order?Yes there is a load balancing between two remote Tuxedo TDomain Gateways.
    The algorithm is random, not RR. Over time this should give equal
    opportunities to both remote TDomain.
    >
    2. If it is ONLY Failover, what determines the order of the tpcall? And,
    is the Failover automatic? Or do we need to code for retry on failure?The load balancing is always there. The failover is automatic. When a
    connection to a remote TDomain encountered a problem (ie network) the remote
    domain will be put on retry open connection (in ON_STARTUP) and the load
    balancing will not select it until the connection re-established.
    However, the tpcall() that encountered the error will not be retried to send
    to different destination. It is up to the application to decide whether it
    want to resend. Any requests called after the error will not select the
    failed Remote TDomain.
    >
    3. ON_DEMAND vs ON_STARTUP: Does ON_DEMAND drop the connection to the
    remote domain upon tpterm? And does ON_STARTUP use a pool of
    TuxedoConnection objects?TPTERM() only terminate your application session to WTC. WTC still maintain
    a secured T-session to remote Tuxedo TDomain. WTC does not use a pool of
    TuxedoConnection Objects, the object stored in the JNDI refers to WTC.
    >
    4. Are there any configuration parameters for
    'max_number-of_connections? What determines how many simultaneous
    connections can be made?No. As described in #3, there is no need to use connection pool in WTC. WTC
    uses session and virtual circuit design concept as Tuxedo TDOMAIN, the
    logical pool is created/destroyed dynamically. That is the reason why you
    can have a lot of TPACALL() outstanding at the same time. (The limitation is
    the availability system resource.)
    >
    >
    Thanks,
    Suresh Mohan.Regards,
    Hong-Hsi :-)

  • 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]

  • 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 ..."

  • WLS6.1sp1 stateful EJB problem =   load-balancing and fail over

              I have three problem
              1. I have 2 clustered server. my weblogic-ejb-jar.xml is here
              <?xml version="1.0"?>
              <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN'
              'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
              <weblogic-ejb-jar>
              <weblogic-enterprise-bean>
                   <ejb-name>DBStatefulEJB</ejb-name>
                   <stateful-session-descriptor>
                   <stateful-session-cache>
                        <max-beans-in-cache>100</max-beans-in-cache>
                        <idle-timeout-seconds>120</idle-timeout-seconds>
                   </stateful-session-cache>
                   <stateful-session-clustering>
                        <home-is-clusterable>true</home-is-clusterable>
                        <home-load-algorithm>RoundRobin</home-load-algorithm>
                        <home-call-router-class-name>common.QARouter</home-call-router-class-name>
                        <replication-type>InMemory</replication-type>
                   </stateful-session-clustering>
                   </stateful-session-descriptor>
                   <jndi-name>com.daou.EJBS.solutions.DBStatefulBean</jndi-name>
              </weblogic-enterprise-bean>
              </weblogic-ejb-jar>
              when i use "<home-call-router-class-name>common.QARouter</home-call-router-class-name>"
              and deploy this ejb, exception cause
              <Warning> <Dispatcher> <RuntimeException thrown b
              y rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid: '2903098842
              594628659S:203.231.15.167:[5001,5001,5002,5002,5001,5002,-1]:mydomain:cluster1',
              oid: '9', implementation: 'weblogic.jndi.internal.RootNamingNode@5f39bc''
              java.lang.IllegalArgumentException: Failed to instantiate weblogic.rmi.cluster.B
              asicReplicaHandler due to java.lang.reflect.InvocationTargetException
              at weblogic.rmi.cluster.ReplicaAwareInfo.instantiate(ReplicaAwareInfo.ja
              va:185)
              at weblogic.rmi.cluster.ReplicaAwareInfo.getReplicaHandler(ReplicaAwareI
              nfo.java:105)
              at weblogic.rmi.cluster.ReplicaAwareRemoteRef.initialize(ReplicaAwareRem
              oteRef.java:79)
              at weblogic.rmi.cluster.ClusterableRemoteRef.initialize(ClusterableRemot
              eRef.java:28)
              at weblogic.rmi.cluster.ClusterableRemoteObject.initializeRef(Clusterabl
              eRemoteObject.java:255)
              at weblogic.rmi.cluster.ClusterableRemoteObject.onBind(ClusterableRemote
              Object.java:149)
              at weblogic.jndi.internal.BasicNamingNode.rebindHere(BasicNamingNode.jav
              a:392)
              at weblogic.jndi.internal.ServerNamingNode.rebindHere(ServerNamingNode.j
              ava:142)
              at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
              2)
              at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
              9)
              at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
              9)
              at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
              9)
              at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
              9)
              at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
              So do i must use it or not???
              2. When i don't use "<home-call-router-class-name>common.QARouter</home-call-router-class-name>"
              , there's no exception
              but load balancing does not happen. According to the document , there's must load
              balancing when i call home.create() method.
              my client program goes here
                   DBStateful the_ejb1 = (DBStateful) PortableRemoteObject.narrow(home.create(),
              DBStateful.class);
                   DBStateful the_ejb2 = (DBStateful) PortableRemoteObject.narrow(home.create(3),
              DBStateful.class);
              the result is like that
                   the_ejb1 = ClusterableRemoteRef(203.231.15.167 weblogic.rmi.cluster.PrimarySecon
                   daryReplicaHandler@4695a6)/397
                   the_ejb2 = ClusterableRemoteRef(203.231.15.167 weblogic.rmi.cluster.PrimarySecon
                   daryReplicaHandler@acf6e)/398
                   or
                   the_ejb1 = ClusterableRemoteRef(203.231.15.125 weblogic.rmi.cluster.PrimarySecon
                   daryReplicaHandler@252fdf)/380
                   the_ejb2 = ClusterableRemoteRef(203.231.15.125 weblogic.rmi.cluster.PrimarySecon
                   daryReplicaHandler@6a0252)/381
                   I think the result should be like under one... isn't it??
                   the_ejb1 = ClusterableRemoteRef(203.231.15.167 weblogic.rmi.cluster.PrimarySecon
                   daryReplicaHandler@4695a6)/397
                   the_ejb2 = ClusterableRemoteRef(203.231.15.125 weblogic.rmi.cluster.PrimarySecon
                   daryReplicaHandler@6a0252)/381
              In this case i think the_ejb1 and the_ejb2 must have instance in different cluster
              server
              but they go to one server .
              3. If i don't use      "<home-call-router-class-name>common.QARouter</home-call-router-class-name>",
              "<replication-type>InMemory</replication-type>" then load balancing happen but
              there's no fail-over
              So how can i get load-balancing and fail over together??
              

              I have three problem
              1. I have 2 clustered server. my weblogic-ejb-jar.xml is here
              <?xml version="1.0"?>
              <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN'
              'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
              <weblogic-ejb-jar>
              <weblogic-enterprise-bean>
                   <ejb-name>DBStatefulEJB</ejb-name>
                   <stateful-session-descriptor>
                   <stateful-session-cache>
                        <max-beans-in-cache>100</max-beans-in-cache>
                        <idle-timeout-seconds>120</idle-timeout-seconds>
                   </stateful-session-cache>
                   <stateful-session-clustering>
                        <home-is-clusterable>true</home-is-clusterable>
                        <home-load-algorithm>RoundRobin</home-load-algorithm>
                        <home-call-router-class-name>common.QARouter</home-call-router-class-name>
                        <replication-type>InMemory</replication-type>
                   </stateful-session-clustering>
                   </stateful-session-descriptor>
                   <jndi-name>com.daou.EJBS.solutions.DBStatefulBean</jndi-name>
              </weblogic-enterprise-bean>
              </weblogic-ejb-jar>
              when i use "<home-call-router-class-name>common.QARouter</home-call-router-class-name>"
              and deploy this ejb, exception cause
              <Warning> <Dispatcher> <RuntimeException thrown b
              y rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid: '2903098842
              594628659S:203.231.15.167:[5001,5001,5002,5002,5001,5002,-1]:mydomain:cluster1',
              oid: '9', implementation: 'weblogic.jndi.internal.RootNamingNode@5f39bc''
              java.lang.IllegalArgumentException: Failed to instantiate weblogic.rmi.cluster.B
              asicReplicaHandler due to java.lang.reflect.InvocationTargetException
              at weblogic.rmi.cluster.ReplicaAwareInfo.instantiate(ReplicaAwareInfo.ja
              va:185)
              at weblogic.rmi.cluster.ReplicaAwareInfo.getReplicaHandler(ReplicaAwareI
              nfo.java:105)
              at weblogic.rmi.cluster.ReplicaAwareRemoteRef.initialize(ReplicaAwareRem
              oteRef.java:79)
              at weblogic.rmi.cluster.ClusterableRemoteRef.initialize(ClusterableRemot
              eRef.java:28)
              at weblogic.rmi.cluster.ClusterableRemoteObject.initializeRef(Clusterabl
              eRemoteObject.java:255)
              at weblogic.rmi.cluster.ClusterableRemoteObject.onBind(ClusterableRemote
              Object.java:149)
              at weblogic.jndi.internal.BasicNamingNode.rebindHere(BasicNamingNode.jav
              a:392)
              at weblogic.jndi.internal.ServerNamingNode.rebindHere(ServerNamingNode.j
              ava:142)
              at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
              2)
              at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
              9)
              at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
              9)
              at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
              9)
              at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:36
              9)
              at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
              So do i must use it or not???
              2. When i don't use "<home-call-router-class-name>common.QARouter</home-call-router-class-name>"
              , there's no exception
              but load balancing does not happen. According to the document , there's must load
              balancing when i call home.create() method.
              my client program goes here
                   DBStateful the_ejb1 = (DBStateful) PortableRemoteObject.narrow(home.create(),
              DBStateful.class);
                   DBStateful the_ejb2 = (DBStateful) PortableRemoteObject.narrow(home.create(3),
              DBStateful.class);
              the result is like that
                   the_ejb1 = ClusterableRemoteRef(203.231.15.167 weblogic.rmi.cluster.PrimarySecon
                   daryReplicaHandler@4695a6)/397
                   the_ejb2 = ClusterableRemoteRef(203.231.15.167 weblogic.rmi.cluster.PrimarySecon
                   daryReplicaHandler@acf6e)/398
                   or
                   the_ejb1 = ClusterableRemoteRef(203.231.15.125 weblogic.rmi.cluster.PrimarySecon
                   daryReplicaHandler@252fdf)/380
                   the_ejb2 = ClusterableRemoteRef(203.231.15.125 weblogic.rmi.cluster.PrimarySecon
                   daryReplicaHandler@6a0252)/381
                   I think the result should be like under one... isn't it??
                   the_ejb1 = ClusterableRemoteRef(203.231.15.167 weblogic.rmi.cluster.PrimarySecon
                   daryReplicaHandler@4695a6)/397
                   the_ejb2 = ClusterableRemoteRef(203.231.15.125 weblogic.rmi.cluster.PrimarySecon
                   daryReplicaHandler@6a0252)/381
              In this case i think the_ejb1 and the_ejb2 must have instance in different cluster
              server
              but they go to one server .
              3. If i don't use      "<home-call-router-class-name>common.QARouter</home-call-router-class-name>",
              "<replication-type>InMemory</replication-type>" then load balancing happen but
              there's no fail-over
              So how can i get load-balancing and fail over together??
              

Maybe you are looking for