Skip to main content

NSX-T BGP Neighbor validation


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.


  1. Using NSX-T Manager UI
  2. 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:

  • Login to NSX-T Edge node using SSH
  • 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

Popular posts from this blog

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

Unable to poweron the VM. (Failed to lock the file)

I have encountered may issues like where after some upgrade or migration we were unable to power on the VM. Figure 1 An error was received from the ESX host while powering on VM HSSVSQL01. Failed to start the virtual machine. Cannot open the disk '/vmfs/volumes/578d835c-18b2c97a-9b0d-0025b5f13920/SAMPLE1_cloud/000000.vmdk' or one of the snapshot disks it depends on. Failed to lock the file In above Figure:1, where while powering on the VM, its prompt for an error. Well, there are several reason for where the VM unable to poweron and you can find many article on this. Here in this article we will discuss to resolve this issue. Please use below step to resolve the disk lock issue  C hecked that VM is running on snapshot if its getting error " VM Consolidation required". Checked the snapshot manager if its showing any snapshot. If yes, try to delete the  snapshot. Verified the same from Esxi cl

VM Creation Date & Time from Powercli

Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment. Somewhere during security auditing we require to provide several information to security team to get successful audit. One of them is the compliance of Virtual machine auditing of creation date and time. Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi. To get the details we will use VMware Powercli to extract the details. By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date. Below is the function which needed to be copy and paste into the Powercli. ======================================================================= function  Get-VMCreationTime  {     $vms  =  get-vm     $vmevts  = @()     $vmevt  =  new-object  PSObject     for