Configure the Service Definition on Panorama

1. (Optional) Configure a Notify Group
   Create a notify group by specifying devices groups that should be notified of changes in the virtual environment. The firewalls included in the specified device groups receive a real-time update of security groups and IP addresses of guest VMs in them. The firewalls use this update to determine the most current list of members that constitute dynamic address groups referenced in policy
   1. Select PanoramaVMwareNotify Group and click Add.
   2. Give your Notify Group a descriptive Name.
   3. Select the boxes of all devices groups that should be notified of changes to the virtual environment. If a device group does not have a check box available, it means that the device group is automatically included by virtue of the device group hierarchy.
   4. Click OK.
2. Add a new service definition.
   You can create up to 32 service definitions on Panorama.
   1. Select PanoramaVMwareNSX-TService Definitions.
   2. Select Add to create a new service definition.
   3. Enter a descriptive Name for your service definition.
   4. (Optional) Add a Description that identifies the function or purpose for the VM-Series firewalls that will be deployed using this service definition.
3. Assign a device group and a template stack to the service definition.
   Make sure to Create Template Stacks and Device Groups on Panorama.

   Because the firewalls deployed in this solution will be centrally administered from Panorama, you must specify the Device Group and the Template Stack that the firewalls belong to. All the firewalls that are deployed using this service definition belong to the specified template stack and device group.
   1. Select the device group or device group hierarchy in the Device Group drop-down.
   2. Select the template stack in the Template drop-down.
      You cannot reuse a template stack or a device group assigned to one service definition in another service definition.
4. Specify the location of the OVF file.
   Download the zip file, unzip it to extract and save the .ovf, mf and .vmdk files to the same directory. The ovf and vmdk files are used to deploy each instance of the firewall.

   If needed, modify the security settings on the server so that you can download the file types. For example, on the IIS server modify the Mime Types configuration; on an Apache server edit the .htaccess file.

   Do not change the Panorama service definition OVF path after a successful NSX Service Deployment of VM-Series firewalls. Changing the OVF path, after a successful VM-Series firewall deployment, can result in a NSX Service Deployment failed state. You may resolve this failure in NSX-T Manager, however this may cause all VM-Series firewalls to redeploy.

   It is recommended that you use an OVF path name that scales and allows you to change the base image without impacting your deployed firewalls. Instead of a path such as https://acme.com/software/PA-VM-NST.9.1.0.ovf, use something such as https://acme.com/software/PanoSvcDef1-Cluster1.ovf. Using a static path reference will eliminate any future need to change the OVF path. It is recommended to create a path for each Panorama service definition (vSphere cluster) in your deployment and change the PAN-OS base images references on the web server as needed.

   In OVF URL, add the location of the web server that hosts the ovf file. Both http and https are supported protocols.

   You can use the same ovf version or different versions across service definitions. Using different ovf versions across service definitions allows you to vary the PAN-OS version on the VM-Series firewalls in different ESXi clusters.
5. (Optional) Select a Notify Group.
6. Select East West as the Insertion Type for your firewall.
7. (Optional) Enable Health Check. Health check is disabled by default. Also called service health check, this NSX-T feature allows you to simulate high availability in the case of a service instance failing. When configured with the VM-Series firewall, if a VM-Series service instance fails, any traffic directed to that firewall is redirect to another firewall instance in the cluster (for service cluster deployments) or a firewall instance on another host (for host-based deployments).
   You cannot disable or enable Health Check in a service definition after committing and deploying VM-Series firewalls in NSX-T. Attempting to commit a change in the Health Check configuration returns commit failure. To change this, you must delete and recreate your service definition and redeploy your VM-Series firewalls.
8. Enable Device Certificate if your OVF is PAN-OS 9.1.5 or later. Otherwise, disable it.
9. Click OK to save the service definition.

10. Attach the service definition to the service manager.
    You cannot use a service definition in more than one service manager.
    1. Select PanoramaVMwareNSX-TService Manager and click the link of the service manager name.
    2. Under Service Definitions, click Add and select your service definition from the drop-down.
    3. Click OK.

11. Add the authorization code to license the firewalls.
    1. Select PanoramaDevice Groups and choose the device group you associated with the service definition you just created.
    2. Under Dynamically Added Device Properties, add the authorization code you received with your order fulfillment email and, optionally, select None from the SW Version drop-down.
       When a new firewall is deployed on NSX-T it is automatically added to the device group, licensed using the authorization code you provided, and upgraded to the PAN-OS version you specified.

       On the support portal, you can view the total number of firewalls that you are authorized to deploy and the ratio of the number of licenses that have been used to the total number of licenses enabled by your authorization code.

12. Commit to Panorama.
13. On the NSX-T Manager, verify that the service definition is available.
    Select Advanced Networking & SecurityPartner ServicesCatalog. The service definition is listed as a Service Instance on the NSX-T Manager.