VMware Networking Community
suhail39
Enthusiast
Enthusiast

Tunnel Status down on Tranport Node in NSX-T

The Tier0 to Tier1 Connectivity is failed, but the Tier0 has all the routes for Tier1.

The host Transport Node has the tunnel status down, is this the main cause for the Tier0 to Tier1 connectivity failure.

What may be the resonable reasons for the Tunnel status as down, after all the configuration.

FYI, Screenshot

pastedImage_1.png

Please do mention some solutions or recommendations to reoslve this issue  

0 Kudos
2 Replies
sivarajmadhu
Contributor
Contributor

i am also having same issues, please some can help me on this.

0 Kudos
VMware_Nitin999
Contributor
Contributor

Tunnel Down

You can view the tunnel status and the reason for tunnel failure in both the vSphere Web Client and in the console of the L2VPN appliance.

Problem tunnel between the client and the server is down.

Cause On the server side, the following generic failure message is displayed when the tunnel is down: Not available.

Please check client and server system logs/cli for details.

On the L2VPN client side, the SSL connect has failed message is displayed when the tunnel is down due to any of the following reasons:

1. Server address is incorrect.

2. L2VPN Edge server is unreachable or not responding.

3. Cipher or port number is misconfigured on the L2VPN server.

However, if the user ID or password is incorrect, or if the site is disabled from the server, the following message is displayed on the client: Authentication failed, try to log in again.

Solution 1: Download the Tech Support Logs for the NSX Edge, and check for any failure or error message in the log files that are related to L2VPN. Typically, all the logs for the L2VPN server have the following format: {Date}NSX-edge-1-0l2vpn:[local0:info]INFO:{MESSAGE} 2.

If the tunnel is down due to a failure in the SSL connection between the client and server, resolve the problem using the following methods:

1. Check whether the server address, server port, and encryption algorithm are configured correctly.

2. Make sure that the standalone L2VPN Edge client has internet connectivity on the uplink port, and the L2VPN Edge server is reachable.

3. Make sure that port 443 is not blocked by the firewall.

4. If the tunnel is down due to an authentication failure, correct the user name or password, and log in again.

0 Kudos