Update azure-vm-certification-faq.yml

iteration-4

Author: prmitiki

articles/marketplace/azure-vm-certification-faq.yml

@@ -494,7 +494,7 @@ sections:
           |NVA Deployment|Deploy a VM using the NVA with 1 NIC. Verify that the deployment is completed in 20 minutes.|If the deployment is not completed within 20 minutes, then verify the NVA image.|
           |NVA Reboot|Deploy a VM using the NVA with 1 NIC. Then, go to the VM in Azure portal, and under section **Support + troubleshooting** in the left pane, click on **Redeploy + Reapply** and redeploy the VM. After redeployment is completed, verify that the status of the VM is *Running* and the NIC port 22 is reachable using Netcat command.|If VM doesn't come up after reboot, then there may be an issue with the NVA image.<br><br>If the Netcat test fails, then it could be because the NIC failed to come up after the reboot even though the VM was running. Please wait for few minutes and try again. If after 20 mins it still fails, then there may be an issue with the NVA image|
           |NVA Redeployment|Deploy a VM using the NVA with 1 NIC. Then, redeploy the VM. Verify that the status of the VM is *Running* and the NIC port 22 is reachable using Netcat command.|If the redeploy does not complete within 15 minutes, then there may be an issue with the NVA image.<br><br>If the Netcat test fails, then it could be because the NIC failed to come up after the reboot even though the VM was running. Please wait for few minutes and try again. If after 20 mins it still fails, then there may be an issue with the NVA image|
-          |High Availability|Deploy a VM using the NVA with 1 NIC. Either No public IP should be attached to NIC or if Public IP is attached then SKU should be standard and IP allocation method should be static. In the same virtual network, setup an Azure Internal [load balancer](../virtual-machines/linux/tutorial-load-balancer.md) using configuration below.<br>Load balancer using *Standard SKU*<br> - Frontend IP using private IP allocation method as dynamic<br> - Health probes using TCP, port 22 with a retry interval of 15 seconds<br> - A load balancing rule with protocol as *all* and enable floating IP set to False.<br> - Backend pool pointing to NVA VM.<br><br>Once the setup is ready, verify that the NVA VM is reachable across the load balancer, using Netcat command.|If the NVA is unreachable across the load balancer, then verify the setup of the VM, load balancer and HA ports feature. If everything is accurate, then there may be an issue with the NVA image.|
+          |High Availability|Deploy a VM using the NVA with 1 NIC. Either No public IP should be attached to NIC or if Public IP is attached then SKU should be standard and IP allocation method should be static. In the same virtual network, setup an Azure Internal [load balancer](../virtual-machines/linux/tutorial-load-balancer.md) using configuration below.<br> - Load balancer using *Standard SKU*<br> - Frontend IP using private IP allocation method as dynamic<br> - Health probes using TCP, port 22 with a retry interval of 15 seconds<br> - A load balancing rule with protocol as *all* and enable floating IP set to False.<br> - Backend pool pointing to NVA VM.<br><br>Once the setup is ready, verify that the NVA VM is reachable across the load balancer, using Netcat command.|If the NVA is unreachable across the load balancer, then verify the setup of the VM, load balancer and HA ports feature. If everything is accurate, then there may be an issue with the NVA image.|
           |VNET Peering|Deploy a virtual machine VM1 using the NVA image, with 1 NIC in a virtual network VNET1. In another virtual network VNET2, deploy a virtual machine VM2 using any Linux image, say ubuntu, with 1 NIC, and VM settings as Dynamic IP allocation method and basic SKU. Create [VNET peering](../virtual-network/virtual-network-manage-peering.md) between VNET1 and VNET2 and **Traffic to remote virtual network** is configured as *Allow (default)*<br><br>Once the setup is ready, verify that from VM2 we can reach private IP of the NIC on the NVA VM1, using Netcat command.|If the NVA VM1 is unreachable from VM2, then verify that the VNET peering is configured correctly and try again. If it still doesn't work, then there may be an issue with the NVA image.|
           |Accelerated Networking (AN)|Deploy a VM with the NVA and 1 [AN enabled NIC](../virtual-network/create-vm-accelerated-networking-cli.md). You can enable AN on a NIC while creating the VM, or on the NIC properties after creating the VM. Verify that the VM will be up and running.|If the deployment fails, then please verify that the NVA image supports Accelerated Networking.|
           |Multi-NIC Basic|Deploy a VM using the NVA with 3 NICs with Dynamic IP allocation method and basic SKU. Get private IP and MAC address for all the NICs (refer to [view Network Interface](../virtual-network/virtual-network-network-interface.md) for instructions). Then, redeploy the VM, and verify that the private IP and MAC address for all the NICs remain the same as before redeploying.|If the private IP and MAC address for all the NICs change after redeploying, then there may be an issue with the NVA image.|