ctivity Overview: In this graded activity, students will provision additional virtual networks and resources, establish an Active Directory Domain, and connect virtual networks via peering. Students will then verify connectivity of all created resources.

Activity Outcomes: After completing this activity will be able to

• Demonstrate configuration of cloud-based virtual network functions
• Demonstrate configuration of cloud-based Load Balancing and NAT
• Demonstrate the configuration of internetwork connectivity
• Demonstrate remote connectivity to compute resources in the cloud

Deliverable: Upload all requested screenshots below, as a .pdf export from the editor of your choosing.

Naming convention: “lastnamefirstinitial_Assignment#.pdf” e.g: “smithp_A1.1.pdf”

Be sure to include your name, student number, and course (CNW-2511) at the top of your document.

Connecting Networks in Azure

Many enterprise networks consist of multiple locations with various shared functions, often due to internal or external requirements (e.g. disaster recovery or regulation). When migrating traditional resources to a virtualized environment in the cloud, engineers must be able to maintain the segmentation and distribution of those resources while providing a seamless transition for their end-users.

Follow this link to log in to the Azure Portal. Virtual Machines (and many other billed resources), must be disabled/deleted via the Azure dashboard to prevent continuous billing. Shutting down a VM within the OS will not disable them.

After you have completed this activity, you will delete all created resources, then verify with screenshots.

Do not create any resources unless you are specifically requested to. This runs a very high risk of your student account credits ($200 cap) being spent in their entirety, at which point you will no longer be able to access any of the resources required for this course, and future courses.

In this lab, you will be provisioning:

• Three (3) virtual NIC’s
• Two (2) virtual networks with one subnet each
• One (1) Load Balancer
• One (1) Public IP
• Three (3) Virtual Machines
• Two (2) V-Net connections via peering

As you progress through this activity, your instructor will request that you capture a screenshot periodically (on Mac OS: “command+shift+3” to capture the whole screen, or “command+shift+4” then drag the cursor over the area you would like to capture). These screenshots are part of your required deliverable and will be graded.

Please attend or view Live Lecture (Week 2 Part 2) when available for the latest walkthrough. It is important to understand Cloud Service Provider (CSP) platforms change frequently, so the available recording here may look differently than what you see. You are welcome to use your best judgement to navigate any differences, or wait until the Live Lecture recording becomes available for further elaboration.

Diagram of Activity Outcome

Lab Requirements (LNFI-MMYYY Resource Group)

1. Create two (2) virtual networks within any two regions which permit you to create VMs in (see Live Lecture for further elaboration), respectively, I am using US West and Central in the example below. No Firewalls
   1. Region 1: “LNFI-West” Address Space – 10.0.0.0/24, Subnet: 10.0.0.0/24
   2. Region 2: “LNFI-Central” Address Space 10.0.1.0/24, Subnet: 10.0.1.0/24
2. Create NSG (one NSG applied to the West US Subnet) permitting RDP (Port 3389), or allow all inbound if there are issues
3. Peer the West US and Central US virtual networks
4. Create two (2) virtual machines within West US Region and one (1) VM in Central US Region. There should be three (3) total VM’s created. You do not need to use D2s_v3 if it is not available, you can use any VM size which has at least 2 vCPUs and 8GB of RAM.
5. VM Size and OS:
   1. 1x D2s_v3 VM, Windows 10 (any version, but Enterprise 2H22 is most common) and 1x D2s_v3 VM, Windows Server (any version, datacenter is most common, 2025 may not work) in your first region D2s_v3 VM, finally 1x Win 10 VM in your second region
   2. Allow incoming RDP (3389)
   3. No Public IP
   4. West US host names: “cnw-client01” / “cnw-websrv”
   5. Central US host names: “cnw-client02”
6. Adjust the new VM NIC’s to static private IP’s
   1. West US Server: 10.0.0.100
   2. West US Client: 10.0.0.200
   3. Central US Client: 10.0.1.200
7. Create a Load Balancer (provision a new public IP within this wizard) in West US Network (Take note of the Public IP that is provisioned). The Load Balancer and Public IP need to be standard SKU. The Load Balancer should be ‘Regional’ or ‘Internal’.
   1. Create a new inbound NAT rule to a single VM: cnw-client01
      1. Service: Custom
      2. Protocol: TCP
      3. Frontend Port: 33891
      4. Target virtual Machine: CNW-Client01
      5. Port mapping: Custom
      6. Floating IP: Disabled (may not be an option)
      7. Target/Backend port: 3389

Final Configurations and Testing

1. In Azure Portal, go to Virtual Networks, complete this configuration in both:
   1. Select DNS Servers, change to “Custom”
   2. Input two DNS Servers: 10.0.0.100 (primary) and 8.8.8.8 (secondary)
   3. Be sure to save your changes
2. Open Microsoft Remote Desktop client applicable for your computer
   1. Connect to: cnw-client01
   2. Input the public IP for your Load-Balancer followed by the external port, example: “52.100.10.54:33891”
   3. Input the login credentials created when you provisioned your VM
   4. PLEASE NOTE: If you have verified that your NSG and ingress access rules are configured correctly, but still cannot RDP into your VM’s, please just note that RDP was not able to connect and any troubleshooting steps you took, in place of the RDP screenshots. Sometimes, depending on the network a student is using, RDP is unable to traverse the home network or hot-spots.
3. Once connected to cnw-client01, open RDP within cnw-client01 (use the search bar for “RDP”) and remotely connect to cnw-websrv and cnw-client02 (Use their private IP addresses and the login credentials you created when provisioning them)
   1. While connected to each VM, disable Windows Firewall completely on all network types (this needs to be done for all three VM’s)
   2. Disconnect from cnw-client02 and cnw-websrv (you should still be RDP into cnw-client01)
4. While RDP into cnw-client01, re-open your RDP session to cnw-websrv, and install Active Directory Domain Services, following all prompts that appear. In post configuration, name your domain “CNW.BIZ“
5. Now, add each client VM to the domain by using RDP.
6. After each client has been added, open command prompt and type “ipconfig /all” on both client VM’s to verify they have successfully been added to the domain.
7. After Lab is complete, verify all required screenshots have been taken (below), then delete all resources.

Required Screenshots

The following screenshots should show the configurations identified in lab, for each component (Please number and label your screenshots):

1. Virtual Networks
2. Inventory page (list of both V-Nets created)
3. 2x Diagram Page – From the two V-nets provisioned (should show all resources provisioned during this activity) – these may not populate fully NOTE: IN CLASS ON 3/15 WE FOUND THIS RENAMED AS TOPOLOGY, NOT DIAGRAM.
4. Virtual Machines:
   1. Overview page for cnw-client01
   2. Overview page for cnw-client02
   3. Overview page for cnw-websrv
5. Virtual Networks:
   1. 2x Peerings sub-page, shown as “connected” for each V-net
6. While connect to the following VM’s via RDP:
   1. “ipconfig /all” on cnw-client01 (after it has been added to CNW.BIZ)
   2. “ipconfig /all” on cnw-client02 (after it has been added to CNW.BIZ)
   3. PLEASE NOTE: If you have verified that your NSG and ingress access rules are configured correctly, but still cannot RDP into your VM’s, please just note that RDP was not able to connect and any troubleshooting steps you took, in place of the RDP screenshots. Sometimes, depending on the network a student is using, RDP is unable to traverse the home network or hot-spots.
7. Load Balancers:
   1. Overview Page
   2. Inbound NAT Rules Page
8. All Resources Page showing all provisioned resources deleted
   

There should be 13 individual screenshots.

Struggling with your essay and deadlines?

Get this or a similar paper done in as fast as 4 hours, 24/7.

NB: We do not sell prewritten papers. All essays are written from scratch according to specific needs and instructions

✔Secure Service ✔ Plagiarism Free ✔On-time Delivery

WRITE MY PAPER