Changes

Jump to: navigation, search

OPS335 NFS Lab

4,211 bytes added, 17:48, 4 March 2016
no edit summary
[[Category:OPS335]][[Category:OPS335 Labs]]
==NFS and Automount==
In this lab you'll set up a Fedora VM as an NFS (Network File System) server. Then you'll set up the other VMs as NFS clients that will import their /home directories from this NFS server.
{{Admon/important|Prerequisites|Before you begin make sure your virtual machines are up to date.<br />
Ensure all machines are using the firewalls you created in previous labs.<br />
Ensure both host and VM's have firewalls set up according to prior labs. And ensure you are using your seneca account (the first user created - this will be
<b>critical</b> for success) }}
===Part A: Setting up the NFS Server===
On your VM 2 machine perform the following tasks:
*You do not need to install nfs, as it is present by default on the server installation of Fedora 22. If it is not there use the following command:
dnf install nfs-utils
*edit /etc/exports so that it contains ONLY the following line (where 192.168.x.4 is the IP address of your guest VM):
/home 192.168.x.4(rw,root_squash,insecure)
*Start enable your nfs service (now known as nfs-server.service).*Build the server's list of exports exportfs -r==NFS RESOURCES==
*Run and record the output of the following commandsOnline References: exportfs showmount -e
NOTE*[https: You'll have to adjust your firewall on VM2 to get //prezi.com/sfxdbjbxgu1e/file-servers-nsf-samba/ File Server Notes] (Week 9 class notes)*[http://nfs.sourceforge.net/nfs-howto/ Linux NFS to workHOWTO]*[http://tldp. Run netstat to determine the ports neededorg/HOWTO/NFS-HOWTO/security.html NSF Security] (List of tips regarding NSF and security)
==OVERVIEW=Part B: Setting up the NFS Client=======Configuring the NFS client====*Ensure the VM guest network is functioning properly. You can use the "host cbc.ca" command to see if DNS queries are being answered. *Ensure you have full connectivity to the internet.*Again, you should not have to install any NFS software.*Add the following line to the bottom of the /etc/fstab file on vm03 192.168.x.3:/home /home nfs4 defaults 0 0{{Admon/important|Warning:|Do not change any other lines in this file. Do not change any lines in /etc/fstab on your host machine. Doing so can make your machine fail to boot.}}*Run the following command to avoid an error that would be caused by logging in while root_squash is active: setsebool -P use_nfs_home_dirs 1*Logout of vm03 and shut it down.
====Testing NFS mounts In '''OPS235''', you learned how to install and configure an SSH server to be able to use utilities such as '''ssh''', '''scp''' and '''sftp'''. Although the '''sftp''' utility is useful for transferring files between different computers via the Internet, it is not considered useful or efficient for accessing files on your client====*Restart vm03 and login using your learnidservers that are connected over a local network.
*Check that the home directory is mounted mount | grep /home*If it is not, try running Two popular protocols called '''Network File Server''' ('''NFS''mount /home' as root ) and observe any errors.*On vm03, create an empty '''Samba''' ('''SMB''') are used to provide high speed file using the touch commandaccess between servers on a local network. touch empty_file_created_on_vm03*Now shutdown vm03.*Now The '''NFS''' protocol allows a user to access files on the NFS another server, us ls -l in your learnida local network in a similar way that local files on a same server are accessed. The '''Samba'''s home directory open-source software is used to check for access files from Windows servers using a combination of Windows protocols including NetBIOS, SMB, etc., and will be discussed in the file you just creatednext lab.
===Part C: Setting up Automount This lab will focus on the VM===On vm03 as root perform the following tasks:*Comment or remove the line from /etc/fstab that you entered earlier.*With a server installation of Fedora 22installing, you will not need configuring and using '''NFS''' to install autofs, but access files between different Linux servers on other installations you might need: dnf install autofs*Move the existing file /etc/auto.master: mv /etc/auto.master /etc/auto.master.orig*This is a great way to keep a back up in case you need to restore the file in the future. Now create another: vi /etc/auto.master*Add only the following line: /home /etc/auto.home --timeout=60*Create the file /etc/auto.home and add ONLY the following line: * -fstype=nfs4,rw,nosuid,soft 192.168.x.3:/home/&*Start autofs, and ensure the service will automatically start at bootyour local network.
*Log out of vm3 and log back in using your learn account.
*Open a terminal and enter the command:
mount | grep home
*How does it differ from the previous mount?
*Create another empty file with the name
touch another_empty_file_from_vm03
*Run and record the output of the command
df -hT
*Back on the nfs server run and record the output of ls -l in your home directory.
*You should see the files you created on vm03.
*You may encounter errors with SELinux during the lab (though it has not been a problem recently). It is required that you leave it running. Use the following commands to determine what booleans need to be flipped.
audit2allow < /var/log/audit/audit.log
audit2why < /var/log/audit/audit.log
===Part DINVESTIGATION 1: Setting up Automount on the other VM=USING AUTOMOUNT WITH NFS==*Now that you have VM3 automatically mounting home directories from VM2, configure VM1 to do the same.
In this investigation, we will set up an '''NFS server''' on our '''VM2''' machine. We will then set up an '''NFS client on our <u>VM3</u> machine''' so that we can '''view and import files of '''VM2's /home directory''' from our <u>'''VM3'''</u> machine. {{Admon/important|Prerequistites|Due to the changes made in lab3, '''you will now need your vm1 running (as the DNS server)''' in order for any of your virtual machines to be able to use the internet.}} ===Setting up the NFS Server (VM2)=== '''Perform the following tasks:''' #Make certain that all of your VMs are running.#Switch to your '''VM2''' machine.#Although the NFS application was already installed on your VM, we will install additional utilities for NFS by issuing the following command:<br>'''yum install nfs-utils'''#The '''/etc/exports''' file allows you to restrict the access to servers to access files for security purposes. Edit the '''/etc/exports''' file, and add the following line to the file:<br>'''/home 192.168.x.4(rw,root_squash,insecure)'''#What does the IPADDR 192.168.x.4 represent? Record your answer in your lab logbook.#Issue the following command (in order of appearance) in order to start your NFS server:<br>'''systemctl start rpcbind'''<br>'''systemctl start nfs'''#Use the '''systemctl''' command to enable both the rpcbind and nfs services upon VM startup.#Issue the following command in order to add (or "build") the server's list of permitted exports: <br>'''exportfs -r'''#Run and record the output of the following commands in your lab logbook:<br>'''exportfs'''<br>'''showmount -e'''#You will have to adjust your firewall settings on your VM2 machine to allow NFS to work (Tip: run the '''netstat''' command in order to determine the <u>'''ports'''</u> needed and issue the appropriate ''iptables'' command or commands). Make certain to save your current iptables rules so they remain unchanged whey you reboot your NFS server and your client VM. ==Completing =Setting up &amp; Testing the LabNFS Client (VM3)===During '''Perform the following tasks:''' #make certain that your '''VM3''' machine can connect to the network and that your '''VM1''' machine is running as the DNS server (Tip: you can use the "host cbc.ca" command to see if DNS queries are being answered.#Make certain that you are logged into your '''VM3''' machine.#Install the '''nfs-utils''' package on your '''VM3''' machine.#Add the following line to the bottom of the '''/etc/fstab''' file on your VM3 machine:<br>'''192.168.x.3:/home /home nfs4 defaults 0 0'''{{Admon/important|Warning: Do not change any other lines in this file. |Do not change any lines in '''/etc/fstab''' file contained for your VM3 machine. Doing so can cause your VM3 machine not to boot properly.}}<ol><li value="5">Run the following command to confirm that SELinux will not block the network share:<br>'''setsebool -P use_nfs_home_dirs 1'''</li><li>Issue the following command to mount any network shares without having to logout and login to your VM3:<br>'''mount -a'''<li>Create an empty file within the regular user's home directory on your VM3 machine.<li>Issue the ls-l command for VM2 regular user's <u>'''home'''</u> directory. Do you see a file that you created there?</li><li> Switch to your '''VM2''' machine and view the contents on your regular user's <u>'''home'''</u> directory. What you do you notice? What does this mean in terms of using NFS? Record your observations in your lab logbook.</li><li>'''Restart your VM3 machine''' and login with your regular user id.</li><li>Make certain that you have gained experience getting multiple services iptables rules are the same to allow NFS to work</li><li>Check that the VM3 regular user's <u>'''home'''</u> directory is mounted by issuing the following command:<br>'''mount | grep /home'''</li><li>If it is not, try running '''mount /home''' as root and observe any errors.</li><li>Create another file in the regular user's home directory on your '''VM3''' machine.</li><li>Switch to your '''VM2''' machine to see if you can view that file.</li><li>Finally, issue the '''ls-l''' command in your VM3 regular user's home directory to note the contents.</li></ol> '''Record steps, commands, and your observations in INVESTIGATION 1 in your OPS335 lab log-book'''  ==INVESTIGATION 2: SETTING UP AUTO-MOUNT ON CLIENT (VM3)== In this investigation, we will be setting up to allow a network file share permanently on your VMs. '''Perform the following tasks:''' #Switch to your '''VM3''' machine.#Unmount the /home directory from VM2 by running '''umount /home'''#Comment or remove the line that you added in the '''/etc/fstab''' file in the previous investigation.#Restart your '''VM3''' machine.#Install the '''autofs''' package by issuing the following command:<br>'''yum install autofs'''#Rename the existing file '''/etc/auto.master''' file by issuing the following command:<br>'''mv /etc/auto.master /etc/auto.master.orig'''<br>Keep this file as a back-up in case you need to restore the file in the future.#Use the vi text editor to create a new (empty) '''/etc/auto.master''' file and add the following line:<br>'''/home /etc/auto.home --timeout=60'''#Save your editing changes.#Use the vi text editor to create a file called '''/etc/auto.home''' and add add the following line:<br>'''* &nbsp; -fstype=nfs4,rw,nosuid,soft &nbsp; 192.168.x.3:/home/&'''#Save your editing changes.#Use the '''systemctl''' command to start the '''autofs''' service, and another systemctl command in order to cooperate ensure that the autofs service will automatically start at boot.#Log out of and back into '''vm3''' using your <u>regular</u> user account (i.e. not root. You should be in your regular user account for both VM2 and VM3 machines).#Open a terminal and enter the following command:<br>'''mount | grep home'''#How does it differ from the previous mount? Record your findings in your lab logbook.#On your '''VM3''' machine, create another empty file with each otherthe name:<br>'''touch yet_another_empty_file_from_vm3'''#Run and record the output of the following command (on both your VM2 and VM3 machines):<br>'''df -hT'''#Switch to the nfs server ('''vm2'''), run and record the output of '''ls -l''' in your home directory (You should see the files you created on vm3).#Now that you have used VM3 automatically mounting home directories from your first clientVM2 machine, repeat the steps in this investigation in order to configure your '''VM1''' machine to do the same.  '''Record steps, commands, and your observations in INVESTIGATION 2 in your OPS335 lab log-book''' ==COMPLETING THE LAB== '''Arrange evidence (command output) for each of these items on your screen, then ask your instructor to review them and sign off on the lab's completion:''' ::<span style="color:green;font-size:1.5em;">&#x2713;</span> Show mount information regarding vm3 and vm1 shares with NFS server (vm2)::<span style="color:green;font-size:1.5em;">&#x2713;</span> All files shown in network server (vm2)::<span style="color:green;font-size:1.5em;">&#x2713;</span> Display contents of '''/etc/exports''', '''/etc/auto.master''' and '''/etc/auto.home''' files::<span style="color:green;font-side servicesize:1.5em;">&#x2713;</span> Lab logbook completed ==EXPLORATION QUESTIONS==
Exploration questions:
#What does the no_root_squash option for an NFS mount mean?
#Explain the meaning of the defaults option in an fstab entry. What do the numbers mean at the end?
13,420
edits

Navigation menu