A service definition specifies the configuration for the VM-Series firewalls installed on each host in an ESXi cluster. The service definition must include the device group, the license auth-codes for deploying the VM-Series firewalls, and a template with one or more NSX service profile zones. Typically, you create a service definition for the VM-Series firewall in an ESXi cluster. If you have different ESXi clusters that have workloads that require the VM-Series firewall to handle traffic differently, you can create multiple service definitions on Panorama.
On a Panorama commit, each service definition is registered on the NSX Manager. On registration with the NSX Manager, the NetX API implementation makes each zone (defined within the template) available for redirecting traffic. When you deploy the VM-Series firewalls, you can select the profile name for the VM-Series firewall(s) to which you want to redirect traffic from the objects in NSX security groups. The appropriately configured firewall can then inspect the traffic and enforce policy from the virtual machines that belong to the NSX security groups.
Create the Service Definition on Panorama
Add a new service definition. You can create up to 32 service definitions on Panorama. Select Panorama > VMware Service Manager. Select Add in the VMware Service Definitions section to create a new service definition. The maximum number of characters in a service definition name is 40. On the NSX Manager, this service definition name displays in the Services column on Networking & Security > Service Definitions > Services. (Optional) Add a Description that identifies the function or purpose for the VM-Series firewalls that will be deployed using this service definition.
Assign a device group and a template for the service definition. Make sure to Create the NSX service profile zone(s) for each template. Because the firewalls deployed in this solution will be centrally administered from Panorama, you must specify the Device Group and the Template that the firewalls belong to. All the firewalls that are deployed using this service definition belong to the specified template and device group. Select the device group or device group hierarchy in the Device Group drop-down. Select the template or the template stack in the Template drop-down. You cannot reuse a template or a device group assigned to one service definition in another service definition.
Specify the location of the OVF file. Download the zip file, unzip it to extract and save the .ova, mf and .vmdk files to the same directory. Both the 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. In VM-Series OVF URL, add the location of the web server that hosts the ova file. Both http and https are supported protocols. For example, enter https://acme.com/software/PA-VM-NSX.7.1.0.ovf To want to deploy a multi-tenant solution, the ovf file must be PAN-OS 7.1.0 or a later version. 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.
Add the authorization code to license the firewalls. The auth-code must be for the VM-Series model NSX bundle; for example, PAN-VM-1000-HV-PERP- BND-NSX Verify that the order quantity/ capacity is adequate to support the number of firewall you need to deploy in your network. Enter the auth-code that you received with your order fulfillment email. You can use the same auth-code or different auth-codes across service definitions. The auth-code is used to license each instance of the VM-Series firewall. 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 auth-code.
Set up notification to different device groups as new virtual machines are provisioned or as changes occur on the network. To create context awareness between the virtual and security environments so that policy is consistently applied to all traffic steered to the firewalls, select the device groups to notify when there are changes in the virtual environment. Select each device group to which you want to enable notifications in the Notify Device Groups drop-down. If a device group does not have a checkbox available, it means that the device group is automatically included by virtue of the device group hierarchy. The firewalls included in the specified device groups receive a real-time update of security groups and IP addresses. The firewalls use this update to determine the most current list of members that constitute dynamic address groups referenced in policy.
Save the service definition. Click OK.
Select Commit and Commit Type: Panorama. Committing the changes triggers the process of registering each service definition as a security service on the NSX Manager.
Verify that the service definition and the NSX service profile that you defined on Panorama are registered on the NSX Manager. On the NSX Manager, to verify that the service definition is available, select Networking & Security > Service Definitions > Services. The service definition is listed as a Service on the NSX Manager.
To verify that the zones are available on the NSX Manager: Select Networking and Security > Service Composer > Security Policies, and click Create Security Policy. Select Network Introspection Services, and click Add. In the Service Name drop-down, select a Palo Alto Networks service that you verified in the step above. In the Profile drop-down, verify that you can view all the NSX service profile zones you defined for that service definition on Panorama.
(Optional) Synchronize the configuration between Panorama and the NSX Manager. If you add or update the service definitions configured on Panorama, select NSX Config Sync in the Operations section to synchronize the changes on the NSX Manager. This link is not available, if you have any pending commits on Panorama. If the synchronization fails, view the details to know whether to fix the error on Panorama or on the NSX Manager. For example, if you delete a service definition on Panorama, but the service definition cannot be deleted from the NSX Manager because it is referenced in a rule on the NSX Manager, the synchronization will fail with an error message that indicates the reason for failure.

Related Documentation