Managing the SNS PAYG virtual firewall

SNS PAYG virtual firewalls can be managed via the web administration interface. If you are managing a large number of firewalls, use the Stormshield Management Center server instead, or an orchestrator combined with the NSRPC API.

Use your hypervisor to change the virtual machine's system settings.

Looking up the virtual firewall's dashboard in the web administration interface

  1. Log in to the virtual firewall's web administration interface (https://firewall_IP_address/admin). If it is configured in DHCP, note down its IP address in the console.
  2. When VPAYG-EVA is shown in the upper banner, this means that monthly billing is based on the EVA model, which depends on the virtual machine’s resources.
  3. The Properties widget in the Dashboard shows general information about the firewall.

This table presents the technical requirements of each EVA model:

Model

RAM

HDD

vCPU Max. number of interfaces (within the limits of hypervisor support)

EVA1

max = 2 GB

10 GB (2 GB for swap)

 max = 1 10

EVA2

max = 3 GB

10 GB (2 GB for swap)

 max = 2 10

EVA3

max = 6 GB

10 GB (2 GB for swap)

 max = 4 10

EVA4

max = 8 GB

10 GB (2 GB for swap)

 max = 4 10

EVAU

max = 64 GB

10 GB (4 GB for swap)

 max = 16 10

An EVA must have at least 1 GB of memory (or 2 GB as of SNS v5). You are advised to set aside at least 2 GB of memory if you use the antivirus and sandboxing features frequently.

WARNING
As Microsoft Azure no longer offers virtual machines with 2 GB or 3 GB of memory (4 GB minimum), EVA1 and EVA2 models are no longer available on Microsoft Azure.

Changing the amount of memory on the virtual firewall

You can increase the amount of memory on the SNS PAYG virtual firewall to switch to a different virtual firewall model so that you can operate more processors to manage more users.

Do note that pricing conditions will change when you increase memory. For further information, contact your Stormshield sales representative.

IMPORTANT
You are advised against reducing the memory on the virtual firewall. However, if you choose to do so, ensure beforehand that the new limits applied will be compatible with the existing configuration.

  1. In the web administration interface, go to Configuration > System > Maintenance > Configuration tab and click on Shut down the firewall.
  2. Wait until the virtual firewall shuts down.
  3. In your hypervisor, go to the virtual machine's properties and change the memory, e.g., from 2048 MB to 3072 MB. You may also add processors if you need them.
  4. Restart the virtual machine.
  5. Log in again on to the web administration interface of the virtual firewall.
    On the Dashboard, the Properties widget shows the new virtual firewall model (e.g., VPAYG-EVA2 for 3 GB of memory) as well as its new limits. For further information on each model's limits, refer to the section Looking up the virtual firewall's dashboard in the web administration interface.

Deallocating a virtual machine with Microsoft Azure

Deallocating shuts down the virtual machine and releases its resources, which will no longer be billed.

  1. Log in to the Microsoft Azure portal.

  2. Open the Cloud Shell console by clicking on the icon in the upper bar.

  3. Enter the following command:

    az vm deallocate -g <resource-group> -n <virtual-machine-name>