Currently, I’m working on a migration project where we are migrating VMs from a non-NSX legacy environment to a brand new NSX-enabled infrastructure. During the migration, I needed to apply NSX Security Tags in the destination environment. The tags needed to be applied based on the environment type e.g. Production and Development. And I thought; Yeah! PowerNSX is going to make my life more easier now.
Last week I ran into an issue while I was configuring a Load Balanced Platform Service Controller setup. My initial configuration was as follows: VCSA01 is pointed to the PSC01, and the VCSA02 is pointed to the PSC02 (within the same SSO domain). My goal was to load balance my existing Platform Service Controllers via a VIP on a NSX Load Balancer for the two vCenters and one NSX Manager (Connected to VCSA01).
In my previous blog post I wrote about how to automate the Enable MAC learning function on a VMware NSX Logical Switch via Powershell/PowerNSX. In this post I referred to a script which I used to export the configuration of the portgroup/vlans that where currently existing in the environment. I’m writing this blogpost, to share the script because someone might have a use case for it (more…)
I was working on a project at a customer where we needed to create Logical Switches, DFW rules and sections based upon all the current portgroups of all the environments. Because we are talking about +/- 400 logical switches which need to be created, this is not a job that you want to do via the vSphere Web Client. Therefore I created a script which exported all the current portgoup names and vlan configurations to CSV file. This CSV file is used to import all the stuff.