C R E AT I N G A V I R T U A L N ET W O R K K R U N A L T R I V E D I W W W. T E C H T R A I N I N G P O I N T. C O M

Transcription

1 C R E AT I N G A V I R T U A L N ET W O R K K R U N A L T R I V E D I W W W. T E C H T R A I N I N G P O I N T. C O M

2 Go to portal.azure.com and sign in with your credentials. Click on create a resource, search for Virtual Network and click on Virtual Network in the results.

3 It will open a new blade. Click on create.

4 Give name to your VNet. Since we are going to have two subnets inside our VNet, we need to have the address space as /16

5 Select the resource group that you want or create a new one. Give the name to your subnet as FrontEndSubnet and give the address range as /24. We are going to create another subnet later on. Pin to dashboard and click on create.

6 Open your Virtual Network and click on subnets. Click on Add Subnet to add your second subnet.

7 Give name BackendSubnet to it. Set the address range/cidr block as /24. Leave Network Security Group and Route Table empty since we are going to create them later on. Click on OK.

8 Here you can see that the available address are 251 in both the CIDR blocks. Because, first four and the last (total 5) addresses are used for reserved purposes and cannot be used.

9 Now we are going to create two Network Security Groups. One will be for the front end and the other will be for the back end.

10 Front End NSG FrontEnd NSG will use two rules: - rdp-rule: This will allow RDP traffic to the FrontEnd subnet. Web-rule: This will allow HTTP traffic to the FrontEnd subnet.d

11 Back End NSG BackEnd NSG also contains two rules: sql-rule: This allows SQL traffic only from the FrontEnd subnet. Web-rule: This denies all internet bound traffic from the BackEnd subnet. rdp-rule: This will allow RDP traffic to the BackEnd subnet.

12 Click on create resource and search for network security group. Click on create.

13 Give name FrontEndNSG and use the existing resource group in which you ve made the Virtual Network. Click on create.

14 Likewise, create one more NSG for the backend.

15 Go to your FrontEndNSG and click on Inbound Security Rules. Click on Add.

16 Give the source as Any so that the source port ranges would become * i.e. from anywhere. Destination any. The destination port would be 80. The protocol would be TCP and the action would be allow.

17 The priority would be 100. Lower the number, higher the priority. Make sure to give priorities in multiples of 100 so that if something new comes up, we can easily fix it in between. Give the name WebRule allow. Click on OK.

18 Now we are making a rule for RDP. Add new rule. Keep everything as it is except the port number and priority. Change port number to 3389 and priority to 110. Click on OK. Port number 3389 is for RDP access. You might get a warning saying that this is just for testing purpose and not for production use.

19 The two rules have been created successfully.

20 Then in the BackEndNSG, create a new inbound rule with everything else same except the port number and name. The port number should be 1433 and the name would be SQL rule allow.

21 Add a new Outbound Security Rule whose action would be Deny, port number would be 80 and name would be HttpRuleDeny.

22 Now we have created our NSGs but we have not assigned them to our subnets. So next, we are going to do that.

23 Go to your VNet then to the FrontEndSubnet and click on Network Security Group. Click on FrontEndNSG and click on Save.

24 Similarly, assign BackEndNSG to the BackEndSubnet.

25 Now we need to create Virtual Machines for our Virtual Network where we are going to create one Virtual Machine for each of the subnet.

26 Create a new Virtual Machine with Windows Server 2012 R2 Datacenter.

27 When you click on create, a new blade will be opened.

28 Fill out the fields in the basic settings. Use the existing resource group that you had created for the virtual network and click on OK.

29 For the size, use DS1_V2 Standard type and click on select.

30 Keep Yes on the managed disks. The Virtual Network would be chosen by default. Select the subnet as FrontEndSubnet and keep the Public IP address as it is..

31 Keep the Network Security Group as none. We have already added the NSG to our subnet. Basically, you add the NSG to three levels, at the VNet level, at the subnet level and at the VM level.

32 Create a new Availability set and give a name to it. Keep the fault domains as 2 and keep the update domains as 5.

33 Keep the Boot Diagnosis and Guest OS Diagnosis as disabled.

34 Click on create.

35 Now we need to create one more VM that will be for the SQL server.

36 Click on Virtual Machines, click on Add and search for SQL Server. Select SQL Server 2014 SP2 Enterprise on Windows Server 2012 R2 and click on create.

37 Configure the basic settings and click on OK.

38 Now since it is for the database, it is going to show me a highly configured VM to choose. But since this is just for our demo purposes, we are going to choose a lower configuration one.

39 Click on view all and select the DS1_V2 standard configuration.

40 Choose the subnet as BackendSubnet.

41 Now since we are not going to expose this database publicly, we don t need a public IP address. So for that, choose none.

42 For the NSG as well, choose none because we have applied NSG at the subnet level itself. Rest as it is, click on OK.

43 In the SQL server settings, choose the SQL connectivity as Private where the database can be accessed from within the VNet only. Keep the port number as default. Enable SQL authentication.

44 Keep the storage configuration as general where the IOPS (Input/Output Operations per second is 3200, throughput is 48 MBps and storage size is 1 TB. Now, in every VM, there would be just one disk i.e. the OS disk. But since this is a SQL server, it is also going to add a data disk as well. Keep the storage optimization as General and click on OK.

45 Keep everything else as default and click on OK.

46 Once the validation gets passed, click on Create.

47 If you go to your Resource Group, you will be able to see everything that you have created. It has also created Network Interface Cards by default for each VM. Now we are going to connect to our first VM.

48 Go to your first VM and click on Connect. If it is not running already, click on Start and then click on Connect.

49 When you click on create, it downloads an RDP file. Open that RDP file.

50 If you counter any errors while connecting to the VM, you can go to this link for troubleshooting options.

51 Enter your VM credentials to start the VM and click OK.

52 Once the VM starts, it looks something like this. It doesn t have any IIS server. Basically, this is just a raw VM. So to make it useful as a webserver, we need to configure it.

53 Go to the Server Manager Dashboard and click on Add Roles and Features.

54 Keep click on Next until you reach this window. Add the server role of Web Server (ISS).

55 When you tick it, it will open up new window. Click on Add Features.

56 Keep clicking on Next until you reach the final window. Then click on Install.

57 It will start the installation which will take a while.

58 Once the installation gets finished, you can go and check the C drive of the VM and you will find the inetpub folder there.

59 Now from your VM overview in Azure, copy the public IP address of the VM. Currently it doesn t have any name. Let s see if the public IP is working well or not.

60 It is working perfectly fine.

61 Now we are going to give our VM s IP address a domain name.

62 In the VM overview, click on Configure DNS name. Change the DNS name to whatever you want and click on Save. Now using this address, you can access the VM.

63 You can see that now it available in the overview as well.

64 Now it can be accessed using the given name.

65 Now the Database VM that we had created isn t allowing me to connect normally. It is allowing me to connect via a private IP. So, we need to establish a RDP allow rule for it.

66 So in our BackEnd NSG, we are going to add one more rule.

67 Change the port number to 3389 and protocol to TCP. And click on Save.

68 It will show some warning. But since this is for demo purpose, we are okay with going with it. Click on OK.

69 Go to your database s Network Interface and go to its IP configurations. Find the IP name there and click on it.

70 Enable the public IP address and give it some name and click on Save.

71 Now it is displaying the public IP.

72 Now you can easily connect to your VM. Click on Connect. Open the RDP file. Enter the credentials and it should work all fine.

73 But from this VM, you cannot connect to the internet because the outbound requests are denied.

74 You can see that Google cannot be accessed because of our define NSG.

75 But from our Web Server VM, we can access it.

76 So we can say that our NSGs are functioning properly.

77