Inventory loading slow on secondary vCenter inventory when in SDDC group
Article ID: 323270
Updated On:
Products
VMware Cloud on AWS
Issue/Introduction
To explain the behavior observed when viewing vCenter inventory of a second vCenter that is participating in a SDDC group.
Symptoms:
When using the vcenter-1 FQDN to access vcenter, the inventory of vcenter-1 loads faster whereas the vcenter-2 inventory will take 15 seconds to load after each click on it. If using the vcenter-2 FQDN to access vcenter, the inventory of vcenter-2 loads faster whereas the vcenter-1 inventory will take 15 seconds to load after each click on it.
Symptoms:
When using the vcenter-1 FQDN to access vcenter, the inventory of vcenter-1 loads faster whereas the vcenter-2 inventory will take 15 seconds to load after each click on it. If using the vcenter-2 FQDN to access vcenter, the inventory of vcenter-2 loads faster whereas the vcenter-1 inventory will take 15 seconds to load after each click on it.
Cause
This is caused by a build up of multiple requests being received by the secondary vCenter which results in the delay experienced.
Resolution
This is fixed in SDDC version 1.20. Please work with your Customer Success representative to schedule your SDDC for upgrade.
Workaround:
To avoid delays on the secondary vCenter you can log directly into its FQDN.
Workaround:
To avoid delays on the secondary vCenter you can log directly into its FQDN.
Additional Information
Impact/Risks:
This should not impact production capabilities, but will cause a UX impact to users who view/manage the secondary vCenter inventory in this fashion.
This should not impact production capabilities, but will cause a UX impact to users who view/manage the secondary vCenter inventory in this fashion.
Feedback
Yes
No
Powered by
