Forum Discussion
NimbostratusIsolate guest for vCMP but I need remain the sync between cluster members
I have 3 chassis each with a blade. Two of the three chassis are in the main data center and the other is in the alternate data center.
4 guest were created in each chassis which are clustered in threes, each housed in a chassis.
The customer wants for any reason the guest that is in the chassis roll take alternate data center active within the cluster but if you receive synchronizations sent from the guest that are in the main data center.
I took a look and found an option that worked in a cluster in version 12 but to make the same settings on my client infrastructure no longer worked.
The idea is to modify the "Minimum Number Of Blades Up Device Is Considered Before Available" parameter within the chassis guest in the alternate data center. By modifying this parameter to greater than 1 (4), this guest would enter a state of "failsafe-foult" where virtual server services are disabled but connectivity exists and can receive synchronizations.
When did the change in the guest, its status will not change to failsafe-foult but remains in the standby state.
1 Reply
Chris_GrantEmployee
The system should still report that it's in standby, but if you look at "tmsh show sys ha-status" if you have it set to require more blades than it has it should report a failure. Generally the system's actual status will be:
- Active - taking traffic
- Standby - not taking traffic, but otherwise functional (can connect to self-IPs, for instance)
- Offline - generally manually forced to an offline state, or configuration load failed
- Inactive - Not yet fully up
If you are in failsafe, I would expect the box to remain in standby, but show the failure in ha-status.
