Trending Topics

VMware on AWS - How to restore NSX DFW firewall rules to previous state

Customers who uses NSX day-in, day-out would like to have a point-in time restore functionality of DFW firewall rules. Many customer have a large footprints in VMC and make changes to DFW quite often. This feature was missing for long time and we could see its included in recent versions . Let's see how DFW configuration roll back works  NSX DFW configuration has versioning, and it is stored in the NSX Manager.  Every time when someone update DFW configuration, NSX creates one more version but keep storing the previous ones. You can rollback for previous config but reapplying it once again.  You can find the options under Networking & Security tab , > Security > Distributed Firewall . In the right side we see an Actions drop down. Choose View to get to the below screen.  Let’s go through the use case:  1. Original state- default config with no custom rules:  a. There are no saved configurations during last 30 days: In my existing test setup, with the current setting

[How to] Enable Multi-cast in VMware on AWS - NSX environment

I had a customer who were running few application VMs in their on-premises datacenter which uses multicasting as main mechanism in order to form cluster blocks. They are in process of migrating the workloads from On-premises to VMware on AWS SDDCs. The application Architect wanted to ensure that the VMC supports multicasting within AWS VMC so that they migrate the VMS ( Life & Shift) without major downtime/config changes to their applications clusters.

Let's see how things works within VMC world

In VMC setup the Multi casting feature is enabled by default. In SDDC networks, layer 2 multicast traffic is treated as broadcast traffic on the network segment where the traffic originates. It is not routed beyond that segment.  

VMC Limitation: 

Optimisation features such as IGMP snooping are not supported. 
Layer 3 multicast (such as Protocol Independent Multicast) is not supported in VMware Cloud on AWS.  

In the above example case, the customer has L2 multicast, let's check if the things work by using the omping command.

Example: Run omping command from source VM to the destination VM. ( Make sure the VMs are in the same SDDC Cluster within the SDDC and uses the segments within the VMC range from NSX) 1. omping -m -p 9106

Check if the source vm is able to receive the multi cast response from the destination. If you get the error " omping: Given address is not valid multicast address" then the things are not working as expected. 

In my case the customer had the VMware Distributed firewall in place. In that case, we had to allow the multicast address range in the DFW firewall inorder to make things work. 

Below are the rules were created in the DFW. 

Configuration change at NSX DFW: (Is need only if it does not work by default)  

  • Allow the source and destination ports explicitly. Example, if the source VM IP range is, then enable UDP communication between the networks (multicast):  
  • In DFW, create a new rule for this traffic. Source IP is and destination is The port is ANY and protocol is UDP.  
  1. Use the OMPING to confirm post the network changes  

Popular posts from this blog

What is a Sysvol?


AD LDS – Syncronizing AD LDS with Active Directory