Hi,
We've configured 5400 cluster (HA) with two gateways and we have several VLAN subinterfaces both on a bond and on the physical interfaces. After rebooting the gateways the cluster is not started and we are getting following error message:
[Expert@CP-2:0]# cphaprob state
HA module not started.
(The same error message on both gateways)
We had to manualy start cluster with the command: cphastart on both gateways after each reboot.
We found following sk165073 saying that it could be a problem if there is a lot of non-monitored interfaces in a cluster. (by default not all VLAN subinterfaces are monitored)
We configured following fw kernel parameter in order to monitor all VLAN interfaces also:
[Expert@CP-1:0]# cat $FWDIR/boot/modules/fwkern.conf
fwha_monitor_all_vlan = 1
on both our gateways bu the same issue remains, the cluster is not automatically started after the reboot and has to be manually started on both gateways.
Please if you have some idea how to resolve this cluster issue.
Here is the detail command output:
[Expert@CP-2:0]# fw ctl get int fwha_monitor_all_vlan
fwha_monitor_all_vlan = 1
[Expert@CP-2:0]# cphaprob state
HA module not started.
[Expert@CP-2:0]# cphastart
[Expert@CP-2:0]# cphaprob state
Cluster Mode: High Availability (Active Up) with IGMP Membership
ID Unique Address Assigned Load State Name
1 10.255.253.1 100% ACTIVE CP1
2 (local) 10.255.253.2 0% STANDBY CP2
Active PNOTEs: None
Last member state change event:
Event Code: CLUS-114802
State change: DOWN -> STANDBY
Reason for state change: There is already an ACTIVE member in the cluster (member 1)
Event time: Fri Sep 18 13:27:35 2020
Cluster failover count:
Failover counter: 0
Time of counter reset: Fri Sep 18 13:21:46 2020 (reboot)
[Expert@CP-2:0]# cphaprob -a -m if
CCP mode: Manual (Unicast)
Required interfaces: 11
Required secured interfaces: 1
Interface Name: Status:
eth5 UP
bond1 (LS) UP
bond5 (S-LS) UP
bond4.172 (LS) UP
bond4.20 (LS) UP
bond4.60 (LS) UP
eth6.164 UP
eth6.166 UP
bond4.113 (LS) UP
eth6.165 UP
bond4.10 (LS) UP
S - sync, LM - link monitor, HA/LS - bond type
Virtual cluster interfaces: 10
eth5
bond1
bond4.172
bond4.20
bond4.60
eth6.164
eth6.166
bond4.113
eth6.165
bond4.10
Monitoring mode is "Monitor all VLANs": All VLANs are monitored
