My context HA environment broke in VSX

[Matlu]

Hello, everyone.

I don't have much experience in VSX and MDS environments, hopefully you can clarify the doubt.

I currently have a problem in one of my contexts, and the HA of the Cluster has been lost.

If the “Standby” member of the context is lost, what can be the “most practical way” to recover its operation?

Should I still be able to access that member that appears as “Lost” by the CLI?

Can I check the root-cause of why the Cluster of my context was “broken”?

Thanks for your comments.

[Duane_Toler]

First step is to login to that second node, then run "cphaprob stat" for VS0.  Then go to that one VS (vsenv 3) and run "cphaprob stat" again per-VS.  Start there and it should give you some hints.

[the_rock]

I dont know if all of below work on VSX, but worth comparing.

Andy

cphaprob roles

cphaprob state

cphaprob -i list

cphaprob -l list

cphaprob syncstat

[Lesley]

Able to push policy to this problem vs, and to vs0?

Issue still there if you restart the VS itself?

1. Connect to the command line on the VSX Gateway.
2. Go to the context of the Virtual System:
   • In Gaia Clish, run:
     set virtual-system <VSID>
   • In the Expert mode, run:
     vsenv <VSID>
3. Stop the Virtual System:
   cpstop
4. Start the Virtual System:
   cpstart

[the_rock]

That sounds very logical to me.

Andy