IPCC Failover issue

I have 2 IPCC 7.x server configured for failover. The issue is when I am logged into my agent and my primary server failsover to backup server, my agent looses connection/goes offline and reconnects in not ready after 15 seconds. The same applies if I failback from my secondary to primary server.
Is this a normal behaviour ? Is there a document on cisco that describes the same issue. Please let me know.
Thanks

Not sure with IPCC Enterprise, but IPCC Express (or UCCX nowadays) the behavior you are reporting is expected. From the design guide:
Automatic Failover. Upon failure of the active Cisco Unified CCX server, CAD will automatically re-login agents on the standby server, and the agent will be placed into a Not Ready state. Upon failure of the active Cisco Unified CCX server, active calls on agents phones will survive. However, the call duration and other information that is associated with the call in the historical reporting database may be affected. Historical reports generated for time periods in which a failover occurred will have missing or incorrect data. It will be called out in the report that a failover occurred.
http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_7_0/design/guide/uccx70srnd.pdf (page 25 of the pdf)
It should also be noted that with UCCX, failback to the primary node (when it comes back on line) isn't automatic. Mainly because the failback will exhibit the same behavior (along with an approximate 5 second hit on ACD/IVR functionality). So, the failback should be manual - in my experience anyway.
HTH.
Regards,
Bill
Please remember to rate helpful posts.

Similar Messages

IPCC Resiliency issue - Dummy PG Setup

Hi All,
We have IPCC 7.0 (SR4) geographically distributed setup for resiliency. The Rogger, Agent PG, IP IVR, CCM are distributed across 2 different sites.
Currently there are 2 PG's (PG1 - CCM & IP IVR PIM's, PG2 - MRPG) installed in the Agent PG Servers at both sites. The MR PG is currently out of Service and we are not in a position to start the service currently, but we do not want to remove it either.
Since PG2 is not in service, we are facing problem that the Router failover (to Router B) does not work. We understand from previous postings that installing Dummy PG is the solution to resolve the IPCC resiliency issue.
The question is ...is there a limitation from Cisco that the maximum number of PG's which can installed per server is 2..?.Can we install the 3rd PG on the same physical server (Agent PG), since we have the MR PG out of Service, we can install and start the 3rd PG ( Dummy PG) which we believe will resolve the resiliency issue. Will Cisco come back saying that this is an un-supported configuration..?.
We have busy call routers and other servers in the setup and hence any other systems in the current setup cannot be considered for Dummy PG installation.
Appreciate your suggestions in this regard.

Hi,
Have you considered disabling the PIM on PG2 and starting it so that it connects to the router so you have 2 PG's connected? Then when you are ready just enable the PIM on PG2. This would save installing a 3rd dummy PG.
Whether you can have 3 PG's or not on a server will depend on the specification of the hardware. A dummy PG would not take up much processor or memory as it would not have a PIM enabled.
Cheers,
JD

Weblogic Migrateable Server JSM client failover issue

Hello.
I am experiencing a failover issue with JMS client (i am using wlfullclient.jar)
I've setup a migratable JMS Server (My cluster contains 2 servers: ManagedServer1 and ManagedServer2) and created a module with Sub Deployment to this server. On the module i created Queue and Topic.
Whenever i forecfully ManagedServer2 (That is where JMS Server resides), JMS Client fails to reconnect with the following exception.
How come dispatcher does not try to connect to ManagedServer1, and keeps trying to connect to ManagedServer2?
weblogic.jms.common.JMSException: Error creating session
     at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
     at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:45)
     at weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:2914)
     at weblogic.jms.client.JMSSession.setupConsumer(JMSSession.java:2687)
     at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:2628)
     at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:2608)
     at weblogic.jms.client.WLSessionImpl.createConsumer(WLSessionImpl.java:880)
     at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.createConsumer(AbstractPollingMessageListenerContainer.java:477)
     at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.createListenerConsumer(AbstractPollingMessageListenerContainer.java:221)
     at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.initResourcesIfNecessary(DefaultMessageListenerContainer.java:1005)
     at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:981)
     at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:974)
     at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:876)
     at java.lang.Thread.run(Thread.java:619)
Caused by: weblogic.jms.common.JMSException: Error creating session
     at weblogic.jms.frontend.FESession.setUpBackEndSession(FESession.java:745)
     at weblogic.jms.frontend.FESession.consumerCreate(FESession.java:963)
     at weblogic.jms.frontend.FESession.invoke(FESession.java:2931)
     at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
     at weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServerRef.java:276)
     at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:141)
     at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
     at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.messaging.dispatcher.DispatcherException: could not find Server ManagedServer2
     at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:176)
     at weblogic.messaging.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherManager.java:58)
     at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreate(JMSDispatcherManager.java:219)
     at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreateChecked(JMSDispatcherManager.java:230)
     at weblogic.jms.frontend.FESession.setUpBackEndSession(FESession.java:743)
     ... 9 more
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:ManagedServer2'. Resolved 'weblogic.messaging.dispatcher'; remaining name 'S:ManagedServer2'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
     at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
     at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:172)
     ... 13 more

I am not shutting down both the managed server. Only the first managed server is shut down. As the portal ear is deployed both on admin server and all the managed servers in the cluster, I should be able to access the application through the second managed server.

Cisco ASA 5505 Failover issue..

Hi,
I am having two firewalls (cisco ASA 5505) which is configured as active/standby Mode.It was running smoothly for more than an year,but last week the secondary firewall got failed and It made my whole network down.then I just removed the connectivity of the secondary firewall and run only the primary one.when I login by console i found out that the failover has been disabled .So again I connected to the Network and enabled the firewall.After a couple of days same issue happen.This time I take down the Secondary firewall erased the Flash.Reloaded the IOS image.Configured the failover and connected to the primary for the replication of configs.It found out the Active Mate.Replicated the configs and got synced...But after sync the same thing happened,The whole network gone down .I juz done the same thing removed the secondary firewall.Network came up.I feel there is some thing with failover thing ,but couldnt fin out :( .And the firewalls are in Router Mode.

Please find the logs...
Secondary Firewall While Sync..
cisco-asa(config)# sh failover
Failover On
Failover unit Secondary
Failover LAN Interface: e0/7 Vlan3 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 4 of 23 maximum
Version: Ours 8.2(5), Mate 8.2(5)
Last Failover at: 06:01:10 GMT Apr 29 2015
This host: Secondary - Sync Config
Active time: 55 (sec)
slot 0: ASA5505 hw/sw rev (1.0/8.2(5)) status (Up Sys)
Interface outside (27.251.167.246): No Link (Waiting)
Interface inside (10.11.0.20): No Link (Waiting)
Interface mgmt (10.11.200.21): No Link (Waiting)
slot 1: empty
Other host: Primary - Active
Active time: 177303 (sec)
slot 0: ASA5505 hw/sw rev (1.0/8.2(5)) status (Up Sys)
Interface outside (27.251.167.247): Unknown (Waiting)
Interface inside (10.11.0.21): Unknown (Waiting)
Interface mgmt (10.11.200.22): Unknown (Waiting)
slot 1: empty
=======================================================================================
Secondary Firewall Just after Sync ,Active (primary Firewall got rebootted)
cisco-asa# sh failover
Failover On
Failover unit Secondary
Failover LAN Interface: e0/7 Vlan3 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 4 of 23 maximum
Version: Ours 8.2(5), Mate Unknown
Last Failover at: 06:06:12 GMT Apr 29 2015
This host: Secondary - Active
Active time: 44 (sec)
slot 0: ASA5505 hw/sw rev (1.0/8.2(5)) status (Up Sys)
Interface outside (27.251.167.246): Normal (Waiting)
Interface inside (10.11.0.20): No Link (Waiting)
Interface mgmt (10.11.200.21): No Link (Waiting)
slot 1: empty
Other host: Primary - Not Detected
Active time: 0 (sec)
slot 0: empty
Interface outside (27.251.167.247): Unknown (Waiting)
Interface inside (10.11.0.21): Unknown (Waiting)
Interface mgmt (10.11.200.22): Unknown (Waiting)
slot 1: empty
==========================================================================================
After Active firewall got rebootted failover off,whole network gone down.
cisco-asa# sh failover
Failover Off
Failover unit Secondary
Failover LAN Interface: e0/7 Vlan3 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 4 of 23 maximum
===========================================================================================
Primary Firewall after rebootting
cisco-asa# sh failover
Failover On
Failover unit Primary
Failover LAN Interface: e0/7 Vlan3 (Failed - No Switchover)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 4 of 23 maximum
Version: Ours 8.2(5), Mate Unknown
Last Failover at: 06:17:29 GMT Apr 29 2015
This host: Primary - Active
Active time: 24707 (sec)
slot 0: ASA5505 hw/sw rev (1.0/8.2(5)) status (Up Sys)
Interface outside (27.251.167.246): Normal (Waiting)
Interface inside (10.11.0.20): Normal (Waiting)
Interface mgmt (10.11.200.21): Normal (Waiting)
slot 1: empty
Other host: Secondary - Failed
Active time: 0 (sec)
slot 0: empty
Interface outside (27.251.167.247): Unknown (Waiting)
Interface inside (10.11.0.21): Unknown (Waiting)
Interface mgmt (10.11.200.22): Unknown (Waiting)
slot 1: empty
cisco-asa# sh failover history
==========================================================================
From State To State Reason
==========================================================================
06:16:43 GMT Apr 29 2015
Not Detected Negotiation No Error
06:17:29 GMT Apr 29 2015
Negotiation Just Active No Active unit found
06:17:29 GMT Apr 29 2015
Just Active Active Drain No Active unit found
06:17:29 GMT Apr 29 2015
Active Drain Active Applying Config No Active unit found
06:17:29 GMT Apr 29 2015
Active Applying Config Active Config Applied No Active unit found
06:17:29 GMT Apr 29 2015
Active Config Applied Active No Active unit found
==========================================================================
cisco-asa#
cisco-asa# sh failover state
State Last Failure Reason Date/Time
This host - Primary
Active None
Other host - Secondary
Failed Comm Failure 06:17:43 GMT Apr 29 2015
====Configuration State===
====Communication State===
==================================================================================
Secondary Firewall
cisc-asa# sh failover h
==========================================================================
From State To State Reason
==========================================================================
06:16:32 GMT Apr 29 2015
Not Detected Negotiation No Error
06:17:05 GMT Apr 29 2015
Negotiation Disabled Set by the config command
==========================================================================
cisco-asa# sh failover
Failover Off
Failover unit Secondary
Failover LAN Interface: e0/7 Vlan3 (down)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 4 of 23 maximum
ecs-pune-fw-01# sh failover h
==========================================================================
From State To State Reason
==========================================================================
06:16:32 GMT Apr 29 2015
Not Detected Negotiation No Error
06:17:05 GMT Apr 29 2015
Negotiation Disabled Set by the config command
==========================================================================
cisco-asa# sh failover state
State Last Failure Reason Date/Time
This host - Secondary
Disabled None
Other host - Primary
Not Detected None
====Configuration State===
====Communication State===
Thanks...

Ipsec Stateful Failover issue with Dynamic-Map

Hi all, I have an issue with a couple of Cisco ISR 2921 in Ha Ipsec Stateful Failover configuration.
With static crypto-map, stateful works good, Ipsec sessions are correctly trasmitted from Cisco Active router to Cisco Standby router.
With dynamic-map and profile, stateful fails, Ipsec sessions are not correctly trasmitted from Cisco Active router to Cisco Standby router.
I tried different IOS version:152-1.T3, 152-3.T2 and 153-1.T but I have the same behavior.
Could you help me?
Marco

Yes it is supported. It is supprted on VAM, VMA2, VAM2+.

Pool Master server failover issue in Oracle VM 2.2.1

Hello All , We are new to oracle VM world. Sorry about detailed explanation.
Our current configuration is, server1-poolmaster/utility/VM server & Server2-utility/VM server
We have guest-VM running on both servers, and serverpool-VIP is configured properly. Below is our OVS-version.
#rpm -qa | grep -i ovs
oracle-logos-4.9.17-7ovs
enterprise-linux-ovs-5-1.0
ovs-release-2.2-1.0
ovs-utils-1.0-34
kernel-ovs-2.6.18-128.2.1.4.25.el5
ovs-agent-2.3-42
When we tested HA failover(shutting down server1), it work fine as expected. Pool master moved from server1 to server2, and guest VM restarted on server-2(which was running on server1 earlier).
Now-- Pool master is server2.
When we shutdown server2 now, pool master is not migrated to server1 & the guest-VMs(running on server 2) all went to power-off mode & serverpool is "inactive status'.
Found below error in server1's /var/log/messages.. It seems like some 'dead-lock situation, and the serverpool-VIP is not moved from server2 to server1, until server2 came up online". Why is it so? The expected result should be "pool-master" & serverpool-VIP should moved to server1, but it didnt.
Anyone experienced this? Any help/ input is appreciated.
log file from server1's /var/log/ovs-agent/ovs_remaster.log
2011-01-14 01:47:56 INFO=> run(): release_master_dlm_lock ...
2011-01-14 01:48:02 INFO=> run(): release_master_dlm_lock ...
2011-01-14 01:48:08 INFO=> run(): release_master_dlm_lock ...
2011-01-14 01:48:14 INFO=> run(): release_master_dlm_lock ...
2011-01-14 01:48:20 INFO=> run(): release_master_dlm_lock ...
2011-01-14 01:48:26 INFO=> run(): release_master_dlm_lock ...
***** At this time its waiting to release the server pool-VIP on server 2
*** Once server2 came online, serverpool-VIP released and taken by server1***
2011-01-14 01:54:11 INFO=> cluster_get_next_master: => {"status": "SUCC", "value": "10.24.60.41"}
2011-01-14 01:54:11 INFO=> run(): cluster_get_next_master: => {"status": "SUCC", "value": "10.24.60.41"}
2011-01-14 01:54:13 INFO=> run(): clusterm_setup_master_env: => {"status": "SUCC"}
2011-01-14 01:54:20 INFO=> run(): i am the new master. vip=10.24.60.45
truncated logs from server1's /var/log/messages
Jan 14 01:46:40 fwblade1 kernel: ocfs2_dlm: Node 1 leaves domain 70FFE4CF84634F5DB61BEA66E04693A7
Jan 14 01:46:40 fwblade1 kernel: ocfs2_dlm: Nodes in domain ("70FFE4CF84634F5DB61BEA66E04693A7"): 0
Jan 14 01:47:59 fwblade1 kernel: ocfs2_dlm: Node 1 leaves domain ovm
Jan 14 01:47:59 fwblade1 kernel: ocfs2_dlm: Nodes in domain ("ovm"): 0
Jan 14 01:48:55 fwblade1 kernel: o2net: connection to node fwblade2.wg.kns.com (num 1) at 10.24.60.42:7777 has been idle for 30.0 second
s, shutting it down.
Jan 14 01:48:55 fwblade1 kernel: (0,0):o2net_idle_timer:1503 here are some times that might help debug the situation: (tmr 1294987705.66
5702 now 1294987735.663612 dr 1294987705.665695 adv 1294987705.665724:1294987705.665725 func (53ed487f:505) 1294987705.665424:1294987705
.665428)
Jan 14 01:48:55 fwblade1 kernel: o2net: no longer connected to node fwblade2.wg.kns.com (num 1) at 10.24.60.42:7777
Jan 14 01:48:55 fwblade1 kernel: (5190,0):dlm_send_remote_lock_request:333 ERROR: status = -112
Jan 14 01:48:55 fwblade1 kernel: (5186,2):dlm_send_remote_lock_request:333 ERROR: status = -107
Jan 14 01:48:55 fwblade1 kernel: (5190,0):dlm_send_remote_lock_request:333 ERROR: status = -107
Jan 14 01:48:55 fwblade1 kernel: (5186,2):dlm_send_remote_lock_request:333 ERROR: status = -107
** the above messages is repeated till server1 came online ***
Jan 14 01:48:57 fwblade1 kernel: (4694,2):dlm_drop_lockres_ref:2211 ERROR: status = -107
Jan 14 01:48:57 fwblade1 kernel: (4694,2):dlm_purge_lockres:206 ERROR: status = -107
Jan 14 01:48:57 fwblade1 kernel: (4694,2):dlm_drop_lockres_ref:2211 ERROR: status = -107
Jan 14 01:48:57 fwblade1 kernel: (4694,2):dlm_purge_lockres:206 ERROR: status = -107
Jan 14 01:49:30 fwblade1 kernel: (4651,0):ocfs2_dlm_eviction_cb:98 device (253,0): dlm has evicted node 1
Jan 14 01:49:30 fwblade1 kernel: (32373,0):dlm_get_lock_resource:844 78CD07B6D4C34CEAB756BF56E6D9C561:M00000000000000000002182aa14db5: a
t least one node (1) to recover before lock mastery can begin
** Still no sign of server1 taking up the serverpool-VIP, all the guest-VM are still power-off status***
Jan 14 01:49:35 fwblade1 kernel: (4695,0):dlm_get_lock_resource:844 78CD07B6D4C34CEAB756BF56E6D9C561:$RECOVERY: at least one node (1) to
recover before lock mastery can begin
Jan 14 01:49:35 fwblade1 kernel: (4695,0):dlm_get_lock_resource:878 78CD07B6D4C34CEAB756BF56E6D9C561: recovery map is not empty, but mus
t master $RECOVERY lock now
Jan 14 01:49:35 fwblade1 kernel: (4695,0):dlm_do_recovery:524 (4695) Node 0 is the Recovery Master for the Dead Node 1 for Domain 78CD07
B6D4C34CEAB756BF56E6D9C561
** still no luck.. all guest VM are down***
Jan 14 01:53:59 fwblade1 kernel: (5186,1):dlm_send_remote_lock_request:333 ERROR: status = -92
Jan 14 01:53:59 fwblade1 kernel: (5190,10):dlm_send_remote_lock_request:333 ERROR: status = -92
Jan 14 01:53:59 fwblade1 kernel: (5186,1):dlm_send_remote_lock_request:333 ERROR: status = -92
Jan 14 01:53:59 fwblade1 kernel: (5190,10):dlm_send_remote_lock_request:333 ERROR: status = -92
Jan 14 01:53:59 fwblade1 kernel: (5186,1):dlm_send_remote_lock_request:333 ERROR: status = -92
Jan 14 01:54:00 fwblade1 kernel: (5190,10):dlm_send_remote_lock_request:333 ERROR: status = -92
Jan 14 01:54:00 fwblade1 kernel: (5186,1):dlm_send_remote_lock_request:333 ERROR: status = -92
Jan 14 01:54:00 fwblade1 kernel: ocfs2_dlm: Node 1 joins domain 78CD07B6D4C34CEAB756BF56E6D9C561
Jan 14 01:54:00 fwblade1 kernel: ocfs2_dlm: Nodes in domain ("78CD07B6D4C34CEAB756BF56E6D9C561"): 0 1
Jan 14 01:54:00 fwblade1 kernel: (5190,10):dlmlock_remote:269 ERROR: dlm status = DLM_IVLOCKID
Jan 14 01:54:00 fwblade1 kernel: (5190,10):dlmlock:747 ERROR: dlm status = DLM_IVLOCKID
Jan 14 01:54:00 fwblade1 kernel: (5190,10):ocfs2_lock_create:997 ERROR: DLM error DLM_IVLOCKID while calling dlmlock on resource F000000
000000000000a50dd279960c: bad lockid
Jan 14 01:54:00 fwblade1 kernel: (5190,10):ocfs2_file_lock:1584 ERROR: status = -22
Jan 14 01:54:00 fwblade1 kernel: (5190,10):ocfs2_do_flock:79 ERROR: status = -22
Jan 14 01:54:00 fwblade1 kernel: (5186,1):dlmlock_remote:269 ERROR: dlm status = DLM_IVLOCKID
Jan 14 01:54:00 fwblade1 kernel: (5186,1):dlmlock:747 ERROR: dlm status = DLM_IVLOCKID
Jan 14 01:54:00 fwblade1 kernel: (5186,1):ocfs2_lock_create:997 ERROR: DLM error DLM_IVLOCKID while calling dlmlock on resource F0000000
00000000000a50dd279960c: bad lockid
Jan 14 01:54:00 fwblade1 kernel: (5186,1):ocfs2_file_lock:1584 ERROR: status = -22
Jan 14 01:54:00 fwblade1 kernel: (5186,1):ocfs2_do_flock:79 ERROR: status = -22
Jan 14 01:54:05 fwblade1 kernel: ocfs2_dlm: Node 1 joins domain 70FFE4CF84634F5DB61BEA66E04693A7
Jan 14 01:54:05 fwblade1 kernel: ocfs2_dlm: Nodes in domain ("70FFE4CF84634F5DB61BEA66E04693A7"): 0 1
** Now server2 came online(old pool-master) and server-pool-VIP is moved to server1.** All guest-VM are restarted on SERVER2 itself.
Thanks
Prakash

You might be running into a OCFS2 bug. Check the bug list for bug 1099
http://oss.oracle.com/bugzilla/show_bug.cgi?id=1099
also related to this subject might be bug 1095 and 1080. You might want to check with the OCFS2 guys at Oracle and participate in resolving this bug. Not sure this is the case however I think this is a good starting point.
Please keep us posted.
Regards,
Johan Louwers.

TAF Failover issue when RAC node shutdown

Dear all,
We have a two-node RAC database. We use sqlplus from a client laptop to test RAC TAF failover when one node is being shutdown. And there's a tnsnames.ora file with TAF settings in the client laptop.
First we connect to RAC database via sqlplus, when we are under the "SQL>" command prompt, we type " select instance_name from v$instance; " and we can see what instance we truely connect to. Then we shutdown the node we truely connect to; At the meanwhile, if we type "select instance_name from v$instance;" again right away, sometimes the sqlplus hangs and with no response; but if we wait utill the VIP failover to another node then type "select instance_name from v$instance;" we can see it always show the other node's instance name and we know the session is successfully failover to the healthy node.
My question is :
Does RAC TAF failover can always and "no down time" failover the session to another healthy node? Or there are some circumstances that the session would hang and need to connect again?
Any help would be appreciated.

Hi, thanks for your help.
There are many things you have to do but if you don't have the knowledge will be difficult.Right. The cluster was setup by consultants but we're still trying to pick up basic Oracle knowledge by self study...
Found some messages about eviction in old cssd logs in $ORA_CRS_HOME/log/cssd/. Will further dig into it.
Yes, we tried rebooting different nodes many times in the clusters before, without any problem.
Thanks a lot.
/ST Wong

DHCP and failover issues

Hello,
I am trying to implement failover in our dhcp but I don't get it right....
I have 2 SLES/OES servers both can be used as DHCP server without failover (one active, the other not).
server 1 => SLES11SP1 with OES11 (dhcp version is 3.1.3 ESV)
server 2 => SLES11SP2 with OES11SP1 (dhcp version is 4.2.4-P2)
I have defined my failover dhcp services following TID 7004294, so I have defined to services (ip_serv1 and ip_serv2), each failover service does contain:
a) failover object ( FO2SERV2, FO2SERV1), where
Primary server is 10.7.0.248 10.7.0.248
Primary port is 647 847
Secondary server is 10.7.0.250 10.7.0.250
Secondary port is 847 647
Failover split is 128 128
Max. Client Lead Time 3600 3600
b) subnet 10.11.0.0 10.11.0.0 where these subnets have following pool
c) pool pool_10_11 pool_10_11 and these have the following failover attached to
FO2SERV2 FO2SERV1
I think that these parameter follow precisly the TID 7004294, but when I start the dhcpd services on the primary server I get the following messages:
I move from recover to startup
I move from startup to recover
DHCPDISCOVER from 00:23:24:07:84:53 (REFERENCE) via XXX.XXX.XXX.XXX: not responding (recovering)
and indeed I do not get any lease.
What am I doing wrong????
Any suggestions?
Thanks in advance

Originally Posted by ricard1
Finally I got it!!.
First I upgraded one of my servers to same release level as the second
Then I defined the Failover Objects with the same name as you suggested and using the same port (in my case 847).
That did the trick.
Thanks!
PS. it is a shame that some TID's are so wrong as this one (TID7004294).
Please provide TID feedback on the bottom of the page: https://www.novell.com/support/kb/doc.php?id=7004294
Thomas

Can you help? Two dialer interfaces with IP SLA for default route failover - issues

I have an issue with a Cisco 2821, it has an ADSL2+ HWIC whose ATM interfaces is linked to dialer 1 and a Gi0/1 interface with a pppoe client which is linked to dialer 2. Both dialer interfaces are up with their respective IP addresses. If the ADSL on dialer 1 fails i want the IP SLA to kick and and replace the default route for dialer 1 with one for dialer 2.
This config works if you manually shut down the dialer 1 interface, it injects the default route for dialer 2 and then when you unshut the interface, the default route for dialer 1 comes back. The problem i have is if you take out the cable for the ATM interface and take it down, it does not take the route out the routing table and the default route for dialer2, which works if you just shut down dialer 1 does not appear.
whats the difference between shutting down dialer1 and it fails over the default route and taking the cable out then it does not?
Here is my config, i'm sure its something simple i'm doing wrong, can anyone help???
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname Router
boot-start-marker
boot-end-marker
logging message-counter syslog
enable secret 5 $1$qOOJ$HV5AH6US/YZMuCGPYp3pP.
no aaa new-model
dot11 syslog
ip source-route
ip cef
ip dhcp excluded-address 192.168.0.1
ip dhcp pool pool1
network 192.168.0.0 255.255.255.0
default-router 192.168.0.1
dns-server 188.92.232.50 188.92.232.100
no ip domain lookup
no ipv6 cef
multilink bundle-name authenticated
voice-card 0
no dspfarm
archive
log config
hidekeys
track 1 ip sla 1 reachability
interface GigabitEthernet0/0
description Gi0/30 Local LAN
ip address 192.168.0.1 255.255.255.0
ip verify unicast reverse-path
no ip redirects
no ip unreachables
no ip proxy-arp
ip flow ingress
ip nat inside
ip virtual-reassembly
no ip mroute-cache
duplex auto
speed auto
snmp trap ip verify drop-rate
no mop enabled
interface GigabitEthernet0/1
no ip address
duplex auto
speed auto
pppoe enable group global
pppoe-client dial-pool-number 2
interface ATM0/2/0
description ATM0_DSL
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
ip flow ingress
logging event atm pvc state
logging event subif-link-status
no atm ilmi-keepalive
dsl operating-mode auto
dsl enable-training-log
pvc 0/38
encapsulation aal5mux ppp dialer
dialer pool-member 1
interface Dialer1
ip address negotiated
no ip redirects
no ip unreachables
no ip proxy-arp
ip mtu 1492
ip nat outside
ip virtual-reassembly
encapsulation ppp
dialer pool 1
keepalive 1 3
no cdp enable
ppp lcp predictive
ppp authentication pap chap callin
ppp chap hostname ********@ccsleeds.net
ppp chap password 0 ********
ppp pap sent-username *******@ccsleeds.net password 0 ********
interface Dialer2
ip address negotiated
no ip redirects
no ip unreachables
no ip proxy-arp
ip mtu 1492
encapsulation ppp
dialer pool 2
keepalive 1 3
no cdp enable
ppp lcp predictive
ppp authentication pap chap callin
ppp chap hostname **********@adsllogin.co.uk
ppp chap password 0 *********
ppp pap sent-username *********@adsllogin.co.uk password 0 ***********
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 Dialer1 track 1
ip route 0.0.0.0 0.0.0.0 Dialer1
ip route 0.0.0.0 0.0.0.0 Dialer2 10
no ip http server
no ip http secure-server
ip nat inside source list 1 interface Dialer1 overload
ip sla 1
icmp-echo 8.8.8.8 source-interface di1
timeout 1000
threshold 100
frequency 3
ip sla schedule 1 life forever start-time now
access-list 1 permit 192.168.0.0 0.0.0.255
control-plane
gatekeeper
shutdown
line con 0
line aux 0
line vty 0 4
password test
login
scheduler allocate 20000 1000
end

Sure that EEM can shut/unshut interface...you have "event track" in EEM for monitoring track events...for example:
event manager applet test
event track 1 state down
action 1.0 command "enable"
action 1.1 command "conf t"
action 1.2 command "interfac dialer 1"
action 1.3 command "shut"
action 1.4 syslog "Dialer 1 down!!!"
action 1.5 end
This would be an example from head :)
You would need another EEM similar to this one for unshutting interface with "event track 1 state up" for bringing interface up again.
Again as I said you would need to test this before putting in production and you would maybe need to tweak this a little bit acording to your needs...
BR,
Dragan

Etherchannel Failover issue

I have cisco 2960s switch stacked at my DC site and one 2960s cisco switch at DR site
There are two fiber links from DC to DR site
I have configured etherchannel LACP on both sides.
The fiber links are terimiated to the switches from media converter on both DC and DR site
While testing,
when any one port of etherchannel is shutdown, the traffic flowing from that link takes upto 100 seconds to transfer to another link
For Example
At DC site Gi1/0/24 and Gi2/0/24 are configured in etherchannel
At DR site Gi1/0/23 and Gi1/0/24 are configured in etherchannel
Gi1/0/24 (DC) and Gi1/0/23 (DR) are connected with one fiber link (Link1) with media converter in between
Gi2/0/24 (DC) and Gi1/0/24 (DR) are connected with another fiber link (Link2) with media converter in between
Testing
When Gi1/0/24 is shutdown (Link1 is down), then the traffic switchover to Link2 takes upto 100 seconds
When Gi2/0/24 is shutdown (Link2 is down), then the traffic switchover to Link1 takes upto 100 seconds
Why it takes so much time during switchover?
Kind Regards
Arbin Maharjan

That does seem like an inordiantely long time for traffic to recover. I suspect there are issues besides just LACP at work here. Spanning-tree (and possibly routing) may be involved.
Have you tried turning on a debug during your testing (e.g., debug lacp all) to confirm the LACP recovery is operating as intended?
Also, in the larger context, I am a bit surprised to see you using 2900 series (entry level Catalyst switches) with external media converters for something so business-critical as DR. Is there a reason why you're not using more of an enterprise-class solution like Nexus or Catalyst 6500 series with a prupose-built technology like OTV?
Hope thi shelps.

Radware Failover issue

Hi all,
Currently i am having two radware Web Server Director Pro AS, Cookie Persistency (512 farms).
While configuring VRRP through APsolute insite we got an error while copying configuration from master to backup.
Kindly suggest the solution to proceed further . Below is the error :
There is no corresponding display value in MIB label rsWSDServerBackupPreemption for value: #InvalidValue (0) (valid values are: disable,enable)
Please suggest what is the issue !

Although i guess radware is not a topic in CSC, i would suggest it is some error with the MIB. maybe you have on older version of the MIB inside your APsolute insite. The error seems to say that your Application is trying to change a MIB-value with the wrong things.

Failover issue

Hi Guys,
I have a setup like this:
A central WLC 5508 running code 7.2 with management vlan 10 ( range 10.10.10.0/24), corp-user vlan 100 (10.11.10.0/24) with WPA2 key, guest vlan 200 (192.168.0.0/24, on local dsl modem) with WPA2 key...
A remote WLC 5508 with code 7.2 with managment vlan 10 (range 10.20.10.0/24), corp-user vlan 101 (10.21.10.0/24) with WPA2 key and guest vlan 201 ( 192.168.0.0/24, on local dsl modem) with WPA2 key
corp ssid "Corp-user" on both sites
Guest ssid "Guest" on both sites
Intention is that the AP's (3500) on the remote site should failover to the central WLC in case of any failure on the remote WLC and that the users could remain in their local vlan.
What kind of configuration would make this work?

Scott,
The remote site AP ports are trunked (in our case tagged on HP switches) and vlan support on the flexconnect (H-Reap) tab is enabled with native vlan (should it give a problem that the native vlan id's are the same on both sites?) and the rest of the vlan mapping...
On the central WLC I created an ap goup for the remote site AP's but how should I map the ssid's on the central WLC to the remote vlan's?
Thanks again for your support,

VPN Failover ISSUe

I am currentlyworking on a Site-to-Site VPN deployment that is suppose to failover between aprimary ISP and Secondary ISP link. Such that when the primary link fails, iVPN tunnel should be setup with the backup link as seen in the config below.no ip domain lookupno ipv6 cef!multilinkbundle-name authenticated!!!crypto pkitrustpoint TP-self-signed-3774726989enrollmentselfsignedsubject-namecn=IOS-Self-Signed-Certificate-3774726989revocation-checknonersakeypairTP-self-signed-3774726989!!crypto pkicertificate chain TP-self-signed-3774726989certificateself-signed 013082022B 30820194A0030201 02020101 300D0609 2A864886 F70D0101 0505003031312F30 2D06035504031326 494F532D 53656C66 2D536967 6E65642D 4365727469666963 6174652D33373734 37323639 3839301E 170D3134 30383037 3131353733335A17 0D32303031303130 30303030 305A3031 312F302D 06035504 03132649...
This topic first appeared in the Spiceworks Community

I am currentlyworking on a Site-to-Site VPN deployment that is suppose to failover between aprimary ISP and Secondary ISP link. Such that when the primary link fails, iVPN tunnel should be setup with the backup link as seen in the config below.no ip domain lookupno ipv6 cef!multilinkbundle-name authenticated!!!crypto pkitrustpoint TP-self-signed-3774726989enrollmentselfsignedsubject-namecn=IOS-Self-Signed-Certificate-3774726989revocation-checknonersakeypairTP-self-signed-3774726989!!crypto pkicertificate chain TP-self-signed-3774726989certificateself-signed 013082022B 30820194A0030201 02020101 300D0609 2A864886 F70D0101 0505003031312F30 2D06035504031326 494F532D 53656C66 2D536967 6E65642D 4365727469666963 6174652D33373734 37323639 3839301E 170D3134 30383037 3131353733335A17 0D32303031303130 30303030 305A3031 312F302D 06035504 03132649...
This topic first appeared in the Spiceworks Community

SRW224G4 VLAN and G1/G2 failover issues

Our SRW224G4 details
HW ver: 00.03.00
Boot ver: 1.0.2
FW ver: 1.2.2b
Here is a picture of our back 2 back setup. We are trying to send a time sensitive audio traffic and IP traffic over a GbE link,
We assigned audio traffic (port e1) to VLAN 2 and all other ports 2-24 are in default vlan 1.
issue 1:
As long as we dont connect IP traffic, audio traffic is good. The moment, we connect IP traffic the audio traffic latency increases beyond acceptable level.
The total bandwidth we use is well below 200 Mbps of 1Gbps.
How do we make sure that VLAN2 (audio traffic on e1) gets high priority so regardless of IP traffic present or not present
on other ports, the latency would remain same for audio traffic?
Issue 2:
We have assigned VLAN 1 and 2 to both G1 and G2. We are trying to accomplish a cable redundancy with G1 and G2.
G1 and G2 are configured as trunk and tagged on VLAN setup.
How do we confgure G1 and G2 ports in such a way that only one is active at any time. If the active port fails, then the other port should take over the traffic?
Thanks in advance for any help.

Thanks for your reply.
We tried following with QoS.
1. Assigned CoS 7 (highst priority) to Q4
2. E1 (audio traffic VLAN 2) assigned CoS 7
3. All other ports on CoS 0
Queue priority tried for strict and WRR - no luck
Bandwidth - we tried to assign E1 for ingress 100 Mbps - no luck
We tried to assign E7 - IP traffic for 25 Mbps ingress and egress - no luck
It would be great if some one can shpw how to do VLAN based QoS settings (if it is supported). Basically, we would like to
have the audio traffic on VLAN 2 - highest priority and all other ports (VLAN 1) lowest priority.
Thanks again for any help.

SCOM Agent Failover Issue

We have SCOM 2012 R2 with two Management server , around 200 agent reports to Ist Management server and 50 to management server 2. Once our management server 1 is down , agent reports to Management server 1 is not moved to MS2 , however agents still
shows health in MAnagement server 1 itself ? Any idea why?

Hi 74KMS,
When an Agent is installed and configured to report to a Management Server, it is automatically configured to fail over to ANY other Management Servers. Failover behavior can be configured
via PowerShell scripts or AD Integration. NOTE: Windows agents do NOT report to a resource pool in OpsMgr 2012
http://blogs.catapultsystems.com/cfuller/archive/2012/06/05/how-does-the-failover-process-work-in-opsmgr-2012-scom-sysctr.aspx
Faizan

IPCC Failover issue

Similar Messages

Maybe you are looking for