Quantum Forum V

Quantum Forum for DXi V5000

discovery of Vcenter fails in vmPRO

Discovery of 10.10.42.3 failed  -- Controller UUID: 7d49257a3d9b11e2bc46005056993ccf
\
the IP address belongs to vcenter server ( an appliance version).  Does not happen all the time, but does happen even when I can and even when I am connected to vcenter with the vshpere gui client.

Any thoughts.  I do not have enough hair to be continually pulling it out.

Thanks and best regards.

Views: 131

▶ Reply to This

Replies to This Discussion

Permalink Reply by DoubleDensity on February 11, 2013 at 7:31am

Hi Bill,

Does this cause anything to fail on your vmPRO, either any backup or recovery operations, or activity against the file shares? I have seen this before as a transient alert, and usually the appliance will acknowledge the alert without issue and keep running.

Permalink Reply by Bill Bajcz on February 11, 2013 at 7:47am

Yes it does.  Following ths, the backup report shows no VMs discovered and NO VMs backed up.

So this is a catastrophic failure.

Permalink Reply by Bill Bajcz on February 11, 2013 at 8:27am

Here is a screenshot of an error from "discovery".  The user and password credentials for Vcenter have NOT changed and in fact I am logged into Vcenter via the Vshoere client.

Attachments:
Permalink Reply by DoubleDensity on February 11, 2013 at 9:35am

What happens when you enter in your vCenter IP/hostname, login and password and hit the 'Test Login' button -- does it show you the version number for the vCenter server?

Is the vCenter server managing ESX hosts with at least a vSphere Essentials license installed? The reason for that is that it is the minimum required license in order to use the vSphere VADP backup API with vmPRO..

Permalink Reply by Bill Bajcz on February 11, 2013 at 9:41am

It says cannot login due to incorrect username 0or password.

But NEITHER the user nor the password have changed.   It does NOT work even if I refresh the user name and password.  But I CAN log into vcenter using these selfsame credentials from the vsphere client.

Permalink Reply by DoubleDensity on February 11, 2013 at 10:13am

Could you try connecting vmPRO to the IP address of the ESX servers instead of the vCenter server? Are there any other user accounts in vCenter that you could try?

Permalink Reply by Bill Bajcz on February 11, 2013 at 10:20am

This is what I get whenever I use a host other than Vcenter.  There has to be a way because I was told by Quantum that Vcenter was NOT a necessity.

If I either delete the Vcenter from the vmPRO config and then re-add it,  I can connect.  If I power off and power up vmPRO I can connect.

Please remember that all the while I AM CONNECTED to and can manipulate   all VMs through Vcenter via the vsphere client.

 

Attachments:
Permalink Reply by DoubleDensity on February 11, 2013 at 10:44am

Is there a chance that there are still some steps remaining to be completed for the deployment wizard on that VMware vSphere vCenter Virtual Appliance (VCSA)? See page 274 of the attached vSphere documentation. 

If you do try using an ESX host instead of a vCenter server, be sure to delete the existing vCenter server registration first under the Configure -> Servers settings:

Attachments:
Permalink Reply by Bill Bajcz on February 11, 2013 at 11:09am

Vcenter has been running here for a while.  It runs.  All of the config steps were performed.  I can log into vcenter.

Permalink Reply by DoubleDensity on February 11, 2013 at 11:29am

Is the network that you are deploying vmPRO into behind a firewall, or restricted in access to the vCenter server or ESX hosts? Is it in the same network you are connecting to your vCenter with vSphere Client from?

Also, is your vCenter Server joined to a Windows Domain? Could you try entering your Username in a DOMAIN\user format in the Server settings on vmPRO?

Permalink Reply by Bill Bajcz on February 11, 2013 at 11:47am

The network is in my office.  I have two racks of servers,  Our VMware is a paid version. One VM host is running on an 2 year-old Intel motherboard with 2 4C Xeons  and 16G of RAM and supports 7 VMs, most of which are not running all the time because they are only used for support to test customer scenarios.

The second VM host is running on an Intel Canoe-Pass MB with 2 6C Xeons, and 32G of RAM.  It supports 4 VMs including our Linux production server, the vmPro appliance and an instance of Acronis VMprotect 8 that I just downloaded for testing (currently powered off)

While we do have windows servers here, none of them are running the dreaded "Active" directory.  We never turn that on for any network until there are in excess of 45 users.  We have been doing networks since before Microsoft knew networks  existed and prefer to configure them ourselves.

There are no firewalls inside the network.  There is a hardware Cisco device between our network and the public Internet.

As a matter of information, while I am new to this product, I am not new to computers or networking.  I started banging on computers in 1967, have been  designing, installing and troubleshooting networks professionally since 1985 (arcnet), and have Masters degrees in both Chemistry and in Computing.  I mention these items only because there is no way for you to know this without my listing it here.

There are a lot of things I like about this product.  However, its stability so far seems to be a whimsical as a teenager.  I want to ensure that this whimsical behavior can be subdued before I sell this application to a customer for whom I have performed support for twenty years.

Thanks for your replies.  I hope this additional information is helpful.

Permalink Reply by DoubleDensity on February 11, 2013 at 12:30pm

Thank you for the details, it sounds like a very nice environment. What was the type of computer you were using in 1967? 

I am surprised that you can't connect to either vCenter or ESX -- are you using DHCP or a manually-assigned IP address on the vmPRO? Is there a DNS server specified?

RSS

Tips + Tricks

© 2024   Created by Quantum Forum V.   Powered by

Badges  |  Report an Issue  |  Terms of Service