CFS HA Failover: When CFS HA failover is performed, not able to bring back the nodes back to their's original states.Below are the output after performing back to original state actionsOn Master:admin@ncs> show high-availability statushigh-availability status mode masterhigh-availability status current-id masterhigh-availability status assigned-role masterhigh-availability status read-only-mode falseadmin@ncs>On Slave:admin@ncs> show high-availability statushigh-availability status mode nonehigh-availability status assigned-role slavehigh-availability status master-id masterhigh-availability status read-only-mode falsePlease also find the UI output enclosed herewith.
Hi Dinesh,Please share you setup info. We will take a look.Thanks,LinhHi Linh,NSO CFS Master: 10.194.57.204NSO CFS Slave: 10.194.57.45VIP: 10.194.57.58admin/Ovatest123@ - For all the nodes above.Thanks,DineshHi Dinesh,Last time Van, you and me debugged and we could not reproduce the issue. Have you try this issue again. Is it reproducable? If not, I would like to close this ticket.Thanks,LinhHi Linh,I'm testing a scenario that without any failover, My Master as master and Slave as slave,And the master goes down (i.e., unreachbale) and when it comes back by itself the following is found to be the it's status. admin@ncs> show high-availability statushigh-availability status mode nonehigh-availability status assigned-role slavehigh-availability status master-id standbyhigh-availability status read-only-mode falseadmin@ncs>Untill a ncs restart or vm reboot is performed, this doesn't turns into acting slave.NSO CFS Master: 10.194.57.204NSO CFS Slave: 10.194.57.45VIP: 10.194.57.58admin/Ovatest123@ - For all the nodes above.Thanks,DineshSteps to reproduce:1. Bring-up CFS HA with 5.7.2.1 #M52. Power shutdown the master VM manually3. Power-on the master VM back.4. Verify that the failover happened and the respective status for "show high-avialability status" found as expected in both the nodes.Please do let me know if any other information/details if required.Thanks,DineshServer Size is : SmallHi Dinesh ,I have increased the <tick-timeout>PT200S</tick-timeout> from 20 to 200 sec.Now it is working fine.Please try out and let us know if you still see issue.In your lab i tried failover ,as expected primary became standby and original standby took over as master .ThanksPriyankaHi Priyanka,Can you point out to the change where exactly?Is it a property of linux or NSO? Please confirmThanks,DineshI could able to see that the ncs.conf - ha section has been updated with your suggested variable.I performed powering-down the node whatever that is acting master.And turned it on. But still could not see that is coming up with proper expected state: Please check below.Output from Standy:admin@ncs> show high-availability statushigh-availability status mode nonehigh-availability status assigned-role slavehigh-availability status master-id masterhigh-availability status read-only-mode falseOutput from Master:admin@ncs> show high-availability statushigh-availability status mode masterhigh-availability status current-id masterhigh-availability status assigned-role masterhigh-availability status read-only-mode falseNOTE: Please be noted, that the failover I do is my manual power-off the master and then turn on the master.Thanks,DineshHi Dinesh ,As discussed over webex,we need to manually do switch over.It's not automatically, NSO cli can be used as discussed over a call.ThanksPriyanka.Correct steps have been provided.