vNEX's Accepted Solutions

unfortunately upgrade is only possible between minor releases ... 5.5.x to 5.5.x etc. Upgrading vSphere Replication The downloadable ISO image is the only means of upgrading from vSphere Repl... See more...
unfortunately upgrade is only possible between minor releases ... 5.5.x to 5.5.x etc. Upgrading vSphere Replication The downloadable ISO image is the only means of upgrading from vSphere Replication 5.1.x, 5.5.x, or 5.6 to vSphere Replication 5.8. You cannot upgrade vSphere Replication from version 5.1.x, 5.5.x, or 5.6 to version 5.8 by using vSphere Update Manager or the official VMware Update Repository from the VAMI of the vSphere Replication appliance. See the compatibility matrix for further information on supported versions. See Upgrading vSphere Replication to upgrade to vSphere Replication 5.8. See:
you should look at VMware HCL for compatible Storage/SAN systems->Array type: NAS ... for relevant ESXi host release. VMware Compatibility Guide: Storage/SAN Search For Buffalo Inc. there is ... See more...
you should look at VMware HCL for compatible Storage/SAN systems->Array type: NAS ... for relevant ESXi host release. VMware Compatibility Guide: Storage/SAN Search For Buffalo Inc. there is only one type listed: - Buffalo, Inc TS-2RZxxxTxxD but there are much other NAS vendors you can choose... One affordable VMware Ready NAS from Lenovo: http://shop.lenovo.com/gb/en/servers/network-storage/lenovoemc/ix2/ VMware Compatibility Guide: Storage/SAN Search or some from QNAP SMB range TSx53 or TSx69 series: http://www.qnap.com/useng/index.php?lang=en-us&sn=862&c=355&sc=526 VMware Compatibility Guide: Storage/SAN Search:  x69series VMware Compatibility Guide: Storage/SAN Search:  x53 series or Seagate STDF100 http://www.seagate.com/files/www-content/product-content/seagate-business-fam/seagate-nas-pro/en-us/docs/seagate-nas-pro… VMware Compatibility Guide: Storage/SAN Search: STDF100 hope it helps... Message was edited by: vNEX
Hello Oliver, yes it could but I would recreate the .pfx using the same certificate and private key from which was created the previous PFX file: openssl.exe pkcs12 -export -in rui.crt -inkey... See more...
Hello Oliver, yes it could but I would recreate the .pfx using the same certificate and private key from which was created the previous PFX file: openssl.exe pkcs12 -export -in rui.crt -inkey rui.key -name rui -passout pass:testpassword -out rui.pfx
Hi, from both error messages it seems like corrupted install source/iso try to re-download vCenter 5.5 U2 iso image and run installer again. In addition its better if you disable UAC on the... See more...
Hi, from both error messages it seems like corrupted install source/iso try to re-download vCenter 5.5 U2 iso image and run installer again. In addition its better if you disable UAC on the server before install and just to be sure verify if any AppLocker rules are not applied: Windows 7 / Windows Server 2008 R2: AppLocker - Ask the Performance Team - Site Home - TechNet Blogs For any ongoing issues refer to "Known issues" section in Release Notes: vCenter Server 5.5 Update 2 Release Notes In addition verify installation media integrity with MD5: VMware KB: Verifying the integrity of downloaded installer files VMware KB: Checking media integrity for ESX/ESXi host installations or upgrades Message was edited by: vNEX
Hi Dennis, Answers to your questions: At the next step i can click "save with appliance" or i can select a datastore with max 3 HD's a 1024 TiB. What is the difference? With "Store with a... See more...
Hi Dennis, Answers to your questions: At the next step i can click "save with appliance" or i can select a datastore with max 3 HD's a 1024 TiB. What is the difference? With "Store with appliance" checkbox selected...wizard will deploy disks in same datastore which was selected for your VDP appliance...if you want to store disks elsewhere uncheck "Store..." checkbox and chose another datastores accessible to VDP appliance. Can i use VMWare DP with a Standard licence? Yes its included from Essential Plus license and higher...
Go to -> revert to specific snap in the chain Revert to current -> revert to the snapshot from which VM is actually running i.e. to the state the VM was before taking that snapshot Delete All -... See more...
Go to -> revert to specific snap in the chain Revert to current -> revert to the snapshot from which VM is actually running i.e. to the state the VM was before taking that snapshot Delete All -> commit all snapshots/changes to base/parent disk Delete snapshot -> commit changes in selected snapshot to its parent in the chain ("You Are here" icon under desired snapshot) Consolidate -> used for repairing snapshot hierarchy i.e. leftover delta files in VM directory after Delete operation etc. ad1) Use -> Go to or Revert to  (not delete) ad2 Use Delete ad3 If you will do this you will broke entire snapshot chain and your Guest will end with PSOD If you want to delete/ discard changes made by some snapshot in the chain you must stand with "You are here" icon above that snapshot and then use "Delete" "This will also discard any snapshots in the chain tree below You Are here state" If you have only one snapshot and want to revert/discard changes use "Go to" or "Revert to current snap..." the state in Snap Manger remains the same but you will find your VM in state which it has in time where the snapshot was created...so every changes to the VM from that moment (snapshot creation) are discarded. Hope it helps...
continue to "Select a Disk" section and there under Create a Disk task you will have an option under "Disk Provisioning" to select desired disk type.
another approach exist how to detect zombie/orphaned files you can use find command from shell or some sophisticated PowerCLI scripts to detect files which were not modified for a long time. Fin... See more...
another approach exist how to detect zombie/orphaned files you can use find command from shell or some sophisticated PowerCLI scripts to detect files which were not modified for a long time. Find command below just check  mtime timestamp for the files specified... Examples of "find" command: find -iname "*" -mtime +14 (any file not modified in the last 14 days) find -iname "*-flat.vmdk" -mtime +30 ... .. . The list of files you get should be carefully revisited because it could contain valid files ... so its on your judgement to make final decision what could and what cannot be deleted. Below is PowerCli script which detects only orphaned VMDKs but it can be modified to search for another file types: Orphaned files and folders - Spring cleaning - LucD notes Regarding other file types see: Re: Orphaned Files/Folders
L2/L3 switches are out of drivers boundary for vSphere hypervisor so you cannot find any on HCL list ... Below is IBM BladeCenter interop matrix for VMware: IBM ServerProven Compatibility an... See more...
L2/L3 switches are out of drivers boundary for vSphere hypervisor so you cannot find any on HCL list ... Below is IBM BladeCenter interop matrix for VMware: IBM ServerProven Compatibility and here is interoperability of Cisco Catalyst switch 3012 with IBM BladeCenter chassis: IBM BladeCenter Interoperability Test Program hope this helps...
Hi, Check this blog post: http://www.jonathanmedd.net/2012/03/which-vms-restarted-after-a-vsphere-ha-event.html Anyway usually cluster event tab entries will tell you all the information a... See more...
Hi, Check this blog post: http://www.jonathanmedd.net/2012/03/which-vms-restarted-after-a-vsphere-ha-event.html Anyway usually cluster event tab entries will tell you all the information about HA events. If your vCenter is not for some reason available you can check aam.log (4.x) or fdm.log (5.x) files on remaining hosts directly or from syslog repository. Message was edited by: vNEX
Hi VirtualRay, there is only one metric (for both Host/VM) you can watch out only if host is actively swapping which is called "Memory Latency" it shows how much time (in %) is virtual machine... See more...
Hi VirtualRay, there is only one metric (for both Host/VM) you can watch out only if host is actively swapping which is called "Memory Latency" it shows how much time (in %) is virtual machine waiting for the memory to be swapped back in (to be read) from the disk. I usually look for ESXi memory housekeeping metrics like ballooning, compression, swapping if host is overcommited or in "time of peace" for Active/Consumed memory ratio etc... plus N%L metric which show how much time the VM is kept within its (local) NUMA node boundary... If you want to measure memory latency you can do it from inside the guest OS on Windows try to use SiSoft Sandra if you want to dig a bit deeper for hosts with Intel CPUs and Linux guests try Intel® Memory Latency Checker: https://software.intel.com/en-us/blogs/2014/01/28/memory-latencies-on-intel-xeon-processor-e5-4600-and-e7-4800-product-f… https://software.intel.com/en-us/articles/intelr-memory-latency-checker#Installation For more detailed reference on memory metrics see these sources: VMware KB: VMware vSphere 5 Memory Management and Monitoring diagram http://pubs.vmware.com/vsphere-55/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-55-monitoring-performance-guid…
Hi, 2TB-512bytes is limit for vSphere 5.1release if you need larger virtual disks  you need  5.5 release...
sorry its my fault its BIOS setting but on M520 is quite limited i.e. no delay range. Anyway try to add this command "sleep 120" to local.sh file just above exit 0 line. Refer to this KB: ht... See more...
sorry its my fault its BIOS setting but on M520 is quite limited i.e. no delay range. Anyway try to add this command "sleep 120" to local.sh file just above exit 0 line. Refer to this KB: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2043564
Hi, unfortunately Z68 chipset does not support Intel vt-d technology see: ARK | Intel® Z68 Express Chipset (Intel® BD82Z68 PCH)
Hi, this is a known issue see these KBs: VMware KB: VMware ESXi 5.x host experiences a purple diagnostic screen mentioning E1000PollRxRing, E1000DevRx and Ne… VMware KB: VMware ESXi 5.x host... See more...
Hi, this is a known issue see these KBs: VMware KB: VMware ESXi 5.x host experiences a purple diagnostic screen mentioning E1000PollRxRing, E1000DevRx and Ne… VMware KB: VMware ESXi 5.x host experiences a purple diagnostic screen mentioning E1000PollRxRing and E1000DevRx
This KB applies also for 5.x releases vim-cmd hostsvc/hosthardware works for me on 5.1 release .... same for VMware's CPUID ISO at the end of the article. You can also use esxcli to ret... See more...
This KB applies also for 5.x releases vim-cmd hostsvc/hosthardware works for me on 5.1 release .... same for VMware's CPUID ISO at the end of the article. You can also use esxcli to retrieve CPUID info  esxcli hardware cpu cpuid get or  esxcli hardware cpu global get I am sure some command exist for PowerCLI but cannot tell you right now... Lastly you can also grab some CPU info from inside the guest OS with this tools: http://www.cpuid.com/ Intel Processor Identification Utility — Intel Processor Identification Utility download for Windows
Hi, for VIB/driver install to take effect you must reboot you host. If something goes wrong don't worry you can use alt-bootbank to rollback the changes made by installer. To successfully rol... See more...
Hi, for VIB/driver install to take effect you must reboot you host. If something goes wrong don't worry you can use alt-bootbank to rollback the changes made by installer. To successfully rollback to previous image use Shift+R during initial boot process of ESXi. _________________________________________________________________________________________ If you found this or any other answer helpful, please consider to award points. (use Correct or Helpful buttons) Regards, P.
Hi, you can download tools here: http://packages.vmware.com/tools/esx/index.html Index of /45848/tools/esx/5.5latest Index of /45848/tools/esx/5.1latest Regards, P.
Hello Mike, hope this helps: 4. Track the vCenter VM through a vCenter alarm triggered script http://www.v-front.de/2013/07/do-you-know-where-your-virtual-vcenter.html Regards, P.
Hi, starting with the new licensing model there is NO memory limit (nor vRAM) for any paid edition of vSphere! so you can safely go for 128GB RAM with your Essentials edition. No reason for t... See more...
Hi, starting with the new licensing model there is NO memory limit (nor vRAM) for any paid edition of vSphere! so you can safely go for 128GB RAM with your Essentials edition. No reason for talking about vRAM pooling anymore .... (Same applies for free ESXi 5.5 hypervisor) vRAM Policy Effective August 27, 2012, VMware is eliminating the vRAM restriction on licenses to VMware vSphere. The removal of the vRAM limit from VMware vSphere licenses applies retroactively to any past and existing users of VMware vSphere, in addition to any new users of VMware vSphere. This new policy replaces and supersedes any conflicting terms in any license agreement previously agreed upon between VMware and any licensee of VMware vSphere. This change does not apply to VMware vSphere users under the VMware Service Provider Program. For details see also Licensing & Pricing whitepaper: http://www.vmware.com/files/pdf/vsphere_pricing.pdf Q: Does the new vSphere 5 licensing model—per-processor without limitation on the number of virtual machines, cores or amount of physical RAM—apply to vSphere 5.0, 5.1 and 5.5? A: Yes. The vSphere 5 licensing model applies to vSphere 5.0, 5.1 and 5.5 customers. This also applies to vSphere with Operations Management customers. Regards, P.