Load Balance Network Cards and Fail over services

Hi,
Im looking at setting up 2 MAC server each with basic services (ie AFP, Open Driectory, software updates and DHCP)
Both servers are less then 12 months old and are both attached with GB ports to the RAID where all the user data is stored.
My questions is how to I setup the 2 network interface cards to act as one and load balance the traffic accross both interfaces?
also I was wondering if it was possible to fail over AFP services, so if one server went down the other would pickup file services where it left off?
I know how to fail over OD and the other services dont matter to much.
Thanks in advance for your assistance

My questions is how to I setup the 2 network interface cards to act as one and load balance the traffic accross both interfaces?
This is simple link aggregation in System Preferences -> Network
Click the + button at the bottom and choose new Link Aggregate. Choose the existing interfaces (presumably en0 and en1) and you're set.
Note that this requires support in the switch the server is connected to (it needs to support LACP), and that you will bounce your network connection when you set this up (so don't do it when the server is actively servicing clients)
also I was wondering if it was possible to fail over AFP services, so if one server went down the other would pickup file services where it left off?
It's possible, but you need to be very careful with regards to data integrity. For example, typically each server is going to have a local directory (or directories) that are shared. If Server A fails and Server B takes over, how do you intend to ensure that Server B's data is up-to-date, especially with regard to files that might have been in use at the time?
It's a tricky problem to solve without putting the data on a shared storage device using something like XSAN to manage arbitration, and now you could be talking serious $$$s.
I'd recommend looking closely at your file serving needs and work out if it's necessary, or whether you could get by with dividing the load across servers (e.g. some sharepoints are on one server, other sharepoints on the other) so that only a subset of your users are impacted should one server fail.
File synchronization/replication is a major issue (read $$$$$) for a lot of companies.

Similar Messages

Load balancing not happending but fail over is for Read only Entity beans

          The following are the configuration.
          Two NT servers with WL5.1 sp9 having only EJBs(Read only entity beans)
          One Client with WL5.1 sp9 having servlet/java application as
          EJB client.
          I am trying to make a call like findbyprimarykey in one of the
          entity bean. I could see the request is being directed only to the one of the
          server always. When I bring that server, fail over is happening to the other server.
          Here are the settings I have in the ejb-jar.xml :
                    <entity>
                         <ejb-name>device.StartHome</ejb-name>
                         <home>com.wl.api.device.StartHome</home>
                         <remote>com.wl.api.device.StartRemote</remote>
                         <ejb-class>com.wl.server.device.StartImpl</ejb-class>
                         <persistence-type>Bean</persistence-type>
                         <prim-key-class>java.lang.Long</prim-key-class>
                         <reentrant>False</reentrant>
                         <resource-ref>
                              <res-ref-name>jdbc/wlPool</res-ref-name>
                              <res-type>javax.sql.DataSource</res-type>
                              <res-auth>Container</res-auth>
                         </resource-ref>
                    </entity>
          Here are the settings I have in the weblogic-ejb-jar.xml.
          <weblogic-enterprise-bean>
                    <ejb-name>device.StartHome</ejb-name>
                    <caching-descriptor>
                         <max-beans-in-cache>50</max-beans-in-cache>
                         <cache-strategy>Read-Only</cache-strategy>
                         <read-timeout-seconds>900</read-timeout-seconds>
                    </caching-descriptor>
                    <reference-descriptor>
                         <resource-description>
                              <res-ref-name>jdbc/wlPool</res-ref-name>
                              <jndi-name>weblogic.jdbc.pool.wlPool</jndi-name>
                         </resource-description>
                    </reference-descriptor>
                    <enable-call-by-reference>False</enable-call-by-reference>
                    <jndi-name>device.StartHome</jndi-name>
               </weblogic-enterprise-bean>
          Am I doin any mistake in this?
          Any one's help is appreciated.
          Thanks
          Suresh


we are using 5.1
          "Gene Chuang" <[email protected]> wrote in message
          news:[email protected]...
          > Colocation optimization occurs if your client resides in the same
          container (and also in the same
          > EAR for 6.0) as your ejbs.
          >
          > Gene
          >
          > "Suresh" <[email protected]> wrote in message
          news:[email protected]...
          > > Ok....the ejb-call-by-reference set to true is making the call to one
          server
          > > only. i am not sure why it is. I removed the property name and it
          works.
          > > Also I have one question, in our prduct environment, when i cache the
          ejb
          > > home it is not doing the load balancing. can any one help me for that.
          > > thanks
          > >
          > > Mike,
          > > From the sample pgm I sent, even from single client calls get load
          > > balanced.
          > >
          > > Suresh
          > >
          > >
          > > "Gene Chuang" <[email protected]> wrote in message
          > > news:[email protected]...
          > > > In WL, LoadBalancing will ONLY WORK if you reuse your EJBHome! Take
          your
          > > StartEndPointHome lookup
          > > > out of your for loop and see if this fixes your problem.
          > > >
          > > > I've seen this discussion in ejb-interest, and some other vendor
          (Borland,
          > > I believe it is), brings
          > > > up an interesting point: Clustering and LoadBalance is not in the
          J2EE
          > > specs, hence implementation
          > > > is totally up to the vendor. Weblogic loadbalances from the remote
          > > interfaces (EJBObject, EJBHome,
          > > > etc..), while Borland loadbalances from JNDI Context lookup.
          > > >
          > > > Let me suggest a third implmentation: loadbalance from BOTH Context
          > > lookup as well as stub method
          > > > invocation! Or create a smart replica-aware list manager which
          persists
          > > on the client thread
          > > > (ThreadLocal) and is aware of lookup/evocation history. Hence if I do
          the
          > > following in a client
          > > > hitting a 3 node cluster, I'll still get perfect round-robining
          regardless
          > > of what I do on the
          > > > client side:
          > > >
          > > > InitialContext ctxt = new InitialContext();
          > > > EJBHome myHome = ctxt.lookup(MY_BEAN);
          > > > myHome.findByPrimaryKey(pk); <== hits Node #1
          > > > myHome = ctxt.lookup(MY_BEAN);
          > > > myHome.findByPrimaryKey(pk); <== hits Node #2
          > > > myHome.findByPrimaryKey(pk); <== hits Node #3
          > > > myHome = ctxt.lookup(MY_BEAN);
          > > > myHome.findByPrimaryKey(pk); <== hits Node #1
          > > > ...
          > > >
          > > >
          > > > Gene
          > > >
          > > > "Suresh" <[email protected]> wrote in message
          > > news:[email protected]...
          > > > > Mike ,
          > > > >
          > > > > Do you have any reasons for the total number of machines to be 10.
          > > > >
          > > > > I tried with 7 machines.
          > > > >
          > > > >
          > > > > Here is my sample client java application running individual in the
          > > seven
          > > > > machines.
          > > > >
          > > > > StartEndPointHome =
          > > > > (StartEndPointHome)ctx.lookup("dev.StartEndPointHome");
          > > > > for(;;)
          > > > > {
          > > > > // logMsg(" --in loop "+currentTime);
          > > > > if (currentTime > nextRefereshTime)
          > > > > {
          > > > > logMsg("****- going to call");
          > > > > currentTime=getSystemTime();
          > > > > nextRefereshTime=currentTime+timeInterval;
          > > > > StartEndPointHome =
          > > > > (StartEndPointHome)ctx.lookup("dev.StartEndPointHome");
          > > > > long rndno=(long)(Math.random()*10)+range;
          > > > > logMsg(" going to call remotestub"+rndno);
          > > > > retVal =
          > > > >
          > >
          ((StartEndPointHome)getStartHome()).findByNumber("pe"+rndno+"_mportal_dsk36.
          > > > > mportal.com");
          > > > >
          > > > > logMsg("**++- called stub");
          > > > > }
          > > > >
          > > > >
          > > > >
          > > > > The range value is different for each of the machines in the
          cluster.
          > > > >
          > > > > If the first request starts at srv1, all request starts hitting the
          same
          > > > > server.
          > > > > If the first request starts at srv2, all request starts hitting the
          same
          > > > > server.
          > > > >
          > > > > I have the following for the url , user and pwd values for the
          context
          > > .
          > > > >
          > > > > public static String url="t3://10.11.12.14,10.11.12.117:8000";
          > > > > public static String user="guest";
          > > > > public static String password="guest";
          > > > >
          > > > >
          > > > >
          > > > > It would be great if you could help me.
          > > > >
          > > > > Thanks
          > > > > suresh
          > > > >
          > > > >
          > > > > "Mike Reiche" <[email protected]> wrote in message
          > > > > news:[email protected]...
          > > > > >
          > > > > > If you have only one client don't be surprised if you only hit one
          > > server.
          > > > > Try
          > > > > > running ten different clients and see if the hit the same server.
          > > > > >
          > > > > > Mike
          > > > > >
          > > > > >
          > > > > > "suresh" <[email protected]> wrote:
          > > > > > >
          > > > > > >The following are the configuration.
          > > > > > >
          > > > > > > Two NT servers with WL5.1 sp9 having only EJBs(Read only entity
          > > beans)
          > > > > > >
          > > > > > > One Client with WL5.1 sp9 having servlet/java application as
          > > > > > > EJB client.
          > > > > > >
          > > > > > >
          > > > > > >I am trying to make a call like findbyprimarykey in one of the
          > > > > > >entity bean. I could see the request is being directed only to
          the
          > > one
          > > > > > >of the
          > > > > > >server always. When I bring that server, fail over is happening
          to
          > > the
          > > > > > >other server.
          > > > > > >
          > > > > > >
          > > > > > >Here are the settings I have in the ejb-jar.xml :
          > > > > > > <entity>
          > > > > > > <ejb-name>device.StartHome</ejb-name>
          > > > > > > <home>com.wl.api.device.StartHome</home>
          > > > > > > <remote>com.wl.api.device.StartRemote</remote>
          > > > > > > <ejb-class>com.wl.server.device.StartImpl</ejb-class>
          > > > > > > <persistence-type>Bean</persistence-type>
          > > > > > > <prim-key-class>java.lang.Long</prim-key-class>
          > > > > > > <reentrant>False</reentrant>
          > > > > > > <resource-ref>
          > > > > > > <res-ref-name>jdbc/wlPool</res-ref-name>
          > > > > > > <res-type>javax.sql.DataSource</res-type>
          > > > > > > <res-auth>Container</res-auth>
          > > > > > > </resource-ref>
          > > > > > > </entity>
          > > > > > >
          > > > > > >
          > > > > > >Here are the settings I have in the weblogic-ejb-jar.xml.
          > > > > > >
          > > > > > ><weblogic-enterprise-bean>
          > > > > > > <ejb-name>device.StartHome</ejb-name>
          > > > > > >
          > > > > > > <caching-descriptor>
          > > > > > > <max-beans-in-cache>50</max-beans-in-cache>
          > > > > > > <cache-strategy>Read-Only</cache-strategy>
          > > > > > > <read-timeout-seconds>900</read-timeout-seconds>
          > > > > > > </caching-descriptor>
          > > > > > >
          > > > > > > <reference-descriptor>
          > > > > > > <resource-description>
          > > > > > > <res-ref-name>jdbc/wlPool</res-ref-name>
          > > > > > > <jndi-name>weblogic.jdbc.pool.wlPool</jndi-name>
          > > > > > > </resource-description>
          > > > > > > </reference-descriptor>
          > > > > > > <enable-call-by-reference>False</enable-call-by-reference>
          > > > > > > <jndi-name>device.StartHome</jndi-name>
          > > > > > > </weblogic-enterprise-bean>
          > > > > > >
          > > > > > >
          > > > > > >Am I doin any mistake in this?
          > > > > > >
          > > > > > >Any one's help is appreciated.
          > > > > > >Thanks
          > > > > > >Suresh
          > > > > >
          > > > >
          > > > >
          > > >
          > > >
          > >
          > >
          >
          >

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??

Load-balancing and fail-over between web containers and EJB containers

When web components and EJB components are run in different OC4J instances, can we achieve load-balancing and fail-over between web containers and EJB containers?
null

It looks like there is clustering, but not loadbalancing available for rmi
from the rmi.xml configuration. The application will treat any ejbs on the
cluster as one-to-one look-ups. Orion will go out and get the first ejb
available on the cluster. See the docs on configuring rmi.xml (and also the
note below).
That is a kind-of failover, because if machine A goes down, and the
myotherAejbs.jar are on machine B too, orion will go out and get the bean
from machine B when it can't find machine A. But it doesn't go machine A
then machine B for each remote instance of the bean. You could also specify
the maximum number of instances of a bean, and as one machine gets "loaded",
orion would go to the next available machine...but that's not really
loadbalancing.
That is, you can set up your web-apps with ejbs, but let all of the ejbs be
remote="true" in the orion-application.xml file:
<?xml version="1.0"?>
<!DOCTYPE orion-application PUBLIC "-//Evermind//DTD J2EE Application
runtime 1.2//EN" "http://www.orionserver.com/dtds/orion-application.dtd">
<orion-application deployment-version="1.5.2">
<ejb-module remote="true" path="myotherAejbs.jar" />
<ejb-module remote="true" path="myotherBejbs.jar" />
<ejb-module remote="true" path="myotherCejbs.jar" />
&ltweb-module id="mysite" path="mysite.war" />
... other stuff ...
</orion-application>In the rmi.xml you would define your clustering:
<cluster host="230.0.0.1" id="123" password="123abc" port="9127"
username="cluster-user" />
Tag that is defined if the application is to be clustered. Used to set up
a local multicast cluster. A username and password used for the servers to
intercommunicate also needs to be specified.
host - The multicast host/ip to transmit and receive cluster data on. The
default is 230.0.0.1.
id - The id (number) of this cluster node to identify itself with in the
cluster. The default is based on local machine IP.
password - The password configured for cluster access. Needs to match that
of the other nodes in the cluster.
port - The port to transmit and receive cluster data on. The default is
9127.
username - The username configured for cluster access. Needs to match that
of the other nodes in the cluster.

Recommended configuration for load balanced Portal with load balancer, multiple gateways and multiple servers.

Does anyone have a recommended network, hardware and software configuration guide for a Portal installation running with multiple gateways load balanced (ie one URL) that talk to multiple servers?

David,
We've used Resonate (software) to load balance the gateways. It allows
you to group all the gateways under 1 virtual URL and load balance the
incoming connections over each gateway depending on the rules that you
define in Resonate. Look in the SUN portal whitepapers there is one that
talks about it specifically.
As far as load balancing the calls to the portals, the gateways will
automatically load balance across all the portals that they know about
using a simple round-robin rotation. You may be able to use Resonate in
front of the portals but you may need to activate persistance within
Resonate to ensure that the user always ends up on the portal that he
established his initial connection on (if you want that), check with Sun
on this one.
David Broeren wrote:
Recommended configuration for load balanced Portal with load balancer,
multiple gateways and multiple servers.
Does anyone have a recommended network, hardware and software
configuration guide for a Portal installation running with multiple
gateways load balanced (ie one URL) that talk to multiple servers?
Try our New Web Based Forum at http://softwareforum.sun.com
Includes Access to our Product Knowledge Base!

Hi, I loaded an iTunes card and bought an audiobook a few weeks back! I was unable to download it because my wifi was down, my wifi has just been fixed but now my audiobook purchase is not available but the cash has been taken? Any ideas how to solve this

Hi, I loaded an iTunes card and bought an audiobook a few weeks back! I was unable to download it because my wifi was down, my wifi has just been fixed but now my audiobook purchase is not available but the cash has been taken? Any ideas how to solve this

When I use find file http://www.macupdate.com/app/mac/30073/find-file (which does tend to find files that "Finder" can't), it's not coming up with any other itunes library files that have been modified in the past week, which I know it would have been - unfortunately, I don't have a very recent backup of the hard drive. It would be a few months old so it wouldn't have the complete library on it....any ideas? I'm wondering if restarting the computer might help but have been afraid to do so in case it would make it harder to recover anything...I was looking at this thread https://discussions.apple.com/thread/4211589?start=0&tstart=0 in the hopes that it might have a helpful suggestion but it's definitely a different scenario.

After adding 2nd WiSM and failing over AP's some apps don't work

We have a dual core made up of 2 6513's. In 6513#1 we have WiSM#1 which we have had for sometime now. We have added a 2nd WiSM in 6513#2 for redundancy purposes also we are going to be re-configuring the WiSM in 6513#1 to more match that of the new WiSM in 6513#2. We have installed the new WiSM and failed over the AP's from 6513#1 so we can re-configure it's WiSM. The failover went great and no issues, with the exception that a web application or two didn't function from wireless clients and users were having issues getting to some mapped drives. The only difference from the new WiSM config vs the old WiSM is that on the old WiSM the AP's were in the same VLAN as the controller management interfaces. Now with the new WiSM it's configuration has the controllers AP mgt interfaces ip addresses in a different VLAN from the AP's, we are doing this based on Cisco best practices. If we revert the AP's back to the original WiSM/controllers the PC's where they are on the same vlan/subnet the applications and shares that were having issues the other way work. We have placed a call with Cisco TAC and they say our configs look good and we even sent them some packet captures and they said everything looks normal. The wireless clients can ping and resolve the server hosting the application database just fine.
Thanks

We did create the mobility groups, and we are using DHCP opt 43. The AP's find the 2nd WiSM#2 just fine and associate to the controllers and all the WLAN's work just fine. The only issue is that after the AP's are on the new WiSM and controllers there is an application or 2 that is having trouble locating it's database server and that some share's are not working. Again the only difference in this new setup in that now the AP's are on a different subnet/vlan from the controller mgt addresses where as before they were in the same subnet/vlan and the application and shares worked fine. It's almost like it is a bit of a routing issue?
Thanks

Question about load balancing between Portal and ABAP

Hi,
I have the problem whit load balancing between Portal and ECC (ERC) ABAP
Exist two system:
1) ECC (ERP) ABAP = Backend Module = HR
2) EP (JAVA) = Frontend
The users (9000 users) logon in the EP and run query (data personal) in the ECC. The problem to all user connect in Central Instance and not in the Dialog Instance.
How can balancing the conecction HTTP (EP) to ECC (ABAP)??
I need balancing in the ECC to Dialog Instance

Jco -> right. Another possibility is that you use iviews that point to the backend in this case you will need to use a load balanced entry for the backend system in the [system landscape|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/47/8c1e438d7017fce10000000a42189c/frameset.htm] -> SAP_R3_LoadBalancing
If you have ESS deployed on your portal, you will most probably need to do both.
Cheers Michael

Forms load balancing and fail-over

Using cisco context switches instead of metric server/metric client. Having trouble making forms fail-over when a 9ias server fails. Has anybody done this?
If so, how?

Using cisco context switches instead of metric server/metric client. Having trouble making forms fail-over when a 9ias server fails. Has anybody done this?
If so, how?

Load-Balancing between Foreign and two Anchors

Hi, we have two foreign controllers (one active, one standby) and two anchor controllers. All APs are connected to the active foreign controller. The layer 3 networks for the wlan clients on both anchors are different for the same SSID. SSID: Internet, anchor 1: Subnet A, anchor 2: Subnet B. So when a client is getting anchored to Anchor 1, the clients will get an ip from subnet A and when the client is getting anchored to anchor 2, the client will get an ip from subnet B.
This is so far not a big problem because we only have a few accesspoints in some rooms. But what will happen, when we have a full covered wlan and the client roams from one AP to the other AP? Is there a possibility, that the client will anchored to a different anchor while roaming? I think this will result in a lack of connectivity because without a real disconnect the client will not ask for a new IP address.
Other question: Is it possible to disable this load-balancing between anchor controllers? Or can i make a client sticky to only one anchor as long as an access-session is established?
All controllers are 5760 with 3.3.3 software.

Hi acontes,
It's an interesting question.
In this case, if all AP's are on WLC-A and there is no possibility that an L3 inter-subnet roam will occur between WLC-A and WLC-B, I would just forward WLC-A to Anchor A and WLC-B (in the event of fail over) to Anchor B (if Anchors reside on different subnets). If you must specify Anchor A and Anchor B on each WLC for redundancy purposes, it's important to understand the guidelines and limitations with regard to Foreign / Anchor Design.
As Scott mentioned, the limitation with Anchoring design is that there is no primary / secondary configuration for an Anchor on the Foreign WLC.
If WLC-A has two entries (1) for Anchor-A and (2) for Anchor-B, the EoIP tunnels are establish and load-balancing occurs in a round robin fashion.
Keep in mind the following with regard to guest N+1 redundancy:
•A given foreign controller load balances wireless client connections across the list of anchor controllers configured for the guest WLAN. There is currently no method to designate one anchor as primary with one or more secondary anchors.
•Wireless clients that are associated with an anchor WLC that becomes unreachable are re-associated with another anchor defined for the WLAN. When this happens, assuming web authentication is being used, the client is redirected to the web portal authentication page and required to re-submit their credentials.
Since traffic is transported at Layer 2 via EoIP, the first point at which DHCP services can be implemented is either locally on the anchor controller or the controller can relay client DHCP requests to an external server. Since the IP address directly correlates to the DMZ subnet or the interface where the traffic egresses, it is possible for some clients to get IP's from both Subnet A or Subnet B in the event that WLC-A is building EoIP to both anchors.
1) What happens if my clients roam?
Nothing... since all AP's are on WLC-A, it's Intra-Controller Roaming
Each controller supports same-controller client roaming across access points managed by the same controller. This roaming is transparent to the client as the session is sustained, and the client continues using the same DHCP-assigned or client-assigned IP address. The controller provides DHCP functionality with a relay function. Same-controller roaming is supported in single-controller deployments and in multiple-controller deployments.
Would it be better to choose the same DHCP Pool on both anchors?
It's probably better to have redundant anchors on the same subnet, but it's not required.
3) How would you design this :-)
WLC-A <--EoIP--> Anchor A (DHCP Pool A)
WLC-A <--EoIP--> Anchor B (DHCP Pool A)
It's important to remeber what Scott mentioned about the lack of a primary / secondary relationship. If multiple controllers are added as mobility anchors for a particular WLAN on a foreign controller, the foreign controller internally sorts the controller by their IP address. The controller with the lowest IP address is the first anchor. For example, a typical ordered list would be 172.16.7.25, and 172.16.7.28. If the first client associates to the foreign controller's anchored WLAN, the client database entry is sent to the first anchor controller in the list, the second client is sent to the second controller in the list, and so on, until the end of the anchor list is reached. The process is repeated starting with the first anchor controller.
If any of the anchor controller is detected to be down, all the clients anchored to the controller are deauthenticated, and the clients then go through the authentication/anchoring process again in a round-robin manner with the remaining controller in the anchor list. This functionality is also extended to regular mobility clients through mobility failover. This feature enables mobility group members to detect failed members and reroute clients.

Sun Identity Manger 8.0 and fail over..

We are setting up a fail/recovery site for our Sun Identity Manager solution, I had pictured a seem less fail over, but that looks near impossible to do with oracle database. I had pictured load balanced Appserver, with load balanced data bases, sort of a multi-master like LDAP allows..
Curious what others are using for a fail over site / setup.
Thanks

We're using 7.0. For us failover is basically mulitple servers all using the same DB repository, with a "smart" loadbalancer in front of them (smart meaning, able to detect which back end servers are responsive).
IdM doesn't use any inter-server temp-data synchronization, all the servers running off the same repository communicate by committing changes to the database.
So if a specific IdM instance dies, on the next page load the user will be redirected to a new server. That server will redirect to the login page and ask the user to re-auth, with the desired page placed after login.jsp as a "nextPage" argument. After (re-)logging in, the user's returned to the page they were trying to get to. However, in-progress edits that had not been committed back to the database will be lost.
We looked at high availability arrangements where valid sessions are shared across a new server, but fundamentally the limitation is that the app servers still don't sync in-progress edits, so the only difference between an HA environment and a more passive fail-over environment (like ours) is that in an HA environment the user doesn't have to re-login on a server failure; they still lose in-progress edits. So HA didn't seem like it added value to us.
If you are literally talking about an off-site, completely standby, seamless failover site, I agree I don't see how you would do that. I'd expect that you'd need the offsite setup to be a cold-standby site; configured to use the replicated database, but with the apps powered down until you actually need them. Otherwise, I think you'd have problems with the standby site servers not wanting to "standby". You could ensure no users end up on the standby servers, but background processes are likely to be run across both the primary and the standby services; I don't think you can enforce an "idle but running" status for the standby servers.
Edited by: etech on Feb 4, 2009 7:37 PM

To Load Balance or Not to Load Balance? ISE and F5 Big IP

Currently my team is debating whether to put our two ISE appliances (PSN nodes) behind our F5 load balancing deployment.
Our network is relatively small in size (5K users) with a small wireless deployment (4 Cisco controllers with 300 Access points). Network growth should remain relatively minimal over the coming years.
We will be rolling out wired Dot1X, followed by posture assessment and remediation. (BYOD is not an option).
On one hand, the Big IP features could make it easier for us to perform load balancing, maintenance and troubleshooting.
On the other hand, the Big IP adds another element of complexity into an already complex deployment. We already have the capability to load balance from the switches themselves. Load balancing for wireless should not be an issue as our deployment is very small and I expect it to remain so. Given the size of my environment, there seems to be relatively little to gain for the additional effort and potential pitfalls.
Would anyone care to share their honest opinion on this issue?
Thanks,
Phill

Load balancers are elegant and do their job nicely when it comes to distributing the load between servers. You already have one so I would suggest using it if you have the technical expertise to configure it.
With that being said, if your team is not 100% comfortable with F5 then you should definitely skip it. Instead, you can configure your WLCs to use Node #1 as primary and Node #2 as secondary Radius server and then your Switches to use Node #2 as primary and Node#1 as secondary.
I hope this helps!
Thank you for rating helpful posts!

OracleAS 10g (9.0.4.0.2) Load Balancing Forms, Discoverer and reports

I am having some problems trying to load balance with Oracle Forms, Discoverer and reports Oracle Application Server Release 10g (9.0.4.0.2) and I was wondering if you could help. Has any one ever got this to work consistently? We are an ERP product written mostly in forms (904) and are trying to implement are largest customer there performance issue so we need the load balancing to work. Will also accept other recommendation as cost effective as solutions.
Site 1:
A: SERVER
     Host as1.xyzco.local
     Version 10.1.2.0.2
     Installation Type Identity Management and Metadata Repository
     Oracle Home E:\oracle\inf_1012
     Farm as1db.xyzco.net
o     HTTP_Server
o     Internet Directory
o     OC4J_SECURITY
o     Single Sign-On:orasso
o     Management
B SERVER
     Host as2. xyzco.local
     Version 9.0.4.0.2
     Installation Type Business Intelligence and Forms
     Oracle Home E:\oracle\mid_904
     Farm as2db. xyzco.net
o     Discoverer
o     Forms
o     home
o     HTTP_Server
o     OC4J_BI_Forms
o     Reports Server
o     Web Cache
o     Management
C SERVER
     Host as3. xyzco.local
     Version 9.0.4.0.2
     Installation Type Business Intelligence and Forms Discoverer and Reports
     Oracle Home E:\oracle\mid_904
     Farm as2db. xyzco.net
o     Discoverer
o     Forms
o     home
o     HTTP_Server
o     OC4J_BI_Forms
o     Reports Server
o     Web Cache
o     Management
All servers Are:
     Windows 2003 Standard Server with current service packs
     Xeon Dual Processor with 4GB ram
     Raid 0 drives 2 for OS and 2 for Oracle
Daniel Brody
([email protected])

I have more then half decent results with webcache as load balancer, but it still is a round robin (as mentioned before). This means that a session will not be transfered from one application server to the other once the session has been created.
So far I did not discover any benefits of a hardware loadbalancer over webcache, because (here it is again:) you are not able to transfer open sessions from one application server to the next. This has to do with the Oracle Forms architecture. In fact it is still client-server, only with the application server functioning as extra server ;)

CSS load balance - Lock Outlook 2007 - RPC over http

I have problema whit load balance for configuration of client Outlook 2007. (using protocol RPC over http). Through the CSS, after a period of utilization, the Outlook lock. And without the CSS doind load balance, no ocurred the problem.
I appreciate any help.
Thanks!

Jason,
CSS is not created in a source group of "exchange2007rcvir. Is that the problem is that?
**** OWNER ****
content exchange2007rcvir
vip address 10.58.32.123
add service scmt801cto
add service scmt801cas
redundant-index 205
protocol tcp
advanced-balance sticky-srcip
sticky-inact-timeout 30
active
content exchangehtvir
vip address 10.58.32.89
add service scmt700cto
add service scmt700cas
redundant-index 201
protocol tcp
advanced-balance sticky-srcip
sticky-inact-timeout 30
active
content exchangewavir
vip address 10.58.32.33
add service scmt800cto
add service scmt800cas
redundant-index 51
protocol tcp
advanced-balance sticky-srcip
sticky-inact-timeout 30
active
***** GROUP *****
group exchangehtvir
add destination service scmt700cto
add destination service scmt700cas
vip address 10.58.32.91
active
group grp_axiavir
vip address 10.58.32.83
add destination service scxt393cas
add destination service scxt394cas
add destination service scxt395cas
add destination service scxt393cto
add destination service scxt394cto
add destination service scxt395cto
active
** No have exchange2007rcvir

Load Balancing with OSPF and maximum-paths command

Hello,
Just a quick query really, we have a disribution layer 3 switch, in its routing table it has 3 default routes all with the same metric from the core router, this is because the core router is setup with the comamnd "default-information originate always metric 50" which obviously proagates the default route around the area and the metric never changes from 50.
So i have a routing table that looks like this:
O*E2 0.0.0.0/0 [110/50] via 77.95.176.9, 06:44:51, GigabitEthernet4/9
[110/50] via 77.95.176.17, 06:44:51, Vlan903
[110/50] via 91.203.72.5, 06:44:51, Vlan262
Three default routes with the same metric, does this mean that the router IOS will load balance traffic over all three routes evenly? I mean i have been reading up on it and appartemtly i dont have the command "maximum-paths 3" under my ospf process?
I have been doing some traceroutes from this switch to the internet (various sites) and all the traffic seems to be going out over the first route in the table that next hop is 77.95.176.9
My question is how can i verify that load balancing is taking place, or if its not then i need to add this "maximum-paths 3" command to the ospf on the local switch? I would say load balancing is not taking place but im sure i have seen traffic from one customer being routes over all 3 paths due to matching spikes on the SNMP sensors?
Many Thanks.
Matt

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Yes, your traffic should use all three paths, as Rick notes, OSPF, on Cisco, normally defaults to using up to 4 equal cost paths.
As Rick also notes mentioning CEF, how actual traffic is forwarded across ECMP can vary. Often, the device will keep all traffic for the same flow on the same egress port, and attributes selected for actual egress port selection might be deterministic. I.e. it's possible same traffic flow will always be sent to the same egress port. (This means even with ECMP, you may not see an equal load distribution.)

Load Balance Network Cards and Fail over services

Similar Messages

Maybe you are looking for