Hello Guys,
While upgrading my Esxi host in VCenter 6.5 my update manager gives me an incompatible error stating " The upgrade contains the following set of conflicting VIBs: Intel_bootbank_net-ixgbe_3.19.1-1OEM.500.0.0.472560 ". When I run the command esxcli network nic list I see that ixgbe is used by two of my NIC's . Will it be safe to remove this vib ?
I have attached the screenshot below.
Thank you
Hello guys,
I really need your help with my problem ASAP, my VCSA 6.7 setup get stopped at 63% every time I try to install it.
I searched if there is any SW requirements for the deployment but I found nothing !
** I attached the log.
Last lines in the log:
2019-01-28T20:13:42.917Z - info: output:ERROR
+ <Errors>
+ <Error>
+ <Type>ovftool.http.send</Type>
+ <LocalizedMsg>
+ Failed to send http data
+ </LocalizedMsg>
+ </Error>
+ </Errors>
2019-01-28T20:13:46.843Z - info: output:RESULT
+ ERROR
2019-01-28T20:13:46.843Z - info: Xml output from ovftool: <data><ManifestValidate valid="true"/><Errors><Error><Type>ovftool.http.send</Type><LocalizedMsg>Failed to send http data</LocalizedMsg></Error></Errors></data>
2019-01-28T20:13:46.843Z - error: Ovf Service:vmrefFlag: false
2019-01-28T20:13:46.843Z - info: Cancelling timeout due to error from progress callback
2019-01-28T20:13:46.843Z - error: Progress Controller: [VCSA ERROR] - Progress callback error
2019-01-28T20:13:46.843Z - error: Progress Controller: [VCSA ERROR] - Details Failed to send http data
2019-01-28T20:13:46.863Z - info: Cancelling the ping timer for session mgmt
2019-01-28T20:13:46.863Z - info: Cancelling the ping timer for session mgmt
2019-01-28T20:13:46.965Z - info: ovfProcess child process exited with code 1
2019-01-28T20:14:18.297Z - info: Log file was saved at: C:\Users\Alhawary\Desktop\installer-20190128-215825772.log
Good Afternoon,
I have a vCenter 6.0.0 Build 9313458 running at 100% CPU. In the description it only shows Java (TM) Platform SE Binary that runs and then terminates but maxes out the CPU at 100%.
I upgraded a vCenter Server Appliance 6.0 to 6.7 and things seem to be going well. I have attempted to configure VCSA configuation backups via the Appliance Management interface but receive the following error.
Structure com.vmware.appliance.recovery.backup.job.details.info has a union with a field not required for this case = end_time
First I tried via FTP to a NAS, then when getting the error I setup a FileZilla FTP server on a PC and received the same result. The user account has full RW access and the backup does create the folder structure before quitting. FileZilla logs show the vCenter logging in via FTP (below). I'm seeking information on how to troubleshoot this further. Thank you.
(not logged in) (192.168.X.X)> USER vcbackup
(not logged in) (192.168.X.X)> 331 Password required for vcenter
(not logged in) (192.168.X.X)> PASS ***********
vcenter (192.168.X.X)> 230 Logged on
vcenter (192.168.X.X)> PWD
vcenter (192.168.X.X)> 257 "/" is current directory.
vcenter (192.168.X.X)> CWD vCenter
vcenter (192.168.X.X)> 250 CWD successful. "/vCenter" is current directory.
vcenter (192.168.X.X)> CWD sn_vcenterserver.null.local
vcenter (192.168.X.X)> 250 CWD successful. "/vCenter/sn_vcenterserver.null.local" is current directory.
vcenter (192.168.X.X)> CWD M_6.7.0.21000_20190129-174717_
vcenter (192.168.X.X)> 250 CWD successful. "/vCenter/sn_vcenterserver.null.local/M_6.7.0.21000_20190129-174717_" is current directory.
vcenter (192.168.X.X)> EPSV
vcenter (192.168.X.X)> 229 Entering Extended Passive Mode (|||64934|)
vcenter (192.168.X.X)> PASV
vcenter (192.168.X.X)> 227 Entering Passive Mode (192,168,X,XXX,229,75)
vcenter (192.168.X.X)> disconnected.
ESXi 6.5
Using VR to replicate VMs to remote site.
Using SRM to manage the VMs.
Attempting to change the RPO time for one VM but fails with the error
"Unable to complete the reconfiguration task at remote site for replication group"
I'm testing out enabling smart card authentication for vcenter (yubikey specifically) and I managed to get it working but noticed that once I log out (or get logged out automatically), I cannot login again without closing the entire browser.
If a user has a bunch of tabs open, it's a bit of a pain.
The best I've been able to do is use a private browsing window but that just gets me one more login before I'm stuck again on my next login.
Is this just the way things work or is there a way to make this more workable for users?
Hi,
did someone deploy with success using any deployment method and model PSC/vCSA 6.5/6.7 on Workstation 15?
Deployment of PSC/vCSA 6.5 on Workstation 14 worked great in any model, but I can't deploy it now on Workstation 15.
I've read this articles already:
vCenter 6 VCSA External PSC in VMware Workstation - Cloudy Future
Thank You in advance
Dear Sir/Madam
I have an error when I deploy a .ova template in vcenter 6.5 u1 with 32 esxi 6.0 u3 hosts.
The error is: "transfer failed: the ovf descriptor is not available"
Here is the setup ...
I have an Ubuntu VM's (Ubuntu 18.04 ) on a host called QNAS, that claims to be a VMDK format , we are trying to get our box off this host onto our new vSphere 6.5
When I ty to convert one of the VM it goes to the end and then returns:
FAILED: An error occurred during the conversion: 'GrubInstaller::InstallGrub: /usr/lib/vmware-converter/installGrub.sh failed with return code: 127, and message: FATAL: kernel too old Error running vmware-updateGrub.sh through chroot into /mnt/p2v-src-root Command:
chroot "/mnt/p2v-src-root" /vmware-updateGrub.sh "GRUB2" "(hd0)" "(hd0,1)" /vmware-device.map "grub2-install" '
Can anyone help me with this issue or have suggestions. I tried to manually move the VMDK form this host but VMware says if does nto recognize the VMDK format. QNAS point fingers at VMware of course.
Much obliged!
Hi,
I am trying to write a PowerCli script to move a VM to a chosen folder/resource pool. I found "move-vm" is working fine against a old vCenter 6.0 instance, but doesn't work with new 6.7 VCSA for resource pool.
My code is like :
C:\>$rp=get-resourcepool "a-unique-resource-pool" -location "my-cluster"
C:\>$folder=get-Folder "a-unique-folder"
C:\>$vm=get-vm "one-vm-name"
C:\>move-vm -vm $vm -InventoryLocation $folder
### all work as expected.
C:\>move-vm -vm $vm -destination $rp
The above code works fine for vCenter 6.0, but failed on VCSA 6.7 with following error:
move-vm : 1/30/2019 5:08:43 PM Move-VM Object reference not set to an instance of an object.
At line:1 char:1
+ move-vm -vm $vm -destination $rp
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Move-VM], VimException
+ FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VimAutomation.ViCore.Cmdlets.Commands.MoveVM
I have tried to download the "PowerCLI 6.5 Release 1" from vmware website or directly install VMware.PowerCLI by "install-module VMware.PowerCLI", both have same problem.
"Get-InstalledModule" shows:
6.7.0.1... VMware.DeployAutomation PSGallery This Windows PowerShell module contains PowerCLI Auto Deploy cmdlets.
6.7.0.1... VMware.ImageBuilder PSGallery This Windows PowerShell module contains PowerCLI ImageBuilder cmdlets.
11.1.0.... VMware.PowerCLI PSGallery This Windows PowerShell module contains VMware.PowerCLI
6.7.0.1... VMware.Vim PSGallery This Windows PowerShell module contains PowerCLI Vim.
11.0.0.... VMware.VimAutomation.Cis.Core PSGallery This Windows PowerShell module contains PowerCLI Cloud Infrastructure Suite cmdlets.
11.0.0.... VMware.VimAutomation.Cloud PSGallery This Windows PowerShell module contains PowerCLI Cloud cmdlets.
11.0.0.... VMware.VimAutomation.Common PSGallery This Windows PowerShell module contains functionality required by multiple PowerCLI modules.
11.0.0.... VMware.VimAutomation.Core PSGallery This Windows PowerShell module contains Windows PowerShell cmdlets for managing vSphere.
7.6.0.1... VMware.VimAutomation.HorizonView PSGallery This Windows PowerShell module contains Connect/Disconnect cmdlets for View API service.
10.0.0.... VMware.VimAutomation.License PSGallery This Windows PowerShell module contains PowerCLI cmdlets for managing VMware product licenses.
11.0.0.... VMware.VimAutomation.Nsxt PSGallery This Windows PowerShell module contains PowerCLI NSXT cmdlets.
11.0.0.... VMware.VimAutomation.Sdk PSGallery This Windows PowerShell module contains PowerCLI Sdk.
11.0.0.... VMware.VimAutomation.Security PSGallery This Windows PowerShell module contains PowerCLI security management cmdlets.
11.1.0.... VMware.VimAutomation.Srm PSGallery This Windows PowerShell module contains PowerCLI SRM cmdlets.
11.1.0.... VMware.VimAutomation.Storage PSGallery This Windows PowerShell module contains PowerCLI storage management cmdlets.
1.3.0.0 VMware.VimAutomation.StorageUtility PSGallery This Windows PowerShell module contains utility scripts for storage.
11.0.0.... VMware.VimAutomation.Vds PSGallery This Windows PowerShell module contains PowerCLI VDS cmdlets.
11.0.0.... VMware.VimAutomation.Vmc PSGallery This Windows PowerShell module contains PowerCLI VMC cmdlets.
10.0.0.... VMware.VimAutomation.vROps PSGallery This Windows PowerShell module contains PowerCLI vROps cmdlets.
6.5.1.7... VMware.VumAutomation PSGallery This Windows PowerShell module contains PowerCLI VUM cmdlets.
The latest document I can find is https://code.vmware.com/doc/preview?id=6330#/doc/Move-VM.html
Anybody know how I can use PowerCli to move a VM to a resourcepool against VCSA 6.7?
Thanks,
Jack
We have vsphere 6.7u2 client sdk for HTML, is there any 6.7u2 sdk for flex also? OR going forward flex support will be discontinued from vmware end.
I've configured FileZilla accordingly, created a backup schedule for testing. The backup was estimated to be approx 365mb in size. The schedule kicked in and started uploading content to the FTPS server. At the 297mb mark, vcsa start deleting all the content and spits out and error, "BackupManager encountered an exception." The logs on FileZilla do not show anything unusual, but checking the /var/log/vmware/applmgmt/backup.log, I found this entry:
BackupManager encountered an exception: While reading from '/etc/systemd/network/10-eth0.network' [line 8]: option 'address' in section 'Network' already exists
I checked the file the error is referencing and that particular line is the IPv4 address of the vcsa.
I'm stumped.
Any suggestions?
Hi
I'm currently testing VCSA HA in a lab and I am seeing the following situation.
When I initiate a manual failover everything works fine and the Passive vCenter server becomes the active server and the old active server becomes the passive server. I can also fail back all fine.
However, when I simulate an uncontrolled failure of the active vCenter instance (eg power off the vm) the failover works fine, but the failed vCenter instance fails to rejoin the cluster when powered back up. This has happened every time I have done this.
Is it common for the VCHA cluster to need to be destroyed and recreated after such a failure as I see this is quite a common way to remediate issues?
I'd like to troubleshoot this scenario rather than just to rebuild the cluster each time, but I'm not sure where to look.
If I log into the vCenter server that is failing to rejoin the cluster (the passive node) I can run the Service-Control --status --all command and I notice that not many service are running. Is anyone able to tell me which services should be running on the passive node? In particular should vmware-vcha be running? as when I try to start this it returns the response that the service type is not set to automatic and skips it.
From the VCHA monitoring screen, it shoes me the Active and Witness nodes as 'UP' and the passive as 'DOWN' and suggests I check the passive node is online and accessible over the heartbeat network and I can ping the passive node from the active node all ok using the heartbeat ip address. It then says to check the replication is ok - how do I do this? I can see the vmware-postgres service is running (I had to start this manually) but what more can I do to check the replication is in synch.
Any thoughts would be very much appreciated. I'm most keen to understand what services should be running on the passive as I feel this is going to be the issue.
kind regards
Hello,
I'm trying to do a p2v with vmconverter 6.2.0 from a Redhat 7.4 server. All goes well but at startup between the bios and grud I have the message:
error: can't find command ':'
I press the spacebar several times to get to the grub menu. Then the start of the vm is happening normally.
I'm using vCenter server 5.5.0 build 2183111
Where can this error come from?
Trying to convert SLES 12.1 physical machine to vmware and it fails at the end.
Taken from the log file:
--> description = "GrubInstaller::InstallGrub: /usr/lib/vmware-converter/installGrub.sh failed with return code: 127, and message: --> FATAL: kernel too old --> Error running vmware-updateGrub.sh through chroot into /mnt/p2v-src-root --> Command: chroot "/mnt/p2v-src-root" /vmware-updateGrub.sh "GRUB2" "(hd0)" "(hd0,1)" /vmware-device.map "grub2-install" --> ", --> msg = "An error occurred during the conversion: 'GrubInstaller::InstallGrub: /usr/lib/vmware-converter/installGrub.sh failed with return code: 127, and message: --> FATAL: kernel too old --> Error running vmware-updateGrub.sh through chroot into /mnt/p2v-src-root --> Command: chroot "/mnt/p2v-src-root" /vmware-updateGrub.sh "GRUB2" "(hd0)" "(hd0,1)" /vmware-device.map "grub2-install"
Source system is Suse Linux Enterprise Server 12.1 with kernel 3.12.74-60.64.48-default
Destination system is VMware ESXi-6.0.0-20160302001-standard
Converter is VMware vCenter Converter Standalone, 6.2.0 build-8466193
Any ideas on how to overcome this?
Thanks!
Hi! I have an odd issue in vCenter where despite running a host profile compliance check and the events on each host indicating the check was successful it still shows as "unknown" in vCenter... Anyone have any suggestions what could cause this? Thanks
I have two clusters VC 5.5.0, 1476327
vc1 and vc2
Each has an SRM
Updated vcenter vc2 To version VC 5.5.0, 9911218
Now I can’t get to SRM via vSphere, I write an error: the server coul'd not interpret the client's request, (503)
On server vc2 error
[06484 warning 'LocalVC' connID=vc-admin-153c] Failed to connect: std::exception 'class Vmacore::Ssl::SSLException' "SSL Exception: error:140000DB:SSL routines:SSL routines:short read"
[06128 verbose 'LocalVC' connID=vc-admin-153c] Attempting to connect
[06128 error 'HttpConnectionPool-000000'] [ConnectComplete] Connect failed to <cs p:0000000005584a30, TCP:vck2.___.local:80>; cnx: (null), error: class Vmacore::Ssl::SSLException(SSL Exception: error:140000DB:SSL routines:SSL routines:short read)
[06484 warning 'LocalVC' connID=vc-admin-153c] Version file fetching failed with error std::exception 'class Vmacore::Ssl::SSLException' "SSL Exception: error:140000DB:SSL routines:SSL routines:short read"
[06484 warning 'LocalVC' connID=vc-admin-153c] Failed to connect: std::exception 'class Vmacore::Ssl::SSLException' "SSL Exception: error:140000DB:SSL routines:SSL routines:short read"
but in web-client i see replications
We have currently VCSA 6.0 U2 with an external PSC. We would like to upgrade to VCSA 6.5 U1 or 2 with the same external PSC.
I have been unable to find or understand the procedures to update these TWO items. I keep finding VMware on a MS box with an
embedded PSC.
Hey!,
Want to run my workflows from several vcenters.
We dont use vra in our enviroment.
Is it possible?
Thanks!!
Is it possible to install vcenter 6.5 and not have the update manager installed? If so is it possible to install the update manager?