- CheckMates
- :
- Products
- :
- Quantum
- :
- Management
- :
- Change Standby Member to Active Member
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Change Standby Member to Active Member
Hello,
I am looking for a command to change a Standby Member to Active in a R80.10 VSX Cluster without disrupting services.
Thanks
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes... without VSLS, just execute clusterXL_admin down on the active member. This will cause the Cluster to fail over to the other Cluster Member. You can immediately run clusterXL_admin up on that same member to bring ClusterXL back online. This should bring the 1st Gateway back as the Standby Cluster member.
The procedure would be the same to fail back to the other member once you are done whatever work you are performing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
clusterXL_admin up -p
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry, I do not think that executing "clusterXL_admin down -p" will help you in this case.
First of all the "-p" flag is for "permanent", meaning it is intended use is to survive reboot. To simply cause a failover, the
"clusterXL_admin down" should be executed on the Active member. Attention!!! please verify that your cluster is in a good working state before doing it.
Additionally, if your VSX cluster is running in VSLS mode, performing "clusterXL_admin down" in VS0 will not cause the other VS' running on Active member to failover:sk95133
In case of VSLS, use vsx_util to redistribute VS' to the desired target VSX unit before executing "clusterXL_admin down" in VS0.
Regards,
Vladimir
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
so in that case can i go ahead with clusterXL_admin down without -p ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apologies, I've made an error in my post above and have just corrected it.
The admin_down should be executed on currently active member to cause a failover.
Before you do this, please verify that your clustering, in content of each VS is looking good.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes... without VSLS, just execute clusterXL_admin down on the active member. This will cause the Cluster to fail over to the other Cluster Member. You can immediately run clusterXL_admin up on that same member to bring ClusterXL back online. This should bring the 1st Gateway back as the Standby Cluster member.
The procedure would be the same to fail back to the other member once you are done whatever work you are performing.
