Dosproul at 15:49, 9 May 2013

2013-05-09T15:49:41Z

← Older revision		Revision as of 15:49, 9 May 2013
Line 33:		Line 33:

	[[Category:Unified_IC,_Release_8.0]]		[[Category:Unified_IC,_Release_8.0]]
		+	[[Category:Unified IC, Release 9.0]]
	[[Category:Cisco Unified Intelligence Center, Release 10.0(1)]]		[[Category:Cisco Unified Intelligence Center, Release 10.0(1)]]

Dosproul at 17:00, 7 May 2013

2013-05-07T17:00:52Z

← Older revision		Revision as of 17:00, 7 May 2013
Line 33:		Line 33:

	[[Category:Unified_IC,_Release_8.0]]		[[Category:Unified_IC,_Release_8.0]]
		+	[[Category:Cisco Unified Intelligence Center, Release 10.0(1)]]

Dosproul: 1 revision

2012-01-17T16:29:07Z

1 revision

← Older revision

Revision as of 16:29, 17 January 2012

Otsatya: Created page with "== System: Loss of functionality when publisher node goes down in multi-node deployments == {| border="1" |- ! '''Problem Summary''' | '''Scheduled Reports''' In the multi-nod..."

2012-01-17T13:07:05Z

Created page with "== System: Loss of functionality when publisher node goes down in multi-node deployments == {| border="1" |- ! '''Problem Summary''' | '''Scheduled Reports''' In the multi-nod..."

New page

== System: Loss of functionality when publisher node goes down in multi-node deployments ==

{| border="1"
|-
! '''Problem Summary'''
| '''Scheduled Reports'''
In the multi-node deployment scenario, all scheduler functions run on the publisher node. Consequently, if the publisher node goes down, jobs that are scheduled to execute during the downtime period do not run. When the publisher comes back up and rejoins the cluster, jobs that are scheduled to run after the restart of the publisher node get executed at the scheduled time, but the jobs scheduled to execute between the crash time and restart time are lost forever.

In addition, when the publisher is down, new schedules can be created by clients logged on to the subscriber nodes, but existing schedules cannot be edited.

Also, clicking the Run Now button on any screen of CUIC when the publisher node is down will result in an error.

'''Cluster Membership Changes'''
When a new CUIC node is added to the cluster, or an existing node is required to be removed from the cluster (say, for maintenance activities), cluster membership change CLI commands need to be first executed on the publisher in order to prepare the CUIC cluster for the addition/deletion of a cluster node. If the publisher node is down, it is not possible to add/delete nodes from the CUIC cluster.

|-
! '''Error Message'''
| '''Scheduled Reports''' Failed: Email not sent
|-
! '''Possible Cause'''
| Publisher node failure
|-
! '''Recommended Action'''
| Restart the publisher.

|-
! '''Release'''
| Release 8.0
|-
! '''Associated CDETS #'''
| None
|}

[[Category:Unified_IC,_Release_8.0]]

System: Loss of functionality when publisher node goes down in multi-node deployments - Revision history

Dosproul at 15:49, 9 May 2013

Dosproul at 17:00, 7 May 2013

Dosproul: 1 revision

Otsatya: Created page with "== System: Loss of functionality when publisher node goes down in multi-node deployments == {| border="1" |- ! '''Problem Summary''' | '''Scheduled Reports''' In the multi-nod..."