Migrate the nodes in cluster

On an Advanced Threat Defense cluster setup, if you choose to migrate to Advanced Threat Defense 4.6.0, ensure that you migrate all the nodes in the cluster.

Task

  1. In a typical load-balancing scenario, first migrate the backup node.
    Post migration, the node remains a part of the cluster, however due to version mismatch incoming samples are not submitted to this node. The samples are distributed only between Primary and Secondary nodes. The status column of Backup node in the Load-balancing page displays the following message: Node is on different software version.
  2. Migrate 50 percent of the secondary nodes.
    Note: Migrate the Primary node only after you have migrated 50 percent of the secondary nodes.
  3. Migrate the Primary node.
    Since the Primary node remains down during migration, Backup node takes over the Active role and distributes the incoming samples between Backup node (Active) and the migrated secondary nodes. Even after the Primary node is migrated, the Backup node continues to be in Active role.
  4. Migrate the remaining secondary nodes.