VMware Networking Community
suhail39
Enthusiast
Enthusiast
Jump to solution

NSX-T transport node on Host and Edge - Tunnel status down

Hello Everyone,

I have been facing issues with the transport node on Host and Edge, after successfully adding the nodes, the Tunnel status is down, due to which the transport node throws error status in Dashboard of NSX-T. FYI Screenshot

pastedImage_2.png

Is there anyone who has come across the similar issue? and resolved it.

Regards,

Suhail39

1 Solution

Accepted Solutions
lhoffer
VMware Employee
VMware Employee
Jump to solution

Do you have any active VMs connected to logical switches on that node yet?  The Geneve tunnels used by NSX-T don't get established until there's a VM connected to a logical switch on the given node so while it can be kind of misleading, it'll show the tunnel status as "down" until it actually has a reason to form the tunnel.

View solution in original post

10 Replies
lhoffer
VMware Employee
VMware Employee
Jump to solution

Do you have any active VMs connected to logical switches on that node yet?  The Geneve tunnels used by NSX-T don't get established until there's a VM connected to a logical switch on the given node so while it can be kind of misleading, it'll show the tunnel status as "down" until it actually has a reason to form the tunnel.

skydongdong
Contributor
Contributor
Jump to solution

Edge transport node down is also because no VMs? Or just will cause host TN down if no VMs?

Reply
0 Kudos
lhoffer
VMware Employee
VMware Employee
Jump to solution

Edge node TNs will show the tunnel as "up" once you've got a router deployed to them.  Otherwise, they show the status as "unknown".

Reply
0 Kudos
skydongdong
Contributor
Contributor
Jump to solution

Thanks. Do you have any ideas why the bond status  in TN is unknown or down?

Reply
0 Kudos
suhail39
Enthusiast
Enthusiast
Jump to solution

lhoffer

Hi,

I had a doubt, since its the first time, i am setting up NSX-T, i am not able to establish the connection between Tier0 and Tier1 even after the Linked Ports are set, is it because of the Transport Node, since there is no Transport Node attached to Tier1 Router.

pastedImage_2.png

please do share, if you have any documents to troubleshoot this scenarios.

Reply
0 Kudos
lhoffer
VMware Employee
VMware Employee
Jump to solution

This appears to show that it is connected so when you say you can't establish the connection, are you referring to end to end reachability of networks behind the Tier 1 router?  If so, be aware that by default the T1 router doesn't advertise any of the connected networks upstream so the first thing to check would be to ensure that you've enabled route advertisement under the "routing" tab of the Tier 1 router so that it looks like this:

pastedImage_0.jpg

Reply
0 Kudos
suhail39
Enthusiast
Enthusiast
Jump to solution

Yes, i have enabled all this, still i m not able to reach tier1 from tier0, I have also added a couple of static routes on Tier0 since Tier0 uplink is on different subnet, the Intra Tier0 to Tier1 is on a different subnet, which is the Computer generated switch with 100 series and Tier1 is on a different subnet.

pastedImage_0.png

Even after applying so many Static routes to achieve Connectivity, it fails to ping the Tier0 Intra subnet and Tier1 subnet.

On the Edge Console, when you access the Tier0 and get routes, the Output is only via 192.168.x.x

pastedImage_1.png

How do i confgiure this, so that i will be able to communicate

Please give your inputs

Reply
0 Kudos
mdshyfurr
VMware Employee
VMware Employee
Jump to solution

Hi Boby,

I am experiencing something different. The moment i connect VM to logical segment my tunnel get down. BGP gets discuonncted to physical router. Error has been given below

 

escription: The overall tunnel status of Edge node f5384406-bfe3-42c0-b967-8495ce6a0212 is down.
Recommended Action: Invoke the NSX CLI command `get tunnel-ports` to get all tunnel ports, then check each tunnel's stats by invoking NSX CLI command `get tunnel-port stats` to check if there are any drops. Also check /var/log/syslog if there are tunnel related errors.

Reply
0 Kudos
Marcin4
Enthusiast
Enthusiast
Jump to solution

Which version NSX-T and vCenter are you using ? 

Could you share with us your topology ? 

 

Best Regards
Marcin Gwóźdź
VCP-NV 6, VCIX-DCV 7, VCIX-DTM 7.
linkedin.com/in/marcin-gwóźdź-80b84b122
Reply
0 Kudos
shank89
Expert
Expert
Jump to solution

So I'll ask a few questions to hopefully get all the answers in one spot to make this a little easier to troubleshoot.

  • How many hosts are there?
  • How many edges?
  • Are the edges sitting on hosts that are prepared for NSX-T
  • Are you able to vmkping ++netstack=vxlan <enter edge TEP ip here) -s 8972 -d, run this between host teps and to each edge VM
  • Are the hosts on a different transport vlan to the edges?
  • What version of NSX-T are you using?
  • Are you using vDS/n-VDS?

This link may assist in troubleshooting and working out any TEP addressing issues https://www.lab2prod.com.au/2020/11/nsx-t-inter-tep.html.

I would also remove all the additional static routes you added as they generally aren't need for an out of the box deployment.
The more clearer and detailed you can be with these answers, the easier it will be to diagnose and resolve your issue.

Cheers

Shashank Mohan

VCIX-NV 2022 | VCP-DCV2019 | CCNP Specialist

https://lab2prod.com.au
LinkedIn https://www.linkedin.com/in/shankmohan/
Twitter @ShankMohan
Author of NSX-T Logical Routing: https://link.springer.com/book/10.1007/978-1-4842-7458-3
Reply
0 Kudos