stop / start duplication (dupmgr) on CM during the day?

[learningSkype]

hi all, i need to refresh duplication between my CM pair.

the commands are:
stop -fs dupmgr
start -s dupmgr

i found some documentation but it doesn't tell me if this is service affecting. can these commands be performed during the day w/out causing an impact to the PBX?

 

[kyle555]

I wouldn't. That's not a way I've ever addressed duplication problems. Misconfiguration, time drift, sure.
Just busy out the standby server and reboot and see what happens.

 

[learningSkype]

ok. thanks for the feedback!

 

[AvayaTier3]

Kyle is correct.

duplicated pnc
duplicated servers
duplicated IPSI boards

Think about it!

What is your hardware platform?
What is your CM software version?

If you can login to Linux bash, post output from following commands from each server:
swversion
server
statapp
pingall -a
lanconfig -q
cat /proc/mdd

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

44 years Bell, AT&T, Lucent, Avaya
Tier 3 for 34 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[learningSkype]

well Avaya themselves put this out. why would they put out this KBA if the best approach is to reboot the server?

https://support.avaya.com/ext/index?page=content&id=SOLN131891

 

[learningSkype]

we're running CM 6.3 on HP dlg360 g8 servers.

 

[dialtonebone]

Does your problem match the exact symptoms and versions listed in the SOLN? If not, then that's why. If it does, then go for it. In my own experience, restarting the dupmgr has never been the path I take. I'm not saying it's wrong or won't work, but it's just not how "we" normally fix these issues.


Post the output like avayatier3 asked and we can probably give more insight.

 

[learningSkype]

swversion
Operating system: Linux 2.6.18-417.AV1xen i686 i686
Built: Feb 7 18:49 2017

Contains: 03.0.141.0
CM Reports as: R016x.03.0.141.0
CM Release String: vcm-016-03.0.141.0
Publication Date: 04 October 2012

UPDATES:
Update ID Status Type Update description
------------------------------- ------------ ------- ---------------------------
03.0.141.0-23681 activated cold 6.3.116.0-SP116


KERNEL-2.6.18-417.AV1 activated cold kernel patch KERNEL-2.6.18-

Platform/Security ID Status Type Update description
------------------------------- ------------ ------- ---------------------------
PLAT-rhel5.3-3021 activated cold RHEL5.3-SSP308

Messaging ID Status Type Update description
------------------------------- ------------ ------- ---------------------------


CM Translation Saved: 2018-01-11 01:03:19

CM License Installed: 2017-08-12 00:47:39

CM Memory Config: Large Survivable

dadmin@[xxxxx> server
SERVER STATUS

Cluster ID: 004
Duplication: sw
Standby Busied? no
Standby Refreshed? no
Standby Shadowing: off
Duplication Link: down
Elapsed Time since Init/Interchange: 12d 02:50:18 (curbs in)

xxxxxxxx xxxxxxx

ID: 007 (2) ID: 006 (1)
Mode: Active Mode: Standby
Major Alarms: yes Major Alarms: no
Minor Alarms: yes Minor Alarms: yes
Control Network: 0 / 7 / 7 Control Network: 0 / 0 / 0
Processor Ethernet: up Processor Ethernet: up
PE Priority: high PE Priority: high
Server Hardware: okay Server Hardware: okay
Processes: okay Processes: okay
dadmin@xxxxxxx> statapp
Watchdog 11/11 UP
TraceLogger 3/ 3 UP
ENV 1/ 1 UP
LicenseServer 2/ 2 UP
SME 10/10 UP
MasterAgent 2/ 2 UP
CMSubAgent 1/ 1 UP
CMLoadAgent 1/ 1 UP
CMFPAgent 2/ 2 UP
INADSAlarmAgent 1/ 1 UP
GMM 4/ 4 UP
SNMPManager 1/ 1 UP
arbiter 2/ 2 UP
filesyncd 8/ 8 UP
dupmgr 3/ 3 UP
MCD 1/ 1 UP
CommunicaMgr 86/86 UP
dadmin@xxxxxxx> pingall -a
Testing..

HostName IPAddress Status
ipsi-A08b 172.17.7.96 Pass
ipsi-A08a 172.17.7.32 Pass
ipsi-A07b 172.17.26.216 Pass
ipsi-A07a 172.17.26.152 Pass
ipsi-A06b 172.17.14.73 Pass
ipsi-A06a 172.17.14.9 Pass
ipsi-A05b 172.17.92.96 Pass
ipsi-A05a 172.17.92.32 Pass
ipsi-A04b 172.17.32.96 Pass
ipsi-A04a 172.17.32.32 Pass
ipsi-A03b 172.17.1.97 Pass
ipsi-A03a 172.17.1.33 Pass
ipsi-A02b 172.17.1.96 Pass
ipsi-A02a 172.17.1.32 Pass
dadmin@xxxxxxx> lanconfig -q
-bash: lanconfig: command not found
dadmin@xxxxxxx> cat /proc/mdd
cat: /proc/mdd: No such file or directory

 

[AvayaTier3]

This is why you should always supply platform and software information with your issue.

The KB article addresses s8730 and cm5 (this is what I based command output on)
Hardware duplication and software duplication are both possible. (some commands do not apply to your problem on your platform)

You have a problem with duplicated system platform servers with which virtual CM duplication works totally different for DL360 G8
with CM duplication over network connections. Yours is also a duplicated ESS server pair.

Do you know the history on this? Has the duplication ever worked or is this a new install?


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

44 years Bell, AT&T, Lucent, Avaya
Tier 3 for 34 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[learningSkype]

thanks for your feedback. Avaya opened the ticket and engaged us so i'll wait to hear from them for next steps.

 

[dialtonebone]

Okay, good luck OP. Can you post the results when you arrive to a solution? This data helps people googling for answers.

 

[learningSkype]

nothing yet, waiting for their feedback.