Hello,
I see Release Notes
These CPU restrictions apply to vSphere, or only to hosts with ESXi 6.7?
These CPU restrictions apply only to host with VCSA 6.7 VM, or to all hosts in organization?
↧
vSphere 6.7 Unsupported CPUs question
↧
Stepwise porcedure to Upgarde esxi 6.5
Need stepwise Pocedure to upgrade esxi 6.5
1) what is Prerequisite for upgrade ESXi 6.5
2) What shoud be upgrade before upgrade esxi 6.5
3) What steps need to be taken care before Up gradation.
4) What is min H/w Criteria.
Thanks in Advance
↧
↧
Error upgrade to VCSA 6.7
Hello,
I try upgrade VCSA 6.5 to 6.7, but on final stage get error:
Error setting network. Details : 23/04/2018 14:08:46 [ERROR] Cannot run /sbin/ifup eth0 command. Unknown error. Return code : 256 output: Make sure the interface is down or not assigned any IP eth0 is DOWN or not assigned an IP. Bringnig eth0 up... Can not find the manual filename, let us search for the auto filename Performing duplicate address check for IPv4 address a.b.c.d [1;31mError: IP already exists in the network [0;39m Unable to set the network parameters
Failed to set network
-------------------
a.b.c.d is IP of old VCSA (6.5)
↧
Upgrade from 5.0 to 6.0 insights
I have a customer that has requested assistance in this upgrade scenario, and am looking for any feedback on my thought process.
Current:
VSphere 5.0 Standard environment
5 ESXi 5.0 hosts
1 vCenter Server 5.0 (Windows platform)
No additional or ancillary VMWare solutions deployed in this environment
Upgrade goals::
1) Replace each ESXi host with a new hardware resource. The hardware will be equivalent in terms of CPU resources.for the purposes of licensing.
2) Upgrade each ESXi host from 5.0 to 6.0
3) Upgrade vCenter Server from 5.0 to 6.0 and any other components to compatible versions (of course).
My thought process in terms of process:
1) Upgrade vCenter Server 5 to vCenter Server 6
2) vMotion any vms from existing ESXI 5 host-1 to other existing ESXI 5 hosts
3) Remove ESXi 5 host-1 from environment
4) Shut down now vacated ESXi 5 host-1 to be replaced
5) Set up new hardware host resource with ESXi 6
6) Add new ESXi 6 host-1 to environment and configure appropriately for storage, etc.
7) vMotion any vms from existing ESXi 5 host-2 to other existing ESXi 5 and newly deployed ESXi 6 host-1
8) Remove ESXi 5 host-1 from environment
9) Shut down now vacated ESXi 5 host-2 to be replaced
10) Set up new hardware host resource with ESXi 6
11) Add new ESXi 6 host-2 to environment and configure appropriately for storage, etc.
12 and on...) repeat steps 7-11 until all ESXi 5 hosts are replaced with ESXi 6 hosts
Any feedback, thoughts, advice, etc.; on anything I might be missing here? Any input appreciated.
Cheers and Thanks
↧
Upgrade 6.0 to 6.5 with new hosts - new cluster or not
Hi,
We currently have a small cluster of ESXi 6.0U2 hosts using shared storage. We are about to add an additional six hosts which we will install ESXi 6.5U1 and we will then upgrade our current production hosts to the same version (ESXi 6.5U1).
We have already upgraded vCenter to 6.5.
My initial thoughts were to
1. Create a new cluster for the new 6.5 hosts
2. Migrate using vMotion some VMs from the original 6.0 cluster
3. Gradually upgrade the original ESXi 6.0 to 6.5 using VUM and then move them into the new cluster
4. Continue migrating VMs to the new cluster and upgrading the ESXi 6.0 hosts
Or do I just add the new 6.5 hosts into the production cluster with the 6.0 hosts without the need to create a new cluster? I assume if I wanted to use this approach I should initially create some affinity rules specifying that VMs should run on either the 6.0 or 6.5 hosts so that I can control their migration (vMotion) in case of any unexpected results?
Having not created the production cluster initially I assume if we wanted to create a new cluster I just need to replicate the settings that are on the Configure tab of the current cluster?
I understand that I would need to continue using hardware level 11 and that if we created any VMFS-6 datastores on the 6.5 hosts that the VMs hosted on them would need to remain on ESXi 6.5
I would really appreciate some views on the best method and if there are any issues that I need to consider.
Thanks a lot.
↧
↧
Issue when moving the host into cluster
Hello all,
I'm getting "The host's CPU hardware should support the cluster's current Enhanced vMotion Compatibility mode…" error when trying to move Lenovo x3650 M5 into the cluster with EVC enabled.
What I've tried so far:
1) As per KB 1003212, I've checked VT and XD are enabled in the BIOS
2) As per IBM RETAIN tip: H214692, I've set Operating Mode to Maximum performance
3) With EVC disabled, the host can be added to the cluster
4) I've tried all available EVC Modes (starting from "Merom"). Still the same error.
The server is pretty new, but now I'm going to check for firmware updates. Any other hints/recommendations? I feel like it should be something simple, that I might forgot.
The server is Lenovo x3650 M5 8871AC1 with Xeon E5 2690.
Environment is vSphere 6.5
↧
Can't install "VMware-ClientIntegrationPlugin-5.6.0.exe" ( got error from Windows10 OS)
Hi. Support staff,
I tried to install "VMware-ClientIntegrationPlugin-5.6.0.exe" but install program got fail
with error as follows, (Language is Japanese)
Hence, I am not able to login Web console from my PC blower.
---------------------------------------------------------------------------------------
このWindowsインストーラパッケージは問題があります。
セットアップの一部として実行されるプログラムは正しく
完了しませんでした。サポート担当者またはパッケージの
ベンダーに問い合わせてください。
---------------------------------------------------------------------------------------
PC: windwos10 pro
ver 1709
OS build 16299.431
Regards,
↧
VM Version on ESXi 6.7
Hi all,
I am in the process of upgrading my hosts from 5.5 to 6.5 then to 6.7
My VMs are either version 8 or 10.
My question is does ESXi 6.7 support VM version 8/10? Or do I need to upgrade my VMs one by one before powering them back on after my host is upgrade to 6.7?
Thanks
↧
Upgrading Windows vcenter 5.5 to vcenter appliance 6.7
I don't see a direct route but I see I can go from 5.5 to 6.5 and I should be able to go from 6.5 to 6.7
So I am trying to go from 5.5 to 6.5 and am running into an issue.
I'm using the following guide.
How to upgrade Windows vCenter 5.5 to the 6.5 Appliance - VirtuallyBoring
When I try running the migration-assistant (and I do run as Administrator as indicated) I keep getting the message:
Check that VMware vCenter Server services are up and running, and that the entered credentials are valid.
As far as I know all services are running. I checker in the service manager and all that should normally be running are. There are a few services that I do not normally run.
Like Orchestrator Server and Configuration and Snapshot provider. All the rest of my VMware services are running. I even tried running all of these, with the same result.
I verified that the firewall is disabled and I verified that the credentials let me into the web interface.
Administrator@vsphere.local works with the password I am providing to the web interface.
What other tests can I run to find where the issue is? Is there another method of upgrading. It is a semi simple environment I don't mind reorganizing my machines into folders. I just need them to continuously run as I migrate.
↧
↧
Windows VMs lost disks?
So, I have an odd one:
I'm setting up a small business virtual environment. Right now, I only have 2 servers involved:
Disk: 2012 R2 physical server that has a Dell SCSI array attached to it. It shared out those disks over iSCSI. I also have vSphere installed on there (not optimal, but it will work for a while)
Host: ESX 5.5 host with small business licensing on it. I have 2 VMs spun up, both 2012 R2, one a DC and the other a terminal server.
The Host machine sees the Disk's arrays via a cross over cable. Not great - but it works.
It was all setup and working fine, with the host looking at the iscsi disks on the Disk server, and the VMs running on the host. Then, I'm guessing we had a power outage at some point?
The disk server came back up fine. It sees the SCSI disks and has no errors.
The host came back up, but the VMs did not. They didn't have auto boot turned on. I booted them by hand.
My problem: both my VMs came up saying that the operating system can't be found, like the disk is missing?
- The disk is there an attached. I verified in vsphere and the config file
- The iscsi disks are mountable and I can browse and view all the files just fine
- I removed the VMs from inventory and readded, same problem.
- I removed the hard disks and readded them, same thing.
Its almost like both VMs lost their boot partitions or something? I boot the VMs into their BIOS, and they don't see the disks, even though they are attached.
Any thoughts on how to fix this? I just started, and could start over, but I"m concerned I have a bigger issue. I can't have this happen once these are in production.
Thanks!!!
↧
vCenter server (Appliance) at the remote console turned to login page - I cannot turn it back to page F2 - F11 to restart
I pressed some key combination by mistake - and I do not remember which one
Please give me a hint to shut it down or to restart - I need to switch on the shell
↧
vcenter 6.5 update2 to 6.7
Is it true I cannot upgrade from 6.5update 2 to 6.7?
if so is vmware going to fix this issue in the future?
I upgraded my vcenter to 6.5u2 all on windows vcenters. Now i am planning on going to 6.7 via a direct upgrade
↧
Enabling audio
Reading on forums and blogs I see that I can enable sound for client Windows Server VMs running as Windows Remote Desktop servers hosted by VMware ESXi 5.5 hosts by adding the following lines to the .vmx file:
sound.present = "true"
sound.allowGuestConnectionControl = "false"
sound.virtualDev = "hdaudio"
sound.fileName = "-1"
sound.autodetect = "true"
sound.pciSlotNumber = "34"
It works fine for me and I am considering adding the lines to the .vmx file of all the Remote Desktop Server VMs in my vSphere infrastructore.
Given that only few VMs will really use audio, is there any reason for not enabling sounf for all the VMs?
Regards
marius
↧
↧
Can`t boot the OS in VM on the nested ESX 6.0...
Hi guys , i have Hyper-V role enabled on the laptop , where there is an ESX running as a VM , on which i have deployed VM and now trying to boot the OS from ISO or existing vmdk...
while doing it , the following problem comes up (CentOS):
and this one with Windows Server ISO:
so it is just permanently hanging at that stage and no chance to break out of the deadlock...
do you know how to overcome that? would be very grateful if you can propose smth on that case
Thanks in advance!
↧
VCSA 6u2 check for updates fails using internet proxy
I am having this problem that if I use Check Updates -> Check URL I get the error "Download Failed." in the VMware Appliance Management Interface (VAMI)
Internet Proxy is configured in VAMI.
This problem applies to both of these versions.
VMware vCenter Server Appliance
6.0.0.20000 Build Number 3634791
VMware vCenter Server Appliance
6.0.0.10200 Build Number 3343022
I am checking
/var/log/vmware/applmgmt/software-packages.log
and find
Resolving vapp-updates.vmware.com... failed: Name or service not known.
wget: unable to resolve host address `vapp-updates.vmware.com'
Yes DNS server does not resolve internet IPs but that is no problem for vRO appliance or older vSphere Update Manager or any internet browser.
Actually nothing reaches the internet proxy (logging on firewall) it appears the VCSA does not even try to contact the internet proxy.
Anybody an idea what's wrong? I think DNS shouldn't have to forward to internet DNS, I mean VRO and older vSphere Update Manager can do without it as well.
↧
Moving licenses around to different machines or hosts
If I purchase a vsphere license pack, can I feel free to move the licenses around to different machines or hosts?
If there an activation / deactivation process?
If I wipe a machine and want to use that same license on the same machine, can I free install a new version of esxit?
↧
ESXI 6.N kickstart preinstall section questions
I am looking into what is possible to do using the kickstart preinstall section with busybox as the shell. I have some questions that I have not been able to find the answers to.
1) Can you access a console during the install by entering a command key combination? (you can do this with anaconda)
2) What commands are available to the busybox shell for during the preinstall.
3) What is the best way to log?
4) Can messages be sent to the console at least for debugging?
Same questions for the post install section.
The firstboot section I have no problems.
↧
↧
Migrate 5.1 host to 6.5 cluster
Hi, I need to migrate an existing single/stand alone ESXi server (with 9 VMs) to a new 2 nodes cluster that I'm going to setup soon.
The old host is running VMware ESXi 5.1 U3, the new cluster will use VMware ESXi 6.5 U2.
Please note that I'm planning to move to the new cluster with all the VMs down,
I do not need (nor want!) to migrate any live system.
A full weekend downtime is not an issue and hopefully enough.
The old system has only local storage, the new cluster has a SAN, of course the two systems are connected via network.
I also have in place Veeam Backup & Replication (Enterprise), but licensed only for 2 hosts (was 1 host, upgraded to 2 hosts for the new cluster).
What is the best/suggested/easier way to migrate the VMs to the new cluster?
Thank you in advance.
Enrico
↧
After upgrade to 6.5 update 1 broken AD authentication
I have upgrade VCSA to 6.5 Update 1 (from 6.5)
After this I can't login using AD credentials. administrator@vsphare.local is still working
Logs say:
Invalid credentials
exception 'com.vmware.identity.idm.IDMLoginException: Native platform error [code: 851968]
Network packects at port 389 are going. And i can add permissions at objects: vcenter sees users from AD.
"Identify Source" for domain is configured with "use machine account".
When i try to using SPN, I need type SPN as STS/domain.local, but i have error: SPN can't be found
Now i have configured AD as LDAP service, but it is not good way.
Does anyone know something about this problem ?
↧
vCenter 6.5 : failed to stat the service "vpxd"
Hello,
I have this error message :
"
Cmd "sc queryex vpxd" failed with exit code 1060
Cmd "sc qfailure vpxd" failed with exit code 1060
"
I just finish to install the vCenter 6.5 (ESXi 6.5 Essential Plus) wit success, and I just restart the Windows server.
------------
From :
c:\Program Files\VMware\vCenter Server\bin\
I try :
service-control --start vpxd-svcs
and the result is :
Perform start operation. vmon_profile=None, svc_names=['vpxd-svcs'], include_coreossvcs=False, include_leafossvcs=False
2018-06-11T15:47:19.793Z Service vpxd-svcs state STOPPED
------------
How to fix this problem ?
Regards,
↧