Skip to main content


Showing posts from January, 2020

NSX-T | Tier0 and Tier 1 Router

You would see many articles\blog on the title but I am putting one simplified definition for my readers. Folks who worked on NSX-v might have heard about the DLR and Edges, right? let's compare this DLR\Edge with Tier0\Tier1. DLR - it is used to connect the logical switch with ESG to exit and connect with outer world, if configured so. ESG - It act as the only mean for internal packet to get out and communicate with external\outer world. It means, VM's traffic goes to DLR (if DLR is default gateway for that VM) and then DLR send the packet to ESG (If there is trunk port configured between DLR and ESG and packet is destined to go out). Below is the reference picture. Picture taken from Now Let's see how Tier0 and Tier1 routers are similar or different than DLR and Edge. In Short, Tier1 act as DLR that is it does east-west routing and Tier0 act as ESG that is it does North-South routing. Below picture will clear all doubts. Taken from docs.vmware.

NSX | BUM Explained

In network, BUM (Broadcast, Unknown-Unicast and Multicast) is the method of sending and receiving layer 2 network traffic. Let's see what is that- Broadcast Traffic - it is used to transmit a message to any reachable destination in the network without the need of knowing the receiver. When Broadcast traffic receives by switch, it send it to all the switch ports except the one it is coming from. Unknown Unicast Traffic - It flooded in the network when a switch receives a frame intended for a destination which is not in its forwarding table. In this case, switch mark this frame for flooding and send it to all ports respective of that VLAN. Forwarding this type of traffic can cause unnecessary overload on network and cause poor performance. Multicast Traffic - As its name, this traffic allowed a host to communicate with subset of hosts or a group. This caused a broadcast when there is no group mechanism is present in the underlay network or physical network. in NSX, selecting m

VCD | How to find an Organization name of VM(s)

One of my ex-colleague requested to share the script so, I thought to create a post and then share it. It is an awesome place to keep an information and can be accessible from anywhere, anytime. Finding Organization name of a VM in vCD is very easy in vCD GUI but when you have demand to extract a report against each and every VM or search a VM's Org quickly then vCD GUI is not helpful and can be a time taking process. I am writing here a very simple and short script to search any VM's Org name in vCD. Here you go..... #Start here $vCD = Read-host "Enter vCD URL starting with https  " #It will connect the vCD $VM = Read-host "Enter the VM name, you want to search " Get-CIVM -Name $VM  | Select Org, OrgvDC #it will give you exact Org and OrgvDC name of any VM that you have given to it. #End here Above script is for one VM. If you need a script which can extract a csv\.xlsx file for all the VMs then feel free to let me know, I will do that for

PowerNSX | Create Logical Switches in bulk

Let's create multiple Logical switches in bulk with PowerNSX. Simply copy below script and paste in your Powershell(I prefer Powershell ISE) console. #Start here $NSXManagerIP = "IP Address" #Mention NSX Manager IP address here in quote(") $VCenterIP = "IP Address" #Mention vCenter Server IP address here in quote (") $NSXManagerUser = "admin" #NSX manager admin username goes here $NSXManagerPassword = "Password" #NSX manager admin password goes here $VCenterUser = "administrator@vsphere.local" #Write down vCenter server admin username $VCenterPassword = "VCenterPassword" #vCenter server admin password goes here #Give the path of csv file containing name of all logical switches $NSXLOGICALSWITCHFILE = import-csv C:\work\NSX_PowerNSX\Logical_Switch_Creation.csv #Connect NSX Manager with below command Connect-NsxServer -Server $NSXManagerIP -Username $NSXManagerUser -Password $NSXManagerPassword -ViUserName $