Architecting a VMware NSX Solution : Operational Considerations : 11.3 NSX Distributed Firewall Operational Considerations : 11.3.1 VMware NSX Distributed Firewall General Operational Considerations
   
11.3.1 VMware NSX Distributed Firewall General Operational Considerations
Consider the following VMware NSX distributed firewall operational guidelines:
Verify that the distributed firewall VIBs have been successfully installed on each of the ESXi hosts in the cluster. To do this, on each of the ESXi hosts that are on the cluster, run this command:
esxcli software vib list
Verify the vShield-Stateful-Firewall service is in a running state. To do this, run this command:
/etc/init.d/vShield-Stateful-Firewall status
Verify that the message bus is communicating properly with the NSX Manager.
Note The process is automatically launched by the watchdog script and restarts the process if it terminates for an unknown reason. Run this command on each of the ESXi hosts on the cluster:
ps |grep vsfwd
Verify that port 5671 is opened for communication in the firewall configuration. You can validate that there is an active messaging bus connection by running this command on each of the ESXi hosts on the cluster:
esxcli network ip connection list |grep 5671
Verify that the firewall rules have been deployed on a host and are being applied to virtual machines as follows:
a. Log in as root to the ESXi host through SSH.
b. Run the summarize-dvfilter command.
c. Run the vsipioctl getfwrules -f <name> command.
d. Run the vsipioctl getaddrsets -f <name> command.
Note  
Verify that VMware Tools is running on the virtual machines if firewall rules do not use IP addresses. For more information, see Distributed Firewall Rules in VMware NSX for vSphere 6.0.x continues to apply with virtual machines even if VMware Tools is stopped or removed (2084048) at http://kb.vmware.com/kb/2084048.
The distributed firewall is activated as soon as the host preparation process is completed. If a virtual machine needs no distributed firewall service at all, it can be added in the exclusion list functionality (by default, NSX Manager, NSX Controllers and NSX Edge services gateways are automatically excluded from the distributed firewall function). There is a possibility that the vCenter Server access will be blocked after creating a Deny All rule in the distributed firewall.
For more information, see vCenter Server access gets blocked after creating a Deny All rule in NSX Distributed Firewall (DFW) (2079620) at http://kb.vmware.com/kb/2079620.