Hello Experts,
We have ESX 5.1 in our datacenter and we would like to upgrade to ESX 5.5 latest update.
We currently have the following licence on ESX 5.1:
VMware vSphere 5 Enterprise Plus Licensed for unlimited number of VMs
Will the licence be retained after moving to ESX 5.5? Or I need to purchase a new set of licence keys for ESX 5.5?
Is there anything else, I need to take a back-up of?
Could you also point me to relevant pages that will help in the upgrade.
Thanks,
Nirmal
Hi all of you,
how can we monitor esxi state on vcenter appliane the same as with vcenter server ussing powercli
Thank you
If your VMware support is running then you no need to pay additional charge for upgrade 5.1 to 5.5 but if it is expired then you have to take separate license for ESXI and VCenter enterprise 5.5.
Update Manager is the best option to upgrade ESXI 5.1 to 5.5 without any downtime and if you upgrade ESXI then you must be required to upgrade VCenrer from 5.1 to 5.5 else it will not work.
Thanks for the info Paltelkalpesh.
One very dumb question, We have been managing the host with vSphere Client only and do not have vCenter Server installed.
Can the same licence which I have purchased for ESX host 5.1, work for vCenter product?
Regards,
Nirmal
Hi there,
You can use PowerCLI the same with the appliance as you can with the Windows server if you've already had something set up.
What exactly is it you wish to monitor?
vM
-----------------------
VCAP-DCD / VCAP-DCA / VCP-CLOUD / VCP-DT / VCP5 / VCP4
-----------------------
vMustard.com
Hi there,
So am I correct in saying that your host losing the HBA will lose access to all it's datastores in this instance?
If so then essentially your host will be looking at an All Paths Down (APD) condition, the IO for all VMs on that host will timeout and fail and the VMs will be halted.
If you have a HA enabled cluster and all admission control policies are met then these VMs will be restarted on other hosts, if not you will need to power the VMs down before they can be restarted elsewhere (or you restore access to the datastores for your host)
In terms of testing from vCenter I'm not sure how best to do this, usually vCenter will do all it can to prevent an APD as far as I'm concerned as obviously this isn't usually a desirable state! If physically removing the cables from the HBA or switch isn't an option (pulling cables is my preferred way of DR testing anything!), another good way to do this remotely if possible is to shut down the ports on the switch or switches your HBA is connected to.
Hope this helps, good luck
vM
-----------------------
VCAP-DCD / VCAP-DCA / VCP-CLOUD / VCP-DT / VCP5 / VCP4
-----------------------
vMustard.com
To the best of my knowledge the license keys are for major version (like vSphere 5 or vSphere 6).
So your keys should ideally work if you upgrade between same major version.
You can even test this out on any of your test environment (Non-Production) to make this works.
you could go with a normal quadport NIC and let vsphere handle the iSCSI...
Hey... thanks for the response.
Yep, the host losing the HBA (both ports on the single HBA) will no longer be able to see its datastores.
I can disable the ports on the switch no issues... I can even pull cables... But because I'm running on blades, all blades share the same uplinks to the SAN switch, so if I disable all the SAN switch ports or unplug the cables, I disconnect all hosts from the SAN. I thought I might just be able to disable the HBA for a given host from within vCenter or the Blades iLO as I just want to test what happens if one blades HBA fails.
Do I need to set anything up to deal with an APD condition outside of configuring my cluster for HA?
...running ESXi 5.5 u2.
Thanks again
Dryv
Thanks.
Can you please respond on the below question:
Can the same licence which I had purchased for ESX host 5.1, work for vCenter 5.1 or 5.5 product?
hi thx,
as we don't have DVS, is there any other way
Ah yes, understood!
Disabling the paths from that host should produce the same result in that the host will not be able to connect to the datastores, this post has a neat (albeit dangerously powerful) script that may help.
You don't need to configure anything other than standard HA, everything else is built in.
Good luck!
Hi,
by the way I noticed that the VM advanced parameter setting monitor_control.disable_mmu_largepages = "TRUE" actually completely disables EPT large page mapping
what do i have to do ?
Hi,
I'm using the VMware API Python bindings to deploy templates to new VMs.
Part of the deployment is to create a spec file, with a new NIC, for different MAC.
The VM deploys ok, boots with the OS image I want.
However, I could see it boots up to a certain point, then reboots once.
After that all is working fine.
I'm trying to figure out why it is doing this.
The template is a RHEL install, without any NIC currently configured.
These will be added through the spec file during deployment.
My suspicion is that this is causing the reboot once after the deployment.
But I have never seen a VM reboots after I added a NIC to it.
Any help is much appreciated.
Thanks,
Christian
Installation from iLO using the img file works fine for me.
Hi Christian,
I'd recommend to check /var/log/vmware-imc/toolsDeployPkg.log to find out what triggers that reboot, along with /var/log/messages entries in Guest OS.
To confirm whether it's the customization scripts causing it, you might want to test deployment without the customization applied to see how the VM behaves on its own, with no extra steps post-clone process.
Thanks Eugene,
wasn't aware of the deploy log file.
But it looks like the customization is responsible in some sort for the reboot.
But looking at the items to be modified on the host, a normal service restart would be sufficent from my point of view.
Looks like there is not much I can do here.
Last few lines from the deploy log
INFO: Query config for ^(DNS\|SUFFIX\|)
DEBUG: Match Found : DNS|SUFFIX|1
DEBUG: 0
DEBUG: opening file for writing (/etc/dhclient-eth0.conf).
DEBUG: Command: chmod 644 /etc/dhclient-eth0.conf
DEBUG: Result:
INFO: Query config for ^(DNS\|NAMESERVER\|)
DEBUG: Match Found : DNS|NAMESERVER|1
DEBUG: 0
DEBUG: Match Found : DNS|NAMESERVER|2
DEBUG: 1
DEBUG: opening file for writing (/etc/dhclient-eth0.conf).
DEBUG: Command: chmod 644 /etc/dhclient-eth0.conf
DEBUG: Result:
INFO: Customizing Date&Time ...
INFO: Customization completed.
Transitioning from state INPROGRESS to state Done.
ENTER STATE Done
EXIT STATE INPROGRESS
Deployment succeded.
Wait before set enable-nics stats in vmx.
Trying to connect network interfaces, attempt 1
Got VMX response 'queryNicsSupported'
Got VMX response 'disconnected'
Got VMX response 'connected'
The network interfaces are connected on 1 second
Launching cleanup.
Command to exec : /bin/rm
sizeof ProcessInternal is 56
Returning, pending output from stdout
Returning, pending output from stderr
Process exited normally after 0 seconds, returned 0
No more output from stdout
No more output from stderr
Customization command output:
Rebooting
Command to exec : /sbin/telinit
sizeof ProcessInternal is 56
Returning, pending output from stdout
Returning, pending output from stderr
Process exited normally after 0 seconds, returned 0
No more output from stdout
Good day everyone.
We have one Dell Powervault MD3220i with 18x 900GB 10K Rpm drives that currently running out of space. We are planning to attach to it an MD1220 with a 6Gb SAS Cable and having 18x 600GB 15K rpm drives and 4x800GB SSD.
We pretend to move to the SSD volume some of the most I/O intensive servers at least one app server and one exchange server and to use this SSD volumen for VMs snapshot so it can improve the time it takes backup software to create/remove the snapshot wich currently limit us to not run backups/replicas on production hours so our RPO is about 24 hours and we are looking to low that.
Please let me know your thoughts/recommendation on this or better ways to improve it.
Thanks in advance
Did you ever figure this out ?