Configure the Service Definition on Panorama

1. 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.
2. 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.
3. 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.

   Panorama must have network connectivity with the web server to retrieve the OVF file.

   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.
4. Select North South as the Insertion Type for your firewall.
5. To automatically retrieve a device certificate when the VM-Series firewall is deployed by NSX Manager, configure the device certificate.
   Enable this option to apply a device certificate to newly deployed VM-Series firewalls. Only use this option when deploying the firewall using a base image OVF that supports device certificates. Panorama pushes the device certificate information to NSX Manager as part of the service definition. When a new firewall is deployed in NSX, the device certificate is installed on the firewall at bootup.

   For list of OVFs that support device certificates for the VM-Series firewall on VMware NSX, see the Palo Alto Networks Compatibility Matrix.

   If your OVF does support a device certificate, you must Enable device certificates regardless of whether or not you are using a device certificate. If your OVF does not support a device certificate, disable this option.
   1. If you have not done so already, log in to the Customer Support Portal and generate a Registration PIN and PIN ID.
   2. Under Device Certificate, click Enable.
   3. Copy the PIN ID and enter it into the Device Certificate PIN ID field.
   4. Reenter the PIN ID into the Confirm Device Certificate PIN ID field.
   5. Copy the PIN Value and enter it into the Device Certificate PIN Value field.
   6. Reenter the PIN Value into the Confirm Device Certificate PIN Value field.
6. Click OK to save the service definition.

7. Attach the service definition to the 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.

8. 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.

9. Commit to Panorama.
10. On the NSX-T Manager, verify that the service definition is available.
    Select SystemService DeploymentsCatalog. The service definition is listed as a Service Instance on the NSX-T Manager.