Showing posts from April, 2018

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

Update Manager 6.5 issue ""interface com.vmware.vim.binding.integrity.VcIntegrity is not visible from class loader""

This post is related to the issue what we faced today when we replaced the SSL certificates in our setup.  When I launched the web-client and access the update manager tab,  I get the message  "interface com.vmware.vim.binding.integrity.VcIntegrity is not visible from class loader" I started off by restarting the VMWare vSphere Update Manager Service for the affected vCSA: 1. Log into vCenter using the administrator@vsphere.local account. 2. Home - System Configuration - Services - Restart This did not resolve my issue...  And we tried restarting all the services by  SSH/Console into the affected server and run the following commands: service-control --stop --all service-control --start --all Still no luck.  Make sure the certs are applied and it gets reflected in the config file. ( verify if the thumbprint matches)  root@homelab71 [ /usr/lib/vmware-updatemgr/bin ]# pwd /usr/lib/vmware-updatemgr/bin root@ho