djciaro's Accepted Solutions

Nobody else seems to be using StorageTek 6140 with VMware (which I can perfectly understand) We decided in the end to retire the 6140s and replace them with TinTri boxes after a successful POC. W... See more...
Nobody else seems to be using StorageTek 6140 with VMware (which I can perfectly understand) We decided in the end to retire the 6140s and replace them with TinTri boxes after a successful POC. We are going to use the TinTri T540 (even though there is a new T600 series, the order was made before they were released)
Hi Guys, VMware have finally updated the documentation to reflect the correct steps to be followed: https://www.vmware.com/support/pubs/heartbeat_pubs.html Select 6.5 U1 from the drop down and yo... See more...
Hi Guys, VMware have finally updated the documentation to reflect the correct steps to be followed: https://www.vmware.com/support/pubs/heartbeat_pubs.html Select 6.5 U1 from the drop down and you'll see the last update date for each of the docs is now 10/10/2013. The guide now specifically states to restore the vCenter database before proceeding with any other steps, this is copied below for your convenience: "Upgrading the Primary Server Continuation of the upgrade process assumes the upgrade of the Secondary server completed successfully. Procedure 1 Before proceeding with the upgrade procedure, perform a restore of the vCenter Server database, Single Sign-On database, VMware Update Manager database, and SSL certificates that were backed up at Step 4 on the Secondary Server. regards Ciarán
•.vmxf file - This file is a supplemental configuration file that is not used with ESX but is retained for compatibility purposes with Workstation. It is in text format and is used by Workstation... See more...
•.vmxf file - This file is a supplemental configuration file that is not used with ESX but is retained for compatibility purposes with Workstation. It is in text format and is used by Workstation for VM teaming where multiple VMs can be assigned to a team so they can be powered on/off or suspended and resumed as a single object. Compatibility to convert/migrate/copy/move/restore/test between ESXi to Workstation
You can upgrade using the HP ISO, present it to your server, when prompted perform an upgrade rather than an install. The HP iso includes the CIM providers and drivers. Although I always pe... See more...
You can upgrade using the HP ISO, present it to your server, when prompted perform an upgrade rather than an install. The HP iso includes the CIM providers and drivers. Although I always perform a fresh install rather than an upgrade, if you have enterprise plus you can use a host profile to to save the current configuration and reapply after the fresh install.
its esxcfg NOT esx-cfg
Minimum Requirements for vCenter Server 1. - CPU – 2 CPUs - Processor – 2.0GHz or faster Intel or AMD processor. Processor requirements might be higher if the database runs on the same ... See more...
Minimum Requirements for vCenter Server 1. - CPU – 2 CPUs - Processor – 2.0GHz or faster Intel or AMD processor. Processor requirements might be higher if the database runs on the same machine. - Memory – 3GB RAM. Memory requirements might be higher if the database runs on the same machine. vCenter Server includes a service called VMware VirtualCenter Management Webservices. This service requires 128MB to 1.5GB of additional memory. The VirtualCenter Management Webservices process allocates the required memory at startup. - Disk storage – 2GB. Disk requirements might be higher if the database runs on the same machine. - Microsoft SQL Server 2005 Express disk requirements – Up to 2GB free disk space to decompress the installation archive. Approximately 1.5GB of these files are deleted after the installation is complete. - Networking – Gigabit connection recommended. 2. Microsoft SQL Server 2005 Express is Supported in vCenter Server 4.0 3. Make sure the system on which you are installing vCenter Server is not an Active Directory domain controller, primary or backup. more info: http://www.vmware.com/pdf/vsphere4/r40/vsp_40_upgrade_guide.pdf If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!
Download the ISO: http://www.vmware.com/download/download.do?downloadGroup=ESX350U4 and burn to a CD shut down your VMs reboot your ESX and boot from the CD perform an upgrade of... See more...
Download the ISO: http://www.vmware.com/download/download.do?downloadGroup=ESX350U4 and burn to a CD shut down your VMs reboot your ESX and boot from the CD perform an upgrade of the ESX server If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!
try the following vm-support -x - to list vmid's vm-support -X <vmid> to kill it.. once the process has finished try and start your VM If you found this informatio... See more...
try the following vm-support -x - to list vmid's vm-support -X <vmid> to kill it.. once the process has finished try and start your VM If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!
as you are changing the esx.conf you will need to restart (be sure and create a backup of esx.conf... cp /etc/vmware/esx.conf /etc/vmware/esx.conf_backup If you found this informati... See more...
as you are changing the esx.conf you will need to restart (be sure and create a backup of esx.conf... cp /etc/vmware/esx.conf /etc/vmware/esx.conf_backup If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!
In order to remove the RDM disk you would need to stop the VM .. if you can stop the VM you don´t need Storage VMotion, simply stop the VM and migrate to the new Storage. If you found th... See more...
In order to remove the RDM disk you would need to stop the VM .. if you can stop the VM you don´t need Storage VMotion, simply stop the VM and migrate to the new Storage. If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!
you need to place the FQDM and IP address of all ESX servers in the cluster in the host file on each ESX: Do not remove the following line, or various programs that require network fu... See more...
you need to place the FQDM and IP address of all ESX servers in the cluster in the host file on each ESX: Do not remove the following line, or various programs that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost SERVER IP ADDRESS SERVER NAME SERVER IP ADDRESS FQDN SERVER e.g. 192.168.1.12 myserver.mycompany.com If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!
I would suggest go with RAID 10 Number of disks and size depends on the VMs that will be running off the disks, Have a read of this article which i found both interesting and usef... See more...
I would suggest go with RAID 10 Number of disks and size depends on the VMs that will be running off the disks, Have a read of this article which i found both interesting and useful http://www.miracleas.com/BAARF/RAID5_versus_RAID10.txt If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!
restart your management service service mgmt-vmware status (under ESXi via the server GUI) you should be able to perform actions such as power on /off etc on the VM now. If it was an ... See more...
restart your management service service mgmt-vmware status (under ESXi via the server GUI) you should be able to perform actions such as power on /off etc on the VM now. If it was an ESX server you could use the following commands: vm-support -x - to list vmid's and find your VM vm-support -X <vmid> to kill it.. If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!
I hope my comments were of help to you, please don´t forget to award points, its the only payback we get for investing valuable helping others in the forum! If you found this inform... See more...
I hope my comments were of help to you, please don´t forget to award points, its the only payback we get for investing valuable helping others in the forum! If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!
yes its is possible, the storage has nothing to do with NLB, its Network load balancing just about traffic going to different hosts. useful info: http://blog.baeke.info/blog/_archives/2006/2/... See more...
yes its is possible, the storage has nothing to do with NLB, its Network load balancing just about traffic going to different hosts. useful info: http://blog.baeke.info/blog/_archives/2006/2/21/1775587.html If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!
connect to your ESX with the VI client and select administration and roles you should see administrator, read only and no access, you will see clone if you right click on one of those role... See more...
connect to your ESX with the VI client and select administration and roles you should see administrator, read only and no access, you will see clone if you right click on one of those roles (see attached pic) If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!
Do you mean in networking: To change the Network Label and VLAN ID for a port group 1. Log in to the VMware VI Client and select the host from the inventory panel. 2. Click the Conf... See more...
Do you mean in networking: To change the Network Label and VLAN ID for a port group 1. Log in to the VMware VI Client and select the host from the inventory panel. 2. Click the Configuration tab and click Networking. 3. On the right side of the screen, find the vSwitch to edit and click Properties for that vSwitch. 4. Click the Ports tab. 5. Select the port group, and click Edit. 6. Click the General tab. 7. Edit the Network Label or the VLAN ID and click OK to save the new settings. If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!
Maximum number of cores per server 32 (ESX 3.5 & ESX 3.5i) http://pubs.vmware.com/vi301/install/wwhelp/wwhimpl/common/html/wwhelp.htm?context=install&file=install_requirements.4.10.h... See more...
Maximum number of cores per server 32 (ESX 3.5 & ESX 3.5i) http://pubs.vmware.com/vi301/install/wwhelp/wwhimpl/common/html/wwhelp.htm?context=install&file=install_requirements.4.10.html
Hi, When you power off your VM and right-click over your VM (via VI Client) one of the options is migrate, Once you select migrate the Wizard will open and the steps are as follows: ... See more...
Hi, When you power off your VM and right-click over your VM (via VI Client) one of the options is migrate, Once you select migrate the Wizard will open and the steps are as follows: 1. Select destination (this can be another ESX or the same ESX) 2. Select resource pool (again this can be the same) 3. Select Datastore, here you need to choose the option Move virtual machine configuration files and virtual disks and select your SAN 4. Review your selection and click finish You will see the progress in the recent tasks bar in your VI client, once the task has completed you can start up your VM again All the best If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!
60 is the maximum: 4 SCSI * 15 devices SCSI controllers per virtual machine 4 Devices per SCSI controller 15 Devices per virtual machine (Windows) 60 Devices per virtual machine (Linux) 60... See more...
60 is the maximum: 4 SCSI * 15 devices SCSI controllers per virtual machine 4 Devices per SCSI controller 15 Devices per virtual machine (Windows) 60 Devices per virtual machine (Linux) 60 http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_config_max.pdf If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!