So it’s been close to a year since I took this tool out of the murky depths of my
~/code folder and put it on GitHub and during the last twelve months, I have made some minor improvements here and there. But since I’ve been using it, I found although it documents the contents of the DFW configuration well enough, wouldn’t it be great if I could click on a Security Group or IPSET and go straight to the worksheet that contained its configuration.
Well, that’s what I coded up last week. So now when PowerNSX-DFW2Excel is run, it will create Hyperlinks from:
- Service Groups -> Services
- DFW Exclusion List -> VMs
- Security Group Members -> VMs
- Firewall Rule Sheet -> IPSETs, Security Groups, Services, Service Groups & VMs
So for example, the snippet below shows service groups with services as members, and each service field is now a hyperlink, when you click on the Hyperlink it will switch to the worksheet and focus in on the service details. So Name, Protocol, Port and Description will be displayed without trawling through the worksheet or using the find option in excel.
Also, in the hyperlink itself, I have embedded the objectID into the tooltip as a unique field. Below is a small snippet of a universal security group with the tooltip displaying the objectID.
Now that the tool is getting some heavy use, I thought it’s best to standardise on the latest 3.0 release of PowerNSX and make sure I’m not using the master branch of PowerNSX for testing or coding. Most of the DFW functionality I need is in there already, so staying with it makes sense going forward.
One of the major improvements I would like to make is to remove the dependency of using the Windows
-Com Excel.Application object, I think it would be much better to use a third-party Excel module found in PoSH. Making this change in theory would make the tool cross-platform.
Lastly, another great project to checkout is PowerOps, which is intended to help with Day 2 Operations of NSX for vSphere.