VMWARE Lab's

VMware lab 21: Using VMware Vsphere High Availability

Task1: Create a Cluster-Enabled for vShere HA

For this, we will need to create a new cluster. Going through the suggested steps as per the booklet.

Creating the Lab cluster.PNG

 

Task 2: Add your ESXi Host to a cluster

After this we need to add the ESXi’s to the Host, For this, we will simply click and drag the ESXi’s to the New Cluster. But for this I had this warning come up, but this didn’t manage to affect anything.

Issue; 2, b.PNG

So this is how to ended up

Adding the ESxi's to the Lab cluster2; c.PNG

For this I noticed I had some issues, these issues were of which that follow. I went ahead and spent a couple of hours on this problems only to find they were covered in the later part of the task.

Errors; 3.PNG

So for one I gave each ESXi a gateway,’

Errors; 3. New gateway; a.PNG

After this i added management network to each second Virtual switch.

Errors; 3. Added management network; b.PNG

So this seemed to fix these issues. and i went on to look at the hosts and the VM. these were not correct, but before i had the chance to work on this there was a power outage as mentioned in lab M1&1.

This slideshow requires JavaScript.

Task 3: Test sphere HA Functionality

So for this, we are going to restart the Main ESXi which is the AmbersESXi, this is fact will change the master over to the Back up as shown below.

Changed Master; 15.PNG

So once i had recreated a new system i had an issue with the NTP protocol  as showen below. NTP issue; 12.PNG

So I went ahead and cheaked the NTP server, and this had stopped so i restarted it and this issue dissapeared.

This slideshow requires JavaScript.

 

Here is where I discovered an issue with my third Vm that i have created, so i deleted this off and hoped that it would be a one off.

Issues with the third vm; 16.PNG

Task 4: Veiw the vsphere HA Cluster Resource Useage. 

For this we will go into moniter inside of the Resourcen reservation tab. As seen below

This slideshow requires JavaScript.

Task 5: Manage vsphere HA slots Size.

For this, we will need to go into Settings in the new cluster, and we will go into Avalibabillity and edit this.

Edit settings; 18.PNG

First task is to turn on the Avaiablity.

Edit settings; 18a.PNGThe next step requires “Define Failover Capacity by Static number of hosts” which is not an option that we have so i decied to go with “Slot policey” as its in the name of this lab.

Edit settings; 18b.PNG

Once this is done we need to view the slot info for the Cluster,

Edit settings; 18c Sloth infomation.PNG

After this we need to Change the settings of each VM with in the cluster as seen below.

This slideshow requires JavaScript.

After this, we will then go back and have a look at the slot infomation again to note any changes. as you can see the Slot size has changed.

Refreaing the slot info; 20.PNG

After this were going to edit the settings again, in this we will change the fixed slot size, and we will caculate the size based on the VM’s we have. as seen below.

This slideshow requires JavaScript.

The new this is to go back and cheak the slot settings again, noting any changes.

Chaing the Slot settings; 21c.PNG

Again going back and changing the slot settings, as seen below to “Cover all powered-on VMs.”

This slideshow requires JavaScript.

 

Advertisements
VMWARE Lab's

Reconfigurement 1M&1

So the system has crashed again ! and we get to reconfigure the Vsim again !!

So there was a power outage, and that caused system-wide issues, this, in turn, turned off our delicate Vsim.

First off all there seemed to be no issue with the Vsim as seen below.

Aggr seems alright.PNG

But as I went on, I was unable to get into the Gui interface for this cluster.

Issues; 3.PNG

So I went and checked the system health.

Health system after downage.PNG

All seemed to be good, so I wasn’t sure of the system issue. Until I got the following message. System down..PNG

Soo… I got a new Vsim

New vsim.PNG

And I had to create a new cluster for this,

New cluster.PNG

Anc becuase of the System down my VM’s was unassessable to I had to create two new VM’s and a new template.

Create two new VM's.PNG

VMWARE Lab's

VMware Lab 19: Using Alarms

Task1 : Create a VM Alarm to moniter a condition.

For this, we need to create a new Alarm as shown below.

This slideshow requires JavaScript.

And we will create another alarm.

This slideshow requires JavaScript.

Task 2: Create a virtual machine alarm to monitor an event.

For this we need to create a trigger for the alarm we have just made, for this we will need to create two triggers, thus one for each that has only been created.

Triggering an alarm; 3.PNG

Task 3: Trigger Virtual Machine Alarms and acknowledge the alarms. 

For this, we need to run the CPU busy script to there for trigger the alarm.

Triggering an alarm; 3 a.PNG

After this, the alarm will be triggered and will lock down a VM. Once this has happened, we need to reset the turn of the CPU busy script and reset the alarm back.

This slideshow requires JavaScript.

Task 4: Disable VM Alarm

For this, we are going to disable and then delete off the alarm’s we have just created.

Delete alarms; 5.PNG

VMWARE Lab's

VMware Lab 18: Monitoring VM’s performance

Task 1 Create CPU Workload

First of all, we need to log in to the VM console and then run a CPUBusy script, thus making the CPU busy.

Run the CPU script to making it busy; 1.PNG

Task 2: Use Performance Charts to monitor CPU Utilization

For this we are going to the check the CPU charts, for this we need to click on the VM, and then Monitor and Performance. As seen below.

Reatime useage of the Cpu; 2.PNG

After this We need to change the chart metrics, for this, we need to get into chart metrics as seen in blue. For this part, we are going to deselect our VM, and then unselect all of the counters.

selecting chart optiomns and deslecting myself and then selecting none; 3.PNG

Next step would be to select Ready and Used as below.

Delecting ready and used; 4.PNG

Now we can see the change’s we have made, and this is the real-time CPU useage.

New realtime cpu useage; 4.PNG

Now we need to go back and do it for the second VM.

 

This slideshow requires JavaScript.

Now we can go and run the CPU Busy script and compear the different graphs, noteing the different leaves.

Ambers01:

Record of CPU valiue; ambers01; 9.PNG

Ambers02:

Record of CPU valiue; ambers02.PNG

Now we have checked this we are going to go back and stop this script, thus making the CPU quite again.

Ambers01:

without running the CPU busy Ambers01; 10.PNG

Ambers02:

without running the CPU busy Ambers02; 10, b.PNG

Task 3: Undo Changes made to the VM’s.

For this, we are going to change the Infinity back to nothing As seen being done on each VM.

 

This slideshow requires JavaScript.

VMWARE Lab's

VMware lab 17: Managing Resource Pools

From my initial scan through the book there is a needed script that we are not provided. This script makes the CPU run as “busy” as possible. That making the CPU red line Below is the script I found:

cpubusy script.PNG

Task 1 Create CPU Connection

First, at all, we need to turn on both VM’s and have them running so we can open a remote console for each.

Both running; 2.PNG

Once we have done this, we need to create the scripts on both machines. I have done them one by one, i did come across the issue as seen below. This issue was just simply an extra Line, once these were compared side by side the issue was quickly understood and fixed.

Creating the Cpubusy Script 3;b Errors.PNG

So once this issue was identified the scripts were ran to make the CPU busy.

Creating the Cpubusy Script 3;b.PNG

After this we need to schedule affinity, this is taking it from 0-1 as seen below.

This slideshow requires JavaScript.

Task 2: Create Resource Pools

For this, we need to create a resource pool for the allocation of different resources, eg. CPU.

Bew resource pool; 5.PNG

So for this, we need to create two resource pools. As shown below. One has the name “Fin Test” and the other having the name “Fin Prod”.

This slideshow requires JavaScript.

Task 3: Verify Resource Pool Functionality

For this, we will click each resource pool summery and have a look at each shears pane. As shown below.

This slideshow requires JavaScript.

After this, we will then drag each VM into there own resource pool. All the while running the CPU busy script. As seen below there are different in which each VM see’s its CPU usage, where one is running the script at 83% whist the system running at a 99%.  Whereas the other is running the script as 48% where the overall system is running at 100 percent due to the resource pools.

Verofy respurce pool Functionality; 7.PNG

After this, we are going to change each of the recouce pools back to “normal” thus standerzing the pool’s.

Chaning the resources; 8.PNG
Enter a caption

Here we can see the script still running and its slowing standardising.

Chaning the resources; 8b.PNG

 

 

VMWARE Lab's

VMwear lab16: Managing vApps

Task 1: Create a vApp

Fist of all we need to be logged into the flash console for this.  Once logged in we must Shut down all of the VM’s and then navigate through the vCentre Inventory lists to the Vsapp’s as showen below.

Vapps; 2.PNG

Once in here we must create a new vApp, from the icon in the left hand corner.  and follow through the wizdard doing to suggested steps as seen below.

This slideshow requires JavaScript.

Once we have done this we then need to comfirm that it is there. as seen below.

This slideshow requires JavaScript.

Then after this we must create a Vertisl machine. For this we will follow the wizard and the sugested steps as shown below.

This slideshow requires JavaScript.

After this we are going to create three clone’s of the Virtual machine we have just created. , These steps have been taken out of the VMwear guide and are of which that follows:

This slideshow requires JavaScript.

Once we have done this we will then edit the settings, these settings are going to be changed order in which they will start up , and once we have change the start up order to be Ambers-App02, Ambers-App01, Ambers-app03 and then Ambers-App04. As seen below. We will then change the start up time for the fist two, this be be changed from 120 seconds to just 20 seconds as seen below. Once this is done we will then click ok for the noted changes to take ahold

This slideshow requires JavaScript.

Task2: Power on a vApp

For this we will simply turn on the vApp and watch it boot all the Vm’s in the order we have set utilising the time frames we have also set too.

This slideshow requires JavaScript.

 Task 3: Remove a vApp

For this we will completey shut down the vApp itself, which in turn . Turns off all of the VM’s. After this we must then Right click and select “Delete from Disk”

This slideshow requires JavaScript.

 

VMWARE Lab's

VMware Lab 15: Managing Virtual Machines

Task 1: Unregister a VM from VSCA Inventory

Here we still have a VM that is currently migrating, as I said it took over 6 hours. So I went ahead and started another lab. But here we will then remove Ambers01-4 from the inventory.

Removed from inventory; 2.PNG

And as you can see from below it has been removed from the inventory.

Removed from inventory; 3.PNG

But when we went and searched for the files, these are still here. These are still called “hot-clone” for some reason. But because these files get deleted in this lab I’m not going to change the name.

VM 4 showes; 4.PNG

Task 2: Register a VM in the vCentre Server Inventory

So from here, we will “register the VM”, here we made a VM from the “hot clones” files. We also changed the name to Ambers05

This slideshow requires JavaScript.

Task 3: Unregister and Delete a VM from the Disk

For this, we will look at the summery of the VM itself before we delete it off.

VMFS datastore; 7.PNG

 

The next this to do is to “Delete from disk” as seen below.

This slideshow requires JavaScript.

And then we will go back and check to see if the files have in fact been deleted. Which there is no record of “hot-clone” or “ambers05”.

files are nolonger there; 10.PNG

Task 4: Take a snapshot of a VM

For this, we will “launch the remote consol” for the VM

Open the VM; 10.PNG

While we do not have the file iometer.txt, I have created a text file

Deleteing the iometer ; 11.PNG

Once we have created this, we need to delete this and put it in the recycle bin. Then we will clean out the recycle bin.

Deleteing the iometer ; 11;a.PNG

Back in the Vsphere console, we will then create a Snapshot of the VM without the iometer file that we have just deleted. As seen below.

This slideshow requires JavaScript.

Now this is completed we need to create the cpubusy file

cpubusy; 13.PNG

Now, this is created we then need to simulate the deletion of this file and then clean out the recycle bin like the previous pic.

cpubusy; 13;a.PNG

We will then navigate back to the Vsphere console and make another snapshot of the current state of the VM that is without the “iometer or the cpubusy” file.

This slideshow requires JavaScript.

After this, we will then create another snapshot and then navigate to snapshots ass seen below.

Looking at all the snapshots 15.PNG

Task 5: Revert to a snapshot.

For this, we will click on the icon in the left-hand corner and revert to the snapshot “Without iometer or cpubusy”. as seen below.

This slideshow requires JavaScript.

Once this is complete we will then go into the console and look at the “c” drive to check that the created files are not there.

revereted back ; 17.PNG

Now we need to revert back to the “with cpubusy” snapshot. for this we will also cheak that the created files are still not there.

This slideshow requires JavaScript.

Task 6: Delete an individual Snapshot.

For this we are going to be deleing the snapshot called “without iometer or cpubusy” as seen below.

This slideshow requires JavaScript.

Task 7: Use the “Delete all” Function in the Snapshot Manager

As seen below we are going to use the “delete all” function to delete all of the unneeded snapshots.

This slideshow requires JavaScript.