NetApp 11

NetApp 11: SAN

Task 1: License and start the iSCSI service

On the system manager CLI we first will check to see the status of iscsi on the system.

And double check that the service has started on the system manager GUI.

Task 2: Configure iscsi on windows server

On a windows server we open the service manager and click on config then services.

Then we find the iscsi initiator service. It’s already running so we don’t have to touch it.

Next we open the ISCSI initiator config program to look at configuration details of the ISCSI adapter and note down the iqn.

On the Discovery tab we want to click Discover Portal. Here we type int he IP address of the storage system so it can be picked up by our windows machine.

Then we want to click advanced and select Microsoft iSCSI Initiator from the adapter down down list and also select the windows Ethernet adapter.

On the targets tab out storage server should pop up. We then can connect to it.

Since this is our only used iscsi target it becomes the favorite.

Task 3: Use netapp system manager to create a lun

First we start off on the system manager GUI on the LUN page.

Then we can click create to create a LUN. The wizard pops up and we fill in the details from here.

And once we finish it should a appear in the LUN list.

Task 4: Use the CLI to create a LUN

In this task we achieve the same thing except its all done though commands on the CLI.

Fristly we want to show what LUNs are are on system with the show LUN command.

Then we type in the commands to create the LUN setup.

Now we start the setup and input the details as the CLI asks for it.

After it has created the LUN we can check that it exists with the show LUN command.

Task 5: Access LUNs from Windows Server 2008 R2

In this task we add storage to a windows machine through a LUN.

In the disk management pane in the server manager we can add our lun as a disk. All we need to do is click rescan disk on the storage menu item and our new lun should appear in the disk area as a lun. Right clicking on the disk and selecting online and initialize disk bring the disk to a usable state. Then we right click and select New volume and go trough the volume, giving the disk a size and drive letter.

We can then check to see if the disk works by placing a file in it.

 

NetApp 9

NetApp 9: CIFS

Task 1: use netapp system manger to lincense CIFS

This task is just like adding an NFS key, simply on the license pane click add license to add the key.

Task 2: Use netapp system manager to configure CIFS service

In the menu we navigate to the CIFS pane under protocals. Here we simply click setup and the wizard should initiate.

After all the details have been put into the wizard (Next, next, next) we can check that the service is configured the way we want it by viewing the CIFS main page.

Task 3: Create a windows domain user

In this task we create a user that can then be used to access the CIFS shares.

First thing to do is get in to the windows server manager and add the remote server admin tools service.

This can be found under the add feature link in the server manger.

Once that has been installed we can add a user. This can be found through server manager, AD, and then right clicking on the users folder and selecting new user.

Task 4: Use the CLI and system manager to view and create shares.

First we check what shares are on the system with CLI:

Then in the GUI under storage and then qtrees:

On the Shares pane we can see that default shares have been created.

On that shares pane we can create another qtree straight from here with the create share wizard. Which can be initiated by clicking create.

Qtrees and cifs shares can also be created through the CLI also. Here we use the qtree create command and status to make another cifs share.

The we check the status with the qtree status command.

And finally changing the security to ntfs as windows system will be accessing it.

Then we turn the qtree into an actual share with the cifs shares command.

Then we can check that it has worked with the cifs shares <name> command.

Task 5: create a new share with computer management

Same thing as above, we create a cifs share number 3, but we test it’s function with a windows client.

Create another cifs share with the GUI:

But this time we check that it’s working with a windows client.

Task 6: Map the rest of the shares to drive letters

Just like the share above we add the other 2 to the windows client and give them drive letters. All three shares can be added easily by using the windows add network drive wizard.

Task 7: Modify user permissions

Back on the storage system we can change the permissions on one of the shares so that only the userx we created early can read from it.

The first change gives the user read write and execute permissions. But if we want to just have it as read we just specify read.

Task 8: Display cifs sessions

In this task we simply display the cifs session currently being hosted by the storage server.

To display it in the system manager gui all we need to do is navigate to diagnostics and then select cifs.

The session can also be checked on the CLI with the cifs sessions command.

Task 9: Configuring SMB 2.0 protocol

In the storage system CLI we can turn the SMB protocal on with the options cifs.smb2.client. enable on command.

Then on the windows client we can enable smb so that the client uses the smb protocol.

And back at the storage system we can check that the windows client is using the smb protocol by entering the sessions command with -p smb2 tag.

Task 10: Terminate CIFS sessions

Firstly we make sure the windows client doe not have any connections. In the computer management under shared folders we right click and select close all sessions.

The on the storage system CLI we check the sessions, if there are some we terminate the CIFS service.

To reset it we type in the cifs restart command.

On the system manager gui we can do the same tasks.

Firstly  we navigate to the cifs service from the left hand menu and then click the stop button to stop the service.

We see there are no sessions now.

And to start it again we simply click the start button instead.

 

 

NetApp 8

NetApp 8: Configuring NFS

Task 1: Use netapp system manager to license NFS

In the left hand menu under system config and licenses we can add the NFS license to the system.

Task 2: Use Netapp system manager to export a volume

In the export page under volumes then export we can add an export to the system by clicking create on this page.

Task 3: Use the CLI to export a volume

In this task we use the CLI to check on the exports and create another export.

First thing to do is check the rd file and the options on the exports with these commands:

Then we can create a volume in the CLI and list the rd file again to see if it worked.

And a double check with the exportfs command to see if its exported.

We can check that the volume is export and working by using a Linux client to access the storage.

And then we can check the storage system again to see it’s still available.

Task 4: Mount exports from an admin host

In this task we mount the exports created so that they can be used by the client.

In the command in the screenshot below allow us to mount the storage so it can be used by the client.

Then we can test it by making a file inside the mounted storage.

 

 

NetApp 5

NetApp 5: Logical Storage

Task 1: Use the system manage to create a volume

Back at the system manager, we navigate to Storage > Volumes then click create to add a volume.

We make it one gig and call it NASvol.

Then we can practice resizing it. In this example 500mb is added.

The change can be checked in the CLI next.

The volume can also be re-sized trough the CLI.

Task 3: Delete a volume

Fairly straight forward, just right clicking a selecting delete on an object. But the volume needs to be offline first.

From the CLI we can do the same thing, create a volume then delete it with the destroy command.

Take offline:

Then delete:

Task 4: create qtrees

In the system manager we can expand storage then qtrees and click create.

Same thing can be done in the CLI.

Task 5: delete qtrees

Same as deleting volumes, simply right click and select delete.

In the CLI the command delete can be used as well.

 

 

 

NetApp 3

NetApp 3: Basic Administration

In this task ( 2 and 3), we are simply exploring the NetApp on command system manger and connecting to the storage system with CLI.

First thing we do is install the system manager, which basically just includes clicking next. Then we log in the system manager with root and the usual password then add our storage system by clicking add then enter its IP address.

Which then brings us to the home page where we can see some statistics and the menu items on the left.

Task 4: Use the CLI to access the storage system

Next we can practice some basic commands on the storage system through the remote tool putty.

First we log in with the putty client.

Once we have access we can do some commands like sysconfig and date n time.

Task 5: Explore the help command and privilege levels

So staying in the CLI we can use some more commands.

Here we have used the help and ? command.

The help command can also be used on the end of a command to see its options.

The manual page is also usfull for an admin to see.

And we can also set the privilege level.

And verify licenses on the system.

Task 6: List the options on the storage system

For this for just type options in the CLI. With shows all configuration options.

man options gives us something different. This shows us information on the command.

And using option with other elements like tenet and ssh give us their configuration.

Task 7: From the CLI, Examine the system configuration of the storage system

In the CLI we can see what the sysconfig command gives us. We see that it lists all elements that are configurable.

Entering man sysconfig give us information on how to use the command.

There are different switches that can be used with sysconfig also which gives more or less information.

Task 8: Use Netapp system manager to configure DNS

Back in the GUI one of the first admin task is to add the storage system to the domain.

Task 9: Auto Support (Optional)

— Skipped —

 

 

 

 

VMware Lab 21

WMware Lab 21: Installing VMware vCenter Server

Task 1: Access your vCenter Server system

OK so we log in as admin to our vCenter Server through vSphere. Nothing else to it.

Task 2: Configure a SQL Server ODBC connection to a remote data base

— Skipped —

Task 3: Install vCenter Server

In this task we install the vCenter server software which acts as a layer of communication between the hosts and vSphere.

Which is very simple. All we do is load up the vmware disk int eh drive and select install vcenter when the auto loader pops up.

Pretty much all the user inputs are just clicking next many times. Except for the name of the user and selecting Install MSQL server express instance on the Database options. Of course there is also the usual “I agree to this before installing” as well.

Just to confirm that it did install, as this sever doe not have a gui, it only communicates through the vSphere client.

 

VMware Lab 20

VMware lab 20: VMware vCenter Update Manager

Task 1: Install update manager

The software for this program can be found on the disk so all we do is run the auto exe of the disk and click install update manger.

Most of the settings are default except we input of user name and password in and vCenter IP. Other than that it’s mostly next next next.

Task 2: Install the Update manager plugin into the vSphere client

In the vSphere client in Plugins > Manage plugins we can install the update manger.

In the installer we simply click next next next.

And then it gets enabled automatically.

Task 3: Modify cluster settings

In the settings for the cluster we change the vSphere DRS settings to Fully Automated and disable Allow VM power operations that violate availability constrains.

Then we check that the resource allocation has nothing in it on the cluster. Which it doesn’t.

Task 4: Configure Update Manager

In this task we grab a patch file and Import it to the update manager.

So in the config tab of the update manager we select download, then import and browse for the patch on the desktop and tell it to import.

Task 5: Create a patch baseline

In this task we create a baseline patch for out hosts with the patch we just uploaded.

In the baseline and groups tab, under the baselines pane we click Create to make a new baseline.

The wizard should pop up and we fill out the details like so: Name as ESXi Host Update, Basline desc as Patch for ESXi 5.0, Patch options as Fixed, The patch as the only patch in the list we made earlier.

Once that’s all good we click finish and we then have a baseline we can attach to our hosts.

Task 6: Attach a baseline and scan for updates

Here we are simply just attaching the baselines. On the update manager tab with the cluster selected we can click the attach link to add a basline.

The diag should pop up like this. Here we want to select ESXi Host update, check box it and click attach. It should then add it to the clusters baseline.

On the Update manager page selecting scan gives us a view of the status of the hosts.

We find the the hosts are not complainant yet as they have not been staged yet.

Task 7: Stage patches onto ESXi hosts

Now we can apply the patch baseline to the hosts.

All we need to do is click stage on the Update manager tab. the wizard should pop up. We then accept the defaults and click finish.

Once finish is clicked the process begins.

Task 8: Remedeate ESXi hosts

In this task we put the patching process to work by clicking remediation so that the non-compliant hosts can be updated.

Most of the settings input is just clicking next except for a few things like setting the retry delay to 1 and deselecting the DPM option.

After finished has been click the hosts will be re mediated.

So yes, now the hosts are compliant with one another.

 

 

VMware Lab 19

VMware Lab 19: vSphere Distributed Resource Schedular (DRS)

Task 1: Create a DRS cluster

In this task all we need to do is get in tot he cluster settings and check the enable DRS check box.

We then want to change the DRS to manual as its automation level and then move the slider to aggressive.

Clicking OK applies these changes.

Task 2: Verify proper DRS cluster functionality

Here we navigate to the DRS tab whilst having the cluster selected in vSphere. On this page we click the Run DRS link and depending on the state of the hosts we may get a recommendation.

We get this recommendation because the hosts are imbalanced, as we can see in the next screen shot below.

They are imbalanced because one of the hosts is running all the VMs.

So what do we do? Click Apply Recommendations on the DRS page.

DRS then balances out the VM by migrating one on the other host.

We can then check the summary of the cluster to see if it’s balanced.

Task 3: Create, test and disable affinity rules

For this task rules are put in place to control where the VMs will reside on the hosts.

Whilst having the cluster selected, right click and choose edit settings. Then select vSphere DRS > Rules. And then click add.
On this diag box we will input the settings we want for our first rule and add it to the rules list.

The settings for this one were Name as Co locate, Type as Keep VMs Together and VMs as all the VMs named ##-#.

Back on the DRS tab we can then run the Run DRS again by clicking its link. We should see some different recommendations.

Click apply recommendation starts the migration processes again, but this time the VM is moved back onto the same host as the other VM.

We can check to see if it worked by looking at the VM page of the co location host.

As we can see the VMs are back on one host. So the co location worked.

Before we finish this task though we must disable the rule by un checking its tick box. So it does not interfere with the next set of rules.

Task 4: Create, test, and disable anti-affinity rules

In this task we do the opposite of the of the previous task. Here we will be configuring anti-affinity rules as opposed to affinity.
So we’re going to want to add another rule to our DRS configuration. This can be found in the settings of the cluster.

This rule is just as simple as the other. And in it we specify to separate the VMs and then list them in the VM list.

Back at the DRS tab with the cluster selected, we can run DRS again and find a new recommendation.

This will forcefully separate the VMs so they are on different hosts.

As we can see the VMs are on separate hosts now.

Just before we start another task, ensure the rule or rules are disabled as it could interfere with future configurations.

Task 5: Create, test and disable virtual machine to host affinity rules

In this task we create a VM and host DRS group and then rules that dictate that group.

In the cluster settings under vSphere DRS > DRS Groups manager we want to click add on each group to add our VMs and one host. The names of the groups are as follows, Roly0-VM for VMs and Roly-Esxi Host for the one host.

Once the machines have been added we need some rules. In the DRS rules options click add to add a rule. The setting for this rule will be: Name as Run only on ESXi host, Type as Virtual machines to hosts, Cluster VM and Host group as the ones we created above. Clicking OK saves the config and closes the pane.

Back at the DRS tab we can click Run DRS again to see new recommendations.

And then we can apply them.

After DRS has done its thing we can check where the VMs are placed, in the above screen shot we see that one VM on the .11 host has been moved to .4.

We can check to see if the rule is enforced  by manually trying to migrate the VM back.

Just as suspected the VM can’t move back because of the rule telling it to stay on the one host.

The rule should now be disabled for further labs.

 

 

 

 

 

VMware Lab 18

VMware Lab 18: Using vSphere High Availablilty

Task 1: Create a cluster enabled for vSphere HA

Just as the task names describes, this involves adding a cluster to the virtual environment and enable high availability on it.

On the Hosts and Cluster pages we select the data center and click New Cluster. The cluster wizard should pop up. Here we enter all the settings for the new cluster. Most of the settings are default expect for we have specified that HA is turned on and admission control is set as Percentage of cluster resources reserved as fail over spare capacity.

Task 2: Add your ESXi host to a cluster

This is an easy task where we simply add the hosts into the cluster. All we have done is dragged and dropped the hosts right on the cluster.

Some warnings may appear, simply accept them and the VMs will be placed in the cluster.

Now we check the status of the cluster. We find that the first host added is the master, the protected VMs match how many VMs running on the cluster. And that I need to add another data store for heart beating.

Then we check the Config issues to see what needs amending.

We see that I am missing a heart beat data store and so another data store needs to be added to fulfill the requirements.

Task 3: Test vSphere HA functionality

So now we are going to test the cluster HA function.

Here we see what VMs are running on each host.

We then want to reboot one of the hosts so that the VMs running on it are transferred over to the other host that is running.

We can see that the VMs that were on one host are now running on the other after the process is complete. The only running host then becomes the master.

Task 4: Prepare for the next lab

Here we simply remove the server folder that is no longer used as we are using a cluster now.

VMware Lab 17

VMware Lab 17: Using alarms

Task 1: Create a virtual machine alarm that monitors for a condition

In this task we create an alarm which triggers on the CPU hitting a certain percent and then suspends it.

In the Hosts and Clusters page we select the VM we want and then navigate to the alarms tab. When we click definitions we see a list of the alarms already available. To add our own we right click on the white space and select New Alarm.

For this alarm we input the following settings: On the general tab: Name as VM CPU Usage and Alarm type as Monitor for specific conditions or states.

Triggers tab: Type as VM CPU Usage %, Condition as Is above, Warning as 25, condition length as for 30 secs and alert as 50.

We skip the reporting tab as we don’t want to change anything in there.

On the last tab, Actions, we set Action as Suspend VM, Green to yellow as once and yellow to red as nothing.

After all these settings are entered, clicking OK will add the alarm to the alarm list.

Task 2: Create a VM alarm that monitors for an event

In this task an alarm is created to respond to the event. This event is the action of the previous alarm created. When the CPU goes above 25% the VM is suspended, here we create an alarm that is triggered by the suspension.

In the same place as the  other alarm we create a second one. We only need to edit two tabs for this one, General and Trigger. On the general tab we want the name as VM suspend and the monitor type as Monitor for specif events occurring on this object.

On the Trigger tab we want to add the event as VM suspended and then go into the advanced settings of the conditions column and add an argument to the conditions list. Our argument will be VM name is equal to NewFreashRol02-2, the VM that has the other alarm on it.

After OK is clicked twice the alarm is added.

Task 3: Trigger the VM alarms and acknowledge them

This task involves triggering the alarms just created.

First we look at the alarms tab of the VM to see there are no alarms triggered yet.

Now we trigger the CPU alarm by running the cpubusy script on the VM.

The alarm list of the VM should be populated with just the VM suspended alarm. As the CPU alarm only pops up very briefly and the suspend alarm is there to capture the suspension.

Now we know that the alarm has been trigger we can acknowledge it by simply right click on the alarm entry and selecting acknowledge.

After this it’s a good idea to power the machine back on, disable the CPU script and clear the alarm.

Task 4: Disable VM alarms

Since we have finished with the lab it’s a good idea to disable the alarms created.

This is easily done by going into the alarm settings and deselecting the Enable this alarm check box.

The exact same is done for the other alarm. And should end up looking like this in the alarms list: