Difference between revisions of "OPS335 NFS Lab"

From CDOT Wiki
Jump to: navigation, search
 
(33 intermediate revisions by 2 users not shown)
Line 6: Line 6:
  
 
*[https://prezi.com/sfxdbjbxgu1e/file-servers-nsf-samba/ File Server Notes] (Week 9 class notes)
 
*[https://prezi.com/sfxdbjbxgu1e/file-servers-nsf-samba/ File Server Notes] (Week 9 class notes)
 +
*[http://nfs.sourceforge.net/nfs-howto/ Linux NFS HOWTO]
 
*[http://tldp.org/HOWTO/NFS-HOWTO/security.html NSF Security] (List of tips regarding NSF and security)
 
*[http://tldp.org/HOWTO/NFS-HOWTO/security.html NSF Security] (List of tips regarding NSF and security)
  
Line 12: Line 13:
 
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 servers that are connected over a local network.
 
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 servers that are connected over a local network.
  
−
Two popular protocols called '''Network File Server''' ('''NFS''') and '''Samba''' ('''SMB''') are used to provide high speed file access between servers on a local network. The '''NFS''' protocol allows a user to access files on another server in a local network in a similar way that local files on a same server are accessed. The '''Samba''' open-source software is used to access files from Windows servers using a combination of Windows protocols including NetBIOS, SMB, etc.
+
Two popular protocols called '''Network File Server''' ('''NFS''') and '''Samba''' ('''SMB''') are used to provide high speed file access between servers on a local network. The '''NFS''' protocol allows a user to access files on another server in a local network in a similar way that local files on a same server are accessed. The '''Samba''' open-source software is used to access files from Windows servers using a combination of Windows protocols including NetBIOS, SMB, etc., and will be discussed in the next lab.
  
−
This lab will focus on installing, configuring and using '''NFS''' and '''Samba''' to access files between different servers on a local network.
+
This lab will focus on installing, configuring and using '''NFS''' to access files between different Linux servers on your local network.
  
−
==INVESTIGATION 1: USING AUTOMOUNT WITH '''NFS'''==
 
  
−
In this investigation, we will set up an '''NFS server''' on our '''VM2''' machine. We will then set up an '''NFS client''' on our '''VM3''' machine and be able to view and '''import files''' within the VM2 /home directories from the VM3 machine.
+
==INVESTIGATION 1: USING AUTOMOUNT WITH NFS==
 +
 
 +
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.}}
 
{{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.}}
Line 28: Line 30:
 
#Make certain that all of your VMs are running.
 
#Make certain that all of your VMs are running.
 
#Switch to your '''VM2''' machine.
 
#Switch to your '''VM2''' machine.
−
#Although nsf is already on your VM when you installed it, we will install additional utilities for nsf. Issue the following command:<br>'''yum install nfs-utils'''
+
#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 '''/etc/exports''' file, and replace all contents of the file with the following:<br>'''/home 192.168.x.4(rw,root_squash,insecure)'''
+
#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)'''
−
#Start enable your nfs service (now known as '''nfs-server.service''').
+
#What does the IPADDR 192.168.x.4 represent? Record your answer in your lab logbook.
−
#Build the server's list of exports: <br>'''exportfs -r'''
+
#Issue the following command (in order of appearance) in order to start your NFS server:<br>'''systemctl start rpcbind'''<br>'''systemctl start nfs'''
−
#Run and record the output of the following commands:<br>'''exportfs'''<br>'''showmount -e'''
+
#Use the '''systemctl''' command to enable both the rpcbind and nfs services upon VM startup.
−
#You will have to adjust your firewall settings on your VM2 machine to allow NFS to work.<br>Run the '''netstat''' command in order to determine the ports needed and issue the appropriate ''iptables'' command(s).
+
#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.
  
 
===Setting up &amp; Testing the NFS Client (VM3)===
 
===Setting up &amp; Testing the NFS Client (VM3)===
Line 39: Line 43:
 
'''Perform the following tasks:'''
 
'''Perform the following tasks:'''
  
−
#Ensure the VM guest network is functioning properly. You can use the "host cbc.ca" command to see if DNS queries are being answered.  
+
#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.
−
#Ensure you have full connectivity to the internet.
+
#Make certain that you are logged into your '''VM3''' machine.
−
#Again, you should not have to install any NFS software.
+
#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'''
 
#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 on your host machine.  Doing so can make your machine fail to boot.}}
+
{{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 avoid an error that would be caused by logging in while root_squash is active:<br>'''setsebool -P'''<br>'''use_nfs_home_dirs 1'''</li><li>Logout of vm03 and shut it down.</li><li>Restart vm03 and login using your learnid.</li><li>Check that the home directory is mounted:<br>'''mount | grep /home'''</li><li>If it is not, try running 'mount /home' as root and observe any errors.</li><li>On vm03, create an empty file by issuing the following command:<br>'''touch empty_file_created_on_vm03'''</li><li>Now shutdown vm03.</li><li>Now on the NFS server, us ls -l in your learnid's home directory to check for the file you just created.</li></ol>
+
<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 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'''
  
−
===Setting up Automount (VM3)===
+
 
 +
==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:'''
 
'''Perform the following tasks:'''
  
−
#Switch to your VM3 machine.
+
#Switch to your '''VM3''' machine.
−
#Comment or remove the line from /etc/fstab that you entered earlier.
+
#Unmount the /home directory from VM2 by running '''umount /home'''
−
#With a server installation of Fedora 22, you will not need to install autofs, but on other installations you might need:<br>'''dnf install autof'''s
+
#Comment or remove the line that you added in the '''/etc/fstab''' file in the previous investigation.
−
#Move the existing file /etc/auto.master:<br>'''mv /etc/auto.master /etc/auto.master.orig'''
+
#Restart your '''VM3''' machine.
−
#This is a great way to keep a back up in case you need to restore the file in the future. Now create another:<br>'''vi /etc/auto.master'''
+
#Install the '''autofs''' package by issuing the following command:<br>'''yum install autofs'''
−
#Add only the following line:<br>'''/home  /etc/auto.home  --timeout=60'''
+
#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.
−
#Create the file /etc/auto.home and add ONLY the following line:<br>'''*       -fstype=nfs4,rw,nosuid,soft      192.168.x.3:/home/&'''
+
#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'''
−
#Start autofs, and ensure the service will automatically start at boot.
+
#Save your editing changes.
−
#Log out of vm3 and log back in using your learn account.
+
#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/&'''
−
#Open a terminal and enter the command:<br>'''mount | grep home'''
+
#Save your editing changes.
−
#How does it differ from the previous mount?
+
#Use the '''systemctl''' command to start the '''autofs''' service, and another systemctl command in order to ensure that the autofs service will automatically start at boot.
−
#Create another empty file with the name:<br>'''touch another_empty_file_from_vm03'''
+
#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).
−
#Run and record the output of the command:<br>'''df -hT'''
+
#Open a terminal and enter the following command:<br>'''mount | grep home'''
−
#Back on the nfs server run and record the output of ls -l in your home directory.
+
#How does it differ from the previous mount? Record your findings in your lab logbook.
−
#You should see the files you created on vm03.
+
#On your '''VM3''' machine, create another empty file with the name:<br>'''touch yet_another_empty_file_from_vm3'''
−
#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:<br>'''audit2allow < /var/log/audit/audit.log'''<br>'''audit2why < /var/log/audit/audit.log'''
+
#Run and record the output of the following command (on both your VM2 and VM3 machines):<br>'''df -hT'''
−
#Now that you have VM3 automatically mounting home directories from VM2, configure VM1 to do the same.
+
#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 VM3 automatically mounting home directories from your VM2 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 1 in your OPS335 lab log-book'''
+
'''Record steps, commands, and your observations in INVESTIGATION 2 in your OPS335 lab log-book'''
−
 
 
  
 
==COMPLETING THE LAB==
 
==COMPLETING THE LAB==
  
−
Arrange proof that ...
+
'''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-size:1.5em;">&#x2713;</span> Lab logbook completed
  
 
==EXPLORATION QUESTIONS==
 
==EXPLORATION QUESTIONS==
Line 88: Line 101:
 
#What is the role of the /etc/mtab file on the nfs server?
 
#What is the role of the /etc/mtab file on the nfs server?
 
#What port does nfs-server use?
 
#What port does nfs-server use?
−
#What is the purpose of the testparm command?
 
−
#What does SMB stand for? CIFS?
 

Latest revision as of 16:48, 4 March 2016


NFS RESOURCES

Online References:

OVERVIEW

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 servers that are connected over a local network.

Two popular protocols called Network File Server (NFS) and Samba (SMB) are used to provide high speed file access between servers on a local network. The NFS protocol allows a user to access files on another server in a local network in a similar way that local files on a same server are accessed. The Samba open-source software is used to access files from Windows servers using a combination of Windows protocols including NetBIOS, SMB, etc., and will be discussed in the next lab.

This lab will focus on installing, configuring and using NFS to access files between different Linux servers on your local network.


INVESTIGATION 1: USING AUTOMOUNT WITH NFS

In this investigation, we will set up an NFS server on our VM2 machine. We will then set up an NFS client on our VM3 machine so that we can view and import files of VM2's /home directory from our VM3 machine.

Important.png
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:

  1. Make certain that all of your VMs are running.
  2. Switch to your VM2 machine.
  3. Although the NFS application was already installed on your VM, we will install additional utilities for NFS by issuing the following command:
    yum install nfs-utils
  4. 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:
    /home 192.168.x.4(rw,root_squash,insecure)
  5. What does the IPADDR 192.168.x.4 represent? Record your answer in your lab logbook.
  6. Issue the following command (in order of appearance) in order to start your NFS server:
    systemctl start rpcbind
    systemctl start nfs
  7. Use the systemctl command to enable both the rpcbind and nfs services upon VM startup.
  8. Issue the following command in order to add (or "build") the server's list of permitted exports:
    exportfs -r
  9. Run and record the output of the following commands in your lab logbook:
    exportfs
    showmount -e
  10. 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 ports 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.

Setting up & Testing the NFS Client (VM3)

Perform the following tasks:

  1. 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.
  2. Make certain that you are logged into your VM3 machine.
  3. Install the nfs-utils package on your VM3 machine.
  4. Add the following line to the bottom of the /etc/fstab file on your VM3 machine:
    192.168.x.3:/home /home nfs4 defaults 0 0
Important.png
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.
  1. Run the following command to confirm that SELinux will not block the network share:
    setsebool -P use_nfs_home_dirs 1
  2. Issue the following command to mount any network shares without having to logout and login to your VM3:
    mount -a
  3. Create an empty file within the regular user's home directory on your VM3 machine.
  4. Issue the ls-l command for VM2 regular user's home directory. Do you see a file that you created there?
  5. Switch to your VM2 machine and view the contents on your regular user's home directory. What you do you notice? What does this mean in terms of using NFS? Record your observations in your lab logbook.
  6. Restart your VM3 machine and login with your regular user id.
  7. Make certain that you iptables rules are the same to allow NFS to work
  8. Check that the VM3 regular user's home directory is mounted by issuing the following command:
    mount | grep /home
  9. If it is not, try running mount /home as root and observe any errors.
  10. Create another file in the regular user's home directory on your VM3 machine.
  11. Switch to your VM2 machine to see if you can view that file.
  12. Finally, issue the ls-l command in your VM3 regular user's home directory to note the contents.

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:

  1. Switch to your VM3 machine.
  2. Unmount the /home directory from VM2 by running umount /home
  3. Comment or remove the line that you added in the /etc/fstab file in the previous investigation.
  4. Restart your VM3 machine.
  5. Install the autofs package by issuing the following command:
    yum install autofs
  6. Rename the existing file /etc/auto.master file by issuing the following command:
    mv /etc/auto.master /etc/auto.master.orig
    Keep this file as a back-up in case you need to restore the file in the future.
  7. Use the vi text editor to create a new (empty) /etc/auto.master file and add the following line:
    /home /etc/auto.home --timeout=60
  8. Save your editing changes.
  9. Use the vi text editor to create a file called /etc/auto.home and add add the following line:
    *   -fstype=nfs4,rw,nosuid,soft   192.168.x.3:/home/&
  10. Save your editing changes.
  11. Use the systemctl command to start the autofs service, and another systemctl command in order to ensure that the autofs service will automatically start at boot.
  12. Log out of and back into vm3 using your regular user account (i.e. not root. You should be in your regular user account for both VM2 and VM3 machines).
  13. Open a terminal and enter the following command:
    mount | grep home
  14. How does it differ from the previous mount? Record your findings in your lab logbook.
  15. On your VM3 machine, create another empty file with the name:
    touch yet_another_empty_file_from_vm3
  16. Run and record the output of the following command (on both your VM2 and VM3 machines):
    df -hT
  17. 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).
  18. Now that you have VM3 automatically mounting home directories from your VM2 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:

✓ Show mount information regarding vm3 and vm1 shares with NFS server (vm2)
✓ All files shown in network server (vm2)
✓ Display contents of /etc/exports, /etc/auto.master and /etc/auto.home files
✓ Lab logbook completed

EXPLORATION QUESTIONS

  1. What does the no_root_squash option for an NFS mount mean?
  2. Explain the meaning of the defaults option in an fstab entry. What do the numbers mean at the end?
  3. What is the function of the 'exportfs' command?
  4. What is the purpose of the 'showmount' command?
  5. What is the meaning of the "timeout=60" phrase?
  6. What is the meaning of the asterisk (*) in the file /etc/auto.home?
  7. What is the meaning of the ampersand (&) in the file /etc/auto.home?
  8. What is the role of the /etc/mtab file on the nfs server?
  9. What port does nfs-server use?
Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=OPS335_NFS_Lab&oldid=116038"