Hello!
we have two 3355 7.4 MSE appliance in different locations.
They are in the same VLAN (L2 domain).
MSE1 is primary, MSE2 secondary.
- MSE1 10.1.1.2
- Virtual 10.1.1.1
- MSE2 10.1.1.3
MSE1 and MSE2 can ping each other, but can't join in HA pair. MSE can also ping Virtual IP address. But, heartbeats are down.
after trying to add MSE2 to MSE1 from Prime GUI
(Services > Mobility Services Engines> System > Services High Availability > Current High Availability Status) it is ssen:
"Initial setup of high availability configuration has failed. Lost heartbeats with the Secondary. Will retry."
information from MSE2
[root@MSE2 ~]# /etc/init.d/msed status
STATUS:
Health Monitor is running
MSE services are down. This is a secondary server. Services will not be started
unless -
* This secondary is paired with a primary and the primary is up
and synchronized with this secondary
OR
* Associated primary server is down and this server is failing o
ver for it
[root@MSE2 ~]# gethainfo
Health Monitor is running. Retrieving HA related information
----------------------------------------------------
Base high availability configuration for this server
----------------------------------------------------
Server role: Secondary
Health Monitor IP Address: 10.1.1.3
Virtual IP Address: Not Applicable for a secondary
Version: 7.4.100.0
UDI: AIR-MSE-3355-K9:V01:XXXXX
Number of paired peers: 1
----------------------------
Peer configuration#: 1
----------------------------
Health Monitor IP Address 10.1.1.2
Virtual IP Address: 10.1.1.1
Version: 7.4.100.0
UDI: AIR-MSE-3355-K9:V01:YYYYYY
Failover type: Manual
Failback type: Manual
Failover wait time (seconds): 120
Instance database name: mseos3
Instance database port: 1524
Dataguard configuration name: dg_mse3
Primary database alias: mseop3s
Direct connect used: No
Heartbeat status: Down
Current state: SETUP_FAILED
There are no FW or ACL between two nodes.
Does anyone know, what can be the reason and how heartbeats can be troubleshooted?
