3 Replies Latest reply on Mar 19, 2018 4:35 PM by rtindall

    VRNI Application to NSX Firewall Rules

    JLecht Lurker

      Hello,

       

      I've installed vRealize Network Insight (VRNi), built an application in VRNi, and then exported Firewall rules generated by the application.

       

      There's no great way to import the exported VRNi firewall rules into NSX? (either distributed firewall section, or service composer with security tags, security groups, etc.).

       

      Does anything know of a procedure to accomplish this and/or make this task nimble to perform?

        • 1. Re: VRNI Application to NSX Firewall Rules
          lhoffer Hot Shot
          VMware EmployeesvExpert

          The option to export as XML that can be pushed to the NSX API only works when you're grouping by Security Group.  That said, if you've already got NSX deployed, you can pre-build security groups there rather than building applications in vRNI and export the rules that way.

          • 2. Re: VRNI Application to NSX Firewall Rules
            JLecht Lurker

            Hi,

             

            I've been working with VMWare support which gave me examples of how to do every piece of the process using REST api. Security Tags, Security Groups, Firewall rules, etc.

             

            This isn't a nimble process.

             

            Thank you for the reply.

            • 3. Re: VRNI Application to NSX Firewall Rules
              rtindall Enthusiast
              VMware Employees

              Please be aware that unfortunately VMWare is not able to provide scripts or script debugging support. VMWare can guide to documentation and any examples provided within documentation, however it is not able to help script the actual input/output that may be required for a given environment. This would need to be trial and error tested outside the realm of VMWare support. API scripting would also fall under this umbrella. The vRNI API does provide examples of things and how this output may be gathered from vRNI through API, however the support of automating this API output, and then input into NSX would not be supported.