Difference between revisions of "Lab 6 Warnings / Debrief"

From CDOT Wiki
Jump to: navigation, search
(Preparing for Lab Sign-Off)
Line 72: Line 72:
 
* Each "signed-off" lab (before due date) is worth 1% of your final grade.
 
* Each "signed-off" lab (before due date) is worth 1% of your final grade.
 
* Signing-off on labs help to spot errors that can cause problems with future labs.
 
* Signing-off on labs help to spot errors that can cause problems with future labs.
* Do you ask the instructor what to check for! Read at the bottom of the lab the requirements, and have all proof available for instructor to view at same time.
+
* Do not ask the instructor what to check for! Read at the bottom of the lab the requirements, and have all proof available for instructor to view at the same time.
 
* Failing to be prepared and asking instructor what to check when assignment is mark will result in deduct of marks!
 
* Failing to be prepared and asking instructor what to check when assignment is mark will result in deduct of marks!
 
* For example, open multiple terminals with command results. If properly set-up ahead of sign-off, the process should only take instructor approx 20 seconds to sign-off your lab.
 
* For example, open multiple terminals with command results. If properly set-up ahead of sign-off, the process should only take instructor approx 20 seconds to sign-off your lab.
 
* If you do not have your lab-logbook, you MUST show your work and your lab log-book to your instructor for sign-off in the next class. This may cause a late penalty if past the required due date.
 
* If you do not have your lab-logbook, you MUST show your work and your lab log-book to your instructor for sign-off in the next class. This may cause a late penalty if past the required due date.
 
  
 
== Lab 6 Debrief ==
 
== Lab 6 Debrief ==

Revision as of 16:05, 14 July 2015

Purpose / Objectives of Lab 6

Setting up networks is an essential operation for a system administrator. Maintaining network connectivity and securing the network are also essential operations for a system administrator.


In this lab, you will learn the basics of networking by using your Virtual Machines and your c7host machine. You will first set up a virtual private network among those machines. In addition, you will learn to set up network names (to associate with server's IP Addresses), associate network services with port numbers for troubleshooting purposes, and setup firewall policies via the iptables command.

Main Objectives

  1. Configure a private (virtual) network for your VMs and your c7host machine
  2. Configure network interfaces for your Virtual Machines using both graphical and command-line utilities.
  3. Use local hostname resolution to resolve simple server names with their corresponding IP Addresses
  4. Backup more recent files (eg. incremental backup) using the find command and a date/time-stamp file
  5. Use common networking utilities to associate network services with port numbers for troubleshooting purposes
  6. Gain initial exposure to the iptables command used to configure and maintain a firewall for protection and troubleshooting
  7. Configure iptables to allow/disallow/forward different types of network traffic


Configuring a Virtual Private Network (VPN)

For the remainder of this course, we will focus on networking involving our VMs and our c7host machine. This lab will focus on setting up a virtual private network (VPN), connecting our VMs and c7host machine to the VPN, and configuring our VPN to make more convenient to use, troubleshoot and protect. Lab 7 will focus more on configuring SSH and making access to the VPN more secure. Finally, lab 8 will focus on configuring the network for fixed workstations, mobile devices, or both at the same time.

There are several reasons for creating VPNs. The main reason is to safely connect servers together (i.e. to safely limit but allow share information among computer network users). This allows for a secure connection of computers yet controlling access to and monitoring (protecting) access to permitted users (discussed in more depth in lab7).


Two Steps Required to Setup a VPN

File:Steps.png
Explain 2 major steps to do - Configure in virt-manager, and then configure (either graphically or command line for each VM.

If we are going to setup a private network, we must do 2 major operations: First, define a new private network in the Virtual Manager application; and second, configure each of our VMs to connect to this new private network. In Part 1, we will be perform the first operation. In parts 2, 3, and 4, we will be performing the second operation for all VMS (graphical and command-line).


Backing up Only Recent File Changes

Backing up Files |One very important aspect of system admin is performing backups. There are many methods for backing up the data on a a computer system. The following is an example of a common backup system used in Business Unix/Linux systems:

Full Backup: Backup all specified files (eg. configuration, data files, etc)
Incremental Backup: Backup of only files that have changed since last (full) backup.


You will be using the find command to backup recent changes to files. In this case, we will save date/time-stamp information in a file, configure to connect centos1 to the network, run the find command, and run the find command to copy new (back-up file since date/time-stamp) in order to prove that the incremental backup worked (showing the files created as a result of the configuration of centos1 to the VPN).

Networking Tweaks

Connecting a private network is an important task, but a system administrator also needs to "tweak" the network to make it convenient to use, make it safer from unauthorized access, and use troubleshooting utilities to help troubleshoot network connectivity problems as they occur. This investigation will expose you to some useful tricks and utilities to help accomplish this task.

Topics Include:

  • Local Host-name Resolution
  • Obtaining MAC (Hardware) addresses on Network Computers
  • Creating Firewall Policies

Local Host-name Resolution

Obtaining MAC (Hardware) addresses on Network Computers

Creating Firewall Policies


Common Mistakes / Warnings

Important.png
Be Aware of the Following Issues
Be aware of these common mistakes that students make that can cause problems for their future labs.


  • Not following instructions
  • Not constantly issuing commands to verify previous command were properly executed


Preparing for Lab Sign-Off

Students should be prepared with all required commands (system information) displayed in a terminal (or multiple terminals) prior to calling the instructor for signoff.


In order to properly complete your lab and move to the next lab, you must have your instructor "sign-off" on your lab

  • Each "signed-off" lab (before due date) is worth 1% of your final grade.
  • Signing-off on labs help to spot errors that can cause problems with future labs.
  • Do not ask the instructor what to check for! Read at the bottom of the lab the requirements, and have all proof available for instructor to view at the same time.
  • Failing to be prepared and asking instructor what to check when assignment is mark will result in deduct of marks!
  • For example, open multiple terminals with command results. If properly set-up ahead of sign-off, the process should only take instructor approx 20 seconds to sign-off your lab.
  • If you do not have your lab-logbook, you MUST show your work and your lab log-book to your instructor for sign-off in the next class. This may cause a late penalty if past the required due date.

Lab 6 Debrief