I was trying to play with NSX 3.1. It was working fine till, I connect my T1 router to T0. all the routing from physical router can see from my T0. later, I started connecting my T1 to T0. the moments i connect my T1 to T0, BGP gets down. not sure what causing this issue? version of the components given below, is it bug or something no idea.
Need help please. attached the image for your ref.
vCenter Server: 7.0.1
What IP addresses are you using to peer your T0 with the physical network?
I'm with Chris on this one, we will need a little more information and what testing you have already done. By looking at the diagram, you are peering from the 172.16.6.25 IP to your physical router? If so, does that mean you have a single uplink from the T0?
When you say BGP goes down, are you seeing the neighbor go from established to IDLE, ie the peering is being torn down?
I just narrowed down the issue. The moment I connect VM to my logical segment, i noticed, BGP peering gets down. I m getting this below error from the EDGE.
Edge Tunnels Down
Dec 7, 2020 4:16:41 PM
Description: 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.
If I disable or uncheck the NIC from the VM settings. all works and BGP Peering gets established again.
thanks for replying. 🙂
Can you run the commands:
- get tunnel-ports
- get tunnel-port stats
- *during the VM interface add" tail -f /var/log/syslog
It seems not only is you BGP failing, but the tunnels are unable to establish between the Edge Nodes and the Hosts Nodes.
In addition to this can you try
- vmkping ++netstack=vxlan <dstTEPIP> -s 8972 -d from the host to the edge teps and then try between the edge teps and then again between the host teps (if you have more than one host)?
Hi @shank89 @chrisgnoon ,
Problem solved with 3.0. It was a bug i think for 3 u1.
thanks for your support.