NetApp

NetApp Self-paced Lab 2:

Exercise 9: Configuring Storage for SAN Clients

Task 1: Allow iSCSI on the SVML

Here we will log into the Netapp consol on the desktop. We will be logging into Cluster1 and going into the SVML tab and selecting iSCSI like shown below. 1; Start.PNG

Task 2: Create an iSCSI Data lif

Next step is to create a network interface LIF for the iSCSI policy we have just created. This will have the SAN iSCSI protocol and the e0c Port with the suggested Network address given to us from the lab documents. After this, we need to make sure it is enabled. As you can see from below, it is.

This slideshow requires JavaScript.

Task 3: Start the iSCSI Service on the SVML

In this, we need to go into the iSCSI protocol and turn it on by starting it, as shown below.

4; Isucsi Turned on and Working.PNG

Task 4:  Create a Volume to Contain an LUN

For this, we need to create a SAN Volume as shown below. After this is created we need to edit the volume and change the Security Style from UNIX to NTFS

5; Crreation of the Volume.PNG

Task 5: Configure Snapdrive for Windows Transport Protocol Settings.

From this, we need to go into our snap drive and add another transport protocol with the suggested information, as shown below.

6; cheeking the Transport Protocol settings.PNG

Task 6: Establish an iSCSI Session with the Snapdrive iSCSI Management Tool

Still inside of the snap drive, we need to go into the iSCSI management and click on “establish a session” by going through the wizard and doing the options suggested from the Lab documents.  Once this is done we need to make sure it’s there under the iSCSI management tab as shown below.

This slideshow requires JavaScript.

Task 7: Use Snapdrive to Create a LUN on the iSCSI Target.

In the same snap console, we will create a disk by right-clicking on the disks option and clicking “create disk”. We will go through the wizard and put in the suggested options as shown in the lab documents. This Lun will be dedicated to one system and won’t be shared. We will accept the IQN for the Microsoft iSCSI initiator and we will assign an Automatic Initiator Group. After it has been created, we are going to check that the info for it is correct as shown below.

8; Making sure its all there.PNG

Exercise 10: Managing Snapshot Copies

Task 1: Use the CLI to create a Snapshot Copy

In this, we are going to putty into the Cluster and use the code shown below to create a snapshot copy and then we will then check that it is there. 9; Creating a snapshot.PNG

Task 2: Use ONCOMMAND System Manager to create a Snapshot Copy

Then we are going to get into theNetappp console and create the same thing through the GUI interface. We need to go into Volumes and then select a volume and then click on “snapshot copies” and then create. This will then show up in the snapshot copies Tab, as shown below.

10; Mysnapshots.PNG

and then we will delete them afterward.

Task 3:  Configure Snapshot Copies

After this, we are going to configure the snapshot copies. In this, we can choose to do this hourly, daily or weekly.  After this, we are going to go into shares and click on the Eng_projects and go into the Options tab when left clicked. For this, we are going to go into the tab and select the show snapshots. 

Task 4: Use Copy and Paste to Restore Data from Snapshot Copies

Here we will go into the Developer folder in Human resources. Once in here, we will delete a singular folder and then right click select the properties menu for the mapped drive and revert to a previous version. We can go into this and copy over the folder we have just deleted into the current version so we are dragging a copy of the folder we deleted from a previous version. 11; After deletetion.PNG

Task 5: In ONCOMMAND System Manager, Use Snaprestore to Restore a Volume

Once back into the Netapp interface we will then go into Volumes, click on Vol1 and then click on the Snapshot copies tab and click restore. The option below is the option we are going to use. We just need to click restore from here.

11; a BEfore 11.PNG

Task 6: Create a Flexclone Volume Clone

While in the Netapp console we will create a Clone of the volume Vol1,

; 12 A felixvoleme.PNG

and then we will create a new volume.

12; Create volume.PNG

Then we need to mount it as shown below.

13 Clone is mounted.PNG

Exercise 11: Improving Storage Efficiency

Task 1: Configure Storage Efficiency Policies

In this, we will go back into the Netapp console and we will log into Cluster1 ,  we will then add an Efficiency Policy. This is done with credentials given to us in the Netapp lab documents. Once this is done we will make sure it enabled, as shown below.  This will be down twice, one for daily, and one for weekly.15; Added Daily deduplication policey.PNG

Task 2: Create Duplicate Data on a Volume

For this we are going to go into the SVML share and create two course files folders, Once this is done we will go into course files2 and copy the files in this folder into the course files folder we have just created.16; COurse Things being transferred over.PNG

Task 3: Enable Storage Efficiency on a Volume

Here we will go back into the Netapp console and go into volumes and Select Eng_projects  then click edit enable scheduled Deduplication and then put as daily like shown below. After this is done we will then make sure it is enabled.

17; Storage effacilty.PNG

Task 4: Run a Deduplication Operation

For this, we will then select “eng_projects” and then click the Storage efficiency tab at the left hand of the page, as shown below. Then click start on the pop-up box and it will scan the whole volume.  Once this is done we will the refreash the page and then click on the stroage effeincey tab and see the data from the scan.

This slideshow requires JavaScript.

Exercise 12: Moving Volumes from one Aggregate to Another.

Task 1: Assign Multiple Aggregates to an SVML

We will navigate to the Vservers tab under cluster1 and then go into the resource allocation tab as shown below. In this, we will select both aggr1 and Aggr2 to be deduplicated.20; Deligate Arrgigation.PNG

Task 2: Move a Volume

Still, in the Netapp console, we will navigate to “Aggregates” and then click on Volumes at the bottom of the page. Then we will click on the move volume button moving through the wizard selecting the suggested options as done via the lab documents. After this, we are going to make sure that Project-y is moved into Aggr2 as shown below.

This slideshow requires JavaScript.

Advertisements
VMWARE Lab's

Lab 3: Working with Virtual Machines

So, this is something we have already set up I will just explain briefly. In here we will just set up a VM on our web client server. Start place; 1.PNG

We must name it uniquely and put it in our own space, this will limit confusion and errors later. In the select compatibility, we will use the ESXi 6.5 and the later version other as a Guest OS Family and then select VMware ESXi 6.5 as shown below.

ESXi; 2.PNG

Next, we will go and Use a datastore ISO file, making a note to click on the Connect as this connects the ISO up, without it nothing will load. In this section make sure your Vm is on the Right Switch, this will be what all of your other VMs are on. If it’s on a different switch it will not be able to communicate with the other VMS. Once this has been done, we need to install ADDS, but not promote it and then Makesure its on the same network as the others, mine is 169.69.69.0. Once this is done we need to shut down the Vm and make some changes. Once everything is shutdown and is hunkydory, we need to mount  VMware Vs ISO. We also need to add another CPU and More memory, while in here as shown below.

More memory ; 3.PNG

Once we turn on the server again we will need to navigate to “This Pc” and double click on D drive to get things started. ESXi Ios; 4.PNG

In here I stuck to the defaults, sticking in the system name followed by the Domain name. Then create a single sign-on password for the Account which is under administrator and carried on with the Defaults. Once this is done, it will take about 10 minutes for this to start up and get running. But, once it has, we can now navigate to a Local Vshpere client as shown below.

Esxi centre; 5.PNG

This is all installed and working correctly for the next lab.

VMWARE Lab's

Lab 2: Configureing ESXi Hosts

To start off we’re going to look into Hardware Health, the configuration of the processors and the Memory. These are good and healthy as you can see below.

 

This slideshow requires JavaScript.

These were slightly difficult to find in the Flash version of the client, as the instructions were in the HTML version. Once this was done we needed to look into the DNS and Routing. This again was not where they suggested and it was named differently from what the book had stated. But, once I had found it I  just needed to click on the defaults and then edit. We need to make sure the Ip address and the default gateway is correct. DNS Ip configuration ; 5.PNG

Once this is done we need to locate Authentication Services to join a domain. This is where I had a lot of issues. One of the many issues was this lovely graphical interface you can see below. The main issue was connecting, it wouldn’t let the ESXi connect if I didn’t put its name in when I was creating the DNS record. While working with ESXi I was able to ping everyone else in the domain. Then, I tested the other hosts in the domain, to see if they could ping both the IP address and the actual ESXi name. These both worked, which had me stumped, they can communicate – so theoretically they should be connecting.

After 10 hours of working on this I managed to find a work-around, then I created another Datastore and a new host. While I was creating that, I put down the FDQN name instead of the Ip address. This connected straight into the domain and went smoothly! Finally, after so much time!

Directory servises; 7.PNG

After all this time it is connected !!

 

This slideshow requires JavaScript.

VMWARE Lab's

Lab 1: Installing Vsphere Cleint

This lab is all about installing the client, something I have done in previous classes. But with the new Vsphere client, this is made redundant. There is no longer a need to use this because it is not going to be used in the future. The client allows for a Flash and an HTML version. Each has their pros and cons. The HTML looks sleeker and is more efficiently set up, some of the features are not ready yet and this has created issues with the new VMS’. Whereas the Flash version is more like Windows 98, but it has full functional ability. This is something we use on our class server, then the one that I use in Lab 2 is installed on my DC02 Windows 2012 server.

Assessment 3: Deploy and Automate AD DS

Deploy & Automate ADDS Build Blog; 5

So now I know what to run for this assignment, I have gone back and created a new template. This one turned out a lot smaller this time, and The first things that needed to be changed were there was a weird instance in there as shown below, This got deleted.

First change.PNG

And there was for some strange reason five routes when there was only one needed, So I delete all of them off and left it with one route and changed the Ip address as that can’t be blank. as shown below.

And then it errored out on the I am instance as shown. This needs to will be deleted off. Deleting off the Iam.PNGHere, I have further found that I need two routes, and in this, i have added another one now, and I have then further deleted off more that I don’t need. The overall picture from my network is below. Her this is the tidiest I can get it.

 

Pitchure of my system.PNG

I had then Tried to connect to the instance by associating the Elastic IP Address to it, but it would work. I tried adding a rule that allowed Rdp access from my Ip address but still didn’t work. So yeah everything is there, but I have other assignments to hand in. So this is where I’m going to leave it

Un able to connect.PNG

Assessment 3: Deploy and Automate AD DS · Uncategorized

Deploy & Automate ADDS Build Blog; 4

Editing and improving

Here in this i went through and tryed to see what i can edit to make it my own. Here as showen below i have manage to Change the keys and change the name.

Vpc tag.PNG

In this i have tryed to change the names of others, but on changing the name it errors out so its referenceing something else somwehere else.

I have run the temple deisgner and i have noticed somethings that apear to be detached as showen below. but when i have tryed to delete these off there has been issues as they are referncing other things, when i have tryed to change things around so its referncing my stuff instead of the templete that was orginolly use =for the templete theres even more isses that arise.

See if it works with the route 1 not there.

I have changed the Instance type to make it more budget freienly as showen below.

Instance type.PNG

I have also gtryed to remote into the instance that it creates, but as of so far i am unable to get into it. i have noticed that it is being created in another VPC, and that could be the reason why. But i am unsure as of yet.