This new primary workstation is close to being ready for production.
One item at issue is the amount of traffic on the 100Mbps front end network. When performing installs, doing testing, and maintenance on vSphere components and VM's, this front end network becomes very congested.
The plan is to move all vSphere management, Active Directory, and storage traffic to the back door gig-e and run VMware Workstation on the new Win7 workstation for all management access to vSphere. This will ensure that only internet bound VMware traffic will travel over the slower network.
Wednesday, October 13, 2010
Tuesday, October 5, 2010
Issues with the vCenter Server
Attempting to log into vCenter, the cluster is unable to be found and an error is presented stating that VUM (VMware Update Manager) cannot be contacted.
Initial troubleshooting plan is to log out of vCenter and directly into northvale, log directly into alpine (win2k8 box housing vCenter) and check the logs to make sure these are no obvious errors. The only error is a Winlogon application error for GPClient.
More digging. Shutting down vCenter VUM services on alpine and moving to red-bank to ensure SQL Server is happy.
First step is to push all new Windows Updates to red-bank, and rebooting. The errors persist.
red-bank event logs were showing logon errors for a system request along with a SQL scheduled job failing for a database. It was not long before we determined that this is a task for a database that is no longer present.
After removing the task from SQL Management Studio, the errors are gone. We will give the SQL server 30 minutes or so to ensure the errors do not return before restarting vCenter and VUM services on alpine.
Initial troubleshooting plan is to log out of vCenter and directly into northvale, log directly into alpine (win2k8 box housing vCenter) and check the logs to make sure these are no obvious errors. The only error is a Winlogon application error for GPClient.
More digging. Shutting down vCenter VUM services on alpine and moving to red-bank to ensure SQL Server is happy.
First step is to push all new Windows Updates to red-bank, and rebooting. The errors persist.
red-bank event logs were showing logon errors for a system request along with a SQL scheduled job failing for a database. It was not long before we determined that this is a task for a database that is no longer present.
After removing the task from SQL Management Studio, the errors are gone. We will give the SQL server 30 minutes or so to ensure the errors do not return before restarting vCenter and VUM services on alpine.
Subscribe to:
Posts (Atom)