CER 7.1(1) utils dbreplication status

Jason Aarons · ‎02-13-2010

For the sake of Google and helping others, here is what a good Cisco Emergency Responder 7.1.1 database replication

status looks like.

CER Database Replication

from CER publisher here is what a good utils dbreplication status should look like

admin:utils dbreplication status

-------------------- utils dbreplication status --------------------
Output is in file /var/log/active/er/trace/dbl/sdi/ReplicationStatus.2010_02_13_09_19_28.out

Please use "file view activelog er/trace/dbl/sdi/ReplicationStatus.2010_02_13_09_19_28.out " command to see the output
admin:
admin:file view activelog er/trace/dbl/sdi/ReplicationStatus.2010_02_13_09_19_28.out

SERVER                 ID STATE    STATUS     QUEUE CONNECTION CHANGED
-----------------------------------------------------------------------
g_cer001_cer7_1_1_10000_5    2 Active   Local           0
g_cer002_cer7_1_1_10000_5    3 Active   Connected       0 Feb 11 08:55:12

end of the file reached
options: q=quit, n=next, p=prev, b=begin, e=end (lines 1 - 4 of 4) :
admin:

Andy Backus · ‎05-16-2012

You are absolutely correct on this one.

Spent all night on this one (with TAC). You are correct, the only db replication indicator in CER (8.0) it seems is the "status" option. No Cisco Reported, no "utils replication runtime". We saw your post but had no other corroberation. Funny, we all see status should =2 but not for this command (even in CCM, it should show '3 Active' if just pub and sub).

Thanks for the post.

wdejulio312 · ‎07-11-2014

I too have scratched my head on this one when seeing the 3 there. Thanks for the post.

Warner

rogerholdman · ‎08-23-2016

same on v9

SERVER ID STATE STATUS QUEUE CONNECTION CHANGED
-----------------------------------------------------------------------
g_usbpcer01_cer9_0_2_10000_1 2 Active Local 0
g_usshkcer01_cer9_0_2_10000_1 3 Active Connected 0 Jul 31 18:34:26

rogerholdman · ‎01-16-2017

same on v11

admin:file view activelog er/trace/dbl/sdi/ReplicationStatus.2017_01_16_19_54_29.out

Mon Jan 16 19:54:29 2017 main() DEBUG: -->
Mon Jan 16 19:54:30 2017 main() DEBUG: Replication cluster summary:
SERVER ID STATE STATUS QUEUE CONNECTION CHANGED
-----------------------------------------------------------------------
g_2_cer11_0_1_10000_3 2 Active Local 0
g_3_cer11_0_1_10000_3 3 Active Connected 0 Jan 16 18:16:50
Mon Jan 16 19:54:31 2017 main() DEBUG: <--

end of the file reached