Skip to content

Commit c0fe5d2

Browse files
PMEds28PMEds28
authored
Merge pull request #96392 from genlin/master211
Fix issues
2 parents 49cb014 + d98d71f commit c0fe5d2

File tree

2 files changed

+34
-45
lines changed

2 files changed

+34
-45
lines changed

‎articles/load-balancer/load-balancer-troubleshoot.md

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.devlang: na
1111
ms.topic: article
1212
ms.tgt_pltfrm: na
1313
ms.workload: infrastructure-services
14-
ms.date: 08/09/2018
14+
ms.date: 11/19/2019
1515
ms.author: genli
1616
---
1717

@@ -23,6 +23,8 @@ This page provides troubleshooting information for common Azure Load Balancer qu
2323
- VMs behind the Load Balancer are not responding to health probes
2424
- VMs behind the Load Balancer are not responding to the traffic on the configured port
2525

26+
When the external clients to the backend VMs go through the load balancer, the IP address of the clients will be used for the communication. Make sure the IP address of the clients are added into the NSG allow list.
27+
2628
## Symptom: VMs behind the Load Balancer are not responding to health probes
2729
For the backend servers to participate in the load balancer set, they must pass the probe check. For more information about health probes, see [Understanding Load Balancer Probes](load-balancer-custom-probe-overview.md). 
2830

@@ -92,18 +94,20 @@ If a VM does not respond to the data traffic, it may be because either the targe
9294
2. Open a command prompt and run the following command to validate there is an application listening on the data port: 
9395
netstat -an
9496
3. If the port is not listed with State “LISTENING”, configure the proper listener port
95-
4. If the port is marked as Listening, then check the target application on that port for any possible issues.
97+
4. If the port is marked as Listening, then check the target application on that port for any possible issues.
9698

9799
### Cause 2: Network security group is blocking the port on the Load Balancer backend pool VM 
98100

99101
If one or more network security groups configured on the subnet or on the VM, is blocking the source IP or port, then the VM is unable to respond.
100102

101-
* List the network security groups configured on the backend VM. For more information, see [Manage network security groups](../virtual-network/manage-network-security-group.md).
102-
* From the list of network security groups, check if:
103+
For the public load balancer, the IP address of the Internet clients will be used for communication between the clients and the load balancer backend VMs. Make sure the IP address of the clients are allowed in the backend VM's network security group.
104+
105+
1. List the network security groups configured on the backend VM. For more information, see [Manage network security groups](../virtual-network/manage-network-security-group.md)
106+
1. From the list of network security groups, check if:
103107
- the incoming or outgoing traffic on the data port has interference.
104-
- a **Deny All** network security group rule on the NIC of the VM or the subnet that has a higher priority that the default rule that allows Load Balancer probes and traffic (network security groups must allow Load Balancer IP of 168.63.129.16, that is probe port)
105-
* If any of the rules are blocking the traffic, remove and reconfigure those rules to allow the data traffic. 
106-
* Test if the VM has now started to respond to the health probes.
108+
- a **Deny All** network security group rule on the NIC of the VM or the subnet that has a higher priority that the default rule that allows Load Balancer probes and traffic (network security groups must allow Load Balancer IP of 168.63.129.16, that is probe port)
109+
1. If any of the rules are blocking the traffic, remove and reconfigure those rules to allow the data traffic. 
110+
1. Test if the VM has now started to respond to the health probes.
107111

108112
### Cause 3: Accessing the Load Balancer from the same VM and Network interface
109113

‎articles/virtual-machines/troubleshooting/troubleshoot-vm-by-use-nested-virtualization.md

Lines changed: 23 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.workload: infrastructure-services
1313
ms.tgt_pltfrm: vm-windows
1414

1515
ms.topic: article
16-
ms.date: 11/01/2018
16+
ms.date: 11/19/2019
1717
ms.author: genli
1818
---
1919
# Troubleshoot a problem Azure VM by using nested virtualization in Azure
@@ -68,70 +68,55 @@ To mount the problem VM, the Rescue VM must meet the following prerequisites:
6868

6969
## Step 2: Create the problem VM on the Rescue VM’s Hyper-V server
7070

71-
1. Record the name of the disk in the problem VM, and then delete the problem VM. Make sure that you keep all attached disks.
71+
1. [Create a snapshot disk](troubleshoot-recovery-disks-portal-windows.md#take-a-snapshot-of-the-os-disk) for the OS disk of the VM that has problem, and then attach the snapshot disk to the recuse VM.
7272

73-
2. Attach the OS disk of your problem VM as a data disk of the Rescue VM.
73+
2. Remote desktop to the Rescue VM.
7474

75-
1. After the problem VM is deleted, go to the Rescue VM.
75+
3. Open Disk Management (diskmgmt.msc). Make sure that the disk of the problem VM is set to **Offline**.
7676

77-
2. Select **Disks**, and then **Add data disk**.
77+
4. Open Hyper-V Manager: In **Server Manager**, select the **Hyper-V role**. Right-click the server, and then select the **Hyper-V Manager**.
7878

79-
3. Select the problem VM’s disk, and then select **Save**.
79+
5. In the Hyper-V Manager, right-click the Rescue VM, and then select **New** > **Virtual Machine** > **Next**.
8080

81-
3. After the disk has successfully attached, remote desktop to the Rescue VM.
81+
6. Type a name for the VM, and then select **Next**.
8282

83-
4. Open Disk Management (diskmgmt.msc). Make sure that the disk of the problem VM is set to **Offline**.
83+
7. Select **Generation 1**.
8484

85-
5. Open Hyper-V Manager: In **Server Manager**, select the **Hyper-V role**. Right-click the server, and then select the **Hyper-V Manager**.
85+
8. Set the startup memory at 1024 MB or more.
8686

87-
6. In the Hyper-V Manager, right-click the Rescue VM, and then select **New** > **Virtual Machine** > **Next**.
87+
9. If applicable select the Hyper-V Network Switch that was created. Else move to the next page.
8888

89-
7. Type a name for the VM, and then select **Next**.
90-
91-
8. Select **Generation 1**.
92-
93-
9. Set the startup memory at 1024 MB or more.
94-
95-
10. If applicable select the Hyper-V Network Switch that was created. Else move to the next page.
96-
97-
11. Select **Attach a virtual hard disk later**.
89+
10. Select **Attach a virtual hard disk later**.
9890

9991
![the image about the Attach a Virtual Hard Disk Later option](media/troubleshoot-vm-by-use-nested-virtualization/attach-disk-later.png)
10092

101-
12. Select **Finish** when the VM is created.
93+
11. Select **Finish** when the VM is created.
10294

103-
13. Right-click the VM that you created, and then select **Settings**.
95+
12. Right-click the VM that you created, and then select **Settings**.
10496

105-
14. Select **IDE Controller 0**, select **Hard Drive**, and then click **Add**.
97+
13. Select **IDE Controller 0**, select **Hard Drive**, and then click **Add**.
10698

10799
![the image about adds new hard drive](media/troubleshoot-vm-by-use-nested-virtualization/create-new-drive.png)
108100

109-
15. In **Physical Hard Disk**, select the disk of the problem VM that you attached to the Azure VM. If you do not see any disks listed, check if the disk is set to offline by using Disk management.
101+
14. In **Physical Hard Disk**, select the disk of the problem VM that you attached to the Azure VM. If you do not see any disks listed, check if the disk is set to offline by using Disk management.
110102

111103
![the image about mounts the disk](media/troubleshoot-vm-by-use-nested-virtualization/mount-disk.png)
112104

113105

114-
17. Select **Apply**, and then select **OK**.
106+
15. Select **Apply**, and then select **OK**.
115107

116-
18. Double-click on the VM, and then start it.
108+
16. Double-click on the VM, and then start it.
117109

118-
19. Now you can work on the VM as the on-premises VM. You could follow any troubleshooting steps you need.
110+
17. Now you can work on the VM as the on-premises VM. You could follow any troubleshooting steps you need.
119111

120-
## Step 3: Re-create your Azure VM in Azure
112+
## Step 3: Replace the OS disk used by the problem VM
121113

122114
1. After you get the VM back online, shut down the VM in the Hyper-V manager.
123115

124-
2. Go to the [Azure portal](https://portal.azure.com) and select the Rescue VM > Disks, copy the name of the disk. You will use the name in the next step. Detach the fixed disk from the Rescue VM.
125-
126-
3. Go to **All resources**, search for the disk name, and then select the disk.
127-
128-
![the image about searches the disk](media/troubleshoot-vm-by-use-nested-virtualization/search-disk.png)
129-
130-
4. Click **Create VM**.
131-
132-
![the image about creates vm from the disk](media/troubleshoot-vm-by-use-nested-virtualization/create-vm-from-vhd.png)
133-
134-
You can also use Azure PowerShell to create the VM from the disk. For more information, see [Create the new VM from an existing disk by using PowerShell](../windows/create-vm-specialized.md#create-the-new-vm).
116+
2. [Unmount and detach the repaired OS disk](troubleshoot-recovery-disks-portal-windows.md#unmount-and-detach-original-virtual-hard-disk
117+
).
118+
3. [Replace the OS disk used by the VM with the repaired OS disk](troubleshoot-recovery-disks-portal-windows.md#swap-the-os-disk-for-the-vm
119+
).
135120

136121
## Next steps
137122

0 commit comments

Comments
 (0)