Hi, I have 4 blades per the HCL at my disposal to learn VMware on.
I intend to build a two blade cluster in one LAN segment (subnet), build another blade with VMware on it in another LAN segment.
Add a third blade to the first LAN segment (after the above is done).
Accomplish SRM between the two LAN segments.
Please help me by explaining to me the software that I need to install and the order in which to install it.
I am assuming trial editions of software will suffice.
So I believe you'll need to install ESXi on all blades, then deploy vCenter (appliance will probably be simpler) to one of the blades in each subnet and add the hosts to their respective vCenters. Then you'll need to set up SRM, again I believe one for each vCenter.
Provided your networking is all setup to allow the two to communicate this should do the trick I think, but get ESXi on all the blades first.
Hope that helps!
Ok cool. I think I have a handle on at least the installation part. I should be able to learn:
1)Migrating a VM from one blade to another
2)Doing a P2V
I have not one but two questions:
1)What other VMware tasks should I learn on such a setup as described by me
2)What is VMtrubo and can I learn it using my setup
Thanks in advance.
The trial download for vCenter 6 for Linux does NOT have the linux .pkg file. It is not possible to install vCenter on anything other than windows server 2008 (cannot be a pdc). This is not cool. VMware should in the high standards of trial downloads provided by companies not itself provide all the required pieces of software and make it easy for those attempting to learn and embrace VMware
VMware provides most of the VMware products free of cost for 60 days evaluation with all the features.
Login to this URL with VMware ID, register for trial and download VMware vCenter appliance 6.
vCenter Appliance is a Linux Based (SuSE Linux) vCenter server with vCenter software components preinstalled.
See How to deploy vCenter 6 appliance - Virtual Admin: Install VMware vCenter Server Appliance
Thanks for replying. I believe you are not correct.
I signed up for the trial and downloaded the following files:
[root@test90 vcsa]# cd /mnt/VMware/
[root@test90 VMware]# ls -al
drwxr-xr-x 2 nobody nobody 4096 May 19 14:59 .
drwxrwxrwx 29 root root 8192 May 19 12:03 ..
-rwxr--r-- 1 nobody nobody 3039696896 May 19 14:20 Vcenter6.iso
-rwxr--r-- 1 nobody nobody 3039696896 May 19 11:51 VMware-VCSA-all-6.0.0-3634788.iso [this is vCenter server download of Linux]
-rwxr--r-- 1 nobody nobody 365758680 May 18 17:20 VMware-viclient-all-6.0.0-3562874.exe
-rwxr--r-- 1 nobody nobody 2900584448 May 18 18:23 VMware-VIMSetup-all-6.0.0-3634788.iso
-rwxr--r-- 1 nobody nobody 375341056 May 18 17:20 VMware-VMvisor-Installer-6.0.0.update02-3620759.x86_64.iso
-rwxr--r-- 1 nobody nobody 1168900096 May 18 20:23 VMware-vSphere_Replication-184.108.40.20629-3656323.iso
mount -t iso9660 -o loop /mnt/VMware/VMware-VCSA-all-6.0.0-3634788.iso /a [Mounted the Linux vCenter iso on /a]
[root@test90 VMware]# cd /a
[root@test90 a]# ls -al
dr-xr-xr-x 6 root root 2048 Mar 8 06:36 .
dr-xr-xr-x. 21 root root 4096 May 19 14:29 ..
dr-xr-xr-x 2 root root 24576 Mar 8 06:36 dbschema
-r-xr-xr-x 1 root root 1360 Mar 8 06:36 readme-de.txt
-r-xr-xr-x 1 root root 1427 Mar 8 06:36 readme-es.txt
-r-xr-xr-x 1 root root 1460 Mar 8 06:36 readme-fr.txt
-r-xr-xr-x 1 root root 1553 Mar 8 06:36 readme-ja.txt
-r-xr-xr-x 1 root root 1363 Mar 8 06:36 readme-ko.txt
-r-xr-xr-x 1 root root 1260 Mar 8 06:36 readme.txt
-r-xr-xr-x 1 root root 1183 Mar 8 06:36 readme-zh-CN.txt
-r-xr-xr-x 1 root root 1160 Mar 8 06:36 readme-zh-TW.txt
dr-xr-xr-x 10 root root 2048 Mar 8 06:37 rr_moved
dr-xr-xr-x 2 root root 2048 Mar 8 06:36 vcsa
dr-xr-xr-x 7 root root 2048 Mar 8 06:37 vcsa-cli-installer
-r-xr-xr-x 1 root root 3244331 Mar 8 06:36 vcsa-setup.html
[root@test90 vcsa]# cd vcsa
-bash: cd: vcsa: No such file or directory
[root@test90 vcsa]# ls -al
dr-xr-xr-x 2 root root 2048 Mar 8 06:36 .
dr-xr-xr-x 6 root root 2048 Mar 8 06:36 ..
-r-xr-xr-x 1 root root 52 Mar 8 06:36 version.txt
-r-xr-xr-x 1 root root 95482848 Mar 8 06:37 VMware-ClientIntegrationPlugin-6.0.0.exe
-r-xr-xr-x 1 root root 2100091904 Mar 8 06:36 vmware-vcsa
The VMware vCenter Linux package is missing
I forgot to mention here but later thought you would check it on that blog post.
You need to deploy VMware vcsa on ESXi Host, so first install ESXi on One Host.
Then Mount/extract below ISO in Windows System which can connect to ESXi Host.
Install VMware Client Integration plugin and then start vCenter appliance deployment by opening vcsa-setup.html with Internet browser, follow the wizard to deploy vCenter Appliance.
See the complete vcsa deployment process - Virtual Admin: Install VMware vCenter Server Appliance
Note, VMware do not provide any .pkg or rpm files for vCenter Installation on Linux.
Appliance is SuSE Linux Vm with all vCenter component preinstalled, we just need to deploy and configure it.
I see you have mounted ISO in Linux but I would suggest you, get one Windows system and start vcsa deployment form there.
Yes, Any Windows System will work. make sure you have network connectivity with ESXi Host.
can you connect to ESXi Host from Windows System from where you started deployment?
Also make sure your root password meets below requirements.
Password of the root user of the vCenter Server Appliance
The password must be at least 8 characters, but no more
than 20 characters in length.
The password must conform to the following
example, a dollar sign ($), hash key (#), at sign (@),
period (.), or exclamation mark (!).
Still no luck, hangs at "validating"
I set the password per the guidelines
I can ping the ESXi host
I installed putty on the windows system and enabled ssh on the ESXi machine and I can successfully ssh to it
I can open http/https connections to it
Good to know that you are able to fix it.
To get vMotion working, you need to create Vmkernel PortGroup on each Host and mark it for vMotion traffic.
You need to assign IP address to Vmkernel PortGroup.
Make sure each Host's vMotion PortGroup network name is identical.
Below are some useful URLs to setup SRM