Deploy the Palo Alto Networks NGFW Service

Use the following steps to automate the process of deploying an instance of the VM-Series firewall for NSX on each ESXi host in the specified cluster.
  1. Select Networking and SecurityInstallationService Deployments.
  2. Click New Service Deployment (green plus icon), and select the service definition for the Palo Alto Networks next generation firewall you want to deploy, Palo Alto Networks NGFW service in this example. Click Next.
    NSX-deploy_service.png
  3. Select the Datacenter and the cluster(s) on which the service will be deployed. One instance of the firewall will be deployed on each host in the selected cluster(s).
  4. Select the datastore from which to allocate disk space for the firewall. Select one of the following options depending on your deployment:
    • If you have allocated shared storage for the cluster, select an available shared datastore.
    • If you have not allocated shared storage for the cluster, select the Specified-on-host option. Be sure to select the storage on each ESXi host in the cluster. Also select the network that will be used for the management traffic on the VM-Series firewall.
    nsx_storage_on_host.png
  5. Select the port group that provides management network traffic access to the firewall.
  6. Select the IP address pool assignment.
    • Use IP Pool (Define an IP Address Pool) from which to assign a management IP address for each firewall when it is being deployed.
    • Use DHCP on the management interface.
    If you use an IP pool, on deployment, the display name for the VM-Series firewall on Panorama includes the hostname of the ESXi host. For example: PA-VM:10.5.1.120.
    If you use DHCP, the display name for the VM-Series firewall does not include the name of the ESXi host.
  7. Review the configuration and click Finish.
    nsx_pan-firewall_service.png
  8. Verify that the NSX Manager reports the Installation Status as Successful. This process can take a while; click the More tasks link on vCenter to monitor the progress of the installation.
    nsx_pan-firewall_service_2.png
    If the installation of VM-Series fails, the error message is displayed on the Installation Status column. You can also use the Tasks tab and the Log Browser on the NSX Manager to view the details for the failure and refer to the VMware documentation for troubleshooting steps.
  9. Verify that the firewall is successfully deployed.
    1. On the vCenter server, select Hosts and Clusters to check that every host in the cluster(s) has one instance of the firewall.
    2. View the management IP address(es) and the PAN-OS version running on the firewall directly from vCenter server. VMware Tools is bundled with the PAN-OS software image and is automatically enabled when you launch the VM-Series firewall.
      With VMware Tools, you can view resource utilization metrics on hard disk, memory, and CPU, and use these metrics to enable alarms or actions on the vCenter server. The heartbeats allow you to verify that the firewall is live and trigger actions to ensure high availability. You can also perform a graceful shutdown and restart of the firewall using the power off function on vCenter.
      vmware_tools_nsx_IP_and_version.png
  10. Access the Panorama web interface to make sure that the VM-Series firewalls are connected and synchronized with Panorama.
    1. Select PanoramaManaged Devices to verify that the firewalls are connected and synchronized.
      If the firewall gets its IP address from an IP Pool, the Display Name for the firewall includes the hostname of the ESXi server on which it is deployed, for example PA-VM:ESX1.Sydney. If the firewall gets a DHCP assigned IP address, the hostname of the ESXi server does not display.
      nsx_pan-firewall_verify_Panorama.png
    2. Click Commit, and select Commit Type as Panorama.
      A periodic Panorama commit is required to ensure that Panorama saves the device serial numbers to configuration. If you reboot Panorama without committing the changes, the managed devices will not connect back to Panorama; although the Device Group will display the list of devices, the devices will not display in PanoramaManaged Devices.
  11. Verify that the capacity license is applied and apply any additional licenses that you have purchased. At a minimum, you must activate the support license on each firewall.
    When Panorama does not have internet access (Offline), you must manually license each firewall, and then add the serial number of the firewall to Panorama so that it is registered as a managed device, and can receive the template stack and device group settings from Panorama. See Activate the License for the VM-Series Firewall for VMware NSX for more information.
    1. Select PanoramaDevice DeploymentLicenses to verify that the VM-Series capacity license is applied.
      nsx_license.PNG
    2. To apply additional licenses on the VM-Series firewalls:
      • Click Activate on PanoramaDevice DeploymentLicenses.
      • Find or filter for the firewall, and in the Auth Code column, enter the authorization code for the license to activate. Only one authorization code can be entered at a time, for each firewall.
        nsx_license_extra.PNG
    3. Click Activate, and verify that the result of the license activation was successful.
  12. (Optional) Upgrade the PAN-OS version on the VM-Series firewalls, see upgrade-the-pan-os-software-version-vm-series-for-nsx.html#id52f0ed19-6cfd-4ac2-bfaf-29a4bcbbcd5f_id8023d0b7-6fed-40c1-a216-088757069a1b.
  13. Add guest VMs to the right security groups for traffic from those VMs to be redirected to the VM-Series firewall.
    1. Log in to vCenter.
    2. Select Networking & SecurityService ComposerSecurity Groups.
    3. Highlight the security group to which you want to assign guest VMs and click the Edit Security Group icon.
    4. Select Define dynamic membership and click the + icon.
    5. Click Add.
    6. Define the dynamic membership criteria that the guest VMs must meet to be part of the selected security group. The criteria you use depends on your network deployment. For example, you might choose to group VMs by an Entity such as Logical Switch or Distributed Port Group.
      nsx_add_VMs_to_security_groups.png
    7. Click Finish.
    8. Repeat this procedure for each security group that should have its traffic redirected to the VM-Series firewall.

Related Documentation