Stale Manager Service instances are listed in the Replicator Service Management Portal
search cancel

Stale Manager Service instances are listed in the Replicator Service Management Portal

book

Article ID: 315158

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

In the System Monitoring view of the VMware Cloud Director Availability (VCDA) Replicator Service Management Portal, you see a stale offline Manager Service listed in the Manager Service status section.

Environment

VMware Cloud Director Availability 4.x

Cause

This issue can occur when a Cloud Replication Management Appliance has been decommissioned or replaced where the Manager Service has not been unpaired with the local Replicator Service first.

Resolution

To resolve this issue perform the following:

  1. Log in to the Replicator Appliance:
    Access and log in to the Replicator Appliance web interface.
  2. Identify the offline instance ID:
    Navigate to System Health and note down the offline Manager Instance ID.
  3. Verify if the offline Manager is a Local or Remote Manager:
    Go to Manager Services and locate the offline Instance ID you just noted. Check its API URL — if the URL begins with https://tn-* instead of an IP address this confirms the instance belongs to a remote manager.
  4. Confirm the instance is safe to remove: Must be checked across all connected cloud sites.
    Log in to the Manager service (using port 8044 or 8441) for all connected cloud sites. Compare their Manager Instance IDs against your offline ID. If you cannot find a match across any of the cloud sites, the offline instance is safe to remove.
  5. Remove the offline service:
    Return to the Replicator Appliance. Navigate to Manager Services, select the offline Manager Service ID, and click Remove.
  6. Verify the removal:
    Finally, check the System Health dashboard on the Replicator Appliance to confirm the offline manager is no longer displayed.

To work around this issue, contact Broadcom Support and note this Article ID (315158) in the problem description. For more information, see Creating and managing Broadcom support cases.