Network Security Manager 3.2 On-Premises Getting Started Guide

Technical Documentation>  Installating Network Security Manager>  Installing NSM on ESXi>  Installing NSM on ESXi Server
Table of Contents

Installing NSM on ESXi Server

Install NSM On-Premises by deploying an OVA file to your ESXi server. The OVA file contains the software components needed. Deploy the OVA file by using the vSphere or vCenter client, which is available with ESXi.

The elements of VMware must already be in place and the administrator must be familiar with the basics of deploying a virtual appliance on the ESXi server.

To install NSM On-Premises on ESXi server

  1. Access vSphere or ESXi Server.

    Install NSM after setting up your virtual system.

  2. Right-click on your system and select Deploy OVF Template.

  3. Select Local file and click on UPLOAD FILE.

    If using ESXi server, unzip ova file to get the three files: vmdk file, nvram file and ovf file and upload the three files instead ova file.

  4. Navigate to where you stored the NSM OVA file to select it.
  5. Click Open.
  6. Once the file gets attached, click Next.

  7. Specify the Virtual machine name for the NSM On-Premises instance. Be sure it's a meaningful name so you can easily find it lists and tables.

  8. Select the location for the virtual machine and click Next.
  9. Select a compute resource on which to deploy the template and click Next.The system validates the resources so it may take some time before the next window appears.

  10. In the Review details screen, verify the template details and click Next.

    The details you see on this screen are specific to your deployment.

  11. Select the Configuration as per your requirement. Click Next.

  12. In Select storagepage, Select virtual disk format to be Thick Provisioning. Click Next.

  13. In the Select networks screen, set up interface X0 to access the network.

    This is the same naming convention as a SonicWall firewall. X1 is considered a WAN interface so the Destination Network should be changed to an externally accessible subnet.

    Click Next.

    X1 (the default WAN Interface) is set to DHCP by default, with HTTPS management enabled for the NSM On-Premises instance, as this configuration eases deployments in virtual/cloud environments.

  14. In the Customize template screen, verify the information, and click Next.

  15. In the Ready to complete screen, verify all fields and click Finish to create the NSv appliance. The name of the new NSM On-Premises appears in the left pane of the vSphere window when complete.

    The deployment will take some time. You can view the summary and details on the Summary page of the vSphere Client.

  16. When the deployment is complete, be sure the new virtual system is selected and click to power on the system.

  17. To Launch the console, refer Connecting to Console.

Next, you should use the console to configure the network settings. This establishes your ability to access NSM through a browser. Refer to Configuring NSM Network Settings for details.