You can then use the following commands # show control-cluster logical-switches vni 5001 To troubleshoot controller networking you can also use # traceroute įirst make sure to connect on the master controller of the virtual network you want to troubleshoot. NTP is mandatory, so make sure it’s correctly configured # show network ntp-servers Interface Address/Netmask MTU Admin-Status Link-Status Get Controller Statistics # show control-cluster core statsĬontroller networking # show network interface List current connections to your controller. # show control-cluster rolesĪpi_provider Not configured Yes 09/18 08:45:17 6 List the implemented role on your controller, the Not Configured for api_provider is normal, it’s the NSX-Manager who’s published the NSX-v API. Majority status: Connected to cluster majority 09/18 08:45:16 To investigate controller issues, SSH to one of your controller VM to use the CLI (login: admin, password: the one set at deployment time). You can get the IP Address of your Controller by clicking on the VM named NSX_Controller_ in the vSphere Web Client. Note: If you don’t know the name of your VXLAN vmkernel you can easily check it, by looking at the configuration of your VDS.īut you’ve also seen that information in the Logical Network Preparation UI above.
#X PLANE WORLD TRAFFIC UNKNOWN EDGE HOW TO#
If both succeed, but you still don’t have connectivity on the virtual wire, I’ll show you, in the Compute node controller connectivity section, how to investigate that using net-vdl2 -l. Before going any further you have to make sure that these pings works. If both fails it’s a VLAN ID or Uplink misconfiguration.
If this one succeed, it means your MTU isn’t correctly set to at least 1600 on your transport network. If the ping fails, launch another one without the don’t fragment/size argument set ping ++netstack=vxlan -I vmk3 1.2.3.4 s 1572 set packet size to 1572 to check if MTU is correctly setup up to 1600 ++netstack=vxlan instruct the ESXi host to use the VXLAN TCP/IP stack. To check that, SSH to a Compute node and type : ping ++netstack=vxlan -d -s 1572 -I vmk3 1.2.3.4 If VXLAN Connectivity isn’t operational, I mean if a VM on a VXLAN cannot ping another one on the same logical switch the most common reason is a misconfiguration on the transport network. Now click on Network & Security > Installation > Logical Network Preparation and open up each clusterĮach compute node should have a Virtual Tunnel Endpoint (VTEP) vmkernel interface (vmk3 here) with an IP Address assigned to it.ĭon’t worry if you get any errors, this article is meant to help you troubleshoot the root cause.
Next click on Network & Security > Installation > Host Preparation and open up each cluster. You should see a green status for your three controllers.
NSX vSphere Web UIīefore jumping into the marvelous world of command lines, as a starter, we’ll check the state of the environment from the vSphere Web Client UI standpoint.Īuthenticate to your web client, and click on Network & Security > Installation > Management. But wait don’t forget the tab completion on our NSX CLI, it’s pretty nice ) But you have to know where to start, hope this helps. As a cheatsheet, I’m gathering all the CLI to troubleshoot it over here, for easy cut & past, some commands are damn long. NSX vSphere (NSX-v) is a different beast, mostly because it leverage VMware Distributed Switch (VDS) instead of Open vSwitch. Last week we reviewed all the tips & tricks to troubleshoot Open vSwitch and OpenStack Neutron.
0 kommentar(er)
