Two-node cluster status is abnormal after the SMC2.0 is upgraded

Hello, this topic describes how to deal with the problem that two-node cluster status is abnormal after the smc2.0 is upgraded.

Problem Description

After the SMC2.0 is upgraded, the two-node cluster status is abnormal and database synchronization fails.

Handing Process

1. Check whether the names of the active and standby computers are duplicates.

2. Checking whether port 445 on the active and standby nodes is enabled.

3. Check whether the network discovery and file sharing functions are enabled on the active and standby nodes.

4. Use the database access tool to check whether the Publication of the host database exists. Right-click the publication task and choose Replication Monitor from the shortcut menu to check whether the publication is normal, as shown in the following figure.

   
   

   
   

   

5. Open the database of the standby node and check whether the subscription exists on the standby node. Right-click Subscription Task and choose View Synchronization Status from the shortcut menu to check whether the subscription is normal, as shown in the following figure.
   

   

   

6. Log in to the SMC2.0 host and check the SMC2.0 host database. It is found that the database is not released.

7. Run the Stop_Failover_Smc_Services.bat script with administrator privileges.

   1. Stop standby node firstly, and then stop active node services.

   2. Start active node service node, and then start services on the standby node.

      The database synchronization status is normal.

Root Cause

The upgrade guide is not strictly followed.

Before the upgrade, stop services on the standby node and then on the active node.

Upgrade the active node and then the standby node.