Reg Fail over for CCMS

Hi,
I have configured the CEN for CCMS in System A.
Hence System A will monitor Systems X, Y and Z and send me alerts and it is working now
I want to do a failover of CCMS from System A to System B. In other words, if System A fails, only the CCMS should switch over to System B
Please let me know whether this can be achieved. If so please provide me the necessary information
Thanks in Advance

No, I guess it can't be achieved. During failover instances switch to other host, ccms is totally dependent on an instance, is it a seperate third party tool ?..no. then how only ccms The whole instance !

Similar Messages

Fail over for Radius users

Can I put in a second radius address on my As5300 so if the first one goes down the users that are dialing in can be point to the second one with out any interruptions?
TIA

You can do it.
For further information please check the next page:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1830/products_feature_guide09186a00800879e8.html
Bye
FCS
Rate me if I helped.

Replication fail-over and reconfiguration

I would like to get a conversation going on the topic of Replication, I have
setup replication on several sites using the Netscape / iPlanet 4.x server
and all has worked fine so far. I now need to produce some documentation and
testing for replication fail-over for the master. I would like to hear from
anyone with some experience on promoting a consumer to a supplier. I'm
looking for the best practice on this issue. Here is what I am thinking,
please feel free to correct me or add input.
Disaster recovery plan:
1.) Select a consumer from the group of read-only replicas
2.) Change the database from Read-Only to Read-Write
3.) Delete the replication agreement (in my case I am using a SIR)
4.) Create a new agreement to reflect the supplier status of the chosen
replica (again a SIR for me)
5.) Reinitialize the consumers (Online or LDIF depending on your number of
entries)
That is the general plan so far. Other questions and topics might include:
1.) What to do when the original master comes back online
2.) DNS round-robin strategies (Hardware assistance, Dynamic DNS, etc)
3.) General backup and recovery procedures when: 1.) Directory is corrupted
2.) Link is down / network is partitioned 3.) Disk / server corruption /
destruction
Well I hope that is a good basis for getting a discussion going. Feel free
to email me if you have questions or I can help you with one of your issues.
Best regards,
Ray Cormier

There is no failover in Meta-Directory 5.1, you can implement manual failover on the metaview by using multi-master replication with Directory Server. There are limitations and this is a manual process.
- Paul

Weblogic Admin server fail over

Hi,
Please let me know if there is a official documentation from Oracle for admin server fail over for version 8.x, 9.x & 10.x?

I am not sure if there is something as weblogic Admin Server Failover
For Managed Server failover please read
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/cluster/failover.html

Requirements on an EJB to be eligible for a fail-over

Hi all,
          I was reading the EJB developer guide for weblogic server 9.2. When talking about the fail-over feature the guide said
          "EJB failover requiers that bean methods must be idempotent and configured as such in weblogic-ejb-jar.xml"
          There are two points in this statement.
          1) Fail overs must be configured
          This is straight forward.
          2) The bean methods must be idempotent.
          I don't really understand this point. Does this suggest that the bean methods should conform to some guide lines? If so what are they?
          Probably these are clarified in some other document or other resources. Being impatient and a little lazy I would love to have this clarified in the forum.
          Thanks in advance,
          - Madhu

Daniel,
I think since this will be the ONLY system that will be running as a DC providing ADDS and the Direct access server, i should follow this advice from the article you sent:
For users who never connect directly to the Contoso intranet or through a VPN, they must use the DirectAccess
Offline Domain Join process to initially join the appropriate domain and configure DirectAccess. When this process
is complete, the users log on normally and have the same experience as if they were directly connected to the Contoso intranet.
Because remember, no user will ever connect directly to the subnet where the server is. so do an offline join First and then start managing.. Only thing im worried about is: they keep saying that the direct access function has significantly improved in windows
8. hmmmmm many systems will be using windows 7 Pro 64Bit. Some windows 8.1 Pro 64bit. should i worry?

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

Fail-over options for Standalone Print Server

Our organization recently set up 3 2012 r2 Print Servers to handle 3 separate sites. Each printer server contains only the printers within the site - which makes each server a standalone print server. I'm concern with the issue of not
having a fail-over plan in place, in the event one of my server should fail. Does anyone have any fail-over suggestions.

Hi Thomas,
If we want to create a clustered printer server, we need to created another print server in the same site.
For detailed information, please refer to the link below:
https://technet.microsoft.com/en-us/library/cc771091.aspx
Best Regards.
Steven Lee 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]

Multiple j-sessions for IOP fail-over?

Weblogic has the ability to support multiple j-sessions to allow fail-over of the connection.
My understanding is that this is not currently supported in IOP.
When will IOP support multiple j-sessions?
Is it possible to get a patch for this in the current version 11 of IOP?
Thank you.

That is part of the product roadmap to support multiple j-sessions for IOP fail over using Weblogic. That way, if the primary IOP server fails, the user can be re-routed to the backup server in a high-availability fashion. However, that is not supported currently, but will be over the next couple of releases.

Support for fail over/clustering?

Is there any support for fail over/clustering Oracle on a two-node Linux cluster? Is it even possible to run Oracle on a two-node Linux cluster?

To add more, I'm unsure whether an HA product is even needed once Oracle Releases Parallel Server. Also, is it possible to run Oracle w/o Parallel Server on a cluster? If so, what does that buy you?

Replicating router partitions for Fail/Over ?

Hi everyone,
Is it really worth the value to replicate a router partition on the same
node ?
In other words, has anyone ever seen a router partition failing on its
own (eg due
to an out of memory), ie not because of the node failure ?
What I am looking for is to avoid wasting system resources for unneeded
replicates.
Thanks.
Vincent Figari

You will use Active/Standby failover method to keep your fail-over configuration in secondary firewall (PIX).
Active/Standby Failover lets you use a standby security appliance to take over the functionality of a failed unit. When the active unit fails, it changes to the standby state while the standby unit changes to the active state. The unit that becomes active assumes the IP addresses (or, for a transparent firewall, the management IP address) and MAC addresses of the failed unit and begins to pass traffic. The unit that is now in standby state takes over the standby IP addresses and MAC addresses. Because network devices see no change in the MAC to IP address pairing, no ARP entries change or time out anywhere on the network. PIX Security Appliance with 7.x version and above supports failover.
For further information click this link.
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00807dac5f.shtml#regu

ACE MIB Value for Fail over

Hi,
May I know the MIB value ACE (Application Contril Engine )will be generating while a fail over occurs. Is the value same for contetx fail over as well ??
Regards
Jithesh

Hi,
I think this is the error code your looking for;
727012
Error Message %ACE-2-727012: HA: FT Group group ID changed state to NewState. Reason:
reason str.
Table 2-2 NewState Values and Descriptions
NewState Value
Description
FSM_FT_STATE_INIT
The initial state. Visible only when the configuration for the FT group exists but it is not in service.
FSM_FT_STATE_ELECT
After you enter the inservice command when you are configuring an FT group, the ACE enters the ELECT state. The redundancy state machine negotiates with its peer context in the FT group to determine the redundancy role (active or standby)
FSM_FT_STATE_ACTIVE
The active member of the FT group.
FSM_FT_STATE_STANDBY_COLD
This state can be entered if:
•FT VLAN is down but the peer device is still alive.
•Configuration or application state synchronization failure have occurred.
FSM_FT_STATE_STANDBY_CONFIG
The standby context is waiting to receive configuration information. Upon entering this state, the active context will be notified to send a copy of the running configuration.
FSM_FT_STATE_STANDBY_BULK
The standby context is waiting to receive state information. Upon entering this state, the active context will be notified to send a copy of the current states information for all applications.
FSM_FT_STATE_STANDBY_HOT
The standby context is ready to become active in a failover situation.
Values returned for the reason str variable can be one of the following:
•FSM_FT_EV_PEER_DOWN
•FSM_FT_EV_PEER_FT_VLAN_DOWN
•FSM_FT_EV_PEER_SOFT_RESET
•FSM_FT_EV_STATE
•FSM_FT_EV_TIMEOUT
•FSM_FT_EV_CFG_SYNC_STATUS
•FSM_FT_EV_BULK_SYNC_STATUS
•FSM_FT_EV_COUP
•FSM_FT_EV_RELINQUISH
•FSM_FT_EV_TRACK_STATUS
•FSM_FT_EV_UPDATE
•FSM_FT_EV_ENABLE_INSERVICE
•FSM_FT_EV_DISABLE_INSERVICE
•FSM_FT_EV_SWITCHOVER
•FSM_FT_EV_PEER_COMPATIBLE
•FSM_FT_EV_MAINT_MODE_OFF
•FSM_FT_EV_MAINT_MODE_PARTIAL
•FSM_FT_EV_MAINT_MODE_FULL
Check from the above ID onwards for more details around ft status.
Cheers
Scott

Fail over possible for 9i db, using Veritas VCS bet 32bit and 64 bit

Folks,
We are planning to use 9i R2 (9.2.0.2.0) on
Sun Solaris, using Veritas VCS .
Can we have one OS as Solaris 32 bit and
the fail over box as Solaris 64 bit.
Thanks
Ashish

Follow up question -
I am able to successfully fail over the ABAP portion of the ABAP+J2EE environment we have. This is done by altering the profile parameters in the DEFAULT profile to reflect the cluster alias rather than the actual host name.
But in the confitool of the J2EE, there are some fields that have the actual hostname hardcoded. These are in the DB, so they are host independent:
Global Disp. config>managers>ClusterManger:
ms.host = <host>
Global Disp. config>managers>LockingManger:
enq.profile.filename = /usr/sap/<SID>/SYS/profile/<SID>_DVEBMGS##_host
enqu.host = <host>
Global Server Config>managers>Cluster Manager:
ms.host = <host>
Global Server Config>managers>Locking Manager:
enq.profile.filename = /usr/sap/<SID>/SYS/profile/<SID>_DVEBMGS##_host
enqu.host = <host>
I suspect I can change the physical host names to the alias, but how can the J2EE know which profile to look at based on what physical host it's running on? ABAP knows by just reading the profile that has the real host name in it.

Help : Cluster Fail over Test - Could not establish a connection

Hi All
          I'm trying to do Cluster fail over test with two Weblogic 8.1 sp2 instances in cluster.
          During that testing, I'm restarting the one of the instance which is handing my request, to make sure the session is replicated smoothly to the other instance,so that can continue accessing my application without any interuption. But when I restart the instance, I'm getting following exception
          Error 500--Internal Server Error
          java.rmi.ConnectException: Could not establish a connection with 8909815174098071019S:dappsn03:[8201,8201,-1,-1,8201,-1,-1,0,0]:dappsn03-04:TNL:tnl1_81dappsn03, java.rmi.ConnectException: Destination unreachable; nested exception is:
               java.net.ConnectException: Connection refused; No available router to destination
               at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:316)
               at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:488)
               at weblogic.rjvm.RJVMImpl.getOutboundRequest(RJVMImpl.java:584)
               at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:91)
               at weblogic.rmi.internal.activation.ActivatableRemoteRef.invoke(ActivatableRemoteRef.java:69)
               at com.sns.pfk.ejb.PfkSessionBean_mz6mqm_EOImpl_812_WLStub.getPortalRecord(Unknown Source)
               at com.sns.pfk.servlet.PfkMainServlet.getInfofromSB(Unknown Source)
               at com.sns.pfk.servlet.PfkMainServlet.doActionDisplay(Unknown Source)
               at com.sns.pfk.servlet.PfkMainServlet.doGet(Unknown Source)
               at com.sns.pfk.servlet.PfkMainServlet.doPost(Unknown Source)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
               at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
               at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:607)
               at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:400)
               at com.sns.ana.ui.servlet.AuthorisationBaseServlet.service(AuthorisationBaseServlet.java:109)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
               at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
               at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
               at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
               at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          Buddies, anyone hit this issue before, pls show up some light to escape this hickup.
          With Regs
          -SHAN

Hi,
          Thanx for ones, spend time on reading this thread.This problem was due to some missing entries in weblogic-ejb.xml. This got fixed as we got support from BEA.
          With Regs
          -SHAN

SQL Server 2014 Always on HA takes 8-14 seconds to fail over. Application side timeouts occur

Hi All,
I have a very similar post in the SQL Server 2014 forums too (https://social.technet.microsoft.com/Forums/sqlserver/en-US/adb5e338-907e-4405-aa62-d3ea93c7a98a/sql-server-2014-always-on-ha-takes-814-seconds-to-fail-over-application-side-timeouts-occur?forum=sqldisasterrecovery) -
advice in the end was to post a question here.
SQL Server Nodes, 2014 (12.0.2480.0)
1 Share witness (on separate subnet)
1 Cluster
1 Listener
I have been testing the response time to failovers – both manual (right-click, fail over in SSMS) and Automatic (shut down the primary host). The way I am testing response is to have a SSMS query running on my desktop, connected to the listener querying
a small table and hit execute.
The Query response time, from execute to receiving the result, has been between 8 and 14 seconds based on my testing. My previous experience (in a separate environment) showed around 2 second fail over times in a very similar configuration.
Availability DB is 200Mb and is not actively used. The nodes are synchronised.
SQL Server Hosts: Windows 2012, 2 cpu, 8gb RAM.
Questions:
1: It’s a big question but what should I expect for a ‘normal’ fail over time. Keep in mind this scenario is about as simple as it gets.
2: As it stands an 8 to 14 second ‘outage’ could cause some applications to time out. Or am I being un-reasonable? I am seeing the very simple query in SSMS to time out with this:
Msg 983, Level 14, State 1, Line 2
Unable to access availability database 'DATABASE' because the database replica is not in the PRIMARY or SECONDARY role. Connections to
an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation again later.
Cluster logs are long - this section accounts for 8 seconds of the 11 second outage I experienced. I can supply the full log if required. Also this log is just the 2 cluster nodes, I removed the witness share to make sure it was as simple as possible.
00001090.00002128::2015/02/25-03:05:08.255 INFO [GEM] Node 2: Deleting [1:65 , 1:71] (both included) as it has been ack'd by every node
00001ee4.00002130::2015/02/25-03:05:10.107 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
00001090.00002128::2015/02/25-03:05:11.888 INFO [GEM] Node 2: Deleting [1:72 , 1:73] (both included) as it has been ack'd by every node
00001090.00002698::2015/02/25-03:05:11.889 INFO [GUM] Node 2: Processing RequestLock 2:49
00001090.00002128::2015/02/25-03:05:11.890 INFO [GUM] Node 2: Processing GrantLock to 2 (sent by 1 gumid: 67)
00001090.00002698::2015/02/25-03:05:11.890 INFO [GUM] Node 2: executing request locally, gumId:68, my action: /dm/update, # of updates: 1
00001090.00002128::2015/02/25-03:05:12.890 INFO [GEM] Node 2: Deleting [1:74 , 1:74] (both included) as it has been ack'd by every node
00001ee4.00002130::2015/02/25-03:05:15.107 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
00001090.00002128::2015/02/25-03:05:16.988 INFO [GUM] Node 2: Processing RequestLock 1:28
Thanks in advance.
Keegan

Hi Keegan,
From these event log , what I can see is "Sending request Netname" wasted the time .
Could you please tell us the network configuration of that cluster nodes ?
If I recall correctly , it is recommended to only remain Tcp/IP protocol and disable NetBIOS over TCP/IP for "Private Network" , also do not configure DNS/Wins default gateway for "Private Network" :
https://support.microsoft.com/kb/258750?wa=wsignin1.0
After that please test again .
Best Regards,
Elton JI
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 Subscriber Support, contact [email protected] .

Front End pool failed over

Hi all,
1. I setup a pool with three Front End servers (FQDN of pool is pool.site1.sip96x2.com and it's pointed to IP address of three Front End servers). Everything works fine. But When I disable network interface on FE1 and FE2, the Lync clients are disconnected.
I haven't understood clearly how the Lync clients failed over in a pool? Please clarify to me.
2. I have two central site (Root site and Primary site, they have different domain sip96x2.com and site1.sip96x2.com). The simple URL dialin is pointed to Front End server at Root site. So if the link between Root site and Primary site is down, how can the
users at Primary site connect to dialin URL?
3. In building topology for Front End pool, I checked Override FQDN internal web service and the FQDN is "poolint.site1.sip96x2.com". I created three A records "poolint.site1.sip96x2.com" and pointed to three IP addresses of Front End
servers. Is it right?
Thanks so much!

Ah ok, well first thing if I am reading this correctly, pool pairing Standard with Enterprise is not supported. You should only pair Standard with Standard and Enterprise with Enterprise (even though topology builder won't stop you) Take a look here for
support scenarios http://technet.microsoft.com/en-us/library/jj204697.aspx
To deal with the simple URLs in the event of failover you need to add them using Powershell. Take a look at this article which explains and gives an example: http://blogs.perficient.com/microsoft/2012/01/configuring-simple-urls-for-multiple-lync-pools/
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
Georg Thomas | Lync MVP
Blog www.lynced.com.au | Twitter
@georgathomas
Lync Edge Port Check (Beta)

Reg Fail over for CCMS

Similar Messages

Maybe you are looking for