VMware Networking Community
orddie
Enthusiast
Enthusiast
Jump to solution

Edge tunnels down

Running NSX-t 3.2.0

The environment is collapsed

The TEP vlan we use is 90 and subnet is 10.0.90/24

management vlan is 80 with subnet is 172.16.80.0/24

ESXi IP's are below

Host A = 172.16.80.4 & 10.090.4

Host B = 172.16.80.5 & 10.0.90.5

Host C = 172.16.80.6 & 10.0.90.6

when I SSH into the edge node and go into VRF 0, I can ping all three 10.0.90.0/24 IP's but the tunnels are showing as down.

 

where should I be looking to resolve this?

 

Reply
0 Kudos
2 Solutions

Accepted Solutions
jeffersonc47
Enthusiast
Enthusiast
Jump to solution

Are you using VLAN 90 for both host and edge TEPs? If so, move the edges to a separate VLAN. It's supposed to work in 3.2 (and did in 3.1), but there seems to be a bug in 3.2.0 that causes tunnels to not come up when hosts and edges are in the same VLAN.

View solution in original post

Reply
0 Kudos
CyberNils
Hot Shot
Hot Shot
Jump to solution

Reply
0 Kudos
10 Replies
jeffersonc47
Enthusiast
Enthusiast
Jump to solution

Are you using VLAN 90 for both host and edge TEPs? If so, move the edges to a separate VLAN. It's supposed to work in 3.2 (and did in 3.1), but there seems to be a bug in 3.2.0 that causes tunnels to not come up when hosts and edges are in the same VLAN.

Reply
0 Kudos
orddie
Enthusiast
Enthusiast
Jump to solution

Does that mean I need to route them?

Example: hosts, 10.0.90.0/24 and edges 10.0.91.0/24 or keep the same subnet and only change the VLAN ID’s between devices 

Reply
0 Kudos
jeffersonc47
Enthusiast
Enthusiast
Jump to solution

Correct - You will need a large MTU path between the two subnets.

Reply
0 Kudos
orddie
Enthusiast
Enthusiast
Jump to solution

Please confirm 

 

- do I need to route them?

- keep same subnet but split the devices via Vlan 

- both route and split devices 

Reply
0 Kudos
shank89
Expert
Expert
Jump to solution

The simplest design is to have separate VLANs with their own subnet that can route to each other.

 

Ensure you have a minimum of 1600 MTU.

You may find this video useful https://youtu.be/SFa7RUya9nQ

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
orddie
Enthusiast
Enthusiast
Jump to solution

When I separated the networks, the tunnels came up and all is working as expected now.

bummer that collapsed design does not work.  Thinking about getting 30.1 and starting over.

Reply
0 Kudos
shank89
Expert
Expert
Jump to solution

It actually does work in the latest version and have tested it myself, you need to make sure you use VLAN backed segments to wire the edge vm, but this setup isn't the most streamlined and least complicated way. 

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
CyberNils
Hot Shot
Hot Shot
Jump to solution

Check this KB for supported options:

https://kb.vmware.com/s/article/83743

 



Nils Kristiansen
https://cybernils.net/
Reply
0 Kudos
orddie
Enthusiast
Enthusiast
Jump to solution

this is most likely my core issue when trying to use a collapsed design.

Reply
0 Kudos
amitsingh2021
Contributor
Contributor
Jump to solution

Might be there are no VMs associated on NSX segments on the ESX hosts, so that's why tunnel are showing down. Do you have VMs connected on NSX segments?

amitsingh
Reply
0 Kudos