at the time of crash please post from affected VMs and Hosts : vmkernel.log vmware.log /vmfs/volumes/526bda53-1f2b17a6-2ebf-001b21a44f80/Virtual Machines/Production/es-1.company.local/vmx-zdum...
See more...
at the time of crash please post from affected VMs and Hosts : vmkernel.log vmware.log /vmfs/volumes/526bda53-1f2b17a6-2ebf-001b21a44f80/Virtual Machines/Production/es-1.company.local/vmx-zdump.000 /vmfs/volumes/526bda53-1f2b17a6-2ebf-001b21a44f80/Virtual Machines/Production/es-1.company.local/vmmcores.gz
yes i have seen it this is the same script as i mention in my post. you mention just KB which has nothing to do with the custom entries inside config file... To get it working there must be p...
See more...
yes i have seen it this is the same script as i mention in my post. you mention just KB which has nothing to do with the custom entries inside config file... To get it working there must be proper entries/values which reflects exactly what you want ... this cannot be accomplished by KB article itself it is just a baseline. Can you post your config file for analysis?
Hi, for resolution see this thread and Dallo answer at third page: Loading ESXi installer issue " Relocating modules and starting up the kernel" if this doesn't resolve your issue upgrade ...
See more...
Hi, for resolution see this thread and Dallo answer at third page: Loading ESXi installer issue " Relocating modules and starting up the kernel" if this doesn't resolve your issue upgrade your BIOS to the latest available version here: IBM Support: Fix Central
so your domain account must be member of some other group to which more restrictive permissions applies on affected hosts... Please double check if your domain account has administrator role o...
See more...
so your domain account must be member of some other group to which more restrictive permissions applies on affected hosts... Please double check if your domain account has administrator role on the highest (vCenter) level AND that the same account is not part of some local or domain group which has some restrictions at lower level objects-> i.e. those affected hosts... You can also try to create brand new user grant him administrator role at vCenter level...login and test if those two hosts are manageable or not.
when you connect through vCenter server select the host which you cannot manage and look at permissions tab. Post what role on the host is assigned to account you use to login to the vCenter ser...
See more...
when you connect through vCenter server select the host which you cannot manage and look at permissions tab. Post what role on the host is assigned to account you use to login to the vCenter server inventory.
VUM is a part/component of vCenter server installation you cannot manage ESXi 5.5 hosts with VUM 6 without vCenter 6 in your environment ... (can be at the same machine as VC or on diff comp) ...
See more...
VUM is a part/component of vCenter server installation you cannot manage ESXi 5.5 hosts with VUM 6 without vCenter 6 in your environment ... (can be at the same machine as VC or on diff comp) And in addition always start with vCenter server upgrade...follow order below but before have a look at these guides: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2109772 http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2108548 Upgrade First vCenter Single Sign On VMware vCenter Inventory Service VMware vCenter Server VMware vSphere Client VMware vSphere Web Client VMware vSphere Update Manager Upgrade ESXi hosts (VUM) Upgrade VMTools (VUM) Upgrade Virtual Hardware (VUM) Upgrade Product licenses (vCenter , ESXi, …) Upgrade VMFS to proper version (if applicable) Upgrade SRM (if deployed)
Hi, your problem is Intel Xeon CPU E5-2637 v3 @ 3.5GHz because V2 and V3 family includes brand new features mising from the first starting family version. For details on new features see: In...
See more...
Hi, your problem is Intel Xeon CPU E5-2637 v3 @ 3.5GHz because V2 and V3 family includes brand new features mising from the first starting family version. For details on new features see: Intel® Xeon® Processor E5-2600 V2 Product Family Technical Overview | Intel® Developer Zone Intel® Xeon® Processor E5-2600 V3 Product Family Technical Overview | Intel® Developer Zone This difference cannot be cleared by VMHW upgrade .... It is expected that you cannot define EVC baseline right know ... you will not be able to do so until all the VMs in that cluster runs with the same/acceptable feature sets... So you have to power off all the VMs on E5-2637 machine enable EVC on cluster with "Intel Sandy Bridge gen." baseline and then power on all the VMs back. To prevent VMs from auto-migration switch DRS to Manual mode.
Hi, well it depends how your identity sources and permissions were organized before the upgrade, for post upgrade SSO behavior check: How SSO Affects Upgrades Also have a look at these: V...
See more...
Hi, well it depends how your identity sources and permissions were organized before the upgrade, for post upgrade SSO behavior check: How SSO Affects Upgrades Also have a look at these: VMware KB: vCenter Server not listed in the inventory after installing or upgrading to vSphere 5.5 / 6.0 VMware KB: After upgrading to vCenter Server Appliance 6.0 domain user log-in fails with the error: Wrong Username/P… VMware KB: After Installing or Upgrading to vCenter Server 6.0, logging in to the vSphere Web Client for all users r… For roles/permissons backup try these scripts: http://blog.vmote.net/documents/Export-vCenter-Permissions.ps1 http://blog.vmote.net/documents/Import-vCenter-Permissions.ps1
Hello an Welcome to the community, VMware HCL says it supports your HW with Intel Xeon E5-2600-v2 Series which means all the CPUs (26XX) in this serie including 2690v2... Your server model...
See more...
Hello an Welcome to the community, VMware HCL says it supports your HW with Intel Xeon E5-2600-v2 Series which means all the CPUs (26XX) in this serie including 2690v2... Your server model is supported with this CPU family and with Nvidia Quadro K4000 GPU... Please post more details about upgrade failure what errors you get etc. Before you start double check that you have the latest BIOS/Firmware installed on the server and for upgrade download the latest release of ESXi which is 6.0 Update 1, here: https://my.vmware.com/group/vmware/info?slug=datacenter_cloud_infrastructure/vmware_vsphere/6_0 RN: http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-esxi-60u1-release-notes.html#compatibility
check if you are able to download U3 with account which has Super User/Procurement permission at My VMware portal... Otherwise I would contact VMware support for guidance: VMware Support | Un...
See more...
check if you are able to download U3 with account which has Super User/Procurement permission at My VMware portal... Otherwise I would contact VMware support for guidance: VMware Support | United States / Headquarters | United States VMware KB: How to file a Support Request in My VMware There are similar experiences, see: My VMware's "You either are not entitled or do not have permissions to download this product." error, and what to do abo…
Hi, it is a sudden case or it happens after some configuration changes in your infrastructure? How they appear in the inventory HC view as disconnected (grayed), with red-cross sign...?? A...
See more...
Hi, it is a sudden case or it happens after some configuration changes in your infrastructure? How they appear in the inventory HC view as disconnected (grayed), with red-cross sign...?? Also verify your account permissions on hosts I suppose they are not joined to the domain so your direct access account differs from account you used for login to vCenter server. I am I right? There are too many unknowns so please be more specific... Please post vmkernel and fdm.log from hosts. Anyway as an reference for hosts diagnosis see: VMware KB: Diagnosing an ESXi/ESX host that is disconnected or not responding in VMware vCenter Server
Hello, Yes that works with earlier ESXi releases (3/4.x) ....but from ESXi 5.x this is the standard behavior because "direct" web access is only allowed through vCenter server via Web Clien...
See more...
Hello, Yes that works with earlier ESXi releases (3/4.x) ....but from ESXi 5.x this is the standard behavior because "direct" web access is only allowed through vCenter server via Web Client. However from ESXi 6.0 and with the new Embedded Host Client fling you can access host directly without vCenter server and C# client deployed...:) New HTML5 Embedded Host Client for ESXi | virtuallyGhetto
Hi, based on the suffix they are not used and usable in such form and are probably leftover by some 3rd party solution rather than by storage vMotion ... So from this perspective it is safe t...
See more...
Hi, based on the suffix they are not used and usable in such form and are probably leftover by some 3rd party solution rather than by storage vMotion ... So from this perspective it is safe to delete them... nevertheless (from vSpeher 5 above ) if you try to unmount such Datastore you will be presented with unmount prerequisite check that will prevents you from such operation because of existing VMs... If you want to be sure about those files you can perform these checks: Verify the last time they were used: # ls -ltr /vmfs/volumes/<DS_UUID>/<VM_DIR>/ | grep vmdk.orig ; | grep vmx.orig To verify if the file is locked use: # touch /vmfs/volumes/<DS_UUID>/<VM_DIR>/HQEDDB01.vmx.orig ... or # vmkfstools -D /vmfs/volumes/<DS_UUID>/<VM_DIR>/HQEDDB01.vmx.orig If you want to verify what HQEDDB01.vmdk.orig contains you can mount it to another VM or use VMware Workstation or VMware Disk Mount utility here: https://my.vmware.com/web/vmware/details?productId=47&downloadGroup=WKST-550-DISK-MOUNT-UTL
Hi, regarding reverting to the EVAL mode...this is possible only if some eval days remained at the moment of switching to the licensed version. If they weren't exhausted you can switch back t...
See more...
Hi, regarding reverting to the EVAL mode...this is possible only if some eval days remained at the moment of switching to the licensed version. If they weren't exhausted you can switch back to the eval mode through Config tab -> Software, Licensed Features. If there are no eval days left the only option is to reinstall the host, regarding existing datastores you will be asked in interactive installer what you want to do with them (preserve, overwrite...) it depends on their layout and ESXi installation location. It is always recommended to backup VMFS datastores before you will proceed with setup. Because API limitations of the free ESXi version you are quite limited with backup solutions one of the option is ghettoVCB.sh - Free alternative for backing up VM's for ESX(i) 3.5, 4.x & 5.x LACP is only supported on vSphere Distributed Switches (VDS) and yes this feature to be deployed and configured requires vCenter server.
Hello, have you installed CDO 1.2.1 (Collaboration Data Objects) before you launch VDP Tool... "If you use the VDP Exchange configuration tool, the MAPI client libraries and CDO 1.2.1 must be...
See more...
Hello, have you installed CDO 1.2.1 (Collaboration Data Objects) before you launch VDP Tool... "If you use the VDP Exchange configuration tool, the MAPI client libraries and CDO 1.2.1 must be installed on the server you intend to run that tool on. When you install the MAPI client libraries and CDO 1.2.1, it is recommended that you perform that step before you create the VDP Exchange account." anyway in my opinion the "current user" error applies to VDPBackupUser account not to the user currently logged, unless not required (only for Exchange 2007) try to add VDPBackupUser account to the domain admin group at least temporarily.