{
    "id": "f74fc00b-cd74-4367-b955-c8ce4b1466b8",
    "name": "Monitor Networks",
    "slug": "monitor-networks",
    "status": "published",
    "lab_type": "azure",
    "is_sample": false,
    "duration_in_seconds": 1200,
    "metadata": {},
    "session": null,
    "company": "a491bc32-c056-4946-9169-cc053387bada",
    "created": "2020-08-11T12:14:09.939162Z",
    "modified": "2023-10-03T18:57:52.969683Z",
    "is_beta": false,
    "lab_objectives": [],
    "main_learning_area": null,
    "learning_areas": [],
    "categories": [],
    "tags": [],
    "difficulty": null,
    "is_web_access": false,
    "is_lab_experience": false,
    "is_featured": false,
    "cve": null,
    "severity": null,
    "year": null,
    "classification": null,
    "is_trackable": false,
    "cpe_credits": null,
    "is_skill_check": false,
    "external_url": "https://portal.azure.com/",
    "solution_video": "44b31e14-6eea-4747-9064-7f792fa3b323",
    "explanation_video": null,
    "description": "# Task: Monitor Networks\r\n\r\n## Video: Monitor Azure Virtual Networks\r\n\r\n**Estimated time:** 60 minutes\r\n\r\n## Goal\r\n\r\nThe goal of this task is to configure and use Azure network monitoring.  This includes monitoring network activity in multiple networks. This task uses virtual machines and servers configured as follows:\r\n\r\n![Network topology](https://inedemoassets.blob.core.windows.net/taskfiles/azure_admin/VOD3510T060-network.png)\r\n\r\n## Pre-requisites\r\n\r\n1. A non-production Azure subscription\r\n2. Two virtual networks with established peering relationships\r\n3. Two virtual machines\r\n\r\n## Requirements\r\n\r\n1. Requirement 1: Provision a log analytics workspace\r\n1. Requirement 2: Register servers\r\n1. Requirement 3: Add the network monitoring solution\r\n1. Requirement 4: Monitor the network\r\n\r\n## Pre-requisite setup\r\n\r\nThis task requires several Azure resources.  To deploy the resources required for this task, run the following from a bash cloud shell:\r\n\r\n```bash\r\ncurl https://inedemoassets.blob.core.windows.net/taskfiles/azure_admin/deploy-3510T060-pre.sh | sh\r\n```\r\n\r\nThis script provisions the following resources:\r\n|Resource|Name|\r\n|---:|---|\r\n|Virtual Networks||\r\n||**hub-vnet**|\r\n||**internal-vnet**|\r\n|Virtual machines||\r\n||**hub-vm**|\r\n||**internal-vm**|\r\n|Bastion hosts||\r\n||**hub-bastion**|\r\n||**internal-bastion**|\r\n\r\n*Support resources are not shown.*\r\n\r\n***Important: Record the password output.  You will need it for requirement 2.***\r\n\r\n## Requirement 1: Provision a log analytics workspace\r\n\r\nFor the first requirement you will provision a log analytics workspace with the following settings:\r\n\r\n|Setting|Value|\r\n|---:|---|\r\n|Name|**&lt;a unique name&gt;**|\r\n|Resource group|**task-netmon-rg**|\r\n|Region|**East US**|\r\n\r\n## Requirement 2: Register servers\r\n\r\nNext you will configure two virtual machines as network monitors. You will register the **hub-vm** and **internal-vm** virtual machines with your workspace.  You will also configure the firewall rules for each virtual machine to allow TCP monitoring. To complete this requirement:\r\n\r\n- Register both virtual machines with the workspace using the Azure portal.\r\n- open TCP ports on the **hub-vm** virtual machine:\r\n  - Establish an RDP connection to the **hub-vm** using the bastion host.\r\n  - Disable enhanced IE security through the **local server** view of the **Server Manager** applet.\r\n  - Download a PowerShell script from [https://gallery.technet.microsoft.com/OMS-Network-Performance-7ec93b2f](https://gallery.technet.microsoft.com/OMS-Network-Performance-7ec93b2f).\r\n  - Execute the PowerShell script to set the firewall rules necessary for network monitor. Be sure to open PowerShell or PowerShell ISE in administrator mode.\r\n  - Exit the connection.\r\n- Repeat for the **internal-vm** virtual machine.\r\n\r\n## Requirement 3: Add the network monitoring solution\r\n\r\nFor this requirement you will add the network monitoring solution to your workspace. You will then configure it.  To add and configure the solution:\r\n\r\n- Add network performance monitoring for your workspace using the monitor blade in the Azure portal.\r\n- Configure the network performance monitoring solution as follows:\r\n  - Create a network named **production**.\r\n  - Add the two subnets (**10.0.0.0/24** and **10.1.0.0/24**) to the **production** network.\r\n  - Add a rule with the following settings:\r\n    |Setting|Value|\r\n    |---:|---|\r\n    |Name|**Production**|\r\n    |Network|**production**|\r\n    |Subnet|**All subnets**|\r\n    |Protocol|**TCP**|\r\n\r\n*Note: It may take several minutes for the changes that you have made to take effect.  Return to the log analytics summary page and refresh the browser page until the network monitoring solution **View summary** link shows network health.*\r\n\r\n## Requirement 4: Monitor the network\r\n\r\nFinally, you will explore monitoring through the log analytics network monitoring solution and through the Azure monitor blade. To complete this requirement:\r\n\r\n- Click the **View summary** link on the network monitor solution in the log analytics workspace summary.\r\n- Click the network monitoring summary.\r\n- Drill down into the subnet and network performance tiles. Observe which links have errors.\r\n- Navigate to the **Network watcher** view of the monitor blade.\r\n- Add a connection monitor with the following settings:\r\n  |Setting|Value|\r\n  |---:|---|\r\n  |Name|**internal2hub**|\r\n  |Source virtual machine|**internal-vm**|\r\n  |Destination virtual machine|**hub-vm**|\r\n  |Port|**3389**|\r\n- Once the connection is added, confirm that it is reachable.\r\n\r\n## Cleanup\r\n\r\nOnce you have completed this task, delete the **task-netmon-rg** resource group.  Also delete the **internal2hub** connection from network watcher.\r\n",
    "description_html": "<h1>Task: Monitor Networks</h1>\n<h2>Video: Monitor Azure Virtual Networks</h2>\n<p><strong>Estimated time:</strong> 60 minutes</p>\n<h2>Goal</h2>\n<p>The goal of this task is to configure and use Azure network monitoring.  This includes monitoring network activity in multiple networks. This task uses virtual machines and servers configured as follows:</p>\n<p><img alt=\"Network topology\" src=\"https://inedemoassets.blob.core.windows.net/taskfiles/azure_admin/VOD3510T060-network.png\" /></p>\n<h2>Pre-requisites</h2>\n<ol>\n<li>A non-production Azure subscription</li>\n<li>Two virtual networks with established peering relationships</li>\n<li>Two virtual machines</li>\n</ol>\n<h2>Requirements</h2>\n<ol>\n<li>Requirement 1: Provision a log analytics workspace</li>\n<li>Requirement 2: Register servers</li>\n<li>Requirement 3: Add the network monitoring solution</li>\n<li>Requirement 4: Monitor the network</li>\n</ol>\n<h2>Pre-requisite setup</h2>\n<p>This task requires several Azure resources.  To deploy the resources required for this task, run the following from a bash cloud shell:</p>\n<pre class=\"codehilite\"><code class=\"language-bash\">curl https://inedemoassets.blob.core.windows.net/taskfiles/azure_admin/deploy-3510T060-pre.sh | sh</code></pre>\n\n<p>This script provisions the following resources:\n|Resource|Name|\n|---:|---|\n|Virtual Networks||\n||<strong>hub-vnet</strong>|\n||<strong>internal-vnet</strong>|\n|Virtual machines||\n||<strong>hub-vm</strong>|\n||<strong>internal-vm</strong>|\n|Bastion hosts||\n||<strong>hub-bastion</strong>|\n||<strong>internal-bastion</strong>|</p>\n<p><em>Support resources are not shown.</em></p>\n<p><strong><em>Important: Record the password output.  You will need it for requirement 2.</em></strong></p>\n<h2>Requirement 1: Provision a log analytics workspace</h2>\n<p>For the first requirement you will provision a log analytics workspace with the following settings:</p>\n<table>\n<thead>\n<tr>\n<th align=\"right\">Setting</th>\n<th>Value</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td align=\"right\">Name</td>\n<td><strong>&lt;a unique name&gt;</strong></td>\n</tr>\n<tr>\n<td align=\"right\">Resource group</td>\n<td><strong>task-netmon-rg</strong></td>\n</tr>\n<tr>\n<td align=\"right\">Region</td>\n<td><strong>East US</strong></td>\n</tr>\n</tbody>\n</table>\n<h2>Requirement 2: Register servers</h2>\n<p>Next you will configure two virtual machines as network monitors. You will register the <strong>hub-vm</strong> and <strong>internal-vm</strong> virtual machines with your workspace.  You will also configure the firewall rules for each virtual machine to allow TCP monitoring. To complete this requirement:</p>\n<ul>\n<li>Register both virtual machines with the workspace using the Azure portal.</li>\n<li>open TCP ports on the <strong>hub-vm</strong> virtual machine:</li>\n<li>Establish an RDP connection to the <strong>hub-vm</strong> using the bastion host.</li>\n<li>Disable enhanced IE security through the <strong>local server</strong> view of the <strong>Server Manager</strong> applet.</li>\n<li>Download a PowerShell script from <a href=\"https://gallery.technet.microsoft.com/OMS-Network-Performance-7ec93b2f\">https://gallery.technet.microsoft.com/OMS-Network-Performance-7ec93b2f</a>.</li>\n<li>Execute the PowerShell script to set the firewall rules necessary for network monitor. Be sure to open PowerShell or PowerShell ISE in administrator mode.</li>\n<li>Exit the connection.</li>\n<li>Repeat for the <strong>internal-vm</strong> virtual machine.</li>\n</ul>\n<h2>Requirement 3: Add the network monitoring solution</h2>\n<p>For this requirement you will add the network monitoring solution to your workspace. You will then configure it.  To add and configure the solution:</p>\n<ul>\n<li>Add network performance monitoring for your workspace using the monitor blade in the Azure portal.</li>\n<li>Configure the network performance monitoring solution as follows:</li>\n<li>Create a network named <strong>production</strong>.</li>\n<li>Add the two subnets (<strong>10.0.0.0/24</strong> and <strong>10.1.0.0/24</strong>) to the <strong>production</strong> network.</li>\n<li>Add a rule with the following settings:\n    |Setting|Value|\n    |---:|---|\n    |Name|<strong>Production</strong>|\n    |Network|<strong>production</strong>|\n    |Subnet|<strong>All subnets</strong>|\n    |Protocol|<strong>TCP</strong>|</li>\n</ul>\n<p><em>Note: It may take several minutes for the changes that you have made to take effect.  Return to the log analytics summary page and refresh the browser page until the network monitoring solution *</em>View summary** link shows network health.*</p>\n<h2>Requirement 4: Monitor the network</h2>\n<p>Finally, you will explore monitoring through the log analytics network monitoring solution and through the Azure monitor blade. To complete this requirement:</p>\n<ul>\n<li>Click the <strong>View summary</strong> link on the network monitor solution in the log analytics workspace summary.</li>\n<li>Click the network monitoring summary.</li>\n<li>Drill down into the subnet and network performance tiles. Observe which links have errors.</li>\n<li>Navigate to the <strong>Network watcher</strong> view of the monitor blade.</li>\n<li>Add a connection monitor with the following settings:\n  |Setting|Value|\n  |---:|---|\n  |Name|<strong>internal2hub</strong>|\n  |Source virtual machine|<strong>internal-vm</strong>|\n  |Destination virtual machine|<strong>hub-vm</strong>|\n  |Port|<strong>3389</strong>|</li>\n<li>Once the connection is added, confirm that it is reachable.</li>\n</ul>\n<h2>Cleanup</h2>\n<p>Once you have completed this task, delete the <strong>task-netmon-rg</strong> resource group.  Also delete the <strong>internal2hub</strong> connection from network watcher.</p>",
    "tasks": "",
    "tasks_html": "",
    "published_date": "2020-05-23T04:35:06Z",
    "solutions": "",
    "solutions_html": "",
    "flags": [],
    "min_points_to_pass": null,
    "access_type": "default",
    "user_status": "unstarted",
    "user_lab_status": null,
    "user_status_modified": null,
    "user_flags": []
}