Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Rom_D
Contributor

How to failover a VSX cluster in VSLS mode?

Jump to solution

Hi,

I need to perform a full failover of my VSX Cluster XL environment for a maintennace window. (R80.30)

Right now, the VSX cluster uses VSLS but all VSs are active on the same VSX node (member1).

So what would be the best way to force a full failover to the VSX member2?

I read sk56060 which says the best way is "clusterXL_admin down" but in sk95133, it is said that with "clusterXL_admin down" the VS do not become active on the Active Member.

In our case we need to have all VS switched to VSX member2 (included vs0)

Thanks for clarification and help

 

0 Kudos
3 Solutions

Accepted Solutions
Sigbjorn
Advisor

The proper way to do a controlled failover would be to use the "vsx_util vsls" tool.

Run it on the management server, and connect to the vsx cma/sms to change priority and move the virtual systems.

View solution in original post

Sigbjorn
Advisor

That's just to configure the distribution of the virtual systems. We don't process traffic on vs0 for our VSX clusters, that's just for management, snmp etc, so a failover there wouldn't be required for normal upgrade operations.

If you must failover vs0 as well, I think clusterXL_admin down in that context is a decent option.

View solution in original post

Bob_Zimmerman
Advisor

You can always just run 'cphastop'. It's a bit brute force, but should stop clustering entirely on the member where it is run, which will cause the other members to realize it's down and rebalance.

You mentioned you're using VSLS, but all your active contexts are on the same member. That seems odd. Are you sure you're using VSLS and not normal HA?

View solution in original post

7 Replies
Sigbjorn
Advisor

The proper way to do a controlled failover would be to use the "vsx_util vsls" tool.

Run it on the management server, and connect to the vsx cma/sms to change priority and move the virtual systems.

View solution in original post

Rom_D
Contributor

Hello,

Thanks for the reply.

Does this also failover the vs0? or only the other vs?

0 Kudos
Sigbjorn
Advisor

That's just to configure the distribution of the virtual systems. We don't process traffic on vs0 for our VSX clusters, that's just for management, snmp etc, so a failover there wouldn't be required for normal upgrade operations.

If you must failover vs0 as well, I think clusterXL_admin down in that context is a decent option.

View solution in original post

Rom_D
Contributor

Actually, we need to perform a failover for a Case.

We were asked to switch everything on the other node (all VS including vs0).

0 Kudos
Bob_Zimmerman
Advisor

You can always just run 'cphastop'. It's a bit brute force, but should stop clustering entirely on the member where it is run, which will cause the other members to realize it's down and rebalance.

You mentioned you're using VSLS, but all your active contexts are on the same member. That seems odd. Are you sure you're using VSLS and not normal HA?

View solution in original post

Rom_D
Contributor

Yes, VSLS is used as if we are in HA mode. Just in case one day we need to share VS on the different VSX.

Thanks to your answer I was able to play with:

- clusterXL_admin up|down to failover a single VS (1 by 1)

- cphastop to failover everything in 1 command

- vsx_util vsls to switch VS without putting in DOWN state

 

0 Kudos
Anthony_Kahwati
Collaborator

Agree with this as well. We have always used vsx_util to manually move the VS's until we want them back where they belong. If it is for a case, this sounds like the best and cleanest option.