Skip to content

Commit e13626a

Browse files
Acrolinx
1 parent bf66c95 commit e13626a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/site-recovery/vmware-azure-troubleshoot-replication.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ When you try to select the source machine to enable replication by using Site Re
4141
* **vCenter not connected**: Check if vCenter is in a connected state. To verify, go to Recovery Services vault > Site Recovery Infrastructure > Configuration Servers > Click on respective configuration server > a blade opens on your right with details of associated servers. Check if vCenter is connected. If it's in a "Not Connected" state, resolve the issue, and then [refresh the configuration server](vmware-azure-manage-configuration-server.md#refresh-configuration-server) on the portal. After this, virtual machine is not listed on the portal.
4242
* **ESXi powered off**: If the ESXi host under which the virtual machine resides is in a powered-off state, then the virtual machine is not listed or is not selectable on the Azure portal. Power on the ESXi host, and [refresh the configuration server](vmware-azure-manage-configuration-server.md#refresh-configuration-server) on the portal. After this, virtual machine is listed on the portal.
4343
* **Pending reboot**: If there is a pending reboot on the virtual machine, then you won't be able to select the machine on the Azure portal. Ensure to complete the pending reboot activities and [refresh the configuration server](vmware-azure-manage-configuration-server.md#refresh-configuration-server). After this, virtual machine is listed on the portal.
44-
* **IP not found or Machine does not have an IP address**: If the virtual machine doesn't have a valid IP address associated with it, then you is not able to select the machine on the Azure portal. Ensure to assign a valid IP address to the virtual machine, and [refresh the configuration server](vmware-azure-manage-configuration-server.md#refresh-configuration-server). It could also be caused if the machine does not have a valid IP address associated with one of its NICs. Either assign a valid IP address to all NICs or remove the NIC that's missing the IP. After this, the virtual machine is listed on the portal.
44+
* **IP not found or Machine does not have an IP address**: If the virtual machine doesn't have a valid IP address associated with it, then you are not able to select the machine on the Azure portal. Ensure to assign a valid IP address to the virtual machine, and [refresh the configuration server](vmware-azure-manage-configuration-server.md#refresh-configuration-server). It could also be caused if the machine does not have a valid IP address associated with one of its NICs. Either assign a valid IP address to all NICs or remove the NIC that's missing the IP. After this, the virtual machine is listed on the portal.
4545

4646
### Troubleshoot protected virtual machines greyed out in the portal
4747

@@ -215,7 +215,7 @@ This error occurs when trying to enable replication and the application folders
215215

216216

217217
- *C\ProgramData\Microsoft Azure Site Recovery\private*
218-
- The installation directory. For example, if the installation directory is F drive, then provide the correct permissions to -
218+
- The installation directory. For example, if the installation directory is F drive, then provide the correct permissions to:
219219
- *F:\Program Files (x86)\Microsoft Azure Site Recovery\home\svsystems*
220220
- The *\pushinstallsvc* folder in the installation directory. For example, if the installation directory is F drive, provide the correct permissions to -
221221
- *F:\Program Files (x86)\Microsoft Azure Site Recovery\home\svsystems\pushinstallsvc*

0 commit comments

Comments
 (0)