Verifying the UCA replication status

Last Updated : Mar 15, 2023 |

About this task

Use this procedure to verify that UCA replication is operational and the test attribute is replicated to the DR instance.

When you make an administrative change using the primary Avaya Control Manager, the changes are replicated from the primary UCA to the DR UCA.

Important:

Ensure that there are no active UCA alarms. If there are any active UCA alarms, resolve them before the switchover.

Procedure

  1. Log on to the System Manager.
  2. On the System Manager web console, click Elements > Avaya Breeze® > Cluster Administration > Primary Cluster.
  3. In the Cluster field, select Oceana Monitor.
  4. To view the PU status of all the snap-ins, select Cluster 1 > Grid Info.
  5. Verify if the PU status of ucaStoreSpace-GATEWAY is INTACT.

    If the status is Scheduled or Broken, UCA replication is not operational.

    You must correct the issue before proceeding with the switchover.

  6. On the primary site, in the Show Cluster Messages tab, select the UCAStoreService PU.
  7. Verify that the HEARTBEAT message for the replication channel state is ACTIVE.
  8. Repeat steps 1 to 6 for Avaya Oceana® Cluster 1 in Data Center 2.
    Note:

    On the Cluster Messages tab, in UCAStoreService messages, check the time of the last cluster DB updated message on all nodes on the Primary and the DR site.

    Important:

    Perform the subsequent steps after successfully completing steps 1 to 6.

  9. Log on to the Avaya Control Manager on DC1.
  10. Add a new test attribute and save the attribute to the primary UCA instance.

    For more information on creating a new test attribute, see the Adding Attributes to Avaya Control Manager section in Deploying Avaya Oceana®.

    Note:

    If the test attribute does not appear, UCA replication is not operational from primary to DR or the request to save a new attribute to the primary UCA server is not successful. Ensure that you correct these issues before proceeding with the switchover.

  11. Reload the cluster message, select UCAStoreService, and check the new time of the cluster DB updated message.

    The time of the updated message must coincide with the newly added attribute.