diff --git a/docs/tutorials/troubleshooting/ip-assignment.md b/docs/tutorials/troubleshooting/ip-assignment.md
index 1461ecd80..102ff3a85 100644
--- a/docs/tutorials/troubleshooting/ip-assignment.md
+++ b/docs/tutorials/troubleshooting/ip-assignment.md
@@ -1,8 +1,7 @@
 # IP Assignment
-This page describes how to troubleshoot when VM was created and powered on but was stuck in the status with no valid IP addresses.
+This page describes how to troubleshoot when VM was created but was stuck in the status with no valid IP addresses.
 
 ## Procedure
-
 ### 1. Access your namespace in the Kubernetes environment.
 
 ```console
@@ -11,7 +10,11 @@ $ kubectl config use-context <context-name>
 
 See [Get and Use the Supervisor Context](https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-with-tanzu-services-workloads/GUID-63A1C273-DC75-420B-B7FD-47CB25A50A2C.html#GUID-63A1C273-DC75-420B-B7FD-47CB25A50A2C) if you need help accessing Supervisor clusters.
 
-### 2. Check VM network settings
+
+### 2. Check if VM network settings matches underlying networking infrastructure
+If you are specifying `nsx-t` network on a `vds` networking environment (or vice versa), you will encounter below error message.
+
+**Fix**: Specify correct networking interface. Or not specify network interface during VM deployment, VM Operator will utilize default networking.
 
 ```console
 $ kubectl describe vm <vm-name> -n <namespace-name>
@@ -19,13 +22,22 @@ $ kubectl describe vm <vm-name> -n <namespace-name>
 Spec:
   Network Interfaces:
     Network Type:  nsx-t
+...
+Events:
+Type     Reason                 Age                  From                                                                                                 Message
+----     ------                 ----                 ----                                                                                                 -------
+Warning  CreateOrUpdateFailure  5s (x16 over 2m24s)  vmware-system-vmop/vmware-system-vmop-controller-manager-5ff5d769d8-6rwqc/virtualmachine-controller  no matches for kind "VirtualNetworkInterface" in version "vmware.com/v1alpha1"
 ```
 
+### 3. Check NCP VirtualNetworkInterface status if NSX-T networking
 If it's NSX-T networking, check VirtualNetworkInterface status. We expect Conditions Type to be ready and Ip Addresses return valid addresses.
-**Note** When no 
+
+**Note** if vm.spec.networkInterfaces[0].networkName is empty, then vnetif_name equals `<vm_name>-lsp`. Otherwise, vnetif_name equals `<network_name>-<vm_name>-lsp`.
+
+**Fix** Contact VI Admin to check networking health status.
+
 ```console
 $ kubectl describe virtualnetworkinterfaces <vnetif-name> -n <namespace-name>
-
 Status:
   Conditions:
     Status:      True