com.tailf.ha.HaException: ha badfxs

[Chris Wang]

we upgrades NSO from 4.6.1 to 4.7.5 and used the ned packages under 4.7.5.

Below are the neds we used and we re-make them under NSO 4.7.5:

ncs-4.7.5-cisco-asa-6.7.2.tar.gz, ncs-4.7.5-cisco-iosxr-7.13.9.tar.gz, ncs-4.7.5-cisco-fmc-1.2.9.tar.gz, ncs-4.7.5-cisco-nx-5.11.2.tar.gz, ncs-4.7.5-cisco-ios-6.33.7.tar.gz, ncs-4.7.5-citrix-netscaler-4.0.3.tar.gz and ncs-4.7.5-tailf-hcc-4.4.3.tar.gz

When I try to enable HA(master and slave mode), error shows as below:

<WARN> 05-Sep-2019::07:14:12.430 Cluster Timer-1: - Exception
com.tailf.ha.HaException: ha badfxs
at com.tailf.ha.HaException.mk(HaException.java:41)
at com.tailf.ha.Ha.checkError(Ha.java:288)
at com.tailf.ha.Ha.checkResponse(Ha.java:311)
at com.tailf.ha.Ha.beSlave(Ha.java:153)
at com.tailf.ns.tailfHcc.Cluster.updateLocalNode(Cluster.java:1086)
at com.tailf.ns.tailfHcc.Cluster.update(Cluster.java:1225)
at com.tailf.ns.tailfHcc.TcmApp$PeriodicTask.run(TcmApp.java:493)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)

How to solve this issue?

[KJ Rossavik]

Please raise a TAC case. If this is for a customer then user their entitlement, and if it is internal (I see you are Cisco) then bypass entitlement

[lmanor]

So this usually means that the packages on the slave and master NSO nodes do not match _exactly_.  The CDB schema for both NSO nodes needs to be identical. Since the packages define the CBD schema, NSO version and the loaded/running packages need to be exactly the same on both master/slave NSO nodes before enabling HA, which replicates the Master CBD contents to the Slave.