Franske ITC-2300 Assignment

Labs

You are responsible for completing ALL of these labs. You must submit a lab report (click for details about how to write these) for each topic. Each lab report is worth up to 20 points. This falls into the Labs/Homework category of your course grade.

VoIP Labs

• CUCM Install & Chapter 8 Lab (One report for these)
• Chapter 9 Labs (One report for these)
  • NOTE: You will not need to complete the Active Directory (LDAP) Integration lab
• Chapter 10 Labs (One report for these)

Virtualization Labs

IP Addressing Information

Use the following information to correctly address your VMware systems:

Pod	IP Address	Use
1	172.17.144.50	VCSA
	172.17.144.51	ESXi-1
	172.17.144.52	ESXi-2
	172.17.144.53	ESXi-3
2	172.17.144.54	VCSA
	172.17.144.55	ESXi-1
	172.17.144.56	ESXi-2
	172.17.144.57	ESXi-3
3	172.17.144.58	VCSA
	172.17.144.59	ESXi-1
	172.17.144.60	ESXi-2
	172.17.144.61	ESXi-3
4	172.17.144.62	VCSA
	172.17.144.63	ESXi-1
	172.17.144.64	ESXi-2
	172.17.144.65	ESXi-3
5	172.17.144.66	VCSA
	172.17.144.67	ESXi-1
	172.17.144.68	ESXi-2
	172.17.144.69	ESXi-3
6	172.17.144.70	VCSA
	172.17.144.71	ESXi-1
	172.17.144.72	ESXi-2
	172.17.144.73	ESXi-3
7	172.17.144.74	VCSA
	172.17.144.75	ESXi-1
	172.17.144.76	ESXi-2
	172.17.144.77	ESXi-3
8	172.17.144.78	VCSA
	172.17.144.79	ESXi-1
	172.17.144.80	ESXi-2
	172.17.144.81	ESXi-3
9	172.17.144.82	VCSA
	172.17.144.83	ESXi-1
	172.17.144.84	ESXi-2
	172.17.144.85	ESXi-3

Default Gateway: 172.17.144.1 Subnet Mask: 255.255.255.0 DNS: 172.17.139.10

vmWare ESXi Installation Lab

1. Create a new VM in VMware Workstation with the following specifications. Be sure to save the VM to a location on the D drive outside of the CNT Files folder.
   • 12GB RAM
   • 175GB Hard Drive
   • 2 CPUs
2. Locate the ESXi Install ISO file (VMvisor Installer) in the D:\CNT Files\ITC 2300 directory and use it to start the installation
3. Set the networking to "Bridged" and make sure you are connected to the ITC network and bridged to the correct adapter, not using automatic bridging.
4. Set the root password on your ESXi system during the installation, it needs to be at least 7 characters. Be sure to write it down!
5. Create another new VM in VMware Workstation with the following specifications. Be sure to save the VM to a location on the D drive outside of the CNT Files folder.
   • 1GB RAM
   • 25GB Hard Drive
   • 2 CPUs
6. Locate the Windows 7 Enterprise ISO file in the D:\CNT Files directory and use it to start the installation
7. Set the networking to "Bridged" and make sure you are connected to the ITC network and bridged to the correct adapter, not using automatic bridging.
8. Set the Administrative password on your Windows 7 Client system during the installation, be sure to write it down!
9. Browse to the ESXi system in a web browser on your Windows 7 Client system.
10. Download and install the vSphere Client for Windows
11. Open the vSphere Client for Windows and connect to your ESXi system as the root user.
12. Add a new account and give it administrative permissions to the ESXi system. Log out of the root account and in with the new user account.
13. Copy the Linux Mint 17.3 ISO file from the D:\CNT Files directory on your host system into your Windows 7 Client system
14. Use vSphere Client to create a new folder on the ESXi datastore for ISO files.
15. Upload the Linux Mint ISO file to the new ISO folder on the ESXi server datastore.
16. Use the vSphere Client to create a new VM on the ESXi system (not in VMware Workstation) where you can install the Linux Mint system.
17. Shut down your Windows 7 Client
18. Use a web browser on your host system to access the ESXi server's web interface.
19. Log in to the "VMware Host Client" through the web interface using your new login credentials (not the root account)
20. Complete the installation of Linux Mint as a VM on the ESXi host using vSphere Host Client
21. Safely shut down your ESXi server VM.
22. Ensure all your network connections are back to normal and you are connected to the campus network.

vmWare vSphere vCenter Server Installation Lab

1. Connect the PCs in your pod to the ITCnet network
2. Boot your ESXi Server system
3. Obtain static IP addressing information from the table above and change the IP address of each ESXi server in your pod to a unique static IP address.
4. Boot your Windows 7 Client system
5. Download and install the Virtual Clone Drive software in your Windows 7 Client system
6. Mount the vSphere vCenter Installer ISO (VCSA) found in the D:\CNT Files location on your Windows 7 Client system using the Virtual Clone Drive software and install the VMware Client Integration Plugin (found in the vcsa folder of the CD image) on the Windows 7 Client.
7. Open the vcsa-setup.htm file found in the root of the CD image and click install to begin the installation process. If you're unfamiliar with the installation process you can refer back to your readings as well as a VMware walk-through.
8. During the installation you will need to select one of your pod's ESXi servers to install the vCenter appliance onto. Only one VCSA installation per pod!
9. Set a root password for your VCSA server during the installation process, be sure to write this down!
10. When given the option you should install vCenter Server with an Embedded Platform Services Controller
11. When creating a new SSO domain use "podX.local" (where X is replaced by your pod number) as your SSO Domain Name
12. When asked about the appliance size choose a "Tiny" installation.
13. When asked about the database select the option to use an embedded database.
14. Use the correct static IP address for the VCSA from the allocation you received for your pod and choose to synchronize time with the ESXi appliance host.
15. After the installation completes use your credentials (administrator@podX.local) to log in to the VCSA web client at the address provided.
16. Spend a few minutes exploring the VCSA web client interface
17. Create a new Datacenter and give it a name
18. Add the all the ESXi hosts in your pod to the datacenter
19. Try connecting to your VCSA server from your vmWare Client software on your Windows 7 system instead of through the web client and see what similarities and differences you can find.
20. Either using the web client or the desktop client create a few more VMs through VCSA on various different ESXi hosts. Use the ISOs in the CNT Files folder to install another copy of Mint into one, Windows 7 into another, and Windows XP into another.
21. Safely shutdown all running VMs except VCSA
22. Safely shutdown the VCSA appliance
23. Safely shutdown all ESXi hosts
24. Safely Shutdown Windows 7 Client System
25. Ensure your system is reconnected to the campus network

vmWare vSphere Administration Lab

1. Connect the PCs in your pod to the ITCnet network
2. Boot all your ESXi Server systems
3. Boot your VCSA VM Appliance using the ESXi web interface on the ESXi system hosting VCSA.
4. Use the VCSA web interface to create a new VM which is running on an ESXi server OTHER than the one running VCSA (so more RAM is available) to install Windows Server 2012. You will need a VM with 2GB RAM and a 50GB hard drive.
5. Complete the installation of Windows Server 2012 into the new VM. The ISO installation file for Server 2012 can be found in "D:\CNT Files" Use "dc1" as the machine name.
6. Add the Active Directory Domain Services role to the server. Use "podX-ad.local" (where X is your pod number) as the root domain name and "podX-ad" as the NetBIOS domain name.
7. While the Active Directory role is installed and the domain controller promotion script is running (these will take some time to complete) continue through this lab.
8. It's sometimes the case that you may have a malfunctioning web interface and need to start some critical VMs such as VCSA and some Active Directory servers only through the host command line interface. We'll simulate this setup by checking the status and powering on one of our Windows 7 or Linux Mint VMs through this host console.
9. Use the host command line console on your ESXi machines to get a list of the VMs registered at each host.
10. Use the host command line console on your ESXi machines to check the power status of one of your Windows 7 or Mint VMs (they should be off)
11. Verify the VMs are off in the vCenter Server web client
12. Use the host command line console on your ESXi machines to power on one of your Windows 7 or Mint VMs.
13. Verify the VM is powering on through both the Use the host command line console on your ESXi machine as well as through the vCenter web interface.
14. Another useful virtual machine task is to set certain VMs to automatically power on when the ESXi server powers on. Read the VMware KB article on the topic.
15. Set the VCSA VM to automatically power on with the ESXi host.
16. One benefit of the vCenter Server system is that you can migrate VMs from one ESXi host to another. First let's try this with a powered off virtual machine.
17. Choose one of the powered off VMs on one of your hosts in the VCSA Web Client. On the summary tab check to see which host the VM currently resides on.
18. Right click on it and choose migrate to open the migration wizard. You want to move both the compute (CPU/RAM) and storage (disk images) to a new host so make that selection.
19. Select a different ESXi server and a datastore attached to that server and begin the migration.
20. Once the migration is complete check that the VM shows it is on a different host and verify that it still powers up and works.
21. An even more powerful tool is to be able to migrate VMs while they are running, this feature is called vMotion. Take the same VM and try the migration process again (back to the original host) while the machine is powered on.
22. This may take quite a bit longer to complete so let's go back to our Windows Server setup while the vMotion magic is happening.
23. It would be nice to have a single sign on for VMware vCenter Server users which is backed by our Active Directory domain so let's see if we can get that running.
24. Follow the VMware instructions for adding a vCenter Server Single Sign-On identity source. You may also need to read the Active Directory Identity Source Settings.
25. You are going to want to setup Active Directory as an LDAP server so that you don't need to join your VCSA system to your domain. Instructions for setting that up can be found here.
26. Create a new user account in AD and try adding it as an administrator in vCenter Server.
27. Try logging in with the new account in vCenter Server.
28. Safely shutdown all running VMs except VCSA
29. Safely shutdown the VCSA appliance
30. Safely shutdown all ESXi hosts
31. Ensure your system is reconnected to the campus network

Proxmox VE Installation Lab

1. You will be installing a Proxmox VE server on each computer in your group (so do all these steps, unless otherwise indicated, on each computer). If you are unsure about how to do something try checking the Proxmox Wiki site first.
2. Create a new VM in VMware Workstation with the following specifications. Be sure to save the VM to a location on the D drive outside of the CNT Files folder.
   • 12GB RAM
   • 175GB Hard Drive
   • 2 CPUs
   • Enable Intel VTi/VTx Virtualization for the processors in the VM
3. Locate the Proxmox VE installer ISO file in the D:\CNT Files\ directory and use it to start the installation
4. Set the networking to "Bridged" and make sure you are connected to the ITC network and bridged to the correct adapter, not using automatic bridging.
5. Start the Proxmox VE installation making note of these options
   • Use ext4 as the filesystem
   • Record the administrative password for future use
   • Set the IP address using the same table as VMware (above) ESXi addresses
6. Use a web browser on your host system to access the Proxmox VE server's web interface as the root user (username root) and password set during the installation
7. Add a second user account to Proxmox VE and set it up with administrative access. Set the second account up as a Proxmox VE Authentication Server realm account meaning it will only be available in Proxmox and not on the underlying Linux system.
8. Log out of the administrator account and in using the secondary account you just created
9. Upload Windows 7 and Linux Mint ISO files from your host system to the Proxmox VE server using the web interface
10. Try creating a Windows 7 and Linux Mint VM in Proxmox VE and complete the installation (use KVM as the VM type)
11. Safely shut down your Windows and Linux guest systems
12. Safely shutdown your Proxmox VE server
13. Ensure all your network connections are back to normal and you are connected to the campus network.

Proxmox VE Containers and Cluster Lab

1. Connect the PCs in your pod to the ITCnet network
2. Boot all your Proxmox VE Server systems
3. Check the available container templates on your PVE server and make sure you have downloaded the latest Debian and Ubuntu system templates. Also download at least one of the Turnkey Linux appliance templates such as the Wordpress template.
   • NOTE: If you have an incomplete list of container templates it's likely the case that your system was powered off when the auto-run script went to check the list of available templates. You can refresh this list manually from the PVE command line using information from the ProxMox Linux Containers page.
4. After you have the containers downloaded go ahead and deploy a container based on the Ubuntu template, use DHCP addressing.
5. Try using the Ubuntu container to see if it feels any different than a full Ubuntu VM.
6. Create a Proxmox cluster for your pod. Do this on the proxmox node containing the most VMs (the ones you want to save) all other nodes will need to have their VMs wiped before joining the cluster.
7. Add all of the PVE servers/nodes in your pod to your Proxmox cluster
   • NOTE: You will need to remove all of the VMs on the node before you add it to the cluster
8. Deploy a Debian container to a node in your Proxmox cluster, verify it is working
9. Deploy a Wordpress server container to a node in your Proxmox cluster, verify it is working
10. Try migrating one of your VMs from the last lab which is not powered on from one node to another node in the cluster and then powering up and verifying the VM still works
11. Try migrating one of your Linux containers from one node to another node in the cluster (you will have to power it down) and then powering up and verifying it still works
    • NOTE: We are unable to test online migration as Proxmox requires shared storage for online migration (this was also required by VMware until recent versions)
12. Try modifying an existing container or VM by adding extra storage, in the form of an additional virtual disk, to the system
13. Try cloning one of your VMs
14. Safely shut down all your containers and VMs
15. Safely shutdown your Proxmox VE server
16. Ensure all your network connections are back to normal and you are connected to the campus network.

Storage Labs

FreeNAS Installation Lab

1. Connect your PC to the ITC network
2. Download the FreeNAS Installation ISO from the \\win-0\ server share on the ITC Network to your D: drive
3. Create a new VM for FreeNAS in VMware Workstation with the following specifications. Be sure to save the VM to a location on the D drive outside of the CNT Files folder.
   • 12 GB RAM
   • 32 GB Primary Hard Drive
   • Quantity 3 - 100 GB Data Hard Drives
4. Complete the FreeNAS installation onto the 32GB hard drive making note of your root password and using the same static IP address as your third ESXi server above
5. Boot into your FreeNAS system
6. Access the web interface from your host PC (or another PC on the ITC network) and complete the Initial Configuration Wizard.
   • Setup the data disks in a raidz1 pool
7. See if you can get a Windows (SMB) share working that is 10GB in size and copy some files from your host PC D: drive onto the share. Refer to the FreeNAS documentation as necessary. Here are some hints:
   • You need to create a FreeNAS user account and activate the "Microsoft Account" option for the user
   • You need to create a location on your raidz storage pool for the 10 GB file share to exist on, you need to make sure that the user and group you want to have access to the files is the owner of this location (requires changing permissions)
   • You need to create the SMB file share and point it to the storage location
   • You can access a file share in Windows by opening a Run dialog box and entering \\ip.address.of.freenas\ opening your share, and giving the correct username and password when prompted
8. Safely shut down your FreeNAS VM
9. Ensure your computer is reconnected to the campus network and you have a working Internet connection

Homework

Any homework assigned in the course will go here. This falls into the homework category of your course grade.

• For each topic you need to write at least 5 high quality multiple choice questions and submit them in the correct format, with the correct answer and a citation (book name and page number, URL, or other resource). These questions will be worth up to 15 points for each topic based on grammar, quality, spread across the topic content (don't concentrate on just one part of the topic), etc. Be sure to read the Writing Moodle Questions tutorial for additional information.

Participation Activities

Any participation activities completed in the course will go here. This falls into the participation category of your course grade.

• For each topic you need to meet with the instructor at least once to check on your status and understanding of the topic. Each meeting will be worth up to 10 points.

Topic Assessments

You are responsible for completing an online assessment for each topic. These fall into the online assessments category of your course grade.

Other

You are also responsible for completing these things, see the course syllabus for category and weighting information.

• Online Final Exam
• Course Project

Course Project

The course project will take the place of the skills exam in this course and will allow you to continue to experiment with one of the topic areas covered in the course. Additional details will be available later in the course.

Return to ITC-2300 Homepage