Hi NSO experts,
We are using NSO 5.4.1.1 and tailf-hcc 4.4.4 for HA configuration in Production environment.
We are facing a tick timeout issue with the HA pair. When we activate HA on slave node, we do see on Master that slave is connected but as soon as we get a commit on Master, slave gets disconnected with the exception in logs as follows:
ncs NSO HA: Lost connection to master due to: Tick timeout
We checked telnet to 4570 and ping is also quick. crypto file is same, packages are in UP status on both master and slave and same as well. We even copied CDB/ rollback files from Master to slave.
Question is what can be done next to debug? should we increase Tick timeout would it make sense with below output of Ping?
(
PING 10.251.227.56 (10.251.227.56) 56(84) bytes of data.
64 bytes from 10.251.227.56: icmp_seq=1 ttl=64 time=0.130 ms
64 bytes from 10.251.227.56: icmp_seq=2 ttl=64 time=0.282 ms
64 bytes from 10.251.227.56: icmp_seq=3 ttl=64 time=0.248 ms
64 bytes from 10.251.227.56: icmp_seq=4 ttl=64 time=0.251 ms
64 bytes from 10.251.227.56: icmp_seq=5 ttl=64 time=0.285 ms
64 bytes from 10.251.227.56: icmp_seq=6 ttl=64 time=0.202 ms)
This is our running config of HA:
adm_yshaban1@ncs# show running-config ha
ha token tmonsohatoken
ha interval 4
ha failure-limit 10
ha vips vipX.X.X.X
!
ha member ngppol05
address X.X.X.Y
default-ha-role master
vip-interfaces vip-interface ens160 X.X.X.X
!
!
ha member ngppol06
address X.X.X.Z
default-ha-role slave
failover-master true
vip-interfaces vip-interface ens160 X.X.X.X
!
!
Thanks,
Neetika
!
