Hi,

is it possible to automatically start/stop VMs (and create from template if necessary) based on specific criterias?

I think of setting up a template containing a webserver and I want to fire up and shut down instances based on load.

For example criterias might be:

- RAM usage

- CPU usage

- requests/s

- connected users, ie nr of sessions

I think the tool of choice would be the Orchestrator, but how much of the above could it do?

Thanks

Tim

Hello,
I have the following issue in VCenter Server 5.1.0 U1A and SQL Server 2008 R2 SP2 installed in 2 different VMs.
I configured SSO with a single AD domain using ldaps; In identity source I provided an username (domain\vmuser) with read rights on AD and the following behavior happens:

• If I try to login on vcenter using domain\vmuser, it always works
• If I try to login on vcenter using another AD user with all kind of role in vmware, it only works once; next time same user tries to login again, it gives me the following error: "Cannot complete login due to an incorrect user name or password"

I tried to reinstall vcenter and sql server several times but the problems is still the same.

Thank you very much for your help

Sorry, I'm new at this and I'm having a problem installing vCenter 5.1a on Windows Server 2008 R2 using the simple install.  After completing the install without any errors, I start up the vSphere Web Client, log in and it comes up with no vCenter servers and a message that says "To get started install either a vCenter Server system or obtain access permission to an existing vCenter Server system."  I'm on my 4th time though and it's consistant in result, so I figure I should ask.

If it matters, the Windows Server is not a member of Active Directory, the DNS works forward and reverse, I tried both the IP address and the fqdn.

I'm not sure where to being troubleshooting this.  This is my first vCenter installation. I've checked all of the services and they are running.

I have looked at some log files and it seems pretty clear that something is trying to talk to something and is being refused, but I have no idea why.

Anybody have any suggestions?

Thanks

This is the eam.log

This is the vws.log

[2012-11-05 16:49:47,565 VwsInit  INFO  com.vmware.vim.vws.VwsContextListener] Started VWS.

[2012-11-05 16:49:49,031 Thread-24  ERROR com.vmware.vim.vimclient.VimClientFactory] Creating VC client failed, retrying

com.vmware.vim.vmomi.client.exception.ConnectionException: org.apache.http.conn.HttpHostConnectException: Connection to http://localhost:80 refused

[ ... snip ...]

caused by: org.apache.http.conn.HttpHostConnectException: Connection to http://localhost:80 refused

[ ... snip ...]

Caused by: java.net.ConnectException: Connection refused: connect

[ ... snip ...]

[2012-11-05 16:50:15,255 Thread-25  ERROR com.vmware.vim.cimmonitor.qs.provider.impl.QsHelperImpl] Vim configuration exception occurred while creating a provider client

com.vmware.vim.vimclient.exception.VimConfigException: VC client creation failed, retries in progress

at com.vmware.vim.vimclient.VimClientFactory.getVmomiClient(VimClientFactory.java:124)

at com.vmware.vim.cimmonitor.qs.provider.impl.QsHelperImpl.createProviderClient(QsHelperImpl.java:428)

at com.vmware.vim.cimmonitor.qs.provider.impl.QsHelperImpl.access$000(QsHelperImpl.java:63)

at com.vmware.vim.cimmonitor.qs.provider.impl.QsHelperImpl$1.run(QsHelperImpl.java:296)

at java.lang.Thread.run(Thread.java:662)

Hello,

I have a vCenter 4.1 and I would like to disable the connection log.

In order to monitoring my ESXi and VM's problems, I have a script which permits to connect to the vCenter and asks it the states of VM or ESX. This script uses a user declared on the datacenter.

I have ~250 connexions each five minutes, and of course my tables "vpx_event" and "vpx_event_arg" grow rapidly because of these connections.

I know it exists a script to purge these tables, but I would like to know if it exists a solution to disable the logging for this user (or another solution).

Thank for your help

Hello. I have recently completed a upgrade of vCenter from 5.0 > 5.1. I ran into some common teething problems with SSO but things look ok at the moment. I do have one problem that I'd really like to fix - when attempting to sort VMs in the vSphere client, I see the following error:

Unable to connect to web service to execute query. Verify that the 'VMware VirtualCenter Management Webservices' service is running on https://vcenter_server_fqdn:10443 vim.fault.HttpFault

This is repeatable across multiple systems running the VI client. The Viclient log shows:

[viclient:SoapTran:P:43] 2013-07-01 10:25:30.193  Invoke 4283 Finish AcquireSessionTicket on SessionManager:SessionManager [vcenter_server_fqdn] - Serial:0.000, Server:001.425 [ERROR]

Vmomi.Fault.SystemError: vim.fault.HttpFault

   at VirtualInfrastructure.ManagedObject.InvokeMethod(MethodName, Object[])

   at Vmomi.SessionManager.AcquireSessionTicket(String)

   at VmomiSupport.Services.AuthenticationTicketSource.Next()

   at VMware.VimServices.Query.Impl.LoginByTicketQueryCommand.CreateWebQuery()

   at VMware.VimServices.Query.Impl.WebCommandBase.Execute()

   at VMware.VimServices.Query.QueryServiceBase.Login()

   at VMware.VimServices.Query.Impl.QueryCommandBase.PreProcess()

   at VMware.VimServices.Query.Impl.WebCommandBase.Execute()

   at VMware.VimServices.Query.QueryServiceImpl.ExecuteQuery(QueryWebCommand)

   at VMware.VimServices.Query.QueryServiceImpl.Query(String, Int32, LanguageId)

   at VMware.VimServices.Search.Impl.Utils.NewResults(ResultsInternal)

   at VMware.VimServices.Search.ResultsImpl.RetrievePage(Nullable`1)

   at VMware.VimServices.Search.FilterOrderObjectSetProviderImpl`1.GetObjectSet()

   at VirtualInfrastructure.ObjectSetPoller`1.DoPoll()

   at VirtualInfrastructure.ObjectSetPoller`1.<Poll>b__2(Object)

...

   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object)

[viclient:SoapMsg :P:43] 2013-07-01 10:25:30.193  RMI Request Vmomi.SessionManager.AcquireSessionTicket - 4283

<soap:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

  <soap:Header>

    <operationID>4C83B7E2-000010BB</operationID>

  </soap:Header>

  <soap:Body>

    <AcquireSessionTicket xmlns="urn:internalvim25">

      <_this xsi:type="ManagedObjectReference" type="SessionManager" serverGuid="3089D6D0-307C-4B0D-8BD8-94606298C034">SessionManager</_this>

      <serviceKey>1b27d894-3e47-4431-9d7b-c8cb2fd457aa/VIMWEBSVC</serviceKey>

    </AcquireSessionTicket>

  </soap:Body>

</soap:Envelope>

Method Invocation Error Vmomi.SessionManager.AcquireSessionTicket - 4283

Message: vim.fault.HttpFault

Server XML:

<soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <soapenv:Body>

    <soapenv:Fault>

      <faultcode>ServerFaultCode</faultcode>

      <faultstring>vim.fault.HttpFault</faultstring>

      <detail>

        <HttpFaultFault xmlns="urn:internalvim25" xsi:type="SystemError">

          <reason>Invalid fault</reason>

        </HttpFaultFault>

      </detail>

    </soapenv:Fault>

  </soapenv:Body>

</soapenv:Envelope>

[viclient:Error   :P:43] 2013-07-01 10:25:30.193  RMI Error Vmomi.SessionManager.AcquireSessionTicket - 4283

<Error type="Vmomi.Fault.SystemError">

  <Message>vim.fault.HttpFault</Message>

  <DetailedMessage>vim.fault.HttpFault

</DetailedMessage>

  <Reason>Invalid fault</Reason>

</Error>

[viclient:Error   :M: 4] 2013-07-01 10:25:30.193  System.Exception: Unable to connect to web services to execute query.

Verify that the 'VMware VirtualCenter Management Webservices' service is running on https://vcenter_server_fqdn:10443

   at VMware.VimServices.Search.FilterOrderObjectSetProviderImpl`1.GetObjectSet()

   at VirtualInfrastructure.ObjectSetPoller`1.DoPoll()

Vmomi.Fault.SystemError: vim.fault.HttpFault

   at VirtualInfrastructure.Soap.SoapServiceWrapper.DoInvokeSync(ManagedObject mo, MethodName methodName, Object[] parameters, Int32 timeoutSecs)

   at VirtualInfrastructure.Soap.SoapTransport.VirtualInfrastructure.Transport.InvokeMethod(ManagedObject mo, MethodName methodName, Object[] pars)

   at VirtualInfrastructure.ManagedObject.InvokeMethod(MethodName methodName, Object[] pars)

   at Vmomi.SessionManager.AcquireSessionTicket(String serviceKey)

   at VmomiSupport.Services.AuthenticationTicketSource.Next()

   at VMware.VimServices.Query.Impl.LoginByTicketQueryCommand.CreateWebQuery()

   --- End of inner exception stack trace ---

[        :ShowErr :M: 4] 2013-07-01 10:25:30.240  Error: Unable to connect to web services to execute query.

Verify that the 'VMware VirtualCenter Management Webservices' service is running on https://vcenter_server_fqdn:10443

vim.fault.HttpFault

Stack Trace:

   at VirtualInfrastructure.Utils.Log.Trace(String, String, TraceType)

   at VpxClientCommon.Util.Dialogs.Trace(String, String, String, TraceType)

   at VpxClientCommon.Util.Dialogs.ShowError(IWin32Window, String, String)

   at VpxClientCommon.ListViewData.OnDisplayMessage()

   at VMware.CustomControls.ListViewEx.DoDisplayMessage()

   at VMware.CustomControls.ListViewEx.WndProc(Message&)

...

   at System.Windows.Forms.Application.Run()

Any thoughts/suggestions would be gratefully received

My vcenter service is failing to start.  Any one have any idea why?     windows logs attached. 

Hello

I'm installing vCenter 5.1U at the DR site and my AD and everything else is at HQ, We are using VPN to connect the two for what will be SRM.

I have successfully setup SRM in the LAB  via LAN.

While installing vCenter 5.1U SSO on the DR site, I'm getting the "Error 29155.Identity source discovery" I'm not a network guy, but is there a port that is being blocked on my firewall that cause this? is there any blogs on setting up SRM via VPN that you guys can point me to?

Thanks

Bud  

Hi,

I did a fresh installation (simple) of a vCenter5.1. On installation I had a warning 29155. After the simple installation, I started successfully installation of the vSphere Client. I could'nt login with the vSphere Client on the vCenterserver. I did google for the warning 29155. I did a sucessfully login with the new Web vSphere Client. In configure, I added some entrys (add Identity source) Base DN, URL, Domain Name.

It is not possible to use the same login for the regular (Old) vSphere Client! The error is system error: Authorize Exception.

Do I have to less AD rights???? The user is in the domain and has local Administrator rights. If I use the local Administrator then it works! How can I check the authorization? I can't do checks in the AD because only the customer has Domain Login rights...

Thanks for your help!

Hi All,

Does any one got the error of Event id 1000 when starting the Vcenter service, this error comes when we have restarted the Vcenter server, and after that when we try to start the vcenter service we get this error, Does anyone able to solve it, if yes can youplease share what all steps you did to rectify it.

Regards

Raju Gunnal

http://tech2solution.blogspot.com

So I have the vCenter linux appliance latest version (5.1U1) but I have seen this before on earlier releases too.

On the console I have errors like below

=========================================

fsck failed.  Please repair manually and reboot.  The root

file system is currently mounted read-only.  To remount it

read-write do:

     bash# mount -n -o remount,rw /

Atention:  Only CONTROL-D will reboot the system in this

maintanance mode.  shutdow or reboot will not work.

Give root password for maintenance

(or type Control-D to continue):

==========================================

So I've tried just about everything I can think of

Put in the root password and then

# mount -n -o remount,rw /

# exit

System rebooted and ended up in the same spot

Tried Control-D

System rebooted and ended up in the same spot

Tried

Put in the root password and then

# mount -n -o remount,rw /

# Control-D

System rebooted and ended up in the same spot.

Googled it - didn't find anything.

Can't locate a KB either about this.

Any ideas?

TIA

When deploying an OVA/OVF file to vCenter, ovftool requires a locator.

The example locator in the user guide looks like this: vi://user:password@localhost/Datacenter

When I look at the vCenter path with vSphere, the hierarchy we have set up is:

- Location 
-- Department with Spaces 
--- security_group 

Perhaps my assumption that this hierarchy is the locator is incorrect, becausevi://user:password@localhost/Location/Department\ with\ Spaces/security_group just returnsError: Cannot parse VI locator.

Is there a way in vSphere to determine the correct locator of a vcenter for an ovftool deployment?

I have the Virtual Storage Appliance set up and running (VSA)

I have one vCenter Server (running on Win2k8r2 and full MS SQL)

I have two ESXi 5.0 hosts

I have 2 VMs running

When I initially set up the VSA cluster I didn't have access to DNS (and didn't make edits to a host file) so I added them to the vCenter console using their IP address.

I'd like to have them appear by their host names in the vCenter Console.  The simple way of right clicking and renaming isn't an option.

Looking at some of the online docs they don't appear to specifically mention that the procedure will work right with the VSA configured.

Can someone point me in the right direction?

I'm using ovftool 3.0.2 to deploy an OVA to vCenter 5.0.

I'm getting this message:

Error: A connection to the remote object could not be made. OVF Tool does not support this server.

My command with specific values obscured:

./ovftool  --datastore={datastore} --name={name} --prop:gateway={gateway} --prop:DNS:{dns} --prop:netmask0={netmask} --prop:ip0={ip} --X:logToConsole=true --X:logLevel="verbose" --powerOn http://{ova file} vi://{username}@{vcenter}/{Location}/host/{Resource}/

Even after turning logging on, I'm not getting much more information.  Any ideas?  Does 3.0.2 really not support 5.0?

[...]

2013-07-08T15:22:39.667-07:00 [7FCE91761720 verbose 'Default'] Hostsystem used as deploy target: vim.HostSystem:host-2858

2013-07-08T15:22:40.016-07:00 [7FCE91761720 verbose 'Default'] Backtrace:

--> backtrace[00] rip 00007fce92db1f44 Vmacore::System::Stacktrace::CaptureWork(unsigned int)

--> backtrace[01] rip 00007fce92b7cca4 Vmacore::System::SystemFactoryImpl::CreateQuickBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)

--> backtrace[02] rip 00007fce92b12ef8 Vmacore::Throwable::Throwable(std::string const&)

--> backtrace[03] rip 00000000006208c1 ./ovftool.bin() [0x6208c1]

--> backtrace[04] rip 00000000004e787a ./ovftool.bin() [0x4e787a]

--> backtrace[05] rip 00000000004e7dc9 ./ovftool.bin() [0x4e7dc9]

--> backtrace[06] rip 0000000000548722 ./ovftool.bin() [0x548722]

--> backtrace[07] rip 0000000000567056 ./ovftool.bin() [0x567056]

--> backtrace[08] rip 00000000005690fd ./ovftool.bin() [0x5690fd]

--> backtrace[09] rip 000000000056aa99 ./ovftool.bin() [0x56aa99]

--> backtrace[10] rip 00000000004c598e ./ovftool.bin() [0x4c598e]

--> backtrace[11] rip 00000000004c8a04 ./ovftool.bin() [0x4c8a04]

--> backtrace[12] rip 0000003400e1ec5d /lib64/libc.so.6(__libc_start_main+0xfd) [0x3400e1ec5d]

--> backtrace[13] rip 00000000004a3179 std::basic_streambuf<char, std::char_traits<char> >::xsgetn(char*, long)

-->

Error: A connection to the remote object could not be made. OVF Tool does not support this server.

2013-07-08T15:22:40.017-07:00 [7FCE8B88D700 verbose 'Default'] Curl_perform error code 23 (Failed writing received data to disk/application)

Completed with errors

If I'm on the vCenter server logged into the vSphere client as localhost, Windows creds. I get no usage reports for Summary and Virtual Machine tabs. If I log into the ESXi IP and root user, I get reports, but a warning about being manage by another source. Anyone seen this or know the fix?

I'm guessing a permissions issue, but not sure where to change or check.

Hi Guys,

I am running vcenter version 5.1 and my esxi servers are also 5.1.
Now, obviously the vcenter server is joined to the domain.

As we are upgrading the entire infrastructure, the old DC must be decommissioned and hence it is currently shut-down. All FSMO roles etc. have been transferred to the new DC and also the new DC is acting as DNS/DHCP server for the entire network.

We have got 50 PCs running in the network along with exchange server etc. and so far no signs of any glitches anywhere else

Now the issue I am having is that as soon as I shutdown the old DC, I can no longer access the VCENTER server using domain credentials. When I turn it on I can login fine.
The error I receive when I can't login -

1.  A general system error occured: Authorize Exception or
2. Access to VCENTER server was denied.
3. Taking too long to respond.

I followed the steps here http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1015639 i.e. unjoined vcenter server from domain and rejoined to domain whilst having old DC shutdown as well as turned on but absolutely no luck.

I can still log into VCENTER server using local admin login and password but teh issue is that my VEEAM backup is failing as well. It says "Task failed Error: Cannot complete login due to an incorrect user name or password." which is the whole reason I discovered this issue was related to VCENTER login via Vsphere client.

Kindly help

Hello,

I installed a new DC server with Windows Server 2012 in my lab. I moved all roles from my old DC server (Windows 2008 Server) over and demotes the DC server and shut it off.

What happens that Vcenter SSO won't recognize my domain login accounts anymore. I have found a KB article to rejoin the Vcenter server to the domain. Unfortunately this didn't fix my issue.

I logged in to Web client with the admin@domain-system account and saw that sign on and discovery configuration the active directory identity still prompts to the old server. I changed it to the new server, but the test cannot see the new DC server. I realise the ldap url points to a port.3268.

Is this port different or there is another url for DC with Windows 2012 Server? Perhaps Vcenter 5.1 doesn't support Win2012 Server yet.

This is only my lab so not really a big problem.

Thanks,

Edy

Hi,

Our VDP server had some DNS problems. After we solved them, we've found there is no way to manage the appliance through VCenter WebClient. Though the VDP plugin is installed there, our VDP appliance does not show up in the appliances list, thoough there is no way to get to manage it.

The VDP appliance is running fine, backups are getting launched and we get the email reports for the backups, integrity check tasks run fine, the only problem we find is we can't manage the VDP appliance.

Kind regards...

Some hosts are not showing a SHA1 thumbprint when I go to verify the SSL certificated in vCenter.  This is causing the vCenter 5.1 Pre-Upgrade check to hang.  I can get the SHA1 by using openssl at the CLI.

Any ideas?

When selecting a VM to migrate the option to migrate is greyed out.  In fact, Power On, Migrate, Revert to Current Snapshot are greyed out.  I would like to migrate this VM to another host and datastore.

ESXi version 5.1.0 build 1021289

VMware vCenter Server, 5.1.0 build 947673

I've migrated 154 VMs and out of the 154 VMs migrated approximately a dozen VMs would not allow for live migrations(migrate... option greyed out).  I could not identify any commonality between the dozen VMs that did not allow for live migrations.

I really need to migrate this VM in a live state if at all possible.

When vCenter checks to see if a VM is a valid candidate to migrate, what does it check for because the migrate option is NOT grey for about a second before it becomes greyed out?

I'm running vCenter 4.0, and in the middle of doing an upgrade to 5.1 (using the separate installation method).  So far Single SignOn, WebClient, and Inventory Services were installed fine.

While updating the actual vCenter Server, I got this error:  "The SSL certificate for this product is expired.  See Knowledge Base article kb.vmware.com/kb/1009092."

So reading that KB then pointed out "If you are upgrading to vCenter Server 5.1, see Implementing CA signed SSL certificates with vSphere 5.1 (2034833)."

Reading that KB, all I can say is wow!  Is this really all necessary?   I'm wondering if maybe I just need to upgrade the host certificates?  Or some way to tell it to ignore expired certs?