Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

VCenter esxi 5.1 to manage existing VM's

Posted on 2013-06-18
10
Medium Priority
?
755 Views
Last Modified: 2013-06-19
Hi! I have a Vcenter 5.1 esxi server that I wish to manage my 2 vmware hosts.  If I connect to the hosts directly (192.168.1.116 or .117) with the vsphere client, I get a message that they are being managed by 192.168.1.115 (the vcenter server).  But if I log into the vcenter 5.1 server with the vmware web client (as admin@system-domain account), I see nothing, including a "0" for the very Vcenter server I am logged into.  From the home screen, If I click into Vcenter, I get the "getting started page".  If from the home screen I choose administration, I get a dropdown to choose my vcenter server, and the list is blank.  Just a note, this server ran vcenter 5.0 previous to my boss upgrading it.  This server was the ESXi 5.0 vcenter server, and the Ip address remained the same.  Can someone please help me understand why it can't see itself, and how to register 116 and 117?

Thanks!
0
Comment
Question by:pbenningfield
  • 5
  • 4
10 Comments
 
LVL 124
ID: 39257796
can you check with the vSphere Client?

see my EE Article,

HOW TO: Connect to the VMware vSphere Hypervisor 5.1 (ESXi 5.1) using the vSphere Client

it's possible that the upgrade has gone wrong....
0
 
LVL 2

Author Comment

by:pbenningfield
ID: 39257854
Sorry I have to ask, but can I check what specifically?  Do you mean can I use the vSphere Client to connect to the VMware Center server, or to the two hosts?  THANK YOU!!
0
 
LVL 124
ID: 39257863
connect vSphere Client to vCenter Server to check if the hosts are present!
0
Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
LVL 2

Author Comment

by:pbenningfield
ID: 39257901
I cannot connect with the vSphere client-- I receive "The vsphere client could not connect to 192.168.1.115 You do not have permission to login to the server "192.168.1.115" with the admin account.
0
 
LVL 124
ID: 39258024
are you using the same account, which you use with the Web Client?

is this the first time you have tried connecting to vCenter Server via Web Client and vSphere Client since the Upgrade?
0
 
LVL 2

Author Comment

by:pbenningfield
ID: 39258062
Using the webclient, I login as admin@system-domain.  That account will not log into the vsphere client (error you do not have permission to login to the server).  I am trying to log into vcenter using admin, administrator, root, domain/admin2 (and AD account), the local administrator account on the server, etc,  Nothing works.  Is this the first time since the upgrade?  Yes, in that I have been trying for days, but have had success with getting into the webclient fine with admin@system-domain, and once logged in, can show SSO and groups.  There are two accounts listed there, one is the admin and the other is one I created in desperation hoping to be able to log in.  I can see the identity sources there, being the local machine, system-domain, and the AD domain I have added.  If this was your mess, how would you tackle it?
0
 
LVL 124

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 2000 total points
ID: 39258073
bin the vCenter Server and re-create a new one from scratch.

This is not the first time, we've seen an upgrade go wrong.

if you have no hosts showing up in vCenter Server, and cannot access via the vSphere Client.

Add an Account to the Local Administrators group on the server.

can you login with that?
0
 
LVL 2

Author Comment

by:pbenningfield
ID: 39258107
Hi, and thanks.

I can't, I just created a new local admin and tried.  I have no problem ripping out vcenter server on this box and reinstalling... but I can't burn down the OS at this time (no physical access).  I can reboot it without issue though.  Think that will work, any tips or gotcha's I need to watch for?
0
 
LVL 124
ID: 39258572
Reboot is fine it will not affect any running VMs.
0
 
LVL 19

Expert Comment

by:vmwarun - Arun
ID: 39259050
Have you made sure that in the Identity sources option, the AD domain is listed first?

Make sure to save the setting and then try logging in as an AD user.
0

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will show you how to create an ISO CD-ROM/DVD-ROM image (*.iso), and MD5 checksum signature, for use with VMware vSphere Hypervisor 6.5 (ESXi 6.5). It's a good idea to compare checksums, because many installations fail because of a corr…
In this step by step tutorial with screenshots, we will show you HOW TO: Enable SSH Remote Access on a VMware vSphere Hypervisor 6.5 (ESXi 6.5). This is important if you need to enable SSH remote access for additional troubleshooting of the ESXi hos…
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…

773 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question