what does HA/DRS depend on? Does it depend on DNS? will HA work with just IP? how about DRS?
need this info for quick interview
thanks
what does HA/DRS depend on? Does it depend on DNS? will HA work with just IP? how about DRS?
need this info for quick interview
thanks
I have Dell EMC San.
VM-cluster in 5 hosts.
I razed Datastore size from 20 to 22 tb.
In VSphere size rased successful. But when VeaamBR makes backup of any vm size of cluster shrinks to 20Tb.
After clicking "refresh capacity information" on this datastore - ut's updates and displaying sixe 22Tb.
Then story continuing.
What should i do whit this issue?
when I did a restored a virtual disk from veeam back software is restored a wrong virtual disk and replaced my shared date virtual disk on vmware vcenter 6.0
now my shared data virtual disk is missing, is there a way to recover?
my original virtual disk is not any more on the VM folder.
So we added 4 new hosts to our 10 host cluster and suddenly the existing hosts are showing this error:
The vSphere HA agent on this host cannot reach some of the management network addresses of other hosts, and HA may not be able to restart VMs if a host failure occurs:
info
31/07/2019 2:38:57 PM
Hostname
So my guess is that this is happening since we added a new Backup VLAN to the hosts. This backup VLAN has the "Management Traffic" checkbox checked and this is causing the error. I assume that VMware is seeing 2 Management VMKernels, one in the Management VLAN and one in the Backup VLAN and it is confused as to which one to use for management traffic.
If this is the case then is it possible to "tell" VMware to use one VMKernel for management traffic amongst hosts and the other specifically for Backup traffic?
Is anyone else experiencing a failure when installing VC 6.5? I have this occuring when installing using the CLI installer, and when deploying the OVA using the ESXi web client.
The version of VC is 6.5.0 build 4240420, the recent release candidate.
The exception report looks like:
Encountered an internal error. Traceback (most recent call last): File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 2017, in main vmidentityFB.boot() File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 349, in boot self.configureSTS(self.__stsRetryCount, self.__stsRetryInterval) File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 1478, in configureSTS self.startSTSService() File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 1140, in startSTSService returnCode = self.startService(self.__sts_service_name, self.__stsRetryCount * self.__stsRetryInterval) File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 88, in startService return service_start(svc_name, wait_time) File "/usr/lib/vmware/site-packages/cis/utils.py", line 784, in service_start raise ServiceStartException(svc_name) ServiceStartException: { "resolution": null, "detail": [ { "args": [ "vmware-stsd" ], "id": "install.ciscommon.service.failstart", "localized": "An error occurred while starting service 'vmware-stsd'", "translatable": "An error occurred while starting service '%(0)s'" } ], "componentKey": null, "problemId": null }
My group and I am curious to hear whether or not anyone else is experience this and if there are any workarounds.
Thanks!
I recently removed a physical host from a vCenter Server virtual appliance and am not able to add it back to vCenter Server because I get an error about the datastore already existing. I am running a simple vCenter Server environment with two physical hosts and shared storage. I have only been administering vCenter for a few months, so I am relatively new to the technology and processes. I have searched the Internet for a few days now, but have not found any documentation of anyone experiencing the same problem as I (which I find odd considering how simple my configuration and problem), so I wanted to get some help from the VMware community.
I got an error message one day that vCenter Server couldn't connect to one of the two hosts so I removed the host (instead of disconnecting and connecting as I should have done). Now I am not able to connect the host to vCenter server because the shared storage datastore conflicts with the same datastore used by the existing host in vCenter Server. The error message I get is ""Datastore 'datastore_name' conflicts with an existing datastore in the datacenter that has the same URL (ds:///vmfs/volumes/UUID/), but is backed by different physical storage." I try to unmount the datastore from the host, but get the following error message: "The resource 'Datastore Name: datastore_name VMFS uuid: UUID' is in use." The error stack says, "Call "HostStorageSystem.UnmountVmfsVolume" for object "storageSystem" on ESXi "IP address" failed. Cannot unmount volume 'Datastore Name: datastore_name VMFS uuid: 'UUID' because file system is busy. Correct the problem and retry the operation." I have tried removing all virtual machines from inventory, putting the hosts in maintenance mode, rebooting the physical hosts, but none of my troubleshooting is helping.
I am not sure what steps to take to get this datastore unassociated with the host so that I can add it back into vCenter Server. Any help you can provide me is appreciated.
Is there a way to manually copy files to a subscribed content library? I have a subscribed content library that isn't copying one template and I would like to manually put it there then have it seen as being copied.
Hi!
I have VC 5.5u3e on Windows Machine
and have SQL server 2008r2 on another machine
Problem: Vcenter stops after starting
Faulting application name: vpxd.exe, version: 5.5.0.47851, time stamp: 0x57989851
Faulting module name: KERNELBASE.dll, version: 6.3.9600.19178, time stamp: 0x5bc006fd
Exception code: 0xe06d7363
Fault offset: 0x0000000000008e6c
Faulting process id: 0xe40
Faulting application start time: 0x01d551b43fd81620
Faulting application path: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\vpxd.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 37609500-bdaa-11e9-80fd-005056927c7b
Faulting package full name:
Faulting package-relative application ID:
some text from vpxd:
2019-08-13T12:10:45.475+03:00 [07560 warning 'win32vpxdOsLayer_win32'] [VpxUnhandledException] Backtrace
--> backtrace[00] rip 000000018018c5da
--> backtrace[01] rip 0000000180105408
--> backtrace[02] rip 000000018010675e
--> backtrace[03] rip 00007ff6141fe0da
------ In-memory logs start --------
mem> ansaction is detected at the end of the batch. The transaction is rolled back.
mem> 2019-08-13T12:10:45.447+03:00 [11604 verbose 'vpxdvpxdMoHost'] [HostMo::GetLinkedVmInt] Getting linked vm vm-42054 (with vmid 11) on host esx1.ro79.fss.ru for given vmid 11
mem> 2019-08-13T12:10:45.447+03:00 [10636 warning 'Default'] [VdbStatement] Bind parameters:
mem> 2019-08-13T12:10:45.447+03:00 [10636 warning 'Default'] [VdbStatement] datatype: 1, size: 4, arraySize: 23
mem> 2019-08-13T12:10:45.447+03:00 [10636 warning 'Default'] [VdbStatement] value = 64444
mem> 2019-08-13T12:10:45.447+03:00 [10636 warning 'Default'] [VdbStatement] datatype: 1, size: 4, arraySize: 23
mem> 2019-08-13T12:10:45.447+03:00 [10636 warning 'Default'] [VdbStatement] value = 0
mem> 2019-08-13T12:10:45.447+03:00 [10636 warning 'Default'] [VdbStatement] datatype: 3, size: 8, arraySize: 23
mem> 2019-08-13T12:10:45.448+03:00 [10636 warning 'Default'] [VdbStatement] value = 64174248
mem> 2019-08-13T12:10:45.448+03:00 [10636 warning 'Default'] [VdbStatement] datatype: 1, size: 4, arraySize: 23
mem> 2019-08-13T12:10:45.448+03:00 [10636 warning 'Default'] [VdbStatement] value = 3238
mem> 2019-08-13T12:10:45.448+03:00 [10636 error 'Default'] [Vdb::IsRecoverableErrorCode] Unable to recover from 42000:3998
mem> 2019-08-13T12:10:45.448+03:00 [10636 error 'Default'] [VdbStatement] SQLError was thrown: "ODBC error: (42000) - [Microsoft][SQL Server Native Client 11.0][SQL Server]Uncommittable transaction is detected at the end of the batch. The transaction is rolled back." is returned when executing SQL statement "{ call insert_stats_proc(?, ?, ?, ?) }"
mem> 2019-08-13T12:10:45.448+03:00 [10636 error 'clustervpxdMoCluster'] ClusterMo::CollectLocal database error while flushing stats data: "ODBC error: (42000) - [Microsoft][SQL Server Native Client 11.0][SQL Server]Uncommittable transaction is detected at the end of the batch. The transaction is rolled back." is returned when executing SQL statement "{ call insert_stats_proc(?, ?, ?, ?) }"
mem> 2019-08-13T12:10:45.448+03:00 [11840 verbose 'commonvpxTaskInfo' opID=QS-host-51603-5167c51e] [TaskInfoPublisher::IncListeners] host:[host-51603] Return after successful IncListeners (listeners = 2, _connectionGen = 2)
mem> 2019-08-13T12:10:45.448+03:00 [11840 verbose 'commonvpxTaskInfo' opID=QS-host-51603-5167c51e] [TaskInfoListener::TaskInfoListener] copy-constructed. Connection number = 2
mem> 2019-08-13T12:10:45.448+03:00 [10636 verbose 'statsvpxdStatsCollector'] Enter FlushInt()
mem> 2019-08-13T12:10:45.448+03:00 [11840 verbose 'commonvpxTaskInfo' opID=QS-host-51603-5167c51e] TaskInfoChannel created for session[6d8048d0-4b20-14f1-0816-a5ce7d3ea4fd]52c819d4-6e3a-a8c0-579f-8e62044c7fb2
mem> 2019-08-13T12:10:45.448+03:00 [11840 verbose 'commonvpxTaskInfo' opID=QS-host-51603-5167c51e] [TaskInfoPublisher::AddChannel] host:[host-51603] Channel (session[6d8048d0-4b20-14f1-0816-a5ce7d3ea4fd]52c819d4-6e3a-a8c0-579f-8e62044c7fb2) added for task: session[6d8048d0-4b20-14f1-0816-a5ce7d3ea4fd]52c819d4-6e3a-a8c0-579f-8e62044c7fb2
mem> 2019-08-13T12:10:45.448+03:00 [11604 verbose 'vpxdvpxdMoHost'] [HostMo::GetLinkedVmInt] Getting linked vm vm-42050 (with vmid 21) on host esx1.ro79.fss.ru for given vmid 21
mem> 2019-08-13T12:10:45.448+03:00 [11840 verbose 'commonvpxTaskInfo' opID=QS-host-51603-5167c51e] [TaskInfoChannel::GetTaskInfo] task: session[6d8048d0-4b20-14f1-0816-a5ce7d3ea4fd]52c819d4-6e3a-a8c0-579f-8e62044c7fb2 setup for async notification
mem> 2019-08-13T12:10:45.448+03:00 [11604 verbose 'vpxdvpxdMoHost'] [HostMo::GetLinkedVmInt] Getting linked vm vm-42052 (with vmid 25) on host esx1.ro79.fss.ru for given vmid 25
mem> 2019-08-13T12:10:45.448+03:00 [11604 verbose 'vpxdvpxdMoHost'] [HostMo::GetLinkedVmInt] Getting linked vm vm-44865 (with vmid 26) on host esx1.ro79.fss.ru for given vmid 26
mem> 2019-08-13T12:10:45.448+03:00 [11604 verbose 'vpxdvpxdMoHost'] [HostMo::GetLinkedVmInt] Getting linked vm vm-42058 (with vmid 27) on host esx1.ro79.fss.ru for given vmid 27
mem> 2019-08-13T12:10:45.449+03:00 [12780 verbose 'PropertyProvider'] RecordOp ASSIGN: disabledMethod, vm-333961
mem> 2019-08-13T12:10:45.449+03:00 [07560 verbose 'Default' opID=task-internal-1-2244a405-64-81-3a-1f] [JrnlFilePersistenceProvider::DeleteJournal] Deleting C:\ProgramData\VMware\VMware VirtualCenter\journal\1565687249.39.
mem> 2019-08-13T12:10:45.450+03:00 [13152 verbose 'Default' opID=525C109D-000000CD-70] [VpxVmomi] Invoke done: vmodl.query.PropertyCollector.waitForUpdates session: 182ffcf7-eaa2-4130-9ace-f5406219632f
mem> 2019-08-13T12:10:45.450+03:00 [13152 verbose 'SoapAdapter.HTTPService' opID=525C109D-000000CD-70] HTTP Response: Complete (processed 1214 bytes)
mem> 2019-08-13T12:10:45.451+03:00 [12976 verbose 'vpxdvpxdMoHost'] [HostMo::GetLinkedVmInt] Getting linked vm vm-46214 (with vmid 3) on host 10.58.105.133 for given vmid 3
mem> 2019-08-13T12:10:45.451+03:00 [05168 verbose 'Default' opID=72fe638f] [VpxVmomi] Invoking [retrievePropertiesEx] on [vmodl.query.PropertyCollector:propertyCollector] session [8224ffd4-b241-b0dd-cb73-6086c5720462(527742e8-d692-67db-ecc6-c5b610603cad)]
mem> 2019-08-13T12:10:45.451+03:00 [13152 info 'commonvpxLro' opID=72fe638f] [VpxLRO] -- BEGIN task-internal-70159 -- -- vmodl.query.PropertyCollector.retrievePropertiesEx -- 8224ffd4-b241-b0dd-cb73-6086c5720462(527742e8-d692-67db-ecc6-c5b610603cad)
mem> 2019-08-13T12:10:45.452+03:00 [11208 verbose 'vpxdvpxdMoHost'] [HostMo::GetLinkedVmInt] Getting linked vm vm-32075 (with vmid 2) on host esx1.f09.ro2.fss.ru for given vmid 2
mem> 2019-08-13T12:10:45.452+03:00 [11208 verbose 'vpxdvpxdMoHost'] [HostMo::GetLinkedVmInt] Getting linked vm vm-32074 (with vmid 3) on host esx1.f09.ro2.fss.ru for given vmid 3
mem> 2019-08-13T12:10:45.452+03:00 [11208 verbose 'vpxdvpxdMoHost'] [HostMo::GetLinkedVmInt] Getting linked vm vm-32076 (with vmid 4) on host esx1.f09.ro2.fss.ru for given vmid 4
mem> 2019-08-13T12:10:45.452+03:00 [12976 verbose 'vpxdvpxdMoHost'] [HostMo::GetLinkedVmInt] Getting linked vm vm-46215 (with vmid 4) on host 10.58.105.133 for given vmid 4
mem> 2019-08-13T12:10:45.452+03:00 [11604 verbose 'vpxdvpxdMoHost'] [HostMo::GetLinkedVmInt] Getting linked vm vm-465025 (with vmid 28) on host esx1.ro79.fss.ru for given vmid 28
mem> 2019-08-13T12:10:45.453+03:00 [01912 info 'vpxdvpxdVmomi' opID=HB-host-28758@347601-497fe794] [ClientAdapterBase::InvokeOnSoap] Invoke done (esx1.ro51.fss.ru, vmodl.query.PropertyCollector.cancelWaitForUpdates)
mem> 2019-08-13T12:10:45.453+03:00 [07560 error 'commonvpxLro' opID=task-internal-1-2244a405-64-81-3a-1f] [VpxLRO] Unexpected Exception: vmodl.fault.SystemError
mem> 2019-08-13T12:10:45.453+03:00 [07560 verbose 'commonvpxLro' opID=task-internal-1-2244a405-64-81-3a-1f] [VpxLRO] Backtrace:
mem> --> backtrace[00] rip 000000018018c5da
mem> --> backtrace[01] rip 0000000180105408
mem> --> backtrace[02] rip 000000018010675e
Any Ideas?
Hi Guys,
I currently have my prod vCenter running on another vCenter as a VM. I want to take it off and move it to different hardware (one that it manages) and setup HA on it.
I've tried to move it a couple of times using VMWare converter but both times it fails. It seems to boot up and I can log in but after a few mins it just craps out. Its easy to revert back as i can simply power up the VCSA that i converted from. The vCenter is running on a ephermal port on the Distrubuted switch.
I get error 503 when trying to log in,
I was going to try a new approach setup a shared datastore between the 2vcenters migrate vcenter to that and unregister it.
then while vcenter is down, i connect directly to the one of the hosts that the downed vcenter is managing and register it there and boot it up.
I think that should, work, although i thought using vmware converter would have also worked. I read somewhere that maybe it should be running in a stardard vswitch, but when i spoke to vmware tech support he said running on an epermal port should be fine.
any help appreciated.
Since VMware Knowledge Base states Virtual Hardware Version 9 is minimum requirement for Hypervisor-Assisted Guest Mitigation for branch target injection (CVE-2017-5715), Is it safe to upgrade virtual hardware on VCSA?
We recently installed vCenter Server Appliance to replace the existing vCenter server. It automatically installs a Evaluation Mode license and then gives warnings that licenses are about to expire. Since we already own an Enterprise license, we added these licenses to the new vCenter server and then added the existing hosts to the new vCenter server. The hosts were added to the correct license key and the vCenter server was added to the correct license key. The Evaluation Mode license now has a 0 usage. Everything is working correctly except that the eval license is still sitting there and we are still getting warnings. It appears that the only way to get rid of this is to upgrade the eval license to a purchased license, but we don't need to upgrade since we already have a valid Enterprise license.
How can we remove the eval license and remove the warnings that this is generating?
Has anyone else noticed that the option to "Use the Customization Wizard to temporarily adjust the specification before deployment" that exists in the C# client when deploying a machine from a template using the Customization Wizard is missing from the web client?
Has anyone else found that option as useful as I do to make one-off changes to a customization at deployment time that I don't want to save as a new customization?
Has anyone out there found an acceptable work around to this? If it still hasn't made it into 5.5 I don't even think it's on their radar.
Since upgrading from U2 to U3 I'm unable to deploy from a library template if I use a customization spec, it won't go further than the Select Networks screen.
Has anyone else seen this issue?
I have been asked to update ssl certs on a clients VMware 5.5 instance which has me stumped.
SSO and inventory updates worked fine, get to vcenter update step 2 and I get this error
[Fri 08/30/2019 - 8:56:16.07]: Last operation update vCenter Server SSL certificate failed :
[Fri 08/30/2019 - 8:56:16.08]: Cannot log in to vCenter. Please check C:\Users\admin\Downloads\ssl-certificate-updater-tool-1308332\logs\vc-update-ssl.log for more details
---------- C:\PROGRAMDATA\VMWARE\VMWARE VIRTUALCENTER\VPXD.CFG
[Fri 08/30/2019 - 8:55:49.98]: Validating the input parameters...
STATE : 4 RUNNING
HTTPError: Unable to open or read page.
HTTP Error 401: basic auth failed
[Fri 08/30/2019 - 8:56:16.04]: "Cannot log in to vCenter."
[Fri 08/30/2019 - 8:56:16.05]: The vCenter certificate update failed.
I can login to web client but not desktop client as administrator@vsphere.local.
I can login to web client as domain user but get sso error from desktop client.
I have read and confirmed this isn't set in vpxd. VMware Knowledge Base
I have tried VMware Knowledge Base and step 8 I get this error
C:\temp>ssolscli.cmd listServices https://mgmt.domain.com:7444/lookupservices/sdk
Intializing registration provider...
Getting SSL certificates for https://mgmt.domain.com:7444/lookupservices/sdk
Unexpected status code: 404
Unexpected status code: 404
Return code is: OperationFailed
100
I hope someone can enlighten me on the cause/resolution.
Thanks
Hi, there. Could someone tell me if the development of vCenter plugin is open to external third party?
If is open, Is there any documents or guide about how to develop and deploy, and any Develop specification?
I'm getting these errors when i try to install vCenter 6.0
Firstboot script execution Error.
The supplied System Name vcsa6.mydomain.com is not valid.
Posts like this:
Suggest that DNS is the problem. I'm using a home router as my DNS server and it doesn't allow you to manually update DNS records. How can I complete the install without changing my router? There has to be a way to install vCenter Server without a dependency on DNS...
While a VM is Suspended it’s IP address lease may expire and the IP address will be allocated to someone else.
When the VM is Powered ON after being Suspended it still has the original IP address and therefore has an IP address conflict with the “someone else”.
This can cause problems for the “someone else” and the original VM.
It can also cause problems with cached DNS entries on other peoples PC’s
Is there anything we can do avoid this problem?
Can we force the Suspended VM to attempt “renew” its IP address when it is Powered ON?
Is there a vmWare “wakeup” script file we do this in?
Many Thanks
Wayne Clements
Dears,
The database Directory in my Vcenter is around 95%. So i checked the Database and i noticed that tables Event and Event_arg are so huge. So i decided to find the best way to delete the old data from them.
I tried to use Database Retention Policy and I adjusted the event.maxAge to "1" and event.maxAgeEnabled to "True" and as i read, this should delete the old data on those 2 tables at night 00:15 everyday, by keeping Data of the last day only. However that didn't happened.
What could be the problem ?
I ran the VCSA VUM (6.5) and got the following error:
Scan Entity: "There are errors during the scan operation. Check the events and log files for details."
I checked the logs in the CLI and saw the following when grep ing for 'error':
[2019-09-06 20:36:41:000 'VciScanTask.ScanTask{60}' 139866374936320 INFO] [vciTaskBase, 1362] VciTask { id: ScanTask{60}, type: com.vmware.vcIntegrity.ScanTask }: Setting VC task state to: error
That seemed to be the only 'error' in the logs at that time (about one second off the time displayed in the Recent Tasks pane), but it's not very elaborate to be able to resolve the issue. How can I fix this?
I'm getting the same in my Production environment but no changes have been made to our network since we migrated to the VCSA in both. I've used the VUM previously to upgrade in both. We did upgrade the VCSA using the VAMI, recently, but that's about all I can think of that might impact this. Any help is appreciated. Thanks in advance.
EDIT: I just noticed this occurs only when the Virtual Appliance option is the only item checked. It seems to work other wise, as far as I can tell.