Thursday, November 28, 2013

Get your voucher to take exam 74-409 for free

Hey Guys,

I am back with some really important info.


Get your voucher to take exam 74-409 for free here: 
 
The number of free exams is limited; obtaining a voucher does not guarantee a free exam, so schedule your exam soon. Vouchers expire and all exams must be scheduled and taken by June 30, 2014.

Best of luck and once again Happy Learning. 

Warm Regards

Abhi

Thursday, July 4, 2013

Installing vC Ops 5.7.1 on VMware Workstation

Hi Guys,

Back after a long break.

I tried installing Standalone windows version of vC Ops on one of the Windows servers, but i really did not get much time and it was createing more problems than helping me inderstand.

So i thought of installing vApp version.

If you have tried installing the vApp version of vC Ops you must have noticed it will not allow you to import it on VMware Workstation.

As you know i don't have pretty big lab with multiple ESXi hosts i have to make sure that i import the vAPP on my workstation.

Here are the steps you can also follow to import vC Ops 5.7.1 on your desktop LAB.

1) Download latest version of vC Ops (5.7.1)from my vmware portal.
2) as you have a LAB you must have ESXi and vCenter installed there. Powered down all the VMs in the lab and increase RAM to atleast 4 GB for ESX servers.
3) In the LAB vCenter Import the downloaded vApp.
4) Once imported change the RAM setting from 9 and 7 GB to 2 GB per VM.
5) Power on the VM.
6) It will do the initial configuration required to run as a vAPP.
7) Connect it with IP you assigned to UI VM.
8) Power off the VM
9) To make sure everything is working, power it on again and connect to the IP.
10) From vCenter power off the vApp.
11) Go to individual VM in vApp and go to edit settings modify following setting.

12) This disables the vApp settings for the VM
13) Export the VM to OVA or OVF.

Now copy the VM from your virtaul vCenter to Desktop HDDs.
and import the OVF/OVA to your workstation.
As we are doing it for test use thin provisioning for the disks unless you have few 100 Gigs free for vcops.

Power on  Analytics VM wait for some time and the VM to come up, then power on UI VM.

Make sure it is on the same network as your rest of the test machines.

Connect to the UI VM from Browser by IP and do the initial configuration of vC Ops.

We are not done yet.

Once you add vCenter in vC Ops it will reflect in your vCenter, assign proper key else you will be working with foundation version of vC Ops which is free from Vmware.

Hope this will help you to test vC Ops in VMware workstation like me if you to are running low on resources.

Do let me know if it helped you or you faced some issues.

Till then Happy Learning.

Abhi

Monday, May 13, 2013

LAB Boot Process

If you are also planning to get your hands dirty like me may be thats the reason you are reading this blog.

Here i am giving you the boot process i follow to boot and shutdown my LAB as i am doing this on a Desktop and really dont want it to keep running 24x7.

Power ON Process
  1. Power on DC first (for me DC also has extra load of iSCSI disks provided to ESXi servers hence DC/Storage server first.
  2. vShild Manager (Not necessarily at number two but must be before vCloud)
  3. ESXi Hosts (Make sure Storage server is up and running before they boot up)
  4. vCenter (Once ESXi are up and running fire up vCenter)
  5. Power on All the VSE devices
  6. vCloud after every one is up and running
  7. vC Ops at last as you dont want it to stast informing you what is missing if you booted it early.
Now ShutDown Process.
  1. vC Ops
  2.  Power Off all vApps
  3. vCloud Director
  4. VSE devices
  5. ESXi Hosts
  6. vCenter
  7. vShield
  8. finally DC/Storage server.
Let me know if any one has a better option to tweak this boot order

Final post about installing vC Ops in Windows environment for tomorrow.

Till then

Happy Learning.

Upgrade vCloud Director from 1.5.0 to 1.5.2


As said in the morning post this is the first post in he three series post coming.

One of the reasons behind building the LAB is testing various upgrades and upgrading vCD 1.50. to 1.5.2 is one in the list.

First we tried to do it our way.... Installed another CentOS box, installed new vCloud director 1.5.2 and asked him to work on the same Database which was used by older vCloud 1.5.0.

Not to say it Failed big time.

That helped us learn something about the global.properties file (/opt/vmware/vcloud-director/etc/global.properties) they have and a system.info property which stores a key used to encrypt the DB.

The some google gave let us know that we can directly upgrade our vCD.

Here are the steps which we followed.

I already had downloaded vCD 1.5.2 bin file
Apart from that I made sure that cell-management-tool-1.0.0-bin.tar.gz at
/opt/vmware/cloud-director/bin/ is available. (these are required at step 3)

Logged on to vCloud server as root.
Ensured that the installation file is executable.                                                                                   chmod u+x ./vmware-vcloud-director-1.5.2-924077.bin.
Gracefully shut down the cell
    1. Log in to the target cell as root.
    2. Navigate to/opt/vmware/vcloud-director/bin/.
    3. Suspend the scheduler by running this command:                                   cell-management-tool -u username -p password cell -q true
    4. View the tasks that are running using this command:
      cell-management-tool -u username -p password cell -t
    5. When the task count reaches zero, shut down the cell by running this command:
      cell-management-tool -u username -p password cell -s                                                         
Navigate where /tmp and run the command ./vmware-vcloud-director-1.5.2-924077.bin.     This identifies that vCD 15.0 was already installed and then upgraded it to 1.5.2 
         


 It does not finish here once upgrading vCD need to upgrade the Databse as well buy running upgrade script  /opt/vmware/vcloud-director/bin/upgrade and type Y when prompted to upgrade the database. 
 



Start the cloud cell by typing the following command:                                                                            service vmware-vcd start
And you are ready to rock with vCD 1.5.2 login on the console and confirm everything is as it was earlier.

Happy Learning

Pretty busy and fruitful Weekend for my Sandbox

Hey Guys........

Had a really nice weekend for me working in my LAB.
Here are the updates and expect some long posts in follow ups :)
1) Thanks to my Friend my Storage got upgraded with another 250 GB SATA HDD now its 500 GB.
2) We successfully upgraded vcd 1.5.0 to 1.5.2.
3) After a lots of fight vC Ops 5.7.0 standalone windows version is up and running, configuration pending
4) Finalized and tested boot sequence for the LAB.

To followup you can expect atleast 3 posts for point 2-4.

After adding extra HDD DC01 which is hosting iSCSI disks is relocated to this new disk. New vC Ops is also enjoying less Disk contention on the new disk.

Going forward expecting last element in the LAB and that is VCM 5.7 by End of this Week.

So expecting another busy and fruitful week and a weekend ahead.

Till then Happy Learning .........

Friday, May 10, 2013

Finaly my vCloud is working

Hey Good news first My Vmware vCloud 1.5.0 Lab is working

This is how i was in problem and i solved them.

After rigorous fighting with compatibility between my vCLoud Director 1.5.0 and vShield Manager 5.1.2, i reach to a truth that they are not compatible with each other.
That made me use older version of vShiled with my more older vCloud director :).

Going down with vShild version 5.0.0 was not easy as well.
Took my two nights out but i am happy as it is working gr8 no.
There seems some problem with vApp or OVA file of vShiled 5.0.0 I was not able to import it in my Vmware Workstation. It was going till EULA if i accept it was not importing the vApp but again asking me to acceot EULA again, was in a loop.

Good the OVA can be extracted :) with winrar. Then you will find 4 files  you can safely delete 2 small files then what remains are OVF file and a VMDK file.
I tried to directly import the OVF but Vmware was testing me.
I was not able to import ovf as well, this time it was not even going till Eula.
Good you can open OVF file in Wordpad, and tweak it as you need.

After few hours of permutation and combination i found a working ovf file which i can you to import the vApp, Meanwhile i tried making a virtual machine with the VMDK i had extracted that also failed :(.

Finally i was able to import the vApp and launch the vShiled manager, but my test was not over.
After logging in the vShiled and running enable command i was getting error
  “System startup is not complete. Please logout and log back in after a few minutes.”
ahhhhh tried google a lot trashed vshiled a lot and finally got working vShild.

Now you think my issues are resolved and i m writing this blog rite????

Wrong

You know i was trying with latest version of vShild and that was registered with vCenter, i had to get rid of that if i had to register lower version of vshild.

Again doing some google gave me a hint to remove the latest version of vshiled and downgrade to lower version.


Now you are correct, after registering this working vShiled 5.0.0 i am able to create my Org networks, deploy VSE devices and I can proceed further with the LAB.

Pretty long post haaa..

Hope that was not boring but interesting.....afterall this is how i spent my last three nights must be interesting :)

Moral of the story: Dont mix and match version. first check the compatibility matrix and then go for it.
Happy learning.

Tuesday, May 7, 2013

My NEW LAB




As I am getting my Hands dirty with Cloud i definitely needed something which i can use as a sandbox.
Hence invested some money and brought following config, some of the things are borrowed from my Bros old Desktop.

Processor : AMD FX 4100 3.6 GHz with Quad Cores.
RAM        : 4x4 GB
Mbd          : Gigabyte 970 ADS3 (with 4 mem slots supports upt 32 GB of RAM)
Graphics   : ASUS ENGT 520 (Borrowed)
HDD         : 250 GB (again borrowed) Expecting another big disk from a friend :).

Installed windows 7 Ultimate x64 and works like a charm.


Following are the machines running all the time on the system.


While running so many VMs i was thinking RAM would be a Problem but it is not, hardly 10 GB is used with all machines powered on, the problem is with Disk Performance, as it has to write to atleast 5 layers for a single read/write operation.

Will put my new adventures of vCloud LAB soon.

Till then Happy Learning :).