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


                       IBM LUN setup is done using IBM Storage Manager Client or command line tools. Since most of our storage is mirrored the identical LUN has to be created on the both arrays. Storage Manager Client scripting allows easy duplication of identical setup on each array.

Code snippets

Creating host on IBM DS4000 storage system

Create a host entry on with proper host type (LINUX/WINDOWS)(more or less OS type).
create host userLabel="server" hostType=number;
create hostPort userLabel="server-p0" host="server" identifier="210000e0xxxxxxxx" interfaceType=interface


create host userLabel="DBZones3" hostType=8;
create hostPort userLabel="DBZones3-p0" host="DBZones3" identifier="210000e08b9a2466" interfaceType=FC;
create hostPort userLabel="DBZones3-p1" host="DBZones3" identifier="210100e08bba2466" interfaceType=FC;

Creating logical drive (LUN) on IBM DS4000 storage system

create logicaldrive array="Array Name" userlabel="LUN name" capacity=X GB owner=(a|b) usagehint=filesystem;


create logicaldrive array="SATA-Array3" userlabel="DBZones3_1" capacity=150 GB owner=a usagehint=filesystem;
create logicaldrive array="SATA-Array2" userlabel="DBZones3_2" capacity=150 GB owner=b usagehint=filesystem;
create logicaldrive array="SATA-Array1" userlabel="DBZones3_3" capacity=150 GB owner=a usagehint=filesystem;

Assigning the logical drive (LUN) to host on IBM DS4000 storage system

set logicalDrive ["LUN Name"] logicalUnitNumber=number host="server";


set logicalDrive ["DBZones3_1"] logicalUnitNumber=0 host="DBZones3";
set logicalDrive ["DBZones3_2"] logicalUnitNumber=1 host="DBZones3";
set logicalDrive ["DBZones3_3"] logicalUnitNumber=2 host="DBZones3";

Popular posts from this blog


DNS Scavenging.

AD LDS – Syncronizing AD LDS with Active Directory