VMware Networking Community
sathyamoorthyvc
Contributor
Contributor
Jump to solution

NSX-T overlay network configuration tunnel status shown as 'Not available'

NSX -T overlay configuration haivng issue with Tunnel

Tunnel status shown as not available.

Dump attached

MTU set to 1600 for uplink profile and physical switch

IP pool configured and assigned to Transport zone

NSX-T  version: 2.5

ESX: 6.7 U2

Please help me to resolve issue

let me know if you need any further details

pastedImage_0.png

Reply
0 Kudos
1 Solution

Accepted Solutions
ashsevenuk80
Enthusiast
Enthusiast
Jump to solution

Hi,

I had a similar issue, but that was only when i upgraded NSX-v from 6.2 to 6.4, i had to remove and re-add to fix the service.

When it says tunnels, does it mean the vTEPs, if so, see if you can VMKPING the vTEP from one host to another ensure the service is there.

I've not had much exposure to NSX-T, all my experience is NSX-V

Regards

Arshad

View solution in original post

Reply
0 Kudos
7 Replies
mauricioamorim
VMware Employee
VMware Employee
Jump to solution

We need more info to help out. What is shown when you click on a host on the monitor tab? To check connectivity between NSX hosts you can ssh to them and vmkping between their vmk10 IPs to check connectivity and MTU.

Also note that the tunnels are only tested when workloads are attached to them. Just preparing them does not trigger tunnel status check.

Reply
0 Kudos
ashsevenuk80
Enthusiast
Enthusiast
Jump to solution

Hi,

I had a similar issue, but that was only when i upgraded NSX-v from 6.2 to 6.4, i had to remove and re-add to fix the service.

When it says tunnels, does it mean the vTEPs, if so, see if you can VMKPING the vTEP from one host to another ensure the service is there.

I've not had much exposure to NSX-T, all my experience is NSX-V

Regards

Arshad

Reply
0 Kudos
sathyamoorthyvc
Contributor
Contributor
Jump to solution

here is output vmk10

pastedImage_0.png

Reply
0 Kudos
mauricioamorim
VMware Employee
VMware Employee
Jump to solution

This doesn't help. Did you see my first answer? Does vmkping work? How is it show on monitor for each transport node? Have you attached VMs to an overlay segment on each host? This is necessary to trigger tunnel check packets.

Reply
0 Kudos
RShankar22
VMware Employee
VMware Employee
Jump to solution

Try using vmkping to test the TEP connectivity and attached some VM to LS and then check the same.

Reply
0 Kudos
sathyamoorthyvc
Contributor
Contributor
Jump to solution

Thanks. It worked.

Reply
0 Kudos
aravinda-mit
Contributor
Contributor
Jump to solution

I'm also having this problem. I am able to ping to all TEP ip addresses with the large packet size

Reply
0 Kudos