How to Deploy NSM On-Premise 3.2.0 on VMWare
Description
NSM 3.2.0 On-Premises deployment is supported on the following platforms:
- Microsoft Hyper-V
- VMWare
- KVM
- Azure
Prerequisites
The prerequisites are similar for each platform NSM can be installed on:
- Firewalls supported by an NSM On-Premises instance must be in a single Group or Tenancy.
- The firewalls added to NSM On-Premises are not a part of CSC (Capture Security Center) or NSM SaaS.
- All the manually acquired firewalls should have HTTPS management enabled.
If a manually acquired firewall is behind a NAT device, the HTTPS management port must be opened for the NSM On-Premises services to communicate with the firewall.
For a KVM implementation, ensure that your Linux system supports KVM and download the image file to your Linux system (for example, SonicWall_NSM_On-Prem__For_QEMU_VM.img) to your Linux machine.
Capacity Requirements
To use NSM efficiently, NSM recommends the following minimum requirements for the different platforms.
NSM 3.2.0 On-Premises requires minimum 270 GB of disk space for installation. For reporting and analytics data use the Reporting Disk Space Requirements (Data Storage + Cache)/SSD for sizes.
Resolution
Steps to install NSM On ESXi
Install NSM On-Premises by deploying an OVA file to your ESXi server. The OVA file contains the software components needed. Download NSM On-Prem 3.2.0 OVA file from mysonicwall.com.
To deploy NSM On-Premises on ESXi server:
1- Right-click on your system and select Deploy OVF Template.
2- Deploy the OVA file by using the vSphere or vCenter client, which is available with ESXi. Specify the Virtual machine name for the NSM On-Premises instance:
3- Choose the required datastore:
4 - Choose the Network mappings and Configuration as per your requirement and Select virtual disk format to be Thick Provisioning:
6- In the Ready to complete screen, verify all fields and click Finish to create the NSM 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.
7- When the deployment is complete, be sure the new virtual system is selected and click on start button to power on the Virtual Appliance:
8- Connect to console, it will show that NSM is Starting up, goes through Initializing state and finally completes installation:
8- When the initial boot is complete, the CLI Console displays.
9- Run the command "show network" to find out the names of the network interfaces.
10- Use the following syntax to configure network interface IP. In this example, interface with name "eno3s0" is used. CLI should display a Success message. Do a ping test to verify the connectivity.
network interface <interface name> ip <ip addr> netmask <netmask> gateway <gateway> and hit enter.
After few minutes of configuring the network interface IPs, the web interface will be accessible on the browser:
Login with default credentials for the first time, login name: admin, password: password
Reference for CLI commands: CLI Commands