What are the pre and post checks involved in Tiebreaker host migration in a MetroCluster configuration?
Applies to
- ONTAP 9
- MetroCluster
- Tiebreaker
Answer
1. Enable console logging before performing maintenance tasks: enable-console-logging-before-maintenance
2. Remove Tiebreaker monitoring before performing maintenance tasks: concept_remove_mediator_or_tiebreaker_when_performing_maintenance_tasks
3. Collect the command ouput: storage iscsi-initiator show
4. Remove the existing MetroCluster configuration from Tiebreaker: removing-metrocluster-configurations
5. After completing maintenance of the MetroCluster configuration, resume monitoring with the Tiebreaker by adding MetroCluster configurations in the MetroCluster Tiebreaker: adding-metrocluster-configurations
6. Follow the steps in the KB How to collect data from MetroCluster Tiebreaker via Autosupport to verify the status of Tiebreaker
NetApp MetroCluster Tiebreaker :> monitor show –status
NetApp MetroCluster Tiebreaker :> monitor show –stats
NetApp MetroCluster Tiebreaker :> configuration show
NetApp MetroCluster Tiebreaker :> version show
Additional Information
- It is recommended to remove the existing MetroCluster configuration from Tiebreaker, and then, after completing maintenance of the MetroCluster configuration, resume monitoring with the Tiebreaker by adding MetroCluster configurations in the MetroCluster Tiebreaker, as we have seen issues earlier where there will be stale entries left in the database, without removing the existing MetroCluster configuration from Tiebreaker.
- Disabling monitoring will not initiate a switchover. It simply stops the Tiebreaker from monitoring the MetroCluster configuration, ensuring that no automatic actions are taken during the maintenance period.
