NSX-T BGP Neighbor validation

BGP is one of the most popular options for establishing routing adjacencies between NSX and existing networks. It can be configured on the Tier-0 Logical Router.

This article demonstrates various ways from where you can validate the BGP Neighbor status from T0 to its associated ToR switches into the rack.

Let's get started..

Methods from where one could validate BGP status are as below.

Using NSX-T Manager UI
From NSX-T Edge CLI

First thing first, let's discuss using NSX-T Manager UI method.

Login to NSX-T Manager UI
Click on MANAGER mode

Click on Network

Select the desired T0 Gateway > Action > Generate BGP Summary

This will show the BGP Connection status. If Connection status is showing as "ESTABLISHED". This means that T0 router has successfully peering with ToR switch.

The second method where you can validate the BGP Connection status is from NSX-T Edge nodes.

Steps involved:

Get into the logical router using command > get logical-router
Select the service router T0 vrf number 1

SR, the service router get placed on the Edge nodes which provide connectivity to the external world (North-south routing)

Insert the command > get bgp neighbor summary

The above figure shows that it's having a single neighbor (Single ToR) connected to the Edge node and reflecting the status as "ESTABLISHED" means that the edge node is having successful paring with the ToR switch and running stable.

Hope you like the summarization.

Happy learning...

Comments

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out. Now the option left is from the command line of VCSA appliance. Below steps will make it possible to change the FQDN of the VCSA from the command line. Access the VCSA from console or from Putty session. Login with root permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot the VCSA appliance. After reboot you will be successfully manage to change the FQDN of the VCSA . Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client. If you are using self-signed certificate, you can regenerate the certificate with the

Collecting Logs from NSX-T Edge nodes using CLI

This article explains how to extract the logs from NSX-T Edge nodes from CLI. Let's view the steps involved: 1) Login to NSX-T Edge node using CLI from admin credentials. 2) Use of " get support-bundle " for Log extraction. get support-bundle command will extract the complete logs from NSX-T manager/Edge nodes. nsx-manager-1> get support-bundle file support-bundle.tgz 3) Last step is to us e of " copy file support-bundle.tgz url " command. copy file will forward your collected logs from the NSX-T manager to the destination(URL) host from where you can download the logs. copy file support.bundle.tgz url scp://root@192.168.11.15/tmp Here, the URL specified is the ESXi host ( 192.168.11.15) under /tmp partition where logs will be copied and from there one can extract it for further log review. Happy Learning. :)

Removing NSX-T manager extension from vCenter

In NSX-T starting from ver 2.4 NSX-T appliance got decoupled from vCenter where now its not mandatory to run NSX-T on vCenter platform only. Now NSX-T can be managed through standalone ESXi host, KVM or through container platform. As in version 2.4 there is still an option available to connect vCenter to NSX-T using Compute Manager. Here in this blog we will learn how we can unregister and register NSX-T extenstion from vCenter in case of any sync or vCenter connectivity issue with NSX-T. Lets get started.. 1) Login to NSX-T UI Go to -> System ->Compute Manager Here, vCenter is showing in Down status where the status is showing as "Not Registered" 2) When we click on "Not Registered" option its states below error. 3) When try to click on Resolve option its states below. At this stage if the Resolve option doesn't work then its require the remove the NSX-T extenstion from vCenter. To remove the NSX-T e

Search This Blog