Question: SCREENSHOTS from NFS - Client ( Toronto VM ) List the packages for NFS - Client Show the status of rpcbind service df - Th

SCREENSHOTS from NFS-Client (Toronto VM)
List the packages for NFS-Client
Show the status of rpcbind service
df -Th /sharednfs /hqdocs /partner/ast4digit-humber-id-of-partner
Is -I /sharednfs /hqdocs /partnerlast4digit-humber-id-of-partner
View and list the client file that defines settings used at mounting shares
Display and list the client file that keeps track of mounted shares and the local file systems
List the client side NFS startup configuration file
PART-D: NFS MONITORING
Display NFS and RPC I/O statistics on NFS server (SCREENSHOT)
Display NFS and RPC I/O statistics on NFS client (SCREENSHOT)
In NFS client, provide rw statistics for each mounted share. (SCREENSHOT)
PART-E: AUTOFS
Create a new directory /autodir in your NFS server (montreal) and populate it with non-empty files
autodir1 and autodir2 and export /autodir to NFS client (toronto). Using autofs direct map mount it in
toronto VM as /autodirmnt.
Create a new directory /autoindir in your NFS server (montreal) and populate it with non-empty files
autoindir1 and autoindir2 and export /autoindir to NFS client (toronto). Using autofs indirect map mount
it in toronto VM as/misc/autoindirmnt.
SCREENSHOTS: MONTREAL a) cat /etc/exports b)Is -I /autodir /autoindir c)sudo exportfs -avr
TORONTO a) df -Th /autodirmnt /misc/autoindirmnt b) cat /etc/auto.direct c)cat /etc/auto.misc
d) Is - I /autodirmnt /misc/autoindirmnt e)systemctl status autofs f) cat /etc/autofs.conf Igrep master
PART-F: CONFIGURE MOUNT POINT TO BE PERSISTENT
Change root password to a password you can remember
In NFS Client, configure /sharednfs and / branchdocs NFS mount points to be persistent (SCREENSHOT cat
/etc/fstab), reboot and confirm that your configuration works. It is highly recommended to have a backup
of/etc/fstab file before editing it.
NOTE : (in case system fails to restart after entries in /etc/fstab)
NFS server must be running before starting NFS-client, if not NFS client could go to emergency mode
Due to entries in /etc/fstab, the system may enter into emergency mode or rescue mode due to entries in
/etc/fstab file.
In the emergency mode, enter root password to log in as root user.
Now edit/etc/fstab file, correct error in the line you have added, save and reboot OR you can comment
the line you have added by typing # at start of that line to correct it later after successful boot up
Do not comment or alter the lines that has been added by system (/boot,/, swap)SCREENSHOTS from NFS-Client (Toronto VM)
16. List the packages for NFS-Client
17. Show the status of rpcbind service
18. df -Th /sharednfs /hqdocs /partnerlast4digit-humber-id-of-partner
19. ls -l /sharednfs /hqdocs /partnerlast4digit-humber-id-of-partner
20. View and list the client file that defines settings used at mounting shares
21. Display and list client file that keeps track of mounted shares and the local file systems
22. List the client side NFS startup configuration file
PART-D: NFS MONITORING
23. Display NFS and RPC I/O statistics on NFS server (SCREENSHOT)
24. Display NFS and RPC I/O statistics on NFS client (SCREENSHOT)
25. In NFS client, provide rw statistics for each mounted share. (SCREENSHOT)
PART-E: AUTOFS
26. Create a new directory /autodir in your NFS server (montreal) and populate it with non-empty files
autodir1 and autodir2 and export /autodir to NFS client (toronto). Using autofs direct map mount it in
toronto VM as /autodirmnt.
27. Create a new directory /autoindir in your NFS server (montreal) and populate it with non-empty files
autoindir1 and autoindir2 and export /autoindir to NFS client (toronto). Using autofs indirect map mount
it in toronto VM as /misc/autoindirmnt.
SCREENSHOTS: MONTREAL a) cat /etc/exports b)ls -l /autodir /autoindir c)sudo exportfs -avr
TORONTO a) df -Th /autodirmnt /misc/autoindirmnt b) cat /etc/auto.direct c)cat /etc/auto.misc
d) ls -l /autodirmnt /misc/autoindirmnt e)systemctl status autofs f) cat /etc/autofs.conf |grep master
PART-F: CONFIGURE MOUNT POINT TO BE PERSISTENT
28. Change root password to a password you can remember
29. In NFS Client, configure /sharednfs and /branchdocs NFS mount points to be persistent (SCREENSHOT cat
/etc/fstab), reboot and confirm that your configuration works. It is highly recommended to have a backup
of /etc/fstab file before editing it.
NOTE : (in case system fails to restart after entries in /etc/fstab)
NFS server must be running before starting NFS-client, if not NFS client could go to emergency mode
Due to entries in /etc/fstab, the system may enter into emergency mode or rescue mode due to entries in
/etc/fstab file.
In the emergency mode, enter root password to log in as root user.
Now edit /etc/fstab file, correct error in the line you have added, save and reboot OR you can comment
the line you have added by typing # at start of that line to correct it later after successful boot up
Do not comment or alter the lines that has been added by system (/boot,/, swap)
SCREENSHOTS from NFS - Client ( Toronto VM ) List

Step by Step Solution

There are 3 Steps involved in it

1 Expert Approved Answer
Step: 1 Unlock blur-text-image
Question Has Been Solved by an Expert!

Get step-by-step solutions from verified subject matter experts

Step: 2 Unlock
Step: 3 Unlock

Students Have Also Explored These Related Accounting Questions!