AnsweredAssumed Answered

Testing to Configure Enterprise Manager Failover to Work on a Single Host   [linux box]

Question asked by shamal96 on Nov 10, 2015
Latest reply on Dec 8, 2015 by shamal96

Testing to Configure Enterprise Manager Failover to Work on a Single Host   [APM 9.6 in linux box]

 

Goal: To mimic to Configure Enterprise Managers [MOM1 &MOM2] Failover in separate box sharing same smarstor data.

Validation: Primary MOM1 [after restart] to regain control once failed over to Secondary MOM2 

 

mom1  EM properties

introscope.enterprisemanager.port.channel1=5001

introscope.enterprisemanager.webserver.port=8081

introscope.enterprisemanager.failover.enable=true

introscope.enterprisemanager.failover.primary=localhost

introscope.enterprisemanager.failover.secondary=

 

mom2 EM properties

introscope.enterprisemanager.port.channel1=6001

introscope.enterprisemanager.webserver.port=8083

introscope.enterprisemanager.failover.enable=true

introscope.enterprisemanager.failover.primary=localhost

introscope.enterprisemanager.failover.secondary=

 

collector1 EM properties

introscope.enterprisemanager.port.channel1=8001

introscope.enterprisemanager.webserver.port=8082

 

MOM1 & MOM2 shared followings [smartstor data,traces],

introscope.enterprisemanager.smartstor.directory=/var/SHARED/data

introscope.enterprisemanager.threaddump.storage.dir=/var/SHARED/threaddumps

introscope.enterprisemanager.dbfile=/var/SHARED/data/baselines.db

introscope.enterprisemanager.smartstor.directory.archive=/var/SHARED/data/archive

introscope.enterprisemanager.transactionevents.storage.dir=/var/SHARED/traces

 

Observation:

 

1. Primary MOM1 connects to collector and list agents fine as expected

2. Started secondary MOM2  [executed ’./Introscope_ Enterprise_ Manager]   but log shows [it starting as  another Primary MOM]

 

11/09/15 09:16:44.166 AM PST [INFO] [main] [Manager.HotFailover] The Introscope Enterprise Manager is configured as a Primary EM

11/09/15 09:16:44.167 AM PST [INFO] [main] [Manager.HotFailover] Acquiring secondary lock...

11/09/15 09:16:44.168 AM PST [INFO] [main] [Manager.HotFailover] Acquired secondary lock

11/09/15 09:16:44.168 AM PST [INFO] [main] [Manager.HotFailover] Acquiring primary lock...

11/09/15 09:16:44.168 AM PST [INFO] [main] [Manager.HotFailover] Acquired primary lock

11/09/15 09:16:44.168 AM PST [INFO] [main] [Manager.HotFailover] Released secondary lock

11/09/15 09:16:44.169 AM PST [INFO] [main] [Manager.HotFailover] Proceeding with startup

 

3. Stopping MOM1 fails over to secondary MOM2 as exepcted

4. Restarting MOM1 does not take control back but  just starts as another   Primary MOM e.g. step 2

 

MOM Failover without relying on OS/HW is informative  so  tried for single host scenario.

 

Hoping to identify my misstep

cheers!!

Outcomes