Hello!
I have two hardware MSE appliance with 7.2.110 version.
They are successfully paired in HA with automatic Failover and automatic Failback.
Automatic Failover works fine, but automatic Failback doesn't happen without administrator intervention.
The failover/failback scenario:
1) Primary server is powered off
2) The secondary MSE takes the primary role (Current state: FAILOVER_ACTIVE)
3) When the primary MSE boots up, the automatic Failback doesn't happen.
It is mentioned, that automatic failback happens after 30 minutes of sucessful ping from Sec to Prim MSE.
After bootup from Primary MSE console it is seen that Health Monitor is not running
[root@MSE]# /etc/init.d/msed status
STATUS:
Health Monitor is not running
Automatic Failback cannot happen while Health Monitor doesn't run.
After executing [root@MSE]# /etc/init.d/msed start Health Monitor starts and Failback occures after 30 minutes successfully.
From Primary MSE it is also seen, that msed script does not start during booting up, because there is no msed in chkconfig list
[root@MSE]# chkconfig --list | grep msed
[root@MSE]#
So, here is the question.
How can the Failback be automatic, if msed on Primary MSE doesn't start after bootup?
P.S. it is possible to add msed to boot startup (chkconfig --add msed), but I think it is not recommended by Cisco.
