Your environment is now in mixed mode. It is recommended you update your linked vCenter Servers to the same version - Logging into vCenter 7.0 Showing warning message/banner
search cancel

Your environment is now in mixed mode. It is recommended you update your linked vCenter Servers to the same version - Logging into vCenter 7.0 Showing warning message/banner

book

Article ID: 313930

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
  • Logging into vCenter 7.0 Showing warning message/banner : "Your environment is now in mixed mode. It is recommended you update your linked vCenter Servers to the same version"


 
  • vCenter System Configuration topology shows all vCenters are in same version
  • Issue may observe in standalone vCenter as well


Environment

VMware vCenter Server 7.0.x

Cause

This issue can occur if there are stale vCenter entries in lookupservice registration, or nodes that have not been upgraded yet in linked mode.

Resolution

Caution: This procedure involves data modification on vCenter Server Appliance. Ensure you have valid backup of all vCenter Servers in replication partnership. If you are taking a snapshot before the change, all vCenters in replication partnership with the vCenter where the change is made need to be powered off at the same time to take a consistent snapshot state of the vCenter.

To resolve this issue, find the stale registration and unregister it from lookupservice:
  1. login to VCSA using SSH with root credentials
  2. Run the following command to get the service registrations. 
/usr/lib/vmware-lookupsvc/tools/lstool.py list --url https://localhost/lookupservice/sdk --type vcenterserver > /tmp/psc.txt --no-check-cert
  1. use less/vi to open /tmp/psc.txt to review presence of any stale registration
Sample lstool output section for vCenter registration may look like : 

Name: AboutInfo.vpx.name
        Description: AboutInfo.vpx.name
        Service Product: com.vmware.cis
        Service Type: vcenterserver
        Service ID: default-first-site:3c80e5dd-b67f-43c5-ac9d-8091e26c0378
        Site ID: default-site
        Node ID: 12833276-6d55-493f-bf26-285919ae9242
        Owner ID: [email protected]
        Version: 5.1
        Endpoints:

 Name: AboutInfo.vpx.name
        Description: AboutInfo.vpx.name
        Service Product: com.vmware.cis
        Service Type: vcenterserver
        Service ID: abd2e86e-f316-4cb8-8fb7-f389e3a012e1
        Site ID: default-first-site
        Node ID: d4b8027e-d3e8-4c84-aee5-48d5df23f5e7
        Owner ID: [email protected]
        Version: 7.0
        Endpoints:
Name: AboutInfo.vpx.name
        Description: AboutInfo.vpx.name
        Service Product: com.vmware.cis
        Service Type: vcenterserver
        Service ID: 218df911-166d-4d41-a629-917598456876
        Site ID: default-site
        Node ID: 12833276-6d55-493f-bf26-285919ae9242
        Owner ID: [email protected]
        Version: 7.0
  1. From the output if you see a stale registration, note down the Service ID
In this example: default-first-site:3c80e5dd-b67f-43c5-ac9d-8091e26c0378
  1. Remove the old service registration using the below command. 
 
/usr/lib/vmware-lookupsvc/tools/lstool.py unregister --url https://localhost/lookupservice/sdk --id default-first-site:3c80e5dd-b67f-43c5-ac9d-8091e26c0378 --user '[email protected]' --password '<password>' --no-check-cert
 
  1. Re-login to the Web Client. 
Note: This is only intended to remove stale vCenter service registrations. For vCenter registrations in linked mode that have not yet been upgraded, those should be upgraded and not removed using the commands above.