We're running vCenter Server Standard v5.1 Rev A and when we edit a role vCenter becomes unresponsive for several minutes. During that time the vCenter's CPU's spike up to 100%. Eventually the CPU's utilization drops down to normal and vCenter responds normally. Opening a remote console also takes a lot longer than when logged in with a local account than an AD account. A third issue is that the vCenter Server VM takes up to 45 minutes to reboot. It takes 30 minutes just for the VM to show the network adapter as connected and then another 15 minutes or so for the services to fully start.
vCenter Server is virtualized with vCenter Server, SSO, and the inventory service on the same VM. We're using a dvSwitch and vCenter is a member of the switch. vCenter is managing 137 hosts and 2558 VMs. The vCenter VM has 6 vCPU's and 24GB RAM.
We've tried increasing CPU & RAM to the vCenter Server VM and DB VM, we've moved the VM's so they are both on the same server with no other VM's to eliminate networking & resource contention as potential issues. We also moved the VM's to a new unpopulated storage array to check disk performance. No changes to the VM's or physical resources have made a difference. We're looking at SSO possibly being part of the issue since opening a remote console is fast under a local SSO account and slow under an AD account.
Anyone seen anything like this before? We're open to any configuration changes such as moving SSO to a separate VM but wanted to identify the changes most likely to have a positive change to keep downtime as low as possible.
Thanks,
-Mike
