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.
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.
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.
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.
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.
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.
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.
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.