NSO HA function observations: I am working on Crosswork SH 5.0 FT. During my SH testing with NSO HA setup I observed some issues. I am following the below guide for NSO HA setup and testing.My Testbed versionCW: 284cw-na-cat-5.0.0-291cw-na-aa-5.0.0-327cw-na-fp-tmtc-5.0.0-270NSO : ncs-6.1_230124.150846953.5043401bc5beHA : ncs-6.1_230202.150846214.1e784fae5f6b-tailf-hcc-6.0.0.tar.gzObservation 1: If I stop the NSO service on Master node, slave become master, but it is working in read-only mode. So that I am not able to perform any action in NSO. Also, the provisioning option in CW is not showing.If I bring up the nso service in master node then read-only mode changed as false in standby(working as master). Also, I can be able to see the all the option in CW service. Please share your feedback on my observation. Shall I raise CDET if my observation is valid ?Query 2:Do we have to DB sync up manually if the original master node comes up after some time? if yes, please share the procedure for the same.
 Hey Karthikeyan,Can you please setup details?Thanks,RegiReporter shared the setup details:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>172.28.174.203 --> NSO1 (master)172.28.174.205 --> NSO2 (Slave)172.28.174.254 --> VIPadmin / Ovatest123@</pre></div></div>So, with your NSO installation file there should be docs located in: `/opt/ncs/current/doc/pdf/nso_admin_guide-6.1_230124.pdf`To outline related HA details for your queries:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>To prevent split-brain to occur, NSO 5.7 or later comes with a rule-based algorithm. The algorithm is enabled by default, it can be disabled or changed from the parameters: /high-availability/settings/consensus/enabled [true] /high-availability/settings/consensus/algorithm [ncs:rule-based]The rule-based algorithm can be used in either of the two HA constellations: Two nodes: one nominal primary and one nominal secondary configured as failover-primary. Three nodes: one nominal primary, one nominal secondary configured as failover-primary and one perpetual secondary.On failover: Failover-primary: become primary but enable read-only mode. Once the secondary joins, disable read-only. Nominal primary: on loss of all secondaries, change role to none. If one secondary node is connected, stay primary.Note: In certain cases the rule-based consensus algorithm results in nodes being disconnected and will not automatically re-join the HA cluster, such as in the example above when the nominal primary becomes none on loss of all secondaries.To restore the HA cluster one may need to manually invoke the /high-availability/be-secondary-to action.Note #2: In the case where the failover-primary takes over as primary, it will enable read-only mode, if no secondary connects it will remain read-only. This is done to guarantee consistency.Read-write mode can manually be enabled from the the /high-availability/read-only action with the parameter mode passed with value false.</pre></div></div>Let me know if you have anymore questions.Thanks,RegiHello, please let us know if this issue is still valid.If no response is received, ticket will be resolved EOD Sept 2nd.Thank you.Customer was provided information. No further response from customer. Closing ticket.