[SR-Users] kamailio-5.0.5 active/passive pcs/cluster with rtpengine - how to fix calls after failover

[Karsten Horsmann]

Hello Daniel,
hello List,

for a better understanding i attached the "pcs status" and "pcs config"
output -
to show up how things are located and colocated.
It maybe also nice for other people that try to do the same.

The Services rtpengine_service and kamailio_service running always on the
same box.
The same is for the external ip (kamailio_vip_ext) and the internal ip
(kamailio_vip_int).

[root at sipedge1 ~]# pcs status
Cluster name: viercom_sipedge_office_cluster1
Stack: corosync
Current DC: sipedge1 (version 1.1.16-12.el7_4.4-94ff4df) - partition with
quorum
Last updated: Fri Jan  5 10:59:31 2018
Last change: Fri Jan  5 10:59:28 2018 by root via cibadmin on sipedge1

2 nodes configured
4 resources configured

Online: [ sipedge1 sipedge2 ]

Full list of resources:

 kamailio_vip_ext       (ocf::heartbeat:IPaddr2):       Started sipedge1
 kamailio_vip_int       (ocf::heartbeat:IPaddr2):       Started sipedge1
 kamailio_service       (systemd:kamailio):     Started sipedge1
 rtpengine_service      (systemd:rtpengine):    Started sipedge1

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled

[root at sipedge1 ~]# pcs config
Cluster Name: viercom_sipedge_office_cluster1
Corosync Nodes:
 sipedge1 sipedge2
Pacemaker Nodes:
 sipedge1 sipedge2

Resources:
 Resource: kamailio_vip_ext (class=ocf provider=heartbeat type=IPaddr2)
  Attributes: cidr_netmask=29 ip=212.XX.XX.XX nic=bond0
  Operations: monitor interval=10s (kamailio_vip_ext-monitor-interval-10s)
 Resource: kamailio_vip_int (class=ocf provider=heartbeat type=IPaddr2)
  Attributes: cidr_netmask=24 ip=172.20.YY.YY
  Operations: monitor interval=10s (kamailio_vip_int-monitor-interval-10s)
 Resource: kamailio_service (class=systemd type=kamailio)
  Operations: monitor interval=10s timeout=30s
(kamailio_service-monitor-interval-10s)
              start interval=0 on-fail=restart timeout=30s
(kamailio_service-start-interval-0)
 Resource: rtpengine_service (class=systemd type=rtpengine)
  Operations: monitor interval=10s timeout=30s
(rtpengine_service-monitor-interval-10s)
              start interval=0 on-fail=restart timeout=30s
(rtpengine_service-start-interval-0)

Stonith Devices:
Fencing Levels:

Location Constraints:
  Resource: kamailio_service
  Resource: rtpengine_service
Ordering Constraints:
  start kamailio_vip_ext then start kamailio_service (kind:Mandatory)
  start kamailio_vip_int then start kamailio_service (kind:Mandatory)
  start kamailio_vip_int then start rtpengine_service (kind:Mandatory)
  start kamailio_vip_ext then start rtpengine_service (kind:Mandatory)
Colocation Constraints:
  Resource Sets:
    set kamailio_vip_int kamailio_service kamailio_vip_ext kamailio_service
kamailio_vip_int rtpengine_service kamailio_vip_ext rtpengine_service
setoptions score=INFINITY
Ticket Constraints:

Alerts:
 No alerts defined

Resources Defaults:
 No defaults set
Operations Defaults:
 No defaults set

Cluster Properties:
 cluster-infrastructure: corosync
 cluster-name: viercom_sipedge_office_cluster1
 dc-version: 1.1.16-12.el7_4.4-94ff4df
 have-watchdog: false
 no-quorum-policy: ignore
 stonith-enabled: false

Quorum:
  Options:




-- 
Kind Regards
*Karsten Horsmann*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20180105/1de1b105/attachment.html>