Lab 23 Update manager

So, for this lab, it focuses on the update manager for vSphere which is where I had troubles with as it needed flash in terms of the update manager as it doesn’t work with the HTML5 client it was also because since it was through a VM I had to mount it like an ISO and copy over to the VM as this was needed for one of the parts.

The first thing I had to do was basically install the update manager on to the server with vCenter on it. I did this by mounting the same iso for the installing of vCenter but instead of installing I installed the SQL server for the update manager server as this is needed to install the update manager.

After this, I then came across a website which said that flash is installed on the server so I did that as I need flash for uploading the zip folder which has the update on it.

So, after this, I went on to focusing on the lab again and then got the update manager configured so it can work on my vCenter which is why I needed the flash client for.

So, the next part I uploaded the zip folder on to the update manager this is after I copied the zip folder on to the desktop as it was very slow doing it via USB so I suggest not doing that. After the upload finished I then had to verify that it was done and on the patches as if it wasn’t it would mean something is wrong with the zip folder.

After this, I had to create a baseline which was static to change so this meant that it would basically do this once and then be done with it so basically you have to select the host that will need this update as it needs to be selected.

After that is done it has to be attached to the baseline the patch this makes it available to these host on this baseline.

The next thing that needs to be done is to stage these updates which basically means getting the host ready to do these updates and getting them ready to install.

It then does a function called remediate the host which basically means that it will install the updates and restart the hosts in order to finish the updates while doing this it suggested putting the host into maintenance mode as for some reason it doesn’t like this.

Lab 23 20Lab 23 21Lab 23 22Lab 23 24Lab 23 23aLab 23 25Lab 23 26


Lab 22 vSphere DRS cluster

So, for this lab, it focused on implementing a DRS in a cluster so what this basically means is that it keeps an eye on all the vm’s connected to a host and will check that the CPU load isn’t imbalanced if it is it will usually give you recommendations on what to do in order to balance it again.

This slideshow requires JavaScript.

So, again since my vCenter had a cluster already I had to just enable the DRS and set the level of checking/priority to aggressive which basically means that any little imbalance it will pick it up and make a suggestion which for this I used the cpubusy to create the imbalance which the third image shows the level of it in terms of CPU.

But this is where for some reason DRS wouldn’t scan properly this is most likely to when I had to create a new vCenter server and all the settings were reset and the distributed switch that I created basically got destroyed and the ESXI wouldn’t let me take off that Distribute switch so I just created a new one to test if it will work but for some reason wouldn’t so I had to do by turning the VM’s on which triggered the recommendations.

This slideshow requires JavaScript.

It then goes on to affinity rules which this will basically act as a rule so for example with this I used two different rules which basically kept the virtual machines together so basically keep it on the same ESXi host so if one VM is on another host it will then ask once it is scanned to migrate the VM to the same host which the other VM is on.

This slideshow requires JavaScript.

The other rule basically keeps the VM’s on the separate host so if they are together the DRS will pick it up and will then migrate it to the other host.

Then there is the host affinity rule which is basically a group of host that it aims the rule at so for this it aimed a rule which basically keeps the vm’s running on one host so if one is on it’s own host and 3 others are on the same one the one on its own will be migrate to the one with 3 VM’s on it.



Lab 21 vSphere HA

So, for this lab, I kind of started to having troubles in terms of labs again as for some reason it wouldn’t work properly.

The first task was to basically create a cluster to hold the ESXI host but I kind of already created a cluster when I first started these labs so basically I only had to configure my cluster so that it meets the lab specs which was basically enabling it to have HA on.

This slideshow requires JavaScript.

After turning it on I basically for some reason got red warnings on my ESXI host which at this point I ignored as the parts I was using were working so basically the above picture shows that both virtual machines are protected. But in terms of heartbeats it had to have 2 VMFS datastores for it to work as before then it wouldn’t let me use it.

It then got me to edit the vMotion adapter as it needed the management traffic tick box ticked as it needed this for HA to work this is the next part where I had problems as when it came to testing if it would work as for some reason when it came to moving vm’s from ESXI 1 to 2 it wouldn’t have a problem but the other way round it would so it was kind of pain as they had to be off for this to happen.

This slideshow requires JavaScript.

It then asked me to check the reservation of the memory and the cpu of the virtual machines as it shouldn’t have any reservations by default.

Then this brings me to the next part which it asks me to set a memory and cpu reservation for a virtual machine which this basically means that it will have a set amount of CPU and Memory assigned to it.

This slideshow requires JavaScript.

It then basically asks me to do the same for the cluster and to run a calculation for the slots that it wants so basically because of this it basically doubled the protected vm’s.

This slideshow requires JavaScript.


Lab 19 Using alarms

This slideshow requires JavaScript.

So, for this lab it focuses on the alarm function in vCenter server/vSphere which basically involves creating an alarm to basically monitor the condition of a virtual machine, monitor the certain event when it triggered, acknowledge an alarm and to disable an alarm.

So first off was the monitoring of a certain condition which this basically meanns that if a certain condition of a virtual machine is meet it will for example shut down the virtual machine so that it doesn’t slow down the system which the first couple of images above shows me creating a alarm that goes off by the cpu usage that if it goes above a certain amount it will suspend the virtual machine so for when testing this out I used the cpubusy script which was used in a previous lab.

Which after this it basically triggered the alarm that was created which meant it triggered it to suspend the virtual machine so it basically did what it was spouse to do.

Then it moves on to monitoring a certain event so what this basically means that if something like a virtual machine is powered on it will trigger that event and will do what ever the function is set so again suspended the virtual machine which is what I did in terms of this task which once created it showed up in the alarm definition panel.

Which the next task basically focuses on acknowledging alarms which this basically means that if you got a warning that isn’t intended but isn’t important as it means that it will basically acknowledge that you have seen the warning and know that it needs attention.

The last task basically wants me to disable an alarm which is basically done so that it doesn’t keep being trigged in terms of the next lab so the last couple of images in the slideshow basically shows this as it is needed to be able to move on to the next lab.

Lab 18 Mointoring VM performance

This slideshow requires JavaScript.

So, for this lab it’s actually continuing from the last lab as it is using the resource pools that were created to basically monitor the virtual machines performance to create a graph which shows the CPU’s performance but for some reason vCenter wouldn’t produce one for me so can’t really show a screenshot for that but it would basically show the peaks where the CPU was at it’s highest.

It would basically then be repeated for the other 2 VM’s so it will basically compare all 3 together.

Lab 17 Managing Resource pools

So for this lab, it was focusing on resource pools in the vCenter server which was actually a quick lab to do as it was basically creating a resource pool, changing the affinity rule for CPU and seeing if the resource pool stops it from going over the cpu limit.

This slideshow requires JavaScript.

So first off I created the resource pool which I ended up moving the VM’s into the resource pools that they asked me to do. Which after this I had to turn them on and basically create a script called cpubusy which basically when it runs it makes the cpu run really high meaning that it demanding a lot of resources.

So after this was verified I changed the resource pools cpu resources to meet the next labs specs as it can’t be high demanding

Netapp Lab 2

Exercise 9


This slideshow requires JavaScript.

So for this exercise, I had real problems trying to connect to snapdrive which was the application I used halfway through this lab which the problem was connecting to the Storage Virtual Machine with it’s name as for some reason it says it can’t connect to it because it can’t get the Ontap version number but with the IP address it can so I spent hours trying to to find a way around this but just ended up being this in the end.

So, basically for this exercise it was basically focused on trying to make a iSCSI session within snapdrive which basically enables you to create a new disk and connecting it to a volume on the data ontap.

Exercise 10


This slideshow requires JavaScript.

So for this exercise was the last one I could get screenshots for as due to technical difficulties with accessing the lab the next day it just wouldn’t load or anything so the next two exercises will be without screenshots due to this.

So this exercise basically focused on creating a snapshot of the volume that is being used just in case something happens which they got me to delete a folder to test out this snapshot I created and restored and earlier version of the folder that was deleted by copying over a version from the version history.

It also got me to setup flexclone volume which is basically a cloned volume of the original volume vol1.

Exercise 11 and 12

So for this exercise, this is where I had trouble in terms of getting screenshots the second time doing this so basically, I am going to go over what I basically did in terms of the exercises as they were quick and easy to do so it would be quick to describe.

So for exercise 11 it was about setting up deduplication which this basically is setting up so it checks to see if there is anything the same it will keep one block of that same piece of data and the others will then reference to that block which saves space on the volume and disk which this shows that in terms of the amount that is saved which for me was around 50-65mb of data.

Then there was exercise 12 which was the last exercise for the netapp labs which this one focused on moving one volume from an aggregate to another which this was really easy as you basically adding the aggregate in the resource allocation and then going under the volumes tab then selecting the volume want to move and then clicking the volume move button.

This basically opened a new window in the remote desktop I was using and went step by step on selecting the volume that is being moved, what aggregate is free to support it and lastly the summary page which showed all the new information.

This then got me to double check that the volume move didn’t affect the namespace which it didn’t so this means the same namespace is used for it.

Netapp lab 1

So this blog is going to consist of different exercises from the Netapp lab that I did and is going to show what I learned during this process with screenshots but please note that some of these exercises might not have screenshots as I had to do it a second time to get the screenshots and I ran into lots of problems in terms of connecting to these labs.

Exercise 2

So for this exercise it got me to focus on getting use to the interface of the vsim so basically the web client and also SSH into the vsim so basically being able to make changes without being in front of the computer. So it basically got me to have a look at the web client to get to know what was basically the layout was and to know where everything was. But it also got me to configure the SNMP which basically lets me able to access the Data Ontap web client as it would come up with SNMP error after leaving the data ontap after this lab.

Exercise 3

This slideshow requires JavaScript.

The next exercise basically focused on the hardware and being able to manage the components that are with it.

So first off it got me to look at the information for the disk layout which was under the volume window under nodes this basically gives an idea of what the layout of the disk is.

It then basically got me to check the spare disk to see the information on the disk and to see if it been zeroed as this would mean that it hasn’t been checked that it been used.

It then basically turns it’s focus on to the ports so for this it means what network ports are currently active so for this it has 5 ranging from a to e this is so that different ports have different access capabilities that each group can access.

Lastly, it does the same thing with the disk from the web client on the SSH client so basically, the last two images in the slideshow above are basically showing to see if the disk is zeroed, if it connected to any aggregate and port it is on.

Exercise 4

This slideshow requires JavaScript.

So this exercise basically focused actually creating an aggregate and being able to manage it so the first part was actually creating the aggregate that was going to be used which for the name it was just aggr1 this is so that it can be easily identified as you can have any name like aggr1_management as you could have different aggregates for different groups. Which I also had another one that I had to create but this was via the SSH console as you can use that to create an aggregate which honestly I would use the web client as it easy to use and is step by step with examples.

I also had to create another aggregate which this one’s purpose was destroying it via the SSH console which this kind of took time to do as it goes ahead and deletes everything from that aggregate off.

Exercise 5

This slideshow requires JavaScript.

The next exercise basically is focusing on creating an SVM (Storage Virtual Machine) which is a basic step by step process as you basically give it a name and the protocols that it will have in terms of storage, an IP address of its own so that it can be accessed by the machines connected to that port.

So basically to me, this was the easiest exercise without any problems as in the others I have had a problem at some stage even if it was just in terms of understanding what is needed.

Exercise 6

This slideshow requires JavaScript.

This next exercise basically continues from the last one and focuses on creating volumes on the SVM so like creating a normal volume and a aggregate you are basically going to give the volume a name and certain amount of space from an aggregate while also making sure it is on the same port number.

You also make this available to a namespace which is basically making it so it can be mounted as a network drive on a client.

Exercise 7

This slideshow requires JavaScript.

So for this exercise it made me focus on creating CIFS file share which is basically using the namespace in data ontap client to be able to link it to a volume as it needs this in order to be able to connect it as it can’t connect to the volume without the namespace as it acts like a shared path like a network share would use on a network which this is how it connects as a drive on the client that they got me to use.

It also got me to basically set the permissions so that the administrator of the server can connect to these volumes so basically I had to give it full control in order for the volume to be able to be changed by the administrator while also removing access by everyone as they don’t want anyone else accessing the share.

 Exercise 8

This slideshow requires JavaScript.

This is the last exercise in this lab which this exercise basically links to letting a Linux machine which was a lengthy process as you have to configure UNIX to be able to connect to the file share as you needed to configure a UNIX to windows permission and a Windows to UNIX permission as this needs to be done as if one of these aren’t configured you will have problems.

But also I had to create an export rule for the Linux machine as it doesn’t have access to the default rule as it needs NFS enabled on it.

After this it means that the Linux machine can access the shared volume by basically using the mount_point command and making it a directory which the last couple of images show me basically doing this while also creating another secure volume.


Lab 16 Managing vApps

So, for this lab it was focused on creating a vApp, powering it on and removing it from the system. So basically a vApp is a group of Virtual Machines which can be turned on at the same time.

This slideshow requires JavaScript.

So, when it came to creating the vApp it was pretty easy as it was just basically like creating it like a virtual machine. So it is put into a compute resource (one of the ESXIs) but then I had to create for VM’s which in the book it said to have the memory at 2056mb and 100mb for hard drive space but I didn’t know what OS it used so I just ended up cloning my virtual machines.

This slideshow requires JavaScript.

So it then turned on but before this, I had to rearrange the power on sequence of the Virtual Machines in the vApp from 120 secs to 20 secs which basically means there is no delay in. But after that, it basically asks me to delete the vApp from the disk.


Lab 15 Managing Virtual Machines

So for this lab, I have kind of had experience when it comes to snapshots as when it came to taking them and reverting it to those snapshots as it came handy when something breaks in terms of the virtual machines I could revert to the previous snapshot and it would go back to that point before the problem occurred.


This slideshow requires JavaScript.

So the only thing I learned was the unregistering and registering a vCenter Server Appliance Inventory which was basically basic to do as you just right click and remove from inventory then basically going into the datastore that it was on and then registering the VM again on to the vCenter server and went through choosing what host to put it on and what folder it should be under. Then its basically back on to the vCenter server.